Discover the Features
A feature is a description of an interaction of a user with the product or some other action that the product can perform. Examples include: print invoice, see detailed statement, and invite facebook friends.
The description of a feature should be as simple as possible. We start with something the user trying to do, we then consider a feature the product should have to support that task.
How we do it
Since we have already described the personas and the main objectives of the product, we can use the following activity to discover features.
- Put the product goals as column titles on a common feature canvas. Prioritize these goals from left to right, high to low.
- Put the personas as row titles in priority order from top (high) to bottom (low).
- Everyone suggests features and places them on the table. Use the personas and goals to guide the discussion. The key question is “what does the product need to do so that this persona reaches this goal”.
Although the canvas is similar to a matrix, it won’t necessarily have a feature for each combination of goal and persona. It can have multiple features for one persona to reach one specific goal, as well have personas who don’t need a feature for a certain goal.
If we identify goals and features that don't correspond the needs of any persona, they should be discarded or re-thought, because their value is not clearly linked to a user.
|Monday||Introduce the inception, kick off, and Write the Product Vision||The product Is – Is not – Does – Does not|
|Tuesday||Describe the Personas||Discover the Features|
|Wednesday||Technical and Business Review||Show the User Journeys|
|Thursday||Display the Features in the Journeys (coming soon)||Sequence the Features (coming soon)|
|Friday||Build the MVP Canvas (coming soon)||Showcase the results of the inception to those interested in the project|