UX in the Dev Cycle: Moving from Handoff to Handshake

Are you building the thing right, or building the right thing? Learn how a true UX partnership moves your team from a siloed handoff to a collaborative handshake.

#1about 7 minutes

Identifying poor UX with a ticket machine example

Complex UIs, like confusing public transit ticket machines, demonstrate how poor design forces users to learn a system instead of achieving their goals.

#2about 1 minute

The developer's anxiety from unclear feature requests

Receiving feature requests without context creates anxiety and fear of breaking complex systems, which ultimately slows down development.

#3about 2 minutes

Using the jobs to be done framework

Focus on the user's ultimate goal, or 'job to be done,' to simplify the product and remove unnecessary complexity.

#4about 5 minutes

How to validate design assumptions with research

Use explorative interviews to distinguish correlation from causation and paper prototypes to test ideas quickly without writing any code.

#5about 5 minutes

How UX collaboration improves developer happiness and quality

Integrating UX provides developers with purpose, critical context to prevent fear-driven development, and a collaborative partner for solving problems.

#6about 4 minutes

Practical steps to integrate UX into development

Move from handoff to handshake by treating UX as part of the team, using Gherkin syntax for shared understanding, and viewing designs as discussion starters.

#7about 2 minutes