This story will resonate if…

• Your product divisions have their own roadmaps, their own priorities, and their own working definition of “what the company is doing this year” — and they don’t always match
• You’ve watched a go-to-market window close while the teams supposed to hit it were still working to a strategy that existed before the last pivot
• The most accurate picture of your strategic health lives in a spreadsheet someone updates manually before every leadership review
• Your divisions meet their individual targets and the company still misses the year — and the post-mortem never arrives at a clean explanation

The challenge

Their strategy wasn’t wrong. It just kept getting lost between the boardroom and the people building the products.

Consumer technology isn’t an industry that waits. A competitor ships something unexpected, channel partners are asking about the roadmap by the following week, and by the time the go-to-market team is briefing retail operations on the new direction, the engineering divisions are either already aligned — or explaining why they aren’t. The work moves at the speed of the product cycle. Their planning didn’t.

Strategy was set every January, refined in a leadership offsite, and handed down through the usual chain. The hardware division had its own roadmap, organised by launch windows. Software worked to a release schedule. Services ran on a completely different cadence tied to contract renewals. Retail operations planned around seasonal peaks. Five rhythms. Five vocabularies. One company that was, on paper, supposed to be moving together.

For a while, they managed it on relationships. Senior people who knew each other, talked regularly, mostly catching the important stuff. But the company kept growing — past the point where relationships alone could carry the coordination load.

The hardware team would commit to a feature set for the next launch cycle. The software team, working from a different version of the same roadmap, would quietly deprioritise the underlying capability two quarters out. Neither team would find out until integration testing — at which point retail had already briefed channel partners on specifications that were no longer accurate.

A mid-year competitive shift happened. Leadership held an emergency session, adjusted two of the company’s three strategic pillars, and sent the all-hands communication. Six weeks later, two product divisions were still executing against the original plan. Not because anyone had ignored the announcement. Because nobody had updated the goals those divisions were actually being measured against.

Two platform teams independently built their own developer tooling to solve the same underlying problem. Both finished. Both shipped. The overlap came out at a cross-functional demo. Each team had spent the better part of a quarter building toward the same destination without knowing the other existed.

Before every quarterly business review, someone on the strategy team spent two to three weeks chasing status from a dozen division leads, in a dozen different formats, across six different systems. The picture they assembled was always two weeks old before it reached the CEO. The CEO mostly knew. But “mostly” and “two weeks ago” aren’t the same thing as a live picture.

They’d tried the obvious fixes. Shared planning documents. A single roadmap everyone was supposed to read. A cross-functional Slack channel for strategic announcements. Each solution worked for a while. None of them held. The problem wasn’t communication — it was that there was no single, live place where the company’s priorities, their owners, and their current status all lived together.

What finally turned it from a recurring frustration into a board-level priority was a quarterly business review where the Head of Strategy realised she couldn’t honestly answer the CEO’s question: which of our divisions are still working toward the goals we set in January? She had a reconstructed picture. Probably right. That “probably” was the problem.

The solution

They looked at four platforms. The question that decided it wasn’t about planning. It was about pivots.

Most OKR platforms are built for the planning event. The annual offsite. The cascade deck. The quarterly kickoff. They’re optimised for the moment goals get set — not the messy stretch in between, when those goals have to survive contact with a product cycle that doesn’t pause for anyone.

That’s where this company kept getting burned. Setting goals wasn’t the problem. Adjusting them mid-flight — and making sure that adjustment actually reached the teams who needed to act on it — was.

So the question they took into every vendor demo was unusual. Not “how does your cascade work?” but: “Show me what happens when our CEO calls a meeting on Monday, changes one of our three strategic pillars, and needs every product, engineering, and channel team working to the updated direction by Thursday.” Two platforms had no real answer for Thursday. One had a workflow that looked right in the demo and fell apart when they pressed on depth. Profit.co’s cascade actually moved at the speed they needed. That was the call.

The rollout didn’t follow a whiteboard plan. It grew to fit the shape of the organisation.

How the OKR programme actually runs now

A couple of things surprised the strategy team after rollout.

The first was adoption speed. Engineering — which had not historically embraced process tools — adopted the weekly check-in faster than anyone had projected. Partly because it was async and took two minutes. Partly because it replaced the synchronous status meeting they’d been dreading every Monday. Within a quarter, OKR updates were as routine as standups.

The second was what happened in planning sessions. When every division’s OKRs were visible to every other division before the quarter locked, the conflicts that used to erupt in post-mortems started surfacing during planning instead. Harder conversations, earlier — which is the only order in which they can actually be useful. The Head of Strategy described it as the difference between an argument you can resolve and one that happens after the damage is done.

What the leadership team opens every week

Platform integration

OKRs don’t live in isolation. Here’s how they connect the whole operating system.

The results

A year in, the gap between “priorities changed” and “everyone’s working on it” closed.

The metrics moved in the directions you’d expect. Check-in completion climbed past 80% — measured weekly across all divisions over a 12-month deployment period, up from 40–60% before automated nudges. Strategic pivots that had been taking four-plus weeks started landing in days. The board-ready strategy update stopped being a two-week assembly project and became an afternoon’s work.

But the bigger shift — the one the Head of Strategy brought up most in conversations months later — was in how meetings felt. Planning sessions ran shorter. The same debates that used to take an hour because nobody had the current picture now took twenty minutes because everyone did. The time that came back went into decisions, not into building the inputs for them.

And one specific thing changed for the engineering and hardware orgs. They stopped having to defend their roadmaps in every cross-functional review. Because the connection between their OKRs and the company’s priorities was visible — right there, on the same screen everyone else was looking at — they spent less time explaining themselves and more time building.

The one thing that barely moved was OKR scores themselves. Teams didn’t suddenly hit more of their goals. What changed was that when they missed, everyone knew earlier — and the conversation about why was grounded in something real, not assembled from memory at the end of the quarter.