Feature Design

The first 10 questions

This is where the conversation starts. Each answer shapes what gets asked next.

1. 01What feature are you designing, and what product does it live in?
2. 02Who is the primary user of this feature — what's their job, skill level, and what do they care about most?
3. 03What specific pain point does this feature solve? What do users do today instead?
4. 04Where does this feature sit in the product — is it a new area, an extension of an existing flow, or a replacement?
5. 05Who asked for this — user feedback, strategic initiative, or your own observation? What's driving prioritization now?
6. 06What's the strongest signal you have that users actually need this? Have you spoken to any of them directly?
7. 07What must be true for this feature to succeed that you haven't validated yet?
8. 08What hard constraints apply — platform, performance, existing architecture, team capacity?
9. 09What is explicitly out of scope for this version, and why?
10. 10Walk me through the primary user flow step by step: what triggers it, what does the user do, and what is the successful end state?

+ 8 more questions across discovery, validation, and the creative brief — each one adapting to what you've already said.

Related product design project types

• Product ValidationTest whether your product idea is worth building before you build it — with a clear validation plan and a landing-page wireframe to test demand with.
• MVP ScopeDefine what your minimum viable product actually is — the smallest thing you can ship to test your core hypothesis with real customers.
• MVP Scope MatrixTurn your MVP Scope work into a shareable visual — a prioritized matrix plotting each feature by value vs. effort, so the right cuts to make before you start building are obvious.