We need to Recognise Where the Clear Lines Stop
Inside your own walls, accountability is a known shape. A name against a target, a reporting line, a review that eventually catches what went wrong. It isn’t always comfortable, but it is clear: you know, more or less, where it sits.
Accountability at the Edge is different : The Design Principles for Ecosystems Beyond Hierarchy need to be clarified and explained
Something different happens at the edge. A shared commitment with an external partner starts to slip. A joint decision needs making, and no one is quite sure whose call it actually is. A disagreement surfaces between two organizations that both have a stake in the outcome, yet neither has authority over the other.
The shape that worked so cleanly inside your own walls simply doesn’t reach. You can’t put a name against it the old way, nor can you escalate it to someone who can just decide. The line runs out exactly where you need it most.
What’s needed at the edge isn’t a longer line reaching further out. It is a different understanding of what accountability actually looks like once it has to be shared rather than assigned.
The instinct, understandably, is to read this as a gap—a failure of the old structure to extend far enough. But what actually breaks down at that edge isn’t accountability itself. It is the assumption that accountability has to look like clear lines and a single name at all.
Something else becomes possible in that messier space if you let it. Without a fixed hierarchy to lean on, the people actually doing the work have to build shared understanding instead of relying on an org chart to settle it for them.
Shared understanding, built rather than assumed, runs deeper than the version handed down by a reporting line. Decisions made this way carry a different kind of ownership, because no one was simply told to carry them. There is more friction, certainly—but there is also more learning in that friction than in a decision that was simply issued and complied with.
The Internal Echo: Why “No One Is Accountable for the Whole”
This edge dynamic isn’t just an external problem; it creates a quiet failure within our internal boards and decision rooms.
There is a particular kind of agreement that costs nothing to reach and changes nothing once it’s reached. Everyone in the room agrees a shift or partnership is needed. No one disagrees, no one argues the case against it. And afterward, nothing moves—not because anyone refused, but because agreeing was never the same thing as owning it.
Watch how the refusal actually happens: someone asks the real question—Are we prepared to fund this before the return is proven, to hold less control in exchange for more reach?—and what comes back isn’t “No”. It’s: “It’s not in this year’s budget.”
That sentence sounds like a fact about the calendar. Usually, it’s a decision, dressed carefully enough that no one has to be the one who made it.
Then the question moves. The main board passes it to the divisional board. The divisional board passes it to the business unit that would actually have to change. Each level assumes the one below will be the one to finally settle it. No one says no along the way. The question simply keeps traveling until it reaches somewhere too small to hold it, and stops there—unanswered, unrecorded, belonging to no one in particular.
That is what “no one is accountable for the whole” actually looks like from the inside. Not an empty chair where responsibility should sit, but a question that was handed along carefully enough that it never had to land.
Everyone in that chain is still fully accountable—for their existing numbers, their existing targets, the business as it already runs. Nothing in the structure is yet accountable for what is trying to happen at the ecosystem edge, because nothing has ever fed that.
The Structural Anchor: Deciding What You’ll Never Delegate
When leaders realize questions are traveling from room to room without landing, the common reaction is to over-correct in one of two directions.
- Centralized Overreach: Holding everything centrally on the reasoning that accountability only counts if someone senior can personally answer for it. In practice, this slows every decision down to what one office can review, or leads to approving things that haven’t really been examined. Accountability isn’t distributed; it’s just moved upstairs and left to quietly thin out.
- Total Delegation: Handing almost everything off on the reasoning that whoever is closest to the work should own the decision. Without anything held firmly in common, each unit becomes accountable only to its own local definition of success. Nothing holds the whole together.
The fix isn’t a new org chart or a bigger governance document. It is a much smaller, more specific act: deciding, in advance, exactly what you will never hand off—and meaning it about everything else.
+———————————————————————————–+
| THE NON-DELEGABLE CORE ARCHITECTURE |
+———————————————————————————–+
| THE NON-NEGOTIABLE CORE (Short List) | DELEGATED REAL AUTHORITY |
| * Held centrally, never flexes [7] | * Granted to operational teams [7] |
| * Systemic ethics & trust boundaries [7] | * Adaptation, execution, speed [7] |
| * Must have explicit rationale [7] | * Real authority, not reporting [7] |
+———————————————————————————–+
Name a short list of things that never flex, and delegate real authority over everything that isn’t on it. Not a long list—a short one. The handful of things that, if they broke, would break trust across the whole ecosystem regardless of who was operating where. Held centrally, genuinely non-negotiable, not up for local reinterpretation.
Before anything goes on that list, someone must state precisely why it’s there and what it protects. “We’ve always controlled this” is not a reason. If no one can give a better one, it doesn’t belong on the list.
The Operating Verbs: Accountability That Moves
With the non-negotiable core anchored, accountability that spans across boundaries needs a different set of verbs entirely. It cannot be static—holding still and waiting for someone to check.
- It has to PUSH: Enabling movement and initiative rather than waiting for permission across organizational boundaries.
- It has to CONVENE: Bringing the right partners into a decision rather than routing it up a single internal chain.
- It has to ADAPT: Recognizing that conditions and partners on the other side of that boundary are not yours to fix in place.
┌────────────────────────────────────────────────────────────────────────┐
│ THE 4 OPERATIONAL REQUIREMENTS OF CROSS-BOUNDARY FLOW │
├────────────────────────────────────────────────────────────────────────┤
│ 1. TRANSPARENCY AS AN OPERATING REQUIREMENT │
│ What’s known must actually be shared across the boundary [6]. │
│ │
│ 2. CONCRETE INCENTIVE ALIGNMENT │
│ Staying accountable to the shared outcome must benefit both [6]. │
│ │
│ 3. CO-CREATED DECISION FRAMEWORKS │
│ Who decides and on what basis is worked out together [6]. │
│ │
│ 4. PROACTIVE CONFLICT RESOLUTION │
│ Building the path for disagreement before it’s needed [6]. │
└─────────────────────────────────────────────────────────
Making this working design real relies on four core elements:
- Transparency as an Operating Requirement: Trust stops being a value statement in a deck and becomes an operational necessity. What is known must actually be shared across the boundary. Without that, “shared accountability” collapses back into each side privately guarding its own version of events.
- Concrete Incentive Alignment: Does staying accountable to the shared outcome actually benefit the people carrying it on both sides, or does the structure quietly reward whoever protects their own position first? Misaligned incentives don’t announce themselves—they just make the right behavior slightly more costly than the easy one until the pattern sets.
- Co-Created Decision Frameworks: Decision-making frameworks cannot be a single-party design copied onto a partnership. Who actually decides, and on what basis, has to be worked out with the other side rather than handed to them—otherwise “accountability” on their end just means compliance with terms they never set.
- Proactive Conflict Resolution: This is the clearest test of reality. Reactive resolution waits for a dispute to escalate, by which point trust is already a casualty. Proactive conflict resolution builds the path for disagreement before it’s needed: a known way to raise a concern and have it heard well before reaching a formal dispute.
Conclusion: A Deliberate Design Choice
Put together, this is what lets accountability move with an ecosystem instead of stopping at its own edge—not a single owner holding the line, but a working design that keeps trust, incentives, decisions, and disagreement actively tended across a boundary no hierarchy was ever built to reach.
That’s a design choice, made deliberately, not something that emerges on its own from good intentions.
Take a look at the Ecosystem Architecture offered and its structural approaches as well as the Operational Design conditions, these can shape your thinking differently on how to approach Ecosystems.
“If you’re ready to explore your ecosystem needs , let’s talk.”,