Concisely capture what the feature accomplishes so that anyone can not only understand it but easily explain it to someone else.
📏 Measures of Success
Provide clear and measurable outcomes. Each goal should be easily quantifiable, such as “at least 80% of new users will use this feature more than once a week.” This is an excellent opportunity for collaborators to comment on whether those goals are feasible or if they should be higher, given the investment of resources. We use anywhere from 3 to 6, but you’ll need to determine the right amount for you
📣 The "announcement"
The announcement envisions the feature’s impact on customers and how they’ll use it. It will also get your teams excited about the work to be done.
📝 Context
We call this the “big picture need” and it’s where you offer the broader context for the feature you’re building. Include assumptions, statistics, use-cases, and other types of evidence that will help make the feature more compelling
⚙️ Detailed needs and solutions
Before writing down solution ideas, plainly describe each need related to the feature. Then involve everyone in creating and editing a list of solutions that may address that need. The point here isn’t to start with a definitive prescription for how to solve those needs, but to inspire a discussion to create the best solutions.
🎯 Target audience details
As always, consider the target audience for the product. Who are you building this item for, and how will the customer use it in their everyday lives?
🎨 Mockups and design sketches
[hy write when images will do? Including [mockups and sketches](https://www.productboard.com/blog/8-prototypes-examples-mvp/) is a great way to give your idea something tangible to review. Either drop in your ideas, or this can be where designers start adding in their ideas or inspiration from other products or projects.
📊 Market research
What have your customers said in the past about similar products? Have they made any special requests for new products like the one in mind?
rowlie
commented
1 year ago
✍️ Link to Designs
https:\/\/www.figma.com\/file\/ruefQ8lS58wsoWuH2CUxny\/AWS\-Amplify\-UI\-Kit\-(Community)?node\-id=2653%3A2886&t=f2f33Q44AzklIlfW\-0(https://www.figma.com/file/ruefQ8lS58wsoWuH2CUxny/AWS
✍️ Objective update
Concisely capture what the feature accomplishes so that anyone can not only understand it but easily explain it to someone else.
📏 Measures of Success
Provide clear and measurable outcomes. Each goal should be easily quantifiable, such as “at least 80% of new users will use this feature more than once a week.” This is an excellent opportunity for collaborators to comment on whether those goals are feasible or if they should be higher, given the investment of resources. We use anywhere from 3 to 6, but you’ll need to determine the right amount for you
📣 The "announcement"
The announcement envisions the feature’s impact on customers and how they’ll use it. It will also get your teams excited about the work to be done.
📝 Context
We call this the “big picture need” and it’s where you offer the broader context for the feature you’re building. Include assumptions, statistics, use-cases, and other types of evidence that will help make the feature more compelling
⚙️ Detailed needs and solutions
Before writing down solution ideas, plainly describe each need related to the feature. Then involve everyone in creating and editing a list of solutions that may address that need. The point here isn’t to start with a definitive prescription for how to solve those needs, but to inspire a discussion to create the best solutions.
🎯 Target audience details
As always, consider the target audience for the product. Who are you building this item for, and how will the customer use it in their everyday lives?
🎨 Mockups and design sketches
[hy write when images will do? Including [mockups and sketches](https://www.productboard.com/blog/8-prototypes-examples-mvp/) is a great way to give your idea something tangible to review. Either drop in your ideas, or this can be where designers start adding in their ideas or inspiration from other products or projects.
📊 Market research
What have your customers said in the past about similar products? Have they made any special requests for new products like the one in mind?