Most organizations have a strategy. Fewer can show, for any given priority, who owns the work that delivers it, which measures show whether it is working, and which decision is waiting on leadership this month. The distance between those two states is where execution fails, and it is rarely a failure of effort.
Line of sight is the ability to trace a strategic priority down to owned work, and to trace evidence back up to the outcome it was meant to produce. It depends on relationships in how the organization runs, which a reporting tool can display but cannot create.
The chain
Ten links connect strategy to outcomes. Each answers a different question, and each can be present on paper while the connection to its neighbors is missing.
- 01Enterprise strategyWhere the organization is going, and what it will not do.
- 02Strategic prioritiesWhat matters most in this period, in order.
- 03Objectives / OKRsThe change in results each priority must produce.
- 04KPIs / KRsHow progress is measured, by when, and by whom.
- 05DriversThe operational levers that move each measure.
- 06InitiativesThe funded work intended to move the drivers.
- 07Risks / dependenciesWhat could stop the work, across initiatives.
- 08DecisionsWhat leadership must decide, by when, and who decides.
- 09EvidenceThe trusted data that shows what is actually happening.
- 10OutcomesWhether the result was achieved, reviewed against the objective.
When one link is missing, the links on either side still look healthy. The strategy document is well written, the projects are busy, the dashboard refreshes on schedule. That is why the break is hard to see, and why it tends to surface only when a result is already late.
What breaks at each link
| Link | Common failure | Evidence the link is holding |
|---|---|---|
| Enterprise strategy | Written as aspiration, with no choices about what the organization will not do. | Leaders can name what the strategy rules out. |
| Strategic priorities | Too many priorities, each treated as first. | A short list with an explicit order, used to settle tradeoffs. |
| Objectives / OKRs | Objectives restate activities rather than results. | Each objective describes a change in outcome and has one owner. |
| KPIs / KRs | Measures chosen because the data already exists. | Each measure has a definition, a source, a target, and an owner. |
| Drivers | No shared view of what actually moves a measure. | Teams can explain which operational levers move each result. |
| Initiatives | Work funded without a link to any measure. | Every initiative names the driver and measure it is meant to move. |
| Risks / dependencies | Tracked project by project, invisible across the portfolio. | Cross-initiative dependencies are mapped, owned, and reviewed. |
| Decisions | Discussed in meetings, rarely made or recorded. | Decisions are logged with an owner, a date, and a rationale. |
| Evidence | Two systems report two different numbers. | One source of record per measure, with a visible refresh date. |
| Outcomes | Outputs reported as outcomes. | Results are reviewed against the objective, not against the plan. |
Where to look first
The most common breaks sit in the middle of the chain: between measures and drivers, and between initiatives and decisions. Organizations usually have a strategy, and they usually have projects. What they lack is the connective tissue between them, an agreed view of what moves each measure and a forum where tradeoffs between initiatives are decided rather than discussed.
Four signs that the middle of the chain is missing:
- Initiatives are reported by percent complete, and nobody can say which measure they are expected to move.
- A measure goes red, and the conversation turns to who should look into it rather than what to change.
- Two initiatives compete for the same people, and the conflict is resolved by whoever escalates first.
- Leadership reviews status every month, and the decision log, if one exists, is mostly empty.
A dashboard can display line of sight only when the relationships behind it already exist.
Building it without a transformation program
Line of sight does not require a new system or an enterprise-wide rollout. It can be built one priority at a time, inside the operating cadence the organization already has.
- Pick one priority that leadership agrees matters and that is currently hard to track.
- Write the chain for it on one page, from the priority down to the initiatives, naming an owner at every link.
- Mark the missing links. Most organizations find two or three on the first pass, usually drivers, dependencies, or decisions.
- Test each measure before it goes in front of leadership: owner, definition, source, refresh, target, and the decision it informs.
- Put the chain into the existing review. Review the measure, its drivers, the initiatives behind them, and the open decisions in the same conversation.
- Expand to the next priority once the first one runs without special effort.
The first pass usually takes a few weeks, and the most useful output is rarely the page itself. It is the set of conversations about ownership, measures, and decisions that the page forces.
Tools for the work
Two instruments in this library support the steps above. The Measure Quality Scorecard tests whether a KPI or key result is ready for a leadership view. The Decision Rights Map names who decides, who is consulted, and when a decision moves up a level.