The Twenty: Steps to Excellent Product Design

Design isn’t magic, there’s actually a simple recipe to follow for best results. Anyone who’s shipped a real product knows it takes more than creativity. It takes structure, empathy, communication, and a willingness to let go of your ego every time someone doesn’t understand your genius wireframe. This guide is your roadmap. These are The Twenty—the steps that get your idea out of your head, into users’ hands, and (hopefully) loved.

1. Conduct user research & establish user persona

Before you even think about opening Figma, you need to get out of your own head and into your users’ world. User research isn’t a formality, it’s your foundation. Interviews, surveys, observational studies, whatever it takes to uncover real needs, motivations, and frustrations. From there, you build personas: fictional, yet data-informed profiles that give your team a human target to design for. Skip this step, and you’re designing for a mythical creature named “User.”

2. Craft the user journey

This is where empathy becomes a map. Plot out your user's experience across every touchpoint, not just in your product, but around it. What happens before they arrive? What’s going on in their life? What do they expect at each step? Mapping their journey helps you identify gaps, pain points, and emotional highs and lows you can use to design not just for users, but with them in mind the entire time.

3. Formalize the problem statement and user story

Now that you know what’s broken, say it clearly. A solid problem statement frames the issue from the user’s perspective and sets you up for success by giving your team something to rally behind. Pair it with a user story (“As a [type of user], I want to [goal], so that [value]”) to ensure your solution is always anchored in real needs, not internal assumptions.

4. Brainstorm solutions

Time to let loose. Gather your team, grab some markers (real or digital), and throw ideas on the wall—no filter, no judgment. Brainstorming isn’t about landing the final solution; it’s about surfacing possibilities, pushing boundaries, and creating a safe space where strange, unexpected ideas can spark brilliance. The only rule: defer judgment and stay curious.

5. Propose design concept

With raw ideas on the table, it’s time to refine. Choose a direction that balances user needs, business goals, and technical feasibility. Your design concept should communicate the what and why, a vision that others can buy into. Whether you're building a pitch deck, a mood board, or a clickable prototype, this is where your idea takes form and starts to feel real.

6. Establish roles and responsibilities

This step saves you from chaos. Design isn’t a solo act, it’s a full-blown ensemble. So define who owns what: who’s leading design, handling research, writing copy, giving approvals, and supporting dev. Get aligned now to avoid messy handoffs, decision paralysis, and “wait, I thought you were doing that” moments later.

7. Project kickoff (presenting steps 1–6)

A great kickoff is half the battle. Bring your cross-functional team together and present everything: user insights, problem statements, your proposed concept, and who’s doing what. Make sure everyone’s clear on the goals, timelines, and expected outcomes. This meeting sets the tone, so keep it tight, inspiring, and rooted in shared purpose.

8. Establish success metrics

Design without goals is just decoration. Define what success looks like in measurable terms: Are you reducing drop-off? Increasing conversions? Improving task success rates? Clear metrics make it easier to focus your design, defend your decisions, and evaluate impact once it’s live.

9. Create user flows for all UX and expected behavior

Think of user flows as your blueprint. They show how users navigate through your product to achieve goals, click by click, decision by decision. Mapping flows helps you spot edge cases, streamline interactions, and design experiences that feel intuitive, not frustrating. Be exhaustive, not just for happy paths but for when users get lost, make mistakes, or backtrack.

10. Low–high fidelity wireframes

Sketch. Wire. Refine. Start lo-fi to test layout and flow, then evolve to high-fidelity once things are solid. Wireframes are your sandbox for structure and information hierarchy, they’re where usability gets worked out before the shiny stuff distracts everyone. Think of it as the difference between blueprinting a house and arguing about wall colors.

11. Prototype

Bring your designs to life with clickable, tappable, scrollable prototypes. Whether you’re using Figma, InVision, or sticky notes and imagination, this is where you simulate the experience to test interaction logic, pitch to stakeholders, and uncover what still feels clunky. It doesn’t need to be fully functional, it just needs to tell the story of your design.

12. Conduct usability testing

Here’s where the rubber meets the road. Usability testing reveals what’s working, what’s confusing, and what needs a redesign. It’s not about proving your design is perfect, it’s about learning what’s broken before it ships. Test early and often. And don’t take it personally when people don’t “get it.” That’s the point.

13. Iterate based on feedback

THIS IS KEY! Take what you’ve learned from testing and improve. Remove friction, clarify flows, and smooth out rough spots. Iteration isn’t failure, it’s refinement. Each cycle brings you closer to a product that actually works for people.

14. Designs are made responsive for all required platforms

Desktop, tablet, mobile and maybe even your smart fridge. Your design needs to flex and adapt across breakpoints and devices. This step is where you think about thumb reach, tap targets, scaling grids, and making sure your beautiful layout doesn’t fall apart at 1920px wide.

15. UI is finalized and linked with design system

Time to make it pixel-perfect. Use your design system (or create one) to apply consistent styles, components, and interactions. Final UI should feel polished, on-brand, and aligned across the product. Bonus points if your file is clean, documented, and ready for handoff without triggering an anxiety attack.

16. Compare final designs with project documentation

Alignment check: Are your final mocks actually delivering what you said you would? This is where you reconcile your designs with requirements, stories, and specs. Provide links, documentation, and rationale to make sure your work ties back to the original goals—and nothing important got left out along the way.

17. Provide support to engineers during development

Design handoff isn’t the end. Stay close to devs, answer questions, clarify interactions, and adjust where needed. Consider this your co-pilot phase. The smoother the dev experience, the better the final product and the more your design survives the translation from prototype to production.

18. Review what has been developed

Time for a detailed look. QA the live experience, spot visual inconsistencies, missed states, or layout issues. This is your chance to protect the integrity of the design before it reaches users. Be THOROUGH. Be annoying if you have to. This is your name on the line.

19. Document discrepancies and oversights

Not everything will go perfectly and that’s okay. Keep track of what changed, what got left out, and why. Documenting these gaps helps the team learn, improves future projects, and gives you a chance to close the loop later when time or budget allows.

20. Analyze success metrics and KPIs

Remember those metrics from step 8? Time to check how you did. Are users completing tasks faster? Are bounce rates down? Did that new flow actually improve conversion? This data isn’t just for reporting, it fuels your next iteration and helps you design with more insight next time.

Design is equal parts listening, thinking, making, and adjusting. The Twenty aren’t just steps, they’re habits. A mindset. A rhythm. Whether you’re working solo or leading a team, these steps help you design with purpose, partner well with others, and ship work you’re proud of. Save this list, share it with your team, and come back to it when things get messy.