This story will resonate if…

• Your January strategy feels like a different document by Q3
• You’ve sat in a post-mortem and thought: “We should have caught this in planning”
• Pulling together a leadership update takes days of chasing people, not minutes of checking a screen
• Your teams hit their own targets and the company keeps missing what actually mattered

The challenge

Their strategy wasn’t wrong. It just kept getting lost on the way down.

Here’s the situation. This group designs and builds the heavy equipment and systems that sit behind long-lifecycle industrial programmes. The work is technically complex, the programmes run for years, and the stakes of a wrong call don’t show up next quarter. They show up half a decade later.

Now try keeping 15,000 people pointed in the same direction across all of that.

For years they did what most companies do. Strategy set in January. Group heads translated it. Business unit leaders filtered it further. By the time those priorities reached the engineers doing the actual work, they’d passed through five or six layers of interpretation. Not wrong, exactly. Just blurry. A version of the strategy, not the strategy itself.

Nobody was trying to lose the thread. It just kept slipping.

• Two business units would spend an entire quarter executing well, then sit in a portfolio review and realise their roadmaps had been quietly pulling against each other. Both teams were right. Neither had been looking at the same picture.
• Two engineering teams independently developed the same modular component. Both finished. Both were proud of it. Nobody had known to check.
• A mid-year strategic pivot took six weeks to reach the teams who needed to act on it. Six weeks of people executing against a direction that had already changed.
• Before every quarterly review, someone spent the better part of three weeks chasing status updates, assembling a picture that was already weeks old by the time it hit the room.

They tried the usual fixes. Town halls. Shared documents everyone was supposed to read. A succession of tools, each solving one piece of the problem. Some of it helped. None of it held. The problem wasn’t process. It was visibility. There was no single place where the whole picture lived.

The solution

They looked at four platforms. Three cracked under the depth of the org. One didn’t.

When the strategy team started evaluating goal-management tools, one question cut through everything else: can this handle an org that’s actually this deep? Most platforms looked clean at the top. Goals cascaded neatly from company level to division. Push further down and things fell apart. Goals were technically linked but the thread was too thin to follow. Nobody really believed in it.

Profit.co held the cascade at every level. That was the decision. The rollout wasn’t mapped out on a whiteboard. It grew to fit the shape of the organisation.

How the OKR programme actually runs

Platform integration

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

The OKR module is the strategic backbone of Profit.co. But its real power isn’t just goal-setting. It’s what happens when OKRs are connected to the projects executing against them and the people being evaluated on delivering them. Here’s how this organisation uses all three together.

The results

Six months in, something had changed. Not just in the numbers, but in the room.

Six months in, meetings felt different. Business unit leads came into planning with a clearer sense of what was expected upstream. Blockers got raised earlier, not because anyone told them to, but because the platform made silence feel riskier than speaking up. The first quarter was rough in places. Adoption sat in the high 30s for six weeks. Two BU leads nearly pulled out. By quarter two, those same leads were the loudest internal advocates.