This story will resonate if…

• Your strategy gets translated differently by every business line, and everyone thinks their version is right
• You’ve seen a quarterly review where the deck looked fine and the actual performance told a different story
• Regional teams are running hard but pointing in slightly different directions, and nobody notices until the post-mortem
• Pulling together a cross-line strategic update takes days of chasing data, not minutes of opening a screen

The challenge

Their strategy wasn’t wrong. It just got translated differently by everyone who touched it.

Here’s the thing about running a services business at this scale. You’re not one company. You’re three businesses that share a name, a balance sheet, and a set of corporate priorities nobody fully agrees on how to interpret. Advisory teams think in transactions. Facilities teams think in contracts and headcount. Investment teams think in capital cycles and hold periods. All three are right. None of those time horizons are the same.

Add a hundred countries, each with its own market conditions and local leadership teams that’ve been doing it their own way for years, and you start to understand what the head of strategy meant when she said it felt like she was running three different companies that happened to share a CEO.

For a long time, strategy worked well enough. Leadership set the priorities. Business-line heads translated them. Regional MDs filtered them further. By the time those priorities reached the people running accounts and managing facilities across markets, they’d been through five or more layers of interpretation. Not wrong, exactly. Just different. Different enough that two regions executing perfectly against their own version of the plan could still end up pulling against each other.

Nobody was doing anything wrong. That was the frustrating part. The problem was structural.

• A cross-line growth initiative would surface in the advisory segment as a transactions target, in facilities as a new contract type, and in investments as a capital allocation shift. Three business lines, three different interpretations, no shared view of whether the initiative was working
• Regional teams in different geographies would execute well against their own quarterly targets, then sit in a cross-regional review and realise their efforts had been overlapping or, worse, competing for the same client relationships
• A strategic pivot decided at the centre would take weeks to reach operating teams in a meaningful, actionable form. Weeks of people executing against the old plan while the new one was still being explained at the top
• Every quarterly strategy review required someone to spend the better part of two weeks assembling a picture from reporting that came in different formats, at different times, using different definitions of what success looked like

They’d tried the usual fixes. Better templates. More alignment workshops. A push for a common language across service lines. Some of it helped at the margins. None of it solved the underlying problem. There was no single place where the strategy lived, updated in real time, visible across all three business lines and every region at once.

The solution

They needed a cascade that could hold across three business lines and a hundred countries. Most platforms couldn’t.

When the strategy team started looking at OKR platforms, the question wasn’t whether the software could handle goal-setting. Any of them could handle goal-setting. The question was whether it could handle this org, where a single corporate objective had to cascade cleanly into three structurally different business lines, then down through regional layers, and still be recognisably connected to the original at every level.

Most platforms looked fine in the demo. Goals cascaded neatly from company to division. The problem showed up when the team pushed deeper. Objectives that needed to live in multiple alignment paths at once, a cross-line initiative that touched advisory, facilities, and investments simultaneously, would technically link in the platform but the logic would get thin. Leaders stopped trusting it. When leaders stop trusting the cascade, the cascade stops getting maintained. And then you’re back to a spreadsheet and an all-hands deck.

Profit.co held the multi-line cascade. That was the deciding factor. An objective could be shared across business lines and still trace back coherently from any level of the organisation. And the check-in mechanic wasn’t passive, configured nudges, confidence scores, automatic flagging when a KR went stale. The system had opinions about what happened when people stopped updating. That mattered in an org this size.

The rollout started in one business line and grew from there. Not mapped out to the end from the start. The approach was to get it working in one place first, then bring the others in once there was something real to show them.

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 shifted. Not just in the numbers. In the room.

Six months in, the quarterly reviews felt different. Business-line leads came into planning sessions with a clearer sense of what was expected across the firm. Conflicts between regions surfaced in planning while there was still time to do something about them, not in a post-mortem after the damage was done. The measurable outcomes followed from that change in how decisions got made, not the other way around.