Display Features in Journeys
At this point in the inception we should have two pieces of insight: a list of features that the product should have, and the display of user journeys which indicate how users will interact with the product. With this activity we'll unite these two perspectives. Doing this will verify both of these views by integrating them.
Put the main journeys and the visible features side by side
Take each journey, and for each step, record any features that it needs.
When we're done, there's we usually find two kinds of missing links.
- Some journeys are missing features: for these we create feature cards, marking them for effort, value, and uncertainty.
- Some features are not mapped to journeys: we should challenge these features, do we really need them if they play no part in our users' journeys?
|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 Features in Journeys||Sequence the Features|
|Friday||Build the MVP Canvas||Showcase the results of the inception to those interested in the project|