This story will resonate if…

• Your January strategy feels like ancient history by Q3 – not because it changed, but because nobody can find it in the work
• A mid-year pivot takes six weeks to reach the teams who actually need to act on it
• Two divisions spent a whole quarter executing well, then sat in a post-mortem and realised their timelines had been quietly pulling against each other
• Before every quarterly review, someone spends three weeks chasing status updates – and the picture is still stale when it hits the room

The Challenge

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

The company makes enterprise security software. 3,500 people, 50+ markets, a partner ecosystem that runs most of the distribution. After absorbing two product lines and roughly 600 engineers through acquisition, the operating model was carrying two parallel goal-setting cultures – one from before the deal, one from after – and they’d never quite aligned.

Leadership set priorities in January. Division heads translated them. Managers filtered them 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.

The COO ran an internal audit. She found roughly twenty percent of senior engineering capacity tied to a thematic thesis the IC had quietly retired two quarters earlier. The retirement had never re-flowed downward. The affected teams were still executing against a strategy the company had already moved on from. Nobody had lied. The system just had no way of telling anyone.

When the company shifted a corporate priority – and in cybersecurity that happens every time a major CVE drops – the change reached the teams doing the actual work somewhere between four and six weeks later. Six weeks of people executing against a strategy that had already changed. And before every quarterly review, someone spent the better part of three weeks chasing status updates – assembling a picture that was stale before it hit the room.

• Two product teams independently built the same integration. Both finished. Both shipped. Nobody had known to check.
• A mid-year priority shift took six weeks to reach the engineers who needed to act on it – by which point they’d already burned two sprints on the old direction
• Post-acquisition alignment meant two OKR cadences, two goal formats, and two sets of quarterly conversations that never quite pointed the same way

The Solution

The question that cut through everything: can this handle an org where the strategy changes fast?

They evaluated twelve tools. Most got cut quickly – too HR-flavoured, built for smaller companies, or treating OKRs as a form-fill rather than a live cascade. Three made the shortlist. The question that separated Profit.co from the others wasn’t about features. It was about what happened when a priority changed at the top.

In two of the shortlisted tools, child OKRs were a soft link – a label, a tag, sometimes a colour badge. You could create a goal that “belonged to” a higher one without anything flowing between them. Update the parent, the children didn’t know. Pivot at the top, you had to chase every team to refile. That was exactly the problem they were trying to solve.

Profit.co treated cascade as the spine of the system. When a corporate priority changed, the platform surfaced every KR in conflict. Owners triaged in days, not weeks. The strategy ops lead’s vendor memo had one line the COO underlined: “This is the only tool where I can trust that if we change a priority on Monday, every team affected will know by Tuesday.”

They didn’t roll it out everywhere at once. Strategy ops picked one business unit first – the regional GTM team that had taken the worst of the previous quarter’s misalignment. One full planning cycle before extending anywhere. Three months later: equities-equivalent desks on board. By month six, distribution and operations had pulled themselves in after watching engineering and asking for what they were getting.

Three weeks into the rollout, check-in adoption on the first desk stalled at 30%. The COO sat with the question of calling it for a weekend. What kept her in wasn’t faith – it was that going back to the spreadsheet she just couldn’t do. The following Friday, adoption was at 58%. They learned: every function has its own first-three-week trough. The teams that push through see it lift. The one team that didn’t, didn’t.

The channel-partner rollout failed the first time. The weekly check-in rhythm didn’t fit how regional partner teams operated – they ran on monthly territory calls. Adoption sat at 12% for six weeks. Strategy ops scrapped it, redesigned the cadence around the existing monthly call, tried again. The second attempt worked. The lesson: the platform’s flexibility saved them, but only because they admitted the first design was wrong.

How the OKR programme actually runs

Platform integration

The OKR module wasn’t the end of the work — it was the foundation. Once the cascade was live and trusted, the firm connected it to project intake and to the performance review cycle. The result: a single line of sight from company priority to project to individual contribution, all in one system.

The Results

Eighteen months in. Two things landed that nobody had planned for. Quarterly reviews got shorter – down from 90 minutes of narration to about 40, with half the time now spent on what wasn’t tracking rather than what was. And the CFO’s forecast bands tightened, because weekly KR confidence scores were feeding in instead of quarterly ones. Nobody had this on the original project scope.

The bigger shift was cultural, not operational. Directors stopped arriving at planning sessions to receive information. They arrived having already done the cascade work, because the platform had done it for them. The question stopped being “what is everyone working on?” and started being “what should we change?”