<- Product Newsletter /

#86 - UX Roadmaps I

Sent the January 4th
Author face
Article written by
Juan Jesús Millo

Vacations, bitch

Hi! I'll be on holiday until the 10th, so I've scheduled this article talking about UX Roadmaps and the next one about Aino and Elissa Aalto by Rosa Cortázar!

There won't be any resources posts those two weeks, but when I'll be back I'll keep on giving you love! And the design course is just around the corner! ;)

Best regards and happy new year 💕

Writing of the week

Lately I'm creating several roadmaps for projects where I work, and the truth is that many times I feel unsure of what I'm doing, if I'm doing it right, if I'm overanalyzing it too much, if I'm missing some piece of information in the roadmaps... so I'm going to take the opportunity to make some notes about them in the newsletter <3

The basic components are:

  • What is the purpose of the product and the roadmap. This will answer all the questions that stakeholders have when they see the artefact. (e.g., Search Engine Results Page Design Roadmap).
  • Which artefacts are the targets. Always the final artefacts, not the artefacts that are created along the way. If the objective is to have a design, the artefact is not a User Screening, but the design at the agreed level of fidelity (e.g. List Design (1st Iteration).
  • Who is responsible for the roadmap .It can be one person or several, or the ownership can be a team or several.
  • When was the roadmap created, when was it last updated. Data for documentation, as well as answering to people who are not on top of the project whether it is up to date or not. We have to keep in mind that a roadmap is a living artefact and never static. (e.g. Creation of the roadmap: 25/11/21 - Last update: 12/11/21).
  • What chronological scales will you use to categorize the tasks. Here comes a bit your experience on what has worked for you or not; it can be a kanban of "To-Do, Started and Completed or NN Group recommends a "Now, Next, Future", or position these tasks along an X axis and mark each task with a start and end date... there are a thousand ways and none of them are perfect.

Those are kind of the basic components of a roadmap, so if you create one, you could use these pieces of information to generate a very basic template and use the following articles to complete it further!