Analysis Across Horizons

Here is something I keep seeing.

On the same program, in the same week, sometimes in the same building, there are two conversations happening that do not know about each other.

Upstairs, leadership is talking about outcomes. Market position, the case for change, what this is all ultimately for. The conversation is fluent and forward-looking and entirely about why. Nobody in the room could tell you what is in this sprint.

Downstairs, the delivery team is talking about tickets. Acceptance criteria, a blocked dependency, whether a story is really ready. The conversation is precise and grounded and entirely about what and how. Nobody in the room could tell you, in a sentence, why any of it matters to the strategy being discussed one floor up.

Each conversation is coherent on its own. Each is being had by capable people doing exactly their job. And the distance between the two rooms is where most transformation quietly goes wrong.

Analysis has an altitude

We tend to talk about analysis as one activity. It isn’t. It happens at different altitudes, and the altitude changes what analysis even means.

At the strategy altitude, analysis is about direction — framing the problem worth solving, understanding constraints and drivers, deciding where to invest and where not to. The time horizon is long. The questions are about intent.

At the initiative altitude, analysis is about structure — turning direction into shape. Clarifying outcomes, identifying viable paths, breaking the work into pieces, sequencing by value and dependency. The horizon is nearer. The questions are about how the work is organized.

At the delivery altitude, analysis is about execution — making sure the right work is ready, clear, and testable, and that what gets built actually serves what was intended. The horizon is close. The questions are about the next increment of value.

None of this is my invention. The discipline of Agile business analysis has mapped these altitudes for years; the strategy–initiative–delivery framing is established practice, and I am borrowing it, not coining it. What I want to note is not that the three levels exist. Everyone knows they exist. It is something less obvious and more troublesome: they do not stay connected on their own.

Drift is the default

Left alone, the three altitudes drift apart. Not as a risk that occasionally materializes, but as the resting state. Gravity pulls them apart, and something has to actively hold them together, or they separate: slowly, invisibly, and then all at once.

You can see the drift if you know the signatures.

A backlog item that no one can trace upward. Ask why it’s being built and you get a shrug, or a name, or “it was in the requirements.” The thread up to intent has snapped, and the team is now building something efficiently for a reason no one in the room actually holds.

A strategy that no one can trace downward. Leadership can articulate the ambition beautifully, but nothing in the current sprint is recognizably an instance of it. The thread down to execution has snapped, and the strategy has become a document that describes a program running in parallel to the real one.

A status report that is green at every altitude and yet the program is failing. Each level is succeeding at its own version of the work. It is the connections between the levels that are failing, and nothing in the reporting is designed to see a connection — only a level.

The most expensive version of this is the one that stays invisible longest. Everyone is busy. Everyone is productive. Every altitude is, by its own measures, doing fine. And the whole is drifting toward a delivery that is technically excellent and strategically beside the point.

You can build the wrong thing very efficiently. It happens constantly. It almost always looks like success until the moment it doesn’t.

The thread

The work, then — the actual analytical work that matters most and gets budgeted least — is maintaining the connection.

Not a document that claims the connection exists. The living thread itself: a continuous line that lets any decision at delivery be traced up to the intent it serves, and any strategic intent be traced down to the work delivering it.

And it has to run both ways. This is the part people miss when they hear “traceability” and picture a compliance matrix. The thread is not only intent flowing down into execution. It is also execution’s reality flowing back up into intent. Delivery discovers things — constraints, costs, what is actually feasible, what users actually do — that strategy needs to know and usually never hears. A thread that only runs downward turns into a chain of command. A thread that runs both ways turns into a nervous system.

Someone has to be that thread. In practice it is the analyst — not the analyst as scribe, taking down requirements at one altitude, but the analyst as the one person in the program deliberately moving between altitudes, carrying intent down and reality back up, refusing to let the two rooms forget about each other.

That movement is the job — not producing artifacts at each altitude, but keeping the altitudes in contact with each other.

Move fast without losing the plot

The objection I hear is that all of this sounds like overhead. That keeping strategy, initiative, and delivery connected is a governance burden — meetings, mappings, traceability — that slows delivery down.

It is the opposite.

The fastest way to waste a year is to let the altitudes drift and only discover it at the end, when delivery finally surfaces something that contradicts a strategic assumption no one had revisited. The connection is not a brake on speed. It is the thing that makes speed safe — that lets an organization move quickly and still be moving toward the thing it actually meant.

Analysis has an altitude. The mistake is to think you get to pick one. You don’t. The work lives in all three at once, and in the threads between them, and the moment those threads go slack is the moment the program starts building the wrong thing beautifully.

Keep the thread intact, and you can move as fast as you like.

Lose it, and speed is just how quickly you arrive somewhere you didn’t mean to go.

Analysis Across Horizons is a field note from the Studio, a practice of organizational sensemaking. The strategy, initiative, and delivery framing is drawn from established Agile and business-analysis practice; my contribution is the insistence on working across all three at once, and treating the thread between them as a core component of the analyst’s work.

Article outline

Analysis has an altitude

Drift is the default

The thread

Move fast without losing the plot