One strategy, translated into five business units. It arrived looking different every time.

A decade of acquisitions had given this group real engineering depth — and five different ways of writing down what mattered this quarter. Corporate strategy went out once a year. What came back from the plants rarely looked like the same document twice.

Story in 3 sentences

A European industrial group, built through acquisition, had five business units each running its own planning habits — one still worked from spreadsheets, another from a goal-tracking tool nobody else in the company could see into. Corporate priorities went out once a year and got reinterpreted five different ways before reaching a single shop floor.

They adopted Profit.co’s OKRs module — and for the first time, all five units set goals inside one shared cascade, visible to each other, tied back to the same handful of company objectives. The translation problem didn’t get solved by writing better memos. It got solved by removing the need to translate at all.

This story will resonate if…

Your company grew through acquisition, and every acquired unit kept its own way of setting and tracking goals
The same corporate priority gets reinterpreted differently depending on which plant or business unit you ask
Leadership sets a clear annual strategy, and by the time it reaches a site or plant level, nobody agrees what it actually means for their team
You’ve discovered — later than you’d like — that two business units were pursuing the same capital investment independently

The challenge

Growth through acquisition built real engineering strength. It also built five different languages for saying what mattered.

A decade of acquisitions had turned this group into a genuine engineering powerhouse — precision tooling, automation, and manufacturing capability spread across sites in half a dozen countries. Each acquisition brought expertise. Each one also brought its own way of deciding what mattered this quarter, and none of those ways had ever been reconciled into something the whole group could actually read.

One business unit ran its planning off a shared spreadsheet that only its own regional leadership ever opened. Another had adopted a goal-tracking tool years before the acquisition and never migrated off it, so its priorities lived in a system corporate leadership had no visibility into at all. A third ran quarterly planning as a verbal exercise — decided in a room, written up loosely afterward, rarely referenced again until the next quarter’s meeting.

Corporate strategy went out once a year, the same document to every unit. What came back looked like five different interpretations of the same idea, translated not just across language but across incompatible planning cultures. A site director in one country might read “expand automation capability” as a mandate for new capital investment. A plant manager elsewhere might read the same line as a directive to retrain existing staff. Neither was wrong. Neither knew the other had read it differently.

The clearest cost of the gap surfaced during an annual capital planning cycle: two business units, in two different countries, had each independently proposed investing in the same category of automation retrofit — arrived at separately, justified separately, and only caught because a finance reviewer happened to notice the similarity while comparing budget requests side by side.

A finance reviewer, not a strategy owner, was the one who caught two units proposing near-identical capital investments — purely by coincidence of reading both requests in the same sitting
Site-level plans referenced the annual strategy document in name, but tracing an actual quarterly goal back to a specific company priority required a phone call, not a lookup
When leadership wanted a current read on where the five units stood against the year’s priorities, someone had to manually contact each unit and reconcile answers that arrived in different formats, at different levels of detail, on different schedules

Nobody in this story was careless. Each unit was executing well against its own read of the strategy. The problem was that five good-faith interpretations of one document had quietly become five different strategies, and nothing in the system would have caught that until it cost real money.

“Every unit could tell you they were following the strategy. None of them could show me the same version of it. That’s not a communication problem you fix with a better memo — the memo was fine. The problem was that nobody had one place to actually check.”

VP of Group Strategy

European Industrial Engineering Group

The solution

The requirement wasn’t uniformity. It was one place all five units could actually be seen from.

The capital-planning near-miss became the case for change. It was concrete, it had a dollar figure nobody liked discussing, and every business unit leader had a version of the same story from their own quarter. The brief that came out of it was specific: whatever the group adopted needed to hold five different planning cultures inside one shared structure, without forcing any of them to abandon the parts of their process that actually worked for their site.

Profit.co became that shared structure. Every business unit sets its quarterly goals inside the same platform now, tied back to the same handful of company objectives, visible to every other unit in the group — not as a reporting requirement, but as the actual place the planning happens.

The rollout started with the two units from the capital-planning incident. Once their planners could see each other’s goals in the same view, the case for extending it to the remaining three units made itself; nobody needed convincing twice after watching the near-miss almost happen a second time in the pilot.

How the OKR program actually runs now

Once a year — a small number of company objectives, in one language everyone reads the same way

Group leadership agrees on a handful of company-wide objectives. Every business unit connects its own goals to these same objectives — not a locally translated version, the actual same list, visible in the same platform regardless of which country or site is looking at it.

Every quarter — each unit plans in its own rhythm, inside one shared view

Business units keep some autonomy in how they structure their own quarterly goals, but every goal sits in the same system, visible to every other unit. The capital-planning overlap that used to require a finance reviewer’s lucky catch now shows up as a flagged similarity before either proposal is finalized.

