This story will resonate if…

• You’ve asked for a status update on a group priority and received ten slides about things you didn’t ask about — because that’s what the team thought you meant
• Your divisions technically have OKRs, but you couldn’t say right now which group objective each one is actually moving
• A strategic initiative showed green in every report for most of the year, then came in short — and nobody saw it coming
• You’ve tried rolling out a goal framework before and watched adoption fade after the first quarter, because the check-in felt like extra work rather than useful work

The challenge

Nobody was ignoring the strategy. It just kept getting rewritten on the way down.

Every January, the executive committee gathered and set the plan. The sessions were good. The priorities were clear. Then they went into a deck, the deck went into an email, and the email landed with division heads across Europe.

What happened next was almost impossible to trace. Each division had its own planning rhythm. Its own language for goals. Some called them KPIs. Some called them targets. A handful had started using “OKRs” — though what that meant varied by floor. Nobody was being careless. Goals just got quietly rewrapped around whatever work was already running.

By quarter two, the company was effectively running several slightly different strategies. Leadership knew something was off but couldn’t see where the thread had broken. The quarterly review was supposed to surface it — but the data arrived three weeks late, assembled by hand from divisional slide decks, and nobody trusted it was current.

• A strategic initiative stayed green in every status report for three quarters, then came in significantly short at year-end — three divisions had each assumed the others were doing the heavy lifting
• When priorities shifted mid-year, the message took six weeks to reach the teams whose work it affected — by which point commitments had already been made
• Two teams discovered in a post-mortem that they’d been pursuing goals that pulled against each other — a conflict nobody had seen because there was no shared view
• Chiefs of staff spent half their week chasing status updates that should have been visible without asking

The frustrating part was that none of this was dramatic. Good people, working hard, on goals that no longer matched the plan. Not because they’d been told to stop. Because the system had no way to tell them.

The solution

They looked at three platforms. Two cracked under the weight of the org. One didn’t.

The evaluation team had one core question: can this hold the cascade at every level? Most tools looked fine at the top — objectives linked to objectives, two levels down. Push further and the logic frayed. Goals were technically connected but the thread was too thin to follow. Nobody would believe in it.

The first platform was a workflow tool with an OKR module added. The cascade had a shallow ceiling. The second was a dedicated goal tool with better depth, but check-in adoption among its reference customers was stuck around 40% — and the organisation had been through a failed rollout before. Adoption wasn’t a nice-to-have. It was the whole problem.

Profit.co held the cascade at every level — from group objective down to individual contributor — and the check-in was built to be a two-minute job, not a form. During the pilot with two divisions, one division lead opened the platform mid-quarter and saw, for the first time, that her team’s goals overlapped with a neighbouring division’s priorities in ways neither team had known. That one moment — visible, live, actionable — ended the evaluation.

How OKRs actually run now

Platform integration

OKRs are the backbone. Everything else connects through them.

The OKR module is where strategy becomes visible. But its real value is what happens when it connects to the projects executing against it and the performance reviews evaluating the people doing the work. Here’s how this organisation wired all three together.

The results

The dashboards changed. But what changed first was what happened in the room.

Within the first full planning cycle, something shifted that the strategy team hadn’t fully anticipated. Division leads arrived at sessions already knowing what was expected upstream — not because they’d been briefed differently, but because the platform had made the picture visible all week. Blockers came up earlier. A priority flagged amber on a Tuesday prompted a call before Friday, not a post-mortem three months later.

By the end of the first year, check-in completion had climbed past the 80% mark — the Profit.co platform benchmark for organisations using automated nudges — and held there through three consecutive quarters. That’s the part most rollouts miss. Getting adoption in the first quarter is easy. Keeping it through quarter three is the real test.

It didn’t land perfectly everywhere. Some divisions took two cycles to build a real check-in habit. A few teams needed the nudge format adjusted. But the floor rose — and the floor was where most of the misalignment had been living.