Home/Blog/OKRs/OKRs vs Roadmap vs Backlog: How the Thre…
OKRs

OKRs vs Roadmap vs Backlog: How the Three Fit Together

OKRs vs roadmap vs backlog: the goals say what should be different, the roadmap says what you will do, the backlog holds the work, and each must trace upward.

Cover of the FIKR Space guide: OKRs vs Roadmap vs Backlog: How the Three Fit Together

OKRs, a roadmap and a backlog answer three different questions: the goals say what should be different, the roadmap says what you intend to build or do in pursuit of it, and the backlog holds the specific work that implements the roadmap. Problems start when a layer is skipped.

The three get confused constantly because all of them are lists of things a team cares about. The guide's hierarchy is simple, and once you hold it, many familiar problems turn out to have the same root. This article describes each layer, what happens when one is missing, and a way to check that the three are connected.

OKRs vs roadmap vs backlog: three layers, three questions

The easiest way to keep them straight is to ask what each one is for.

LayerThe question it answersWhat it contains
GoalsWhat should be different?Objectives and the key results that show change
RoadmapWhat do we intend to build or do in pursuit of that?The intended pieces of work, in the order you expect to attempt them
BacklogWhat is the specific work that implements it?The individual items the team actually picks up

Each layer sits above the next. The goal does not say how, the roadmap does not say exactly what to do on Tuesday, and the backlog does not explain why. Only the three together give a complete answer.

This is also why a key result must be a changed state and not a piece of work. If the goal layer starts listing deliverables, it duplicates the roadmap and stops doing its own job. The difference is explained in how to write key results.

What goes wrong when a layer is skipped

The guide is specific about two failures.

  • A backlog with no roadmap produces busy incoherence. Plenty of work is done, and none of it adds up to a direction.
  • A roadmap with no goals produces a feature factory shipping confidently in no particular direction. The team is sure of what it is building and cannot say what building it is meant to change.

Notice what those have in common. In both, work continues and progress feels real. The failure is invisible from the inside, because output looks like movement. The distinction between motion and progress is at the centre of what are OKRs.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

The three layers on one example

The guide's own example of a changed state helps here. Suppose the key result is to grow organic signups from forty to one hundred and twenty a month. Publishing twelve articles is, in the guide's words, how you might attempt it.

LayerWhat it says in this example
GoalOrganic signups grow from forty to one hundred and twenty a month
RoadmapPublish twelve articles as the intended attempt
BacklogThe individual pieces of work needed to produce each article

Read upward from the bottom row and each item has a reason. Read downward from the top and the goal has a plan. Notice also what the example protects. If the articles are not moving the number, the roadmap can change while the goal stays, because the goal never said articles. That freedom exists only when the layers are kept distinct.

The trace test

The guide gives a practical discipline for checking the connection. You should be able to trace any item on the board upward to a key result. You should also be able to notice, without drama, when a substantial share of the work cannot be traced anywhere.

Run it as a short exercise.

  1. Pick any item the team is working on this week.
  2. Find the roadmap item it implements.
  3. Find the key result that roadmap item is meant to move.
  4. If any step fails, write down the item and what is missing.

The phrase without drama matters. Untraceable work is not necessarily wrong. There is routine work that keeps a company running. The point is to see how much of it there is, and to choose it rather than drift into it. If a substantial share cannot be traced, the goals may be incomplete, or the team may be spending its time on something nobody chose.

Why the goals must live where the work lives

The mechanical detail that decides everything is whether the goals are connected to the actual work surface. If the goals live in one document and the work lives in a roadmap, a backlog and a board somewhere else, the goals will be forgotten by week three.

The guide is careful about the reason. It is not negligence. People work where the work is, and nobody navigates to a separate file to be reminded of priorities. A goal that cannot be seen from the place where the daily decisions are made has no chance of settling them.

This is why the guide lists leaving the goals somewhere the work is not among its nine biggest mistakes, and why the full set is diagnosed in OKR mistakes founders make.

Founders sometimes hear all this and picture an elaborate system. The guide says the link can be light. It gives three examples.

  • Roadmap items tagged to the key result they serve.
  • The board reviewed against the goals.
  • The backlog ordered by which items move a number.

What matters is that a person looking at their work can see what it is meant to achieve, and that a person looking at a goal can see what work is attached to it. Two views, connected. When they are, the goals stay alive. When they are not, no amount of enthusiasm at kickoff will save them.

You can do all of this with a document and a spreadsheet, as the guide notes. The discipline is in keeping the two in step and not letting either view become the only one that anyone opens.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Ordering the backlog by what moves a number

One of the guide's three light links deserves a closer look: ordering the backlog by which items move a number. It is the most direct way for a goal to shape daily work.

Without it, a backlog is ordered by recency and volume, the same forces that set priority when there are no goals at all. With it, the question when someone is choosing what to pick up next has an answer. The item that moves a key result goes ahead of the one that does not. That does not remove routine work, but it makes the choice visible and arguable.

It also helps the owner. A single named owner can only be accountable for a result if the work attached to it is visible and ordered. How owners and teams line up is described in how to align OKRs across teams.

Connecting the layers to the weekly rhythm

The weekly check is where the three layers meet. When an owner reports the number, their confidence and what is in the way, the answer to the third question usually lives in the roadmap or backlog: something is late, or blocked, or has turned out not to move the number.

If the layers are connected, the owner can see that immediately. If they are not, the conversation is about impressions. The format of the check is in how to run a weekly OKR check in.

Free guide, 32 pages: The OKR Playbook. Send me the guide.

An audit you can run this week

If you suspect your layers have drifted apart, here is a short audit.

  1. List the key results for this quarter.
  2. Beside each, list the roadmap items meant to move it.
  3. Beside each roadmap item, list the backlog items that implement it.
  4. Look for key results with nothing beside them, and work on the board with no key result above it.
  5. Decide, for each gap, whether the goal is missing, the work is misplaced or the item is routine and deliberately outside the goals.

Both kinds of gap tell you something. An empty key result means you have an intention with no plan. Orphan work means you have effort with no purpose you can name.

FIKR OS, strategy meets execution: OKRs, roadmaps and kanbans in one system. See FIKR OS.

Frequently asked questions

Is a roadmap the same as a list of OKRs?

No. The goals say what should be different. The roadmap says what you intend to build or do in pursuit of that. Mixing them makes the goal a task list.

Does every backlog item need a key result?

You should be able to trace any item upward to one, and to notice without drama when a substantial share cannot be traced. Routine work may sit outside the goals, but it should be a choice.

What if we have a roadmap but no goals?

The guide describes that as a feature factory, shipping confidently in no particular direction. Start by writing what should be different, then tag the roadmap items to it.

How heavy does the connection need to be?

Light. Tagging roadmap items to key results, reviewing the board against the goals and ordering the backlog by what moves a number are enough.

The full method, with the checklists, is in The OKR Playbook, a free 32-page playbook.

LG

Luis Goncalves

// Founder & CEO at FIKR Space

Three-time founder. Built and exited Evolution4All before this. Now building FIKR Space — the operating infrastructure underneath every innovation ecosystem (startups, accelerators, governments, investors). Lisbon-based, works global.

Claim your founding member spot.

Every founding member is hand-reviewed. Tell us who you are and how you want to co-create — we get back inside 48 hours.

Role
Job Title
Country
Cookies

We use cookies.

Essential ones keep the site working. The rest only run if you say so. No dark patterns, no pre-ticked boxes.Privacy policy

Co-create with us. It's about building it together.Co-Create With Us