Most strategy offices were set up to steer the strategy. Many end up running a reporting factory: chasing updates, building packs, reconciling numbers from different systems. Strategy deployment software should give that time back, and the office should know what to do with it.
In this guide
Key Takeaways
- →The pattern is common: two weeks a month collecting updates and reconciling them, producing a pack that is accurate and late.
- →The office is busy, valued, and doing the wrong work.
- →It should own the deployment process, evidence of effect, dependencies across, the quarterly review and the annual reflection.
- →Software should take data collection, reconciliation, exception finding and negotiation logistics.
- →It can’t take the judgment: diagnosing why a bet isn’t working and persuading the people involved.
- →Judge a strategy office by the decisions it brings forward, not the reports it produces.
The reporting factory
The pattern is common. A strategy office of four or five people spends the first two weeks of every month collecting updates from objective owners, reconciling them with finance and portfolio data, and building a pack for the executive committee. The pack is accurate and late. The meeting reviews it, asks for more detail on a few items, and the cycle starts again.
The office is busy and valued, and it is doing the wrong work. Its people understand the strategy better than anyone, and they spend most of their time moving numbers between systems.
What a strategy office should own
| Responsibility | In practice |
|---|---|
| The deployment process | Planning calendar, target negotiation rounds, review cadence |
| Evidence of effect | Making sure work progress is compared with results, and exceptions reach leadership |
| Dependencies across | Brokering agreements between functions whose targets depend on each other |
| The quarterly strategy review | Preparing the decisions, not the slides |
| The annual reflection | Which strategic bets worked, as input to the next plan |
A strategy office should be judged by the decisions it brings forward, not by the reports it produces.
The annual reflection in that last row has a method of its own, described in Hansei: Reviewing Last Year’s X-Matrix Before Planning the Next.
How the office’s time should shift
The same five activities, before and after. What changes is not how hard the office works but which half of the month it spends on judgment.
| Activity | Typical today | With deployment software |
|---|---|---|
| Collecting and chasing updates | 35% | 5%: owners check in directly |
| Reconciling and formatting | 25% | 5%: one data model |
| Diagnosing exceptions | 10% | 35% |
| Brokering cross-functional agreements | 10% | 25% |
| Preparing decisions for leadership | 20% | 30% |
What software should take off its plate
- Data collection. Owners update their own objectives and results on a cadence.
- Reconciliation. OKRs, scorecards, hoshin plans and portfolio data on one model.
- Exception finding. Work that isn’t moving results is flagged, not hunted.
- Negotiation logistics. Target rounds run with visible status and a record.
What software can’t do is the judgment: diagnosing why a bet isn’t working, deciding whether to change it, and persuading the people involved. That’s the work the office should have time for.
A worked example: one month, before and after
Here is a hypothetical month of strategy review, week by week, before and after the change:
| Week | Before | After |
|---|---|---|
| 1 | Chase 40 objective owners for updates | Review exception list: 3 bets flagged, 2 delivery problems |
| 2 | Reconcile with finance and PMO data; build pack | Diagnose the 3 flagged bets with their owners |
| 3 | Executive meeting walks through 60 slides | Broker a dependency between service and commercial |
| 4 | Follow up on questions from the meeting | Executive meeting decides on 3 items; decisions recorded on the objectives |
What the reporting factory costs
Five people spending two weeks a month on collection and reconciliation is roughly two and a half full-time people, spent on work that produces no decision. That is the real budget line to compare any tool against, and it is usually larger than the subscription by a wide margin.
Among published alternatives, OnStrategy lists $200 per month for unlimited users. i-nexus publishes a free Starter tier for up to five users and $28 per user per month at its Standard tier. For a strategy office, the question to put to either is narrow: after go-live, who still assembles the monthly pack?
Profit.co publishes two plans, Essentials and Enterprise, quoting against modules and scale rather than a public seat rate. Because OKRs and Goals, Balanced Scorecard, Hoshin Kanri and Strategy Roadmap sit on one data model, the reconciliation step the office spends a quarter of its month on has nothing left to reconcile. Building the Business Case for Hoshin Kanri Software sets out how to total that properly, and the 30-day free trial covers one monthly cycle, which is the cycle this article is about.
The strategy office in Profit.co
In Profit.co, owners check in on their own objectives, OKRs, scorecards and hoshin plans share one model with project portfolios alongside, the exception queue lists what needs attention, and catchball sessions show which negotiations are open. See the strategy deployment software page and Hoshin Review Cadence in Software: Monthly, Quarterly, Annual.
Three of those change what the office does on a Monday:
- The exception queue replaces the chase. Week one becomes a review of what is already flagged rather than forty emails.
- One model replaces the reconciliation. A scorecard measure and an OKR key result are the same record, so there is nothing to match up.
- Catchball replaces the negotiation logistics. Open rounds, their status and their reasoning are visible without a tracker spreadsheet.
What remains is diagnosis, brokering and preparing decisions, which is the work the office was created to do.
Free Product Demo
Give your strategy office its time back
A 30-minute walkthrough, tailored to your team.
Book a free demo
What happens in the call
How your teams set goals, track progress and review results.
Strategy, performance, projects and engagement on one platform, with AI.
A practical path to align teams, execute faster and drive results.
Questions this article answers
Own the deployment process, keep evidence of effect flowing to leadership, broker dependencies between functions, prepare decisions for the quarterly review and run the annual reflection.
Because data lives in many systems and someone has to collect and reconcile it. Without a single model and owner check-ins, that job falls to the strategy office.
Data collection, reconciliation between methods and systems, finding exceptions, and the logistics of target negotiation.
The judgment: diagnosing why a bet isn’t working, deciding whether to change it, and persuading the people involved. That is the work the office should have time for.
By the decisions it brings forward, not by the reports it produces. A useful reference question is to name a decision made earlier than it would otherwise have been.
