Embed Figma files only accessible to specific individuals or teams
Describe the problem (or opportunity) you’re trying to solve. Why is it important to our users and our business? What insights are you operating on? And if relevant, what problems are you not intending to solve?
Describe briefly the approach you’re taking to solve this problem. This should be enough for the reader to imagine possible solution directions and get a very rough sense of the scope of this project. (e.g., if “The Problem” was engagement in the design process from non-designers, “The Approach” might be a feed which surfaces work that's relevant to them.)
Goals & Success
What does success look like? What metrics are you intending to move? Explain why these metrics are important if not obvious.
Give an overview of what we’re building. Provide an organized list of features, with priorities if relevant. Discuss what you’re not building (or saving for a future release) if relevant.
Show some mocks/embeds of the experience. Link to any other documentation as necessary. In general, it’s helpful to organize these around certain user journeys / use cases. Show enough of a clickthrough where people can walk away with a reasonable understanding of how the product works.
⭐️ Now you can embed private Figma files, too!
Open Issues & Key Decisions
Keep track of open issues / key decisions here. Sometimes, certain decisions are made that might feel controversial; document these here so people know that the discussions have happened and there’s strong awareness of the tradeoffs.
Identify any relevant milestones (e.g., a Dogfood or Beta milestone) that people should know about. Make sure to show when you’re expecting to publicly launch, too.
Make sure you answer all of the questions below and involve necessary stakeholders.
Instructions if "Yes” (or unsure)