This story will resonate if…

• Your January strategy feels like ancient history by Q3 — and you can’t quite say where it went
• Your quarterly business reviews keep surfacing surprises that should have been caught months earlier
• Your teams hit their own targets — but the company keeps missing what actually matters
• Pulling together a leadership update takes days of chasing people, not minutes of checking a screen

The challenge

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

The strategy meeting was the part everyone loved. Three days off-site, walls covered in butcher paper, the CEO pacing. By the end they’d land on the year’s bets — four of them, usually. Big ones. Then everyone flew home.

What happened next was the problem. The VP team took those four bets and translated them into department plans. Directors translated department plans into team plans. Managers translated team plans into individual goals. By the time the strategy reached the person building the wholesale forecast or running the influencer programme, it had passed through four rewrites — and it didn’t sound much like the thing the CEO had been pacing about.

The Chief of Staff used to call it “the telephone game.” She wasn’t joking. She kept two examples taped to her monitor. The first was a board-approved priority: “Win in performance footwear.” The second was a Q3 goal from a marketing analyst three levels down: “Run six paid social campaigns by end of quarter.” Both had been approved up the chain. Neither mentioned the other.

• Quarterly business reviews were a parade of green slides that added up to a yellow business — every team’s individual status was fine, the company’s wasn’t
• A strategic shift agreed at the leadership level took six weeks or more to reach the people who needed to act on it — by which point some had already moved in the wrong direction
• The strategy team spent days before every review assembling a picture from Word docs, spreadsheets, and two separate project tools — and it was already stale before it hit the room
• Nobody was trying to lose the thread. It just kept slipping — quietly, consistently, one translation at a time

They tried the usual fixes. All-hands updates. Shared documents everyone was supposed to read. A series of tools, each solving one piece. 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

Six platforms evaluated. One showed you where the chain actually broke.

It was a Thursday in the second week of the new fiscal year. The new COO had been in seat for three months and asked for one simple thing — show me, on one page, how every team is contributing to the four annual priorities.

The strategy office spent six business days trying to assemble it. Goals lived in Word. OKRs lived in a spreadsheet. Departmental plans lived in a project tool the digital team had bought. The quarterly tracker lived in a different tool the merchandising team had bought. By the time the page came together, three teams had already updated their goals and the version was stale. The COO looked at it and asked the obvious question: “How do you make decisions like this?”

The honest answer: they didn’t. They made decisions and hoped things lined up. The strategy team spent the rest of that afternoon looking at platforms. They evaluated six. Two were large HR suites that had bundled OKRs as a feature. Two were OKR-first startups — beautiful interfaces, not much depth. One was a project tool that had added goals as an afterthought. The last was Profit.co.

What separated Profit.co wasn’t the features list. Most shortlisted products had check-ins, dashboards, alignment views. They all demo’d well. The difference showed up in the cascade — what actually happens when you have four company OKRs, seven function OKRs underneath each, and thirty-odd team OKRs below those, and you need to know in real time whether the bottom layer is still pointing at the top. Most tools showed the hierarchy. Profit.co showed the breakage. That was the decision.

The Customer Success team didn’t try to sell them a transformation. They asked what the company wanted to do differently in the next ninety days — and built the rollout around that. The strategy lead said afterward it was the first vendor call she’d been on in two years where the vendor talked her out of something.

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 goal-setting alone — 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 wired all three together.

The results

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

The COO got her one-page view about ten weeks in. She didn’t celebrate it. She just stopped asking for it — which, the strategy lead said, was the biggest compliment the platform could have got. Within the first month, two function leads had separately flagged that their team OKRs didn’t roll up to the company priorities. Profit.co didn’t fix that. It made it visible. Once visible, the function leads fixed it themselves — because nobody wants to be the team with an orphan branch.