Status: π In Design Exploration [be sure to keep this updated throughout the project]
Product Design Lead: ... (document author)
Product Manager: ...
Engineering Manager: ...
Eng Team: ...
Purpose of this doc: To clarify and project development details as part of the product design process. See Product brief (linked below) for more context.
See also: [include Product brief or any other relevant docs here]
- ...identify the key points here as summary points for what is being built and why
- ...
[...write out the story of this feature as it would be told to someone in conversation, or at the beginning of a demo video for the feature...]
- ...identify any specific project goals here
- ...
Category 1 (use categories to group JTBD when applicable)
- As a [user role or other situation] I want to [articulate what the user wants to be able to do]
- ...
The user experience will include:
- ...inventory of new components to be introduced (including new layouts if any)
- identify any key questions to discuss with product, engineering, or other stakeholders here...
- ...
To help keep our process efficient, we can solve for some major decisions at the beginning at a low fidelity stage of the design process that focuses less on the entire UI details and more on just the specific parts in question (usually overall layout, placement of components, etc β things that can be rendered quickly as sketches or with other wireframing tools).
Brief description of the item and what is to be decided (usually a choice about the overall layout, etc), including rationale for different options and images below. Be sure to record discussion notes from each decision stakeholder (typically best done in a triad sync meeting via discussion, and then key points captured here for later reference).
[Example] Option 1: add a new section to the core workflow
Pros | Cons |
---|---|
some upside here... | some downside here... |
some other upside here... | some other downside here... |
Decision Record:
- @team member - notes from decision...
π Sync with ... on ...
Space here for notes from other key discussion (if applicable)
(Figma file here)
Design exploration TODOS:
- add design tasks here for reference if useful (be sure to include on your teamβs project board also!)
- ...
π£ Next steps...
- ...after the initial design work has been completed, there may be several ideas that came up that are not included in initial scope. This space can be used to document those ideas to revisit later (itβs often helpful to write them down in as much detail as possible while they are still top of mind) and any other relevant project sequencing notes.