let's connect

16 Dec Theme-based Roadmap

Posted at 22:57h in Reference by

Theme roadmaps build your business, project, product and any other type of plan around a unifying goal or story. All work activities roll-up to or out from this unifier or theme. Having a thematic roadmap keeps the problem to be solved visible and (hopefully) easy to understand.

WHEN TO USE

HCD Process Phase: Inspiration

BABOK Knowledge Area: Strategy Analysis

PMI-BA Domain: Needs Assessment

tool sophistication0%
collaboration level0%
difficulty to complete0%

OVERVIEW

A theme roadmap is independent of methodology or approach. It is more of an orientation to planning and investigation than a prescribed rule set.

You can develop a thematic roadmap to function as a technology roadmap, project roadmap, marketing roadmap, or any other roadmap type.

While traditional roadmaps make the solution the focus of the planning, thematic roadmaps put the problem to be solved first.

Traditional roadmap example via Road Munk.

 

By focusing on the problem(s), you immediately open up cognitive space for team members to consider:

  • how broad is the impact of the problem(s)?
  • how is the problem(s) being addressed right now?


This space encourages experimenting, innovating, and collaborating to identify and propose as many choices and solutions as possible, while always keeping the user or customer at the centre of your processes.

Additionally, employing an open-ended approach means you avoid (or at least minimize) inducing solution sickness, or focusing on one solution and ignoring alternatives.

THEME CHARACTERISTICS

  • Themes directly and easily translate back into organizational strategic goals or visions. They must clearly communicate a “why”.
  • Themes carry and meet value propositions to be effective.
  • Themes appeal emotionally to the audience and customers. This is how you develop buy-in and support.
  • Themes join activities and tasks to the “big picture” goals and encourage creativity and innovation. This keeps the goal visible and, in turn, keeps the problem to be solved visible.

BASIC STEPS

1. Identify the root problem(s)

This is going to take research and engagement, perhaps quite a bit of both. You need to invest in finding the root problem(s) rather than looking immediately for a solution to a perceived problem.

Your starting point could be your product / project backlog, help desk or service desk tickets, general engagements with users,  or your own observations.

Any number of techniques can be used at this step. Be sure to involve as many people as possible and be diligent in documenting what you find.

2. Identify the theme(s) 
Once identified, group the problems into themes. Themes can be broad or condensed, depending on context. Here are a few examples:

  • Provide a quick and easy check-out process for customers
  • Get the right students into the right program at the right time
  • Automate the calculation and provision of valid final grades

When developing a theme, consider the following questions:

  • does it have emotional appeal?
  • does it clearly communicate an objective?
  • is it succinct enough to keep people focused?

Your final theme(s) should be a calling card for the project, something easily communicated and easily recalled. Try out different theme ideas for the groupings until you find the right fit.

3. Visualize the themes

There are numerous tools and products you can use (e.g. Slack, ProductPlan) to visualize the themes. Find the best visual approach for representing the thematic roadmap and the strategic or financial value represented within it.

Gantt charts or cards are traditional approaches which may work though don’t be afraid to be creative. No matter the approach keep it as simple as possible to increase the visual effectiveness. Make it overly complex or too detailed and you’ll lose buy-in and support.

theme-based roadmap example

Standard theme-based roadmap example vis ProductPlan.

Tags:


error: Content is protected