Rosetta Protocol
The Problem
Every Monday, your leadership team discusses the same problems.
​Decisions take too long. Cross-functional initiatives stall. The same issues resurface quarter after quarter, in slightly different language.
Every executive in the room has a reasonable explanation. And somehow, the organization doesn't get meaningfully easier to run.
Ask five leaders why, and you'll get five different, reasonable answers:
"Our structure creates too many handoffs."
"Decision rights are unclear — nobody knows who can actually say yes."
"People are afraid to make the wrong call, so they escalate everything."
"We keep losing good people to frustration."
Each captures something important. None, by itself, necessarily captures the whole.
And that's exactly the problem: your organization now has four separate initiatives — an org design project, a decision-rights workshop, a culture program, a retention task force — each attacking a different symptom, run by different teams, on different timelines, often working against each other without anyone noticing.
This is what fragmentation looks like from the inside. Not chaos – effort. Real effort, aimed in four directions at once.
Why This Keeps Happening
Each of the four leaders may be describing something important from where they sit.
Each is describing something about the company from where they sit. Finance sees cost. Operations sees process. HR sees people. Legal sees risk. Each is holding a different "representation" of what's happening – a picture built from their role, their data, their vantage point. Their differences do not, by themselves, make any one representation wrong. The organization needs all of them.
Over two decades of working inside large global organizations, we've repeatedly seen the same underlying pattern: real, legitimate tensions — speed versus control, local incentives versus enterprise performance, consistency versus adaptability — that no single function is wrong to hold, and no single initiative can resolve on its own.
The trouble starts when there's no way to see how these representations relate. Each team optimizes locally, with good judgment, and the results combine into something no one intended and no one can quite explain. Traditional tools are good at analyzing within one representation — better financial models, better process maps, better culture surveys — but few are built to show how different, equally valid representations of the same reality connect, conflict, or reinforce each other.
That's the gap this page is about.
What This Looks Like Up Close
The specifics differ by industry, but certain structural patterns recur often enough to be worth naming. Here's one.
In many large organizations, major decisions routinely move through multiple layers of approval before anyone acts — sometimes six or seven. It's the kind of pattern people rarely disagree exists.
Why it happens is where the agreement ends.
"We need that many checks — quality and consistency matter here."
"Managers aren't trusted to decide, so everything gets pushed up."
"It's regulatory. We don't have a choice."
"People have been burned before, so no one wants to be the one who acted alone."
Every one of these is plausible. None of them excludes the others. And critically — they're not competing facts to adjudicate. They're different standpoints on the same arrangement, and most organizations have no structured way to see how, or whether, they relate.
Take just two of them. "Managers aren't trusted to decide" describes how authority is currently arranged. "No one wants to be the one who acted alone" describes a pattern that keeps reproducing itself — a habit of escalating rather than deciding. Seen separately, these look like two initiatives: a trust problem and a behavior problem. Seen together, a different possibility opens up — the two may be reinforcing each other. Low trust pushes decisions upward; that rarely gives anyone the chance to demonstrate they can be trusted with them, which reinforces the original arrangement.
That's not a claim about anyone's psychology. It's a structural pattern — visible only once two representations are held in the same frame instead of treated as separate workstreams. Whether quality control, regulation, or mistrust is doing most of the work in a given organization is a question that requires looking, not assuming.
What's Still Missing
Suppose all four explanations above are reasonable.
How would you know whether they're describing four independent problems, one reinforcing pattern, or different parts of the same underlying structure?
How would you know which initiative should actually come first — or whether any of them should, on its own?
Most organizations don't lack expertise. Finance, Operations, HR, and Legal all understand their piece well. What's harder to find is a disciplined way to compare what they each already know before committing to which explanation to act on.
Rosetta
Rosetta was developed to answer exactly that question.
How do you determine whether different explanations describe different problems, different parts of the same problem, or the same problem viewed from different standpoints?
It does this by giving representations — Finance's, Operations', HR's, an outside expert's — a common structure, so they can be compared directly instead of argued over. Not forced into agreement. Made comparable.
It works through four simultaneous aspects of any situation — how it's arranged, what conditions surround it, what's influencing it, how it's changing — treated as one whole, not four separate categories. That structure is what made the possible relationship between authority and escalation visible — not as two isolated problems, but as aspects of a pattern that may be reinforcing itself.
Rosetta doesn't tell you which explanation is correct: it shows you how your explanations relate to each other — which is often the thing standing between you and a decision.
Coherence
There's a word for what's revealed when this works: "coherence".
Not agreement. Not uniformity. Finance, operations, and the frontline can — and should — keep seeing the business differently; that's what makes each of them useful. Coherence is something else: how well those different representations relate to each other as one working whole, for a given purpose and timeframe.
A startup and a nuclear plant need different kinds of coherence. A team can be highly coherent while the enterprise around it is fragmented. Coherence isn't a score to maximize — it's a pattern worth being able to see clearly, on its own terms, instead of only through its symptoms: turnover, missed deadlines, cost.
Rosetta is being developed to make that pattern visible — not to reduce your organization to a single number.
What Rosetta Is — and Isn't
Rosetta doesn't replace strategy, domain expertise, leadership judgment, or execution. It doesn't determine your values or resolve genuine conflicts of interest. It doesn't guarantee anyone acts on what they learn. And it isn't the right tool for every problem — some things are simply resource-constrained, or already well understood, or a matter of execution rather than understanding.
What it provides is a shared structure through which different representations of a complex situation can be related and evaluated — more clearly than they could be otherwise.
We say "is being developed to" deliberately throughout this page because Rosetta is an active protocol and constantly evolving.
If This Sounds Like Your Organization
If four teams in your company each hold part of the picture, and you still can't get consistent traction, that's usually not a sign anyone is failing. It may be a sign no one has a way to see how those different representations relate.
When intelligent people repeatedly reach different conclusions about the same organization, the first question usually isn't, "Who's right?" It's, "How do these explanations relate to each other?" That's the question Rosetta was developed to help answer.
We're working with organizations to apply Rosetta to exactly this kind of situation.
If your organization continues to face recurring challenges despite significant investments in strategy, culture, leadership development, or transformation, it may be time to look beyond the symptoms and examine the underlying conditions driving them.