A Global Consumer Technology Leader

This story will resonate if…

Your January strategy feels like ancient history by Q3 — not because it changed, but because nobody can find it anymore
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
You’ve sat in a post-mortem and thought: we should have caught this in planning — six weeks ago

The challenge

Their strategy wasn’t wrong. It just kept getting lost on the way down — and nobody had a system for noticing.

Here’s the situation. This company makes hardware, software, services, and sells it all through its own retail stores. That’s not one business — it’s four, all running at the same time, all depending on each other. Add a supply chain spanning continents and partner ecosystems on top of the platforms, and you start to get the picture. Now imagine keeping 100,000 people pointed in the same direction across all of that.

For a long time, they did what most companies do. Strategy set in January. Division heads translated it. Managers filtered it further. By the time those priorities reached the 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 said mattered. Nobody was trying to lose the thread. It just kept slipping.

Here’s what it looked like up close. One year, the company set a firm-wide objective around deepening its services business in emerging markets. A legitimate, well-reasoned priority. By the time it had passed through the cascade, it arrived at a regional operations team as: improve onboarding completion rates. Which was a fine goal. Which was already in their targets from the previous year. The team worked hard all quarter. They hit the number. Their manager told them they’d done well. And the company’s services business in that region didn’t move. Nobody connected the two. Nobody had a system for connecting the two.

The louder version of the same problem showed up in post-mortems.

Two product divisions spent an entire quarter building the same underlying capability — independently, without knowing. Both finished. Both shipped. Nobody had known to check until a roadmap review surfaced the duplication months after both teams had started. The rework took longer than either original build.
A mid-year strategic pivot — leadership had decided to accelerate investment in one product category and slow another — took six weeks to reach the business units with budget implications. For six weeks, teams were executing against a strategy that had already changed at the top.
Before every quarterly review, someone spent the better part of three weeks chasing status updates — assembling a picture that was already weeks out of date by the time it hit the conference room. Leaders were making present-tense decisions from past-tense data.

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.

been here three

“Setting the goals was never our problem. We’ve always been good at ambition. What worried us — what actually kept people up at night — was not knowing whether the goals we’d set in January were still the ones being worked toward in October.”

Head of Strategy

Global Consumer Technology Company

The solution

Most performance tools made the form prettier. They needed the form to do less.

The evaluation list had nine vendors. The traditional HRIS extensions came first: solid, predictable, deeply integrated, and almost all of them produced a fancier version of the form the company already hated. The pure-play performance tools were lighter, but most treated performance as a stand-alone module, disconnected from goals, disconnected from career, disconnected from how the company actually ran.

Profit.co held the cascade at every level. That was it. That was the decision.

The rollout wasn’t mapped out on a whiteboard. It grew to fit the shape of the organisation — which meant accepting that different divisions would move at different speeds, that some teams needed quarterly OKRs while others were on annual ones, and that the people who were never going to give up their spreadsheets still needed a way to connect their work to the picture everyone else was looking at.

Once a year — leadership agrees on the things that have to be true

Senior leadership agrees on five to seven company-wide objectives. Not ten. Not twelve. Five to seven — the ones that, if achieved, make the year worth calling a success. Everything else connects back to these. When something doesn’t connect back to one of them, that’s a signal worth paying attention to.

Every quarter — divisions set their own goals, in the context of everyone else’s

Each business unit sets its own quarterly OKRs and can see — right there in the platform — how their goals sit relative to the company’s priorities and what neighbouring divisions are working on. No more finding out in a post-mortem that two teams had been pulling against each other. The duplication is visible before it becomes expensive.

Every quarter — teams and individuals set goals that actually mean something

Every engineer, designer, and ops lead sets goals that trace 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. The regional operations team improving onboarding rates can see whether that goal actually connects to something the company cares about — before the quarter begins.

Weekly — async check-ins without anyone chasing anyone

Automated nudges, async updates, no synchronous status meetings required. The status picture is always current. Chiefs of staff stopped spending half their week asking “where does this stand?” — the answer is in the platform.

What surprised the team most wasn’t the technology. It was what changed in the conversations.

Within two planning cycles, the quarterly reviews looked different. Division leaders weren’t reading off prepared slides — the slides were already there, live, before anyone walked in. The meeting became what it was always supposed to be: a real conversation about what was tracking, what wasn’t, and where resources needed to shift. The kind of conversation leadership had always wanted to have and almost never had the context for.

One thing nobody had predicted: teams started talking to each other across divisions without being asked. Not because of a mandate — because they could see, in the platform, that another division was building toward the same priority. Product managers started picking up the phone before the duplication got expensive. Cross-functional coordination, which had been a slogan in town halls for years, finally meant something you could point to on a screen.

OKRs power the project portfolio

Every project in the portfolio 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.

Projects feed OKR progress automatically

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 — the platform does that work. An OKR marked “at risk” now comes with a visible reason: which project is behind, and by how much.

OKRs and projects together inform performance reviews

When review time comes, a manager opens the performance form and sees the employee’s OKR completion and their 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, and whether it moved the needle.

Review insights feed the next OKR cycle

Patterns in where teams over-delivered, where they fell short, and where goals quietly became irrelevant mid-year feed back into the next planning round. The system gets smarter over time — not because anyone adds a process, but because the data is already there.

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 connect to the projects executing against them and the people being evaluated on delivering them. Here’s how this organisation uses all three together.

🎯 OKRs → Projects → Performance: how the connection works

OKRs power Projects

Every project in the portfolio 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.

Projects feed OKRs

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 — the platform does that work. An OKR marked “at risk” now comes with a visible reason: which project is behind, and by how much.

OKBoth inform Performance

When review time comes, a manager opens the performance form and sees the employee’s OKR completion and their 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, and whether it moved the needle.

Company OKRs set → Projects linked to OKRs → Project milestones update key results → OKR + project data feeds performance reviews → Review insights inform next OKR cycle

The results

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

“Strategy reviews used to feel like archaeology. You’d come in with a reconstructed picture stitched together from emails and spreadsheets — and everyone knew it was already three weeks out of date. Now I walk in with a live picture. It’s a completely different conversation.”

VP of Operations

Global Consumer Technology Company

Six months in, meetings felt different. 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. The measurable outcomes followed from that cultural shift, not the other way around.

A senior director mentioned, around month seven, that she hadn’t sent a “what are we actually working on?” Slack message in a full quarter. She said it like she was surprised by it. She probably was — she’d been sending three or four of those a week for most of the previous year

Before Profit.co

Quarterly reviews needed three weeks to pull together. Strategic shifts took six weeks to land. Cross-team conflicts surfaced in post-mortems. Nobody had the full picture at the same time. Teams hit their own targets while the company missed what actually mattered.

After Profit.co

Reviews run from a live dashboard any morning. Pivots reach teams in days. Conflicts surface in planning sessions while there’s still time to fix them. Everyone’s looking at the same picture. The question “is this work actually moving the company forward?” finally has an answer someone can point to.

Alignment

“How does my work connect to what the company is doing?” — answered in 30 seconds

Any employee, any level, any time. The connection is real and visible — not something they have to take a manager’s word for. The regional team improving onboarding rates can see whether that goal traces to something the company actually cares about.

Speed

A strategic change that used to take six weeks to land now takes days

No manual translation chain. When priorities change, the cascade updates and every connected team sees it at the same time. The signal travels at the speed of the platform, not the speed of a forwarded email.

Reporting

The quarterly strategy review stopped being a three-week archaeology project

Leadership walks in with a live picture — not a reconstructed one. The data is current. The decisions that follow are better because they’re made from facts, not from a deck that was already stale when it was printed.

Conflict prevention

Problems that used to show up in post-mortems now show up in planning/h3>
When dependencies are visible before work begins, teams catch misalignments while they can still do something about them. The duplicated build that cost nine months of parallel effort? It shows up as an overlap in week two now.

Culture

The org stopped measuring what people did and started measuring what they achieved

When the whole company shares a language for what success looks like, the question shifts from “what did we ship?” to “did it matter?” That shift is slow. But it started here, with everyone looking at the same goals at the same time.

Integration win

OKR health is now real — because project progress updates it automatically

Key results don’t just get manually entered anymore. Project milestones flow into OKR progress automatically — closing the gap between planning and execution. An at-risk OKR now comes with a visible reason, not just a red status dot.