This process is a loose framework for developing and shipping products & features. Each company has different methodologies, but this is what has worked for me in the past.

Written by Nic Clar

🔬 Discovery

• What problem are we trying to solve, and for who?
• Are we sure this is the real problem? Or a symptom of the root problem?
• Can we talk to customers? Can we verify our assumptions?
• What perceived constraints are we facing?
• Are these constraints genuine, or tied to outdated behavior that we’re trying to change?
• If we’re trying to introduce new behaviors, how can we do this incrementally?
• Has a similar feature been built by a competitor? If so, what did they do right/wrong?
• If this is a new feature, can we tie quantifiable value to it?
• What defines success? Can we attach KPIs to this work?
• How will this feature evolve in 3, 6, 9 months?

💭 Ideation

1. Create a user journey for the possible solution. Designers should be loosely involved at this stage.
2. Share user journey with engineers to assess technical feasability.
3. Share user journey with design for any UX red flags.

<aside> ℹ️ This is not the design phase. Depending on the organization’s structure, design can help create the user journey instead of having it prescribed.

</aside>

1. Once both engineering & design approve the user journey, present it to stakeholders.
2. Document every party approving of the user journey.