Value propositions clearly define key aspects of your design that demonstrate it is a valuable and worthwhile product or service. It provides focus for the design of many types of services or products. Here is a template to get you started.
For [describe target users] who [describe problem or need], [name of product/service] is a [describe type of product/service] that [describe benefit or value].
As a team, review all of your work and discuss several possible design directions before settling in on one single value proposition. You will want this statement to be clear, concise, and compelling. It should be supported by your research and analysis up to this point. Begin to map out the features of your solution. This will likely be updated as you go, but start to think about each feature (also could be called user stories) that your solution will provide. This article will give you a good introduction to the concept and you can use this template to get started with the map. Again, this is just a draft of your intended features to provide users and will be adapted later.
❏ Deliverable A document or slide with your team's value proposition and a draft features map.
See feature map example in this article.
✓- Below Standard
✓ At Standard
✓+ Above Standard
Value proposition is provided but is not clear or does not offer a compelling need for the proposed solution.
Value proposition is clear and supported by the team's research.
Value proposition is especially convincing and generates anticipation to see the rest of the project. The value to stakeholders is compelling.
Features map demonstrated little thought in breaking down a solution into needed parts.
Features map demonstrated a thoughtful attempt to define needed features.
Features map demonstrated a particularly careful consideration of a the priority of features to the solution.