Any time — leadership can trace a company priority down to a specific site’s goal

What used to require a phone call to a site director now takes a few clicks. The connection between “expand automation capability” and what a specific plant is actually doing about it is visible, not asserted.

Weekly — async check-ins that don’t depend on which unit’s habits used to govern reporting

The unit that used to run planning as a verbal exercise now checks in the same way the unit that used a dedicated tool does. Nobody had to give up their working style to be visible in the same system.

What changed first wasn’t a dashboard. It was a habit: unit planners started checking what neighboring units had already proposed before finalizing their own capital requests.

That habit didn’t exist before, and nobody mandated it. It became normal because the information was finally sitting somewhere any planner could actually find it, instead of living in a format only their own unit used. A site director in one country described glancing at another country’s roadmap before a planning meeting as routine now — a sentence that would have made no sense to him two years earlier, when he didn’t know that roadmap existed.

Platform integration

Five business units found one thing they’d all actually use. That turned out to matter more than making them match.

The OKR module gave this group a shared language for the first time across units that had little operational overlap otherwise. Its real value showed up once those goals connected to the capital and engineering projects executing against them, and the people being evaluated on delivering them.

🎯 OKRs → Projects → Performance: how the connection works

OKRs power Projects

No capital or engineering project across any unit gets resourced without linking to a company or unit-level OKR. That single rule is what would have caught the duplicated automation-retrofit proposal during planning, not during a finance review months later.

Projects feed OKRs

Milestone progress from any unit’s project updates the key results it’s tied to automatically, regardless of which country the project is running in.

Both inform Performance

Review season pulls OKR completion and project contributions into the same screen, regardless of which business unit — or acquisition — an employee originally came from.

Company OKRs set → Unit projects linked to OKRs → Milestones update key results → OKR + project data feeds reviews → Review insights inform next cycle

The results

The five units still work differently. They just stopped being invisible to each other.

“I used to find out what another site was planning when someone forwarded me an email by accident. Now I check the platform before I finalize my own proposal. Nobody told me to start doing that. It just became the obviously smarter way to work once the information was actually there.”

Regional Site Director

European Industrial Engineering Group

A year into the rollout, the five business units still ran at different paces and kept different local habits around day-to-day execution. That was never the goal to change. What changed was whether anyone got blindsided by what another unit was already doing — the capital-planning near-miss that started this whole search hasn’t repeated, because unit leaders now catch that kind of overlap during planning, not during a budget review.

Adoption wasn’t instant everywhere. The unit that had run planning as a verbal exercise took the longest to build the habit of writing goals down consistently inside the new system — old habits don’t disappear just because a new platform exists. Leadership tracks that gap directly rather than treating it as solved; it’s expected to close as that unit completes more full cycles inside the shared cascade.

Before Profit.co

Five business units, five different planning habits — a spreadsheet, a disconnected tool, a verbal process, and two others in between. Corporate strategy got reinterpreted five different ways. Overlapping capital proposals surfaced by chance, not by design. Getting a current read on all five units meant phone calls and manual reconciliation.

After Profit.co

One shared cascade, five units, the same company objectives visible everywhere. Overlapping proposals get flagged during planning. A current read on any unit is a few clicks away, not a phone call. Every unit checks in on the same rhythm, regardless of what its old habit used to be.

Alignment

Five business units, one set of company objectives, no local reinterpretation

Every unit connects to the same handful of goals — not a translated or locally adapted version. The “which strategy are we actually following” confusion that used to vary by site has a single answer now.

Conflict prevention

The kind of capital-planning overlap that started this search hasn’t recurred

What used to require a finance reviewer’s lucky catch now shows up as a flagged similarity during planning, before either unit has committed budget.

Visibility

Leadership can trace any company priority down to a specific unit’s goal without a phone call

The cascade holds across all five units and every country they operate in — a structural property of the platform, not a reporting exercise someone has to chase.

Cultural integration

Five acquired planning cultures found one thing they’ll all actually use

Nobody was asked to give up the working style that suited their site. Different habits, same underlying structure — which mattered more than forcing every unit onto an identical process.

Habit change

Checking a neighboring unit’s goals before finalizing a proposal became routine

Nobody mandated it. It became normal because the information was finally somewhere any planner could actually find it before committing to a plan, not after.

Adoption reality check

Not every unit adopted the new rhythm at the same pace

The unit that previously ran planning as an informal, verbal process is still building the habit of writing goals down consistently. Leadership tracks that gap in the open — it’s expected to close over further full cycles inside the shared system.

Recognize any of this?

You don’t need five acquisitions for this to apply. If your strategy reads differently depending on which site or business unit you ask, it might be time to talk.

A European Industrial Engineering Group