Skip to content
CoursesLog in
← Statistics glossary

theme (roadmap theme)

Also called: theme, roadmap theme

A high-level customer need, problem or job that groups related work on the roadmap, phrased as a result rather than a solution, e.g. "make reordering effortless for regular buyers".

A theme is the basic building block of an outcome-based roadmap: a customer need, problem or job that the team commits to addressing, without yet committing to how. Think of themes as the goals behind the features. "Fewer surprise costs at checkout" is a theme; "show the delivery price on the product page" is one possible solution for it.

Good themes share a few traits:

  • Phrased as a result for someone. A simple pattern: Ensure [result] for [who], e.g. "ensure regular buyers can reorder in under a minute".
  • Tied to at least one business objective. A theme that can't be linked to any objective is a warning sign.
  • Big enough to matter, small enough to finish. Usually a quarter or two of work for one team.
  • Backed by evidence. Journey maps, interviews, support tickets or data show the problem is real.

Large themes break into subthemes, narrower needs within the same problem. Subthemes are also the right place for a known or probable solution, so the "why" stays visible above it.

Themes help in several ways. They make it easier to say no to requests that serve no theme. They give sales and marketing a story about customer value instead of a feature list. They leave engineers and designers room to find the best solution. And a handful of themes is far easier to read than dozens of features.

Example

CatChow's request list includes: "pause a subscription", "SMS before delivery", "choose a delivery slot", "cheaper delivery for 2+ bags", "reorder in one tap". Interviews and support logs point to two underlying problems, so Sofia groups the requests:

  • Theme A: Ensure owners always know when food will arrive (objective: cut delivery tickets by 30%).
    • Subthemes: delivery notifications; choosing a delivery slot.
  • Theme B: Ensure regular buyers keep food coming with no effort (objective: subscription share from 18% to 30%).
    • Subthemes: one-tap reorder; flexible subscriptions (pause, skip).

"Cheaper delivery for 2+ bags" fits neither theme. It's parked with a note to revisit when unit economics becomes an objective.

Common mistakes

  • Features in disguise. "Mobile app" or "loyalty program" are solutions. Ask what they are for.
  • Themes too vague to act on. "Better UX" can justify anything. Name the user and the result.
  • Themes too narrow. "Change the button color" is a task, not a theme.
  • Orphan themes. A theme that supports no objective usually comes from a loud stakeholder, not from strategy.
  • Mixing levels. Don't rank a theme against a feature; compare like with like.

Learn it in the course

  • Anatomy of a roadmap: the five primary components · The five parts every useful roadmap needs (product vision, business objectives, themes, timeframes and a disclaimer), what each one does, and Sofia's first one-page roadmap for CatChow.
  • Outcomes over outputs · The difference between what a team ships and what changes because of it, how to climb from a feature request to a measurable outcome, and the traps that make an outcome useless.