Technical Skills & Input

What it is

Being a valuable partner for each of the cross-functional leads (engineering, UX, data science, marketing, etc.) in the product delivery process.

Why it's important

• With a solid partner, the solution designer can create the best solution
• You can appreciate why certain things work and why others don't
• The process is more efficient if you comprehend and leverage basic principles

When you need it

• Research: contextual inquiry, persona development, systems analysis, gathering data
• Design: brainstorming, giving meaningful feedback, writing specs that give guidance, are specific enough to be helpful, and/or speak in the language of the respective discipline
• Release strategy: understanding principles of UX as well as architecture can help you to create a phased release that is efficient and empathetic

How to do it

• User research. Make it a priority to plan and carry out contextual inquiry (on-site visits) with target customers/users and at least act as a coordinator for persona research/development.
• Technology research. Make it a priority to plan and carry out systems analysis and market research around technology and patterns that could be leveraged toward an ideal solution.
• Know the principles. Educate yourself and get comfortable with the principles of UX and system architecture so that you can be a valuable contributor to brainstorming and design feedback. You need to be able to cite principles and understand proven concepts rather than just saying "I like this" or "I don't like that".
• User testing. Make sure that every design is tested with target users. If it's a huge change or new product, it needs to be done comprehensively and methodically. If it's a small change to an existing product/feature, you can get by with quick and dirty guerrilla testing.
• Design validation. Pre- and post-development/release, you need to coordinate running designs by stakeholders and target customers/users to validate that you are maintaining/promoting the brand and that you have a solid aesthetic and interaction design.

Resources

• About Face
• The Design of Everyday Things
• Laws of UX
• Don't Make Me Think

The competency

You are able to be a helpful partner in the process of product creation, from concept to feedback on visual/interactive designs and high level system architecture. You don't only understand and are versed in the principles and processes behind product design, but you are also able to employ them intelligently in a conversation with a solution designer in the context of your product -- to the extent that you are a meaningful contributor.

Outputs and deliverables

Maximized quality in every aspect of the product's design (in terms of its performance). Validated solution designs referenced in the specification and (optionally) in the Jira ticket. On the UX side:

• A monthly synthesis of user research shared with the team
• Validated (usability tested, perception tested, design system compliant) mocks for specs on at least a monthly basis
• A system-wide quality-of-experience (QX) score per year / major release, and adjustments based on the audit

Outcomes

• Top/improved QX scores
• Clear ROI attributed to design