Six months in: 5 questions your strategy dashboard should be able to answer

If you’re running a mid-year strategy review, you probably already have dashboards telling you how your strategy is tracking. You have visibility. You have data. You have a view of what’s on track and what isn’t that gets updated regularly and shared with the right people.

And yet, at the midpoint of the year, some of the performance leaders we talk to have a nagging feeling that the picture isn’t complete. Not because the data is wrong, but because there’s a gap between what the dashboard shows and what they’re hearing from the people closest to the work.

That gap is real, and it’s usually structural. Standard performance reporting is designed to capture what happened. It’s much less good at surfacing why, or what it means. Here are five questions your strategy dashboard should be able to answer at the six-month mark, and where to look if it can’t.

1 Which initiatives are consuming effort without moving the needle?

Most dashboards track completion and status. What they don’t track well is the ratio between effort going in and progress coming out. An initiative can be marked on track, updated regularly, and consuming significant team time, while delivering almost nothing against its intended outcome.

By June, this pattern has had six months to establish itself. The teams involved are busy and reporting dutifully. But if you mapped actual effort against actual strategic movement, some of those initiatives would look very different.

What to look for

Pull the initiatives that have consistent green or amber status but haven’t hit a single milestone in the last eight weeks. Then have a direct conversation with the owners. Busyness and progress feel similar from inside the work. From outside it, the difference is usually visible pretty quickly.

2 Who is actually accountable for each initiative right now?

Dashboards can create a false sense of security about accountability. When there’s a name against an initiative, it looks like someone is in charge. So nobody checks whether that’s still true.

Six months in, the reality is often messier than the plan suggests. People have moved. Priorities have shifted. The named owner is still on the record but is now two degrees removed from the actual work, and the people doing the work don’t know they’re supposed to be updating anything. The dashboard didn’t create the problem, but it made it easier not to notice.

What to look for

Any initiative where status updates are consistently vague, consistently late, or consistently filed by someone other than the named owner. That’s usually a signal that the accountability structure has drifted from what the plan says it is. The fix isn’t a new process. It’s a direct conversation with the owner on record: are you still the right person to be driving this?

3 Is that green status genuine, or is the team just recovering well?

This one is subtle, but it matters. An initiative marked on track in June might genuinely be on track. It might also have been behind in March, caught up through a sprint of intensive effort in April and May, and now be sitting at the right completion percentage while the team has been running at full stretch to get there and the underlying delivery risk hasn’t gone away.

Standard status reporting doesn’t distinguish between these two things. On track is on track. But an initiative that has been recovered once is statistically more likely to need recovering again, and the cost of the next recovery is usually higher.

What to look for

Look at the history of status changes, not just the current status. An initiative that has moved from red to amber to green over the past quarter deserves a closer look than one that has been green throughout. The trend tells you something the current status doesn’t.

4 Are your updates reporting progress or describing activity?

Reporting culture drifts toward narrative over time, and the reason is straightforward. Specific updates invite scrutiny. “Vendor contracts finalized, integration 40% complete” tells you something precise, and if it’s wrong or behind, someone will notice. “Project progressing well” tells you almost nothing, and nobody pushes back on it. Over time, people update in the way that takes the least effort and generates the least friction. It’s not a character flaw. It’s what happens when a system treats both types of update the same way.

By mid-year, if your reporting culture has drifted toward narrative, your dashboard is giving you a feeling about how things are going rather than a fact-based picture. That’s a meaningful difference when you’re making resource decisions for the second half of the year.

What to look for

Audit a sample of recent updates across your major initiatives. What percentage include a specific, verifiable claim about progress? What percentage are general statements about momentum or direction? If the balance has shifted toward the latter, the issue isn’t the people. It’s that the reporting system isn’t creating enough reason to be specific. Reset expectations about what a useful update looks like, and make it clear that precision is what gets noticed, not volume.

5 Does your data match what the delivery teams are actually experiencing?

This is the one that dashboards are structurally least equipped to show, and the one that matters most when you’re trying to understand execution risk in the second half of the year. The people closest to the work often have a very different picture of how things are going from the one that shows up in the data. They know which dependencies are at risk. They know which timelines are optimistic. They know which stated priorities aren’t actually being resourced.

That information doesn’t make it into the dashboard because it doesn’t fit neatly into a status field. But it’s often the most accurate leading indicator of where execution is about to get difficult.

What to look for

Build a mid-year conversation into your review process, not just a data review. Ask delivery leads directly: what’s the thing that keeps you up at night that isn’t showing up in your reporting? What would you want leadership to know that you haven’t found a way to escalate? The answers are usually more useful than pulling up the dashboard again.

Your dashboard gives you the picture. You still have to decide what to do with it

None of this means your performance reporting isn’t working. It means performance reporting has limits, and those limits matter most when you’re making the biggest decisions, like right now, when your mid-year strategy review should be informing how you resource and prioritize the months ahead. If you’re already using StrategyBlocks, the visibility is already there: status history, ownership, update trails, and the link between activity and outcomes. This is the moment to use it.

The organizations that finish the year well aren’t necessarily the ones with the best dashboards. They’re the ones that treat their mid-year strategy review as a decision-making exercise, not a reporting one.

If you want to see how StrategyBlocks helps operations and performance leaders maintain a clearer picture of execution reality across their full portfolio, get in touch with our team.