How to Answer 'Are We on Track?' With Data in 5 Minutes

There is a moment in every board meeting , or every executive review, or every quarterly business review , when someone asks the question. It might be phrased differently each time, but it always means the same thing:

“Are we on track?”

What happens next typically follows one of two patterns. Either someone presents a confident narrative supported by carefully selected anecdotes, or someone pulls up a dashboard full of activity metrics that do not actually answer the question. Both responses cost the organisation something. The first costs trust. The second costs time.

The question itself is straightforward. The answer should be too. And yet most organisations cannot produce a reliable, evidence-based answer in under five minutes. Many cannot produce one at all.

Why “On Track” Is So Expensive When Unanswered

The cost of not being able to answer this question is not the awkward silence in the meeting. It is the decisions that follow.

When leadership cannot verify alignment between strategy and execution, they compensate. They add oversight. They request more frequent status reports. They create steering committees. They hire programme managers. Each of these is a rational response to uncertainty, and each adds cost and friction to the organisation.

A CTO who can demonstrate alignment with evidence spends board meetings discussing strategy. A CTO who cannot spends board meetings defending execution.

There is also a subtler cost: delayed correction. If it takes six weeks to discover that a major workstream has drifted from its strategic objective, you have lost six weeks of execution time. If it takes six months , which is not unusual in organisations that rely on quarterly reviews , the cost compounds dramatically. Not just in wasted effort, but in the downstream dependencies and commitments that were built on the assumption of alignment.

The ability to answer “are we on track?” quickly and accurately is not a reporting convenience. It is a strategic capability.

Three Requirements for Evidence-Based Alignment

After working with multiple leadership teams on this problem, we have identified three requirements that separate organisations who can answer the question from those who cannot.

1. A machine-readable expression of strategic intent

Most strategies exist as documents , PDFs, slide decks, Confluence pages, or at best, a set of OKRs in a dedicated tool. These formats are designed for human consumption. They are not structured in a way that allows automated comparison with execution data.

Evidence-based alignment requires that strategic objectives be expressed in a form that can be programmatically compared with operational data. This does not mean reducing strategy to a spreadsheet. It means creating a structured representation that captures objectives, their relationships, their relative priorities, and their expected execution characteristics.

Think of it as the difference between a destination written on a napkin and coordinates entered into a navigation system. Both describe where you want to go. Only one allows automated course correction.

2. Continuous, automated collection of execution evidence

The second requirement is a reliable picture of what is actually happening. This means collecting data from the tools where work is performed , Jira, Azure DevOps, GitHub, Linear, or whatever your teams use , and normalising it into a form that can be compared with strategic intent.

The key word is “continuous.” Point-in-time snapshots are better than nothing, but they create the same delayed-feedback problem as quarterly reviews. Effective alignment measurement requires near-real-time collection, so that drift is detected in days rather than months.

This also means addressing data quality honestly. Execution data from project management tools is often incomplete, inconsistent, or stale. An alignment measurement built on unreliable data is worse than no measurement at all, because it creates false confidence. The collection process must include quality assessment , not just “what does the data say?” but “how much should we trust what the data says?“

3. A comparison engine that acknowledges uncertainty

The third requirement is the ability to compare intent with reality and produce a meaningful assessment. This is where most approaches fail, because they attempt to reduce a complex, uncertain relationship to a simple status indicator.

Good alignment measurement acknowledges uncertainty explicitly. It does not say “we are 73% aligned.” It says “based on data with moderate completeness and high freshness, our confidence that Objective A is being executed as intended is 0.7, with the primary risk being a gap in Workstream C.”

This is more complex than a traffic light. It is also more honest, and more useful. A board member looking at a red/amber/green dashboard knows something is flagged but has no basis for action. A board member looking at a confidence-weighted alignment report knows where the gaps are, how reliable the assessment is, and what specific areas require attention.

What a Real Alignment Report Looks Like

An evidence-based alignment report is not a status update. It is a diagnostic document that answers several specific questions:

Coverage: What proportion of strategic objectives have active, traceable execution work associated with them? If your strategy has eight objectives and only five have associated workstreams, the other three are aspirational, not operational.

Effort distribution: How is actual effort distributed across strategic objectives, compared with how the strategy said it should be distributed? If your strategy prioritises “platform reliability” as the top objective but only 8% of engineering effort is directed there, you have an allocation problem regardless of what the status says.

Drift indicators: Where has execution diverged from intent? This includes work that was planned against one objective but has evolved to serve a different purpose, work that has no strategic connection at all, and strategic objectives that are losing execution momentum over time.

Confidence assessment: How reliable is this report? What is the completeness of the underlying data? How fresh is it? Where are the gaps in coverage that might mask real problems?

Trend direction: Is alignment improving or degrading? A single snapshot is useful. A trend line is actionable. If alignment has been declining for three consecutive periods, that is a different conversation than if it dropped once and recovered.

This kind of report can be produced in minutes , not because it is superficial, but because the underlying measurement is continuous. The report is a view into an ongoing process, not a periodic data-gathering exercise.

From Narratives to Evidence

The shift from narrative-based to evidence-based alignment reporting is not primarily a technology change. It is a cultural one.

Narrative reporting is comfortable. It allows for context, nuance, and , critically , spin. A skilled presenter can make almost any situation sound either encouraging or alarming, depending on the audience. This is not dishonesty; it is the natural consequence of asking humans to summarise complex situations without structured measurement.

Evidence-based reporting is less comfortable. It surfaces problems that narrative reporting might smooth over. It reveals gaps that leaders might prefer to address quietly. It creates accountability that is harder to negotiate.

But it also creates something far more valuable: a shared, verifiable understanding of reality. When everyone in the room is looking at the same evidence, the conversation shifts from “whose version of events do we believe?” to “what should we do about what we all can see?”

This is not about replacing human judgement with automation. Strategic decisions will always require context, experience, and intuition. But those decisions should be informed by evidence, not based entirely on the persuasiveness of the person presenting.

The question “are we on track?” deserves an honest, data-grounded answer. The organisations that can provide one consistently are the organisations that make better strategic decisions , not because they have better strategists, but because they have better visibility into whether their strategy is actually being executed.

Making the Shift

If you recognise your organisation in the narrative-reporting pattern, the transition to evidence-based alignment does not require a transformation programme. It requires three practical steps:

First, structure your strategic intent. Take your current strategy and express it in a form that can be compared with execution data. This is typically a few days of work, not months.

Second, connect your execution tools. Establish automated data collection from the tools where work is actually performed. Read-only access is sufficient , this is observation, not intervention.

Third, start measuring. Produce your first alignment report and see what it reveals. In our experience, the first report is always illuminating, frequently uncomfortable, and invariably the starting point for better strategic decisions.

The question will come again in your next board meeting. The question is whether you will answer it with evidence or with narrative.

---

BAS TrustDesk provides evidence-based alignment measurement between strategy and execution. If answering “are we on track?” takes longer than it should, let us show you what your data says.