- Product manager -
- Designer -
- Developer -
- Project Sponsor -
How are things currently? What’s the problem or how could things be better? How does this impact the business? Including customer quotes or stories can make the problem easier to feel.
What problem(s) are we solving for and why? What problem(s) are we not solving for and why?
New customers? Increased usage? Decrease in support requests? List your KPI’s here. A faux press release could help illustrate this.
- What do we already know (analytics, support requests, etc.)?
- What do we want to find out (data requests, user research)?
What must the thing do to meet its goals? Be specific.
How will this thing work? Spell out UX flow, UI states, and edge cases. Include links to designs and prototypes.
- What other ideas have been discussed and why aren’t we pursuing them?
- What are some extreme edge cases?
- Is this accessible and inclusive? (Eg. does this assume a modern device and fast internet connection?)
- How could this be abused? (Eg. could someone
What do we need in order to track the success or failure of this thing?
Meeting notes, critique feedback, noteworthy email or chat discussions. Collect and record notable conversations and decisions that folks may have missed.
(template lovingly borrowed from Ted Goas via https://uxdesign.cc/all-design-projects-should-start-in-a-google-doc-20ad24f75a8c)