100,000 people. 40+ divisions. One strategy that kept dissolving between layers of management — not because anyone was careless, but because there was no wire connecting the top to the work. Here’s what it took to build one.
Story in 3 sentences
They deployed Profit.co’s OKRs module and, for the first time, any employee could trace their work to the company’s top priorities in under a minute. Strategic pivots that used to take six weeks to land now take days. Quarterly reviews that used to cost three weeks of data assembly now run from a live dashboard in a morning.
This story will resonate if…
Not for you if your OKRs already cascade cleanly from company to individual and you’re looking for better reporting aesthetics. This is a structural story, not a cosmetic one.
Quick test — Write down your company’s top three priorities. Now write three things your team worked on most this quarter. Draw a line between them. If you’re guessing at the connections — or you can’t draw all three — keep reading.
Here’s the situation. This company makes hardware, software, and services, and sells through its own retail stores. That’s not one business — it’s four, all running simultaneously, all depending on each other. Add a global supply chain and partner ecosystems on top, and you start to understand the coordination problem. Now imagine keeping 100,000 people pointed in the same direction across all of that.
For a long time, they did what most large companies do. Strategy set in January. Division heads translated it. Senior managers filtered it further. By the time those priorities reached the engineers and product people doing the actual work, they’d passed through five or six layers of interpretation. Not wrong exactly. Just blurry — disconnected from the thing the CEO had said mattered.
Nobody was trying to lose the thread. It just kept slipping.
The moment that forced action wasn’t internal. Four enterprise customers attended an advisory board session in Q3. One CIO asked what should have been a simple question: “Can you show us where you actually are against your top objectives — right now, in the room?” The Head of Strategy looked at the VP of Operations. He looked back. There was no live view to show. She said she’d follow up with a summary. The CIO nodded politely. Everyone in the room understood what that meant.
Head of Strategy
Global Consumer Technology Company
When the team evaluated goal-management platforms, one question cut through everything else: can this handle an org that’s actually this deep? Most tools looked fine at the top — goals cascaded neatly from company level to division. Push further down and the thread frayed. Goals would technically be “linked” but the connection was too thin to trust. Nobody believed in it.
The Head of Finance pushed back on the whole exercise. His position: “Platforms don’t create alignment — leaders do. If the strategy isn’t landing, that’s a communication problem, not a software problem.” He was half right. But leadership clarity without any way to track whether it reached the front line is just optimism with a slide deck attached. The question wasn’t whether leaders were communicating — they were. It was whether anyone downstream could verify it, or act on a change the next day instead of the next quarter.
Profit.co held the cascade at every level. That was the deciding factor. The decisive moment in the demo: the Head of Strategy asked the consultant to show what happened if a team tried to set a quarterly objective without anchoring it to a company priority. He clicked through. The platform didn’t let them save it without picking a parent. “Not a reminder. A requirement. That’s what we’ve been missing.” They signed within the week.
Senior leadership agrees on five to seven company-wide objectives. Not ten. Not twelve. Five to seven. These are the things that, if achieved, make the year worth calling a success. Everything else connects back to these — and the platform won’t let a goal exist without that connection.
Each division sets quarterly OKRs anchored to one of the company objectives and can see — right there in the platform — what neighbouring divisions are working on. Cross-team conflicts that used to surface in post-mortems now show up in planning, when there’s still time to fix them.
Every engineer, designer, and ops lead sets goals that connect directly up the chain. Any employee can open Profit.co, find their goal, and follow it upward — through their team, department, division — all the way to the company’s top priorities. That connection, visible and real, changes how people think about their work.
Automated nudges, async updates — roughly six minutes per key result. The Monday picture is current before the director call starts. The Head of Strategy started getting time back in thirty-minute blocks. She used the first one to take a walk.
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 connect to the projects executing against them and the people being evaluated on delivering them. Once a project has to link to an OKR before it gets resourced, and once OKR completion feeds a performance review automatically, the three layers stop being separate systems and become one operating rhythm.
OKRs power Projects
Every project must link to at least one OKR before it gets resourced. If a project can’t answer “which company priority does this serve?” — that conversation happens in planning, not in a post-mortem six months later. OKRs become the filter that keeps the portfolio honest.
As projects hit milestones, their progress automatically updates the key results they’re tied to. Leadership doesn’t have to chase project status to understand OKR health. An OKR turning amber now comes with a visible reason: which project is behind, and by how much.
Both inform Performance
When review time comes, a manager opens the performance form and sees the employee’s OKR completion and project contributions — in the same screen, live, connected. The review isn’t a memory exercise anymore. It’s a conversation grounded in what the person actually worked on.
Company OKRs set → Projects linked to OKRs → Project milestones update key results → OKR + project data feeds performance reviews → Review insights inform next OKR cycle
VP of Operations
Global Consumer Technology Company
Team leads came into planning sessions 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. Check-in completion climbed from the high thirties to above 80% within two quarters — not because of a mandate, but because the Monday director meeting started consuming check-in data. Once silence had a visible cost, the habit formed. The measurable outcomes followed from that shift, not the other way around.
Strategy set in January, invisible at team level by Q3. Quarterly reviews took three weeks to assemble and arrived stale. Strategic pivots took six weeks to land. Cross-team conflicts surfaced in post-mortems. Two teams built the same feature without knowing.
Any employee traces their work to company priorities in under a minute. Reviews run from a live dashboard any morning. Pivots reach teams in roughly five days. Conflicts surface in planning sessions while there’s still time to fix them. Check-in completion above 80%.
Alignment
Dipped to ~65% in month two before climbing — the dip happened when managers realised silence was now visible. Once it climbed, it held. Four consecutive quarters above 80%, placing this deployment in the top quartile of similar-scale enterprise rollouts on Profit.co.
Speed
Measured across two real mid-year priority shifts. The CEO updated the company objective on a Friday. Division leads re-anchored by Tuesday. IC check-ins reflected the shift the following Monday.
Reporting
The three weeks didn’t disappear — they moved upstream into weekly check-ins. By the time the quarterly review arrived, the picture was already current. Nobody had to rebuild it.
Conflict prevention
When divisional objectives are visible to each other before work begins, the “we found out on a customer call” moment moves to the planning stage — where it can still be fixed.
Goal quality
The platform won’t save an unmeasurable key result. Within two months, goal language tightened across the whole company. No announcement needed. The constraint did the work.
Still working on it
The cascade is enforced. But writing a measurable KR — one that can be scored without debate — is a skill, and some parts of the org are still building it. Check-in completion dipped briefly in month three before it climbed. That’s typical. Coaching is the next investment. The Head of Strategy would say so directly.
Not a deck. Not a summary email assembled last week. A live view any leader can open and trust. If you can’t, this is a useful 30 minutes.
Welcome to Profit.co 👋
How can I help you today?