Write the problem before the features
Describe who is trying to achieve what, and in which situation. “We need a dashboard” names a solution. “The team needs to see the delivery date and owner in one place” describes a need you can test.
Choose one core journey
Map the path from entering the product to achieving the intended result. Include what makes that path work. Additional report types, roles and advanced personalisation can wait for later releases.
Define the learning goal
Write down the decision the first release should inform. Can people finish the task? Where do they need help? Plan interviews and usability sessions that will surface those observations.
Connect delivery to feedback
The scope, working release and user feedback belong to the same process. Before adding a feature, check whether the original assumption held up. A useful roadmap grows from observations as well as ideas.
Start with one user, one need, one core journey and one question you want to answer.
Explore the related service