L1 of 4 · How the organization is structured and governed
The Unambiguous Organization Manifesto
Written by Katrien Meijdam
We are uncovering better ways of building and operating organizations
in a world where execution is accelerated by AI,
but outcomes are still constrained by ambiguity.
Most organizational dysfunction is not caused by a lack of effort.
It is caused by unclear ownership, vague decision rights, hidden assumptions, unmanaged tensions, and systems that force people to compensate for ambiguity instead of resolving it.
An unambiguous organization is not rigid.
It is legible.
People know how work moves, where decisions live, who owns what, how uncertainty is handled, and how the organization changes.
Values
Values
While there is value in the items on the right, we value the items on the left more.
Explicit ownershipoverimplied responsibility
Work scales when people know what they own, what they influence, and what they do not own.
Ownership should not depend on job titles, tenure, personality, or who happened to be in the meeting.
A responsibility without an owner becomes organizational fog.
Clear mandateoverdistributed authority
Decisions move when it is clear where they can be made.
A mandate defines the scope within which a person, role, or team can act without asking for permission.
Authority should be explicit enough to create movement, not so vague that every decision becomes political.
Defined rolesoverinformal expectations
A role is not merely a person’s job title.
A role is a contract with the system.
It defines purpose, accountabilities, domains, decision rights, boundaries, and interfaces with other roles.
When roles are vague, people compensate with meetings, assumptions, heroics, resentment, or control.
Decision artifactsovermeeting-driven alignment
Alignment does not come from shared attendance.
It comes from shared understanding.
A decision is only real when it leaves behind context, reasoning, assumptions, constraints, consequences, ownership, and review triggers.
Without an artifact, a decision is only a conversation people remember differently.
Visible ambiguityoverhidden uncertainty
Ambiguity is not a failure.
Hidden ambiguity is.
What is unclear should be named, routed, owned, and resolved deliberately.
When ambiguity remains implicit, it is resolved by guessing, politics, seniority, personality, or implementation.
Adaptive governanceoverstatic process
A process that cannot change becomes bureaucracy.
A process that changes invisibly becomes chaos.
Governance should make change explicit, safe, and lightweight.
Roles, mandates, operating rhythms, and decision rules should evolve when reality changes.
Principles
12 principles behind the values
- 01
Ambiguity is the hidden tax on organizational performance
Ambiguity consumes energy without appearing on a roadmap.
It shows up as rework, duplicated effort, political behavior, decision paralysis, unclear accountability, fragmented systems, and quiet disengagement.
The cost is rarely visible in one place.
That is why it scales so easily.
- 02
AI amplifies ambiguity faster than it resolves it
AI makes it cheaper to produce plans, documents, prototypes, tickets, code, analysis, and decisions.
But speed does not create clarity.
If assumptions, ownership, requirements, constraints, and decision rights are unclear, AI will accelerate plausible confusion.
AI does not remove the need for organizational clarity.
It raises the cost of lacking it.
- 03
Every organization has an implicit constitution
Every organization has rules for how work really happens.
Who decides.
Who can block.
Who must be consulted.
Who absorbs uncertainty.
Which meetings matter.
Which artifacts are trusted.
Which conflicts are avoided.
Which exceptions are tolerated.If this constitution is not explicit, people learn it through politics, frustration, and survival.
Unambiguous organizations make the operating system visible.
- 04
Ownership must be explicit
Every meaningful outcome, process, decision, artifact, and recurring responsibility should have an owner.
Shared work is healthy.
Shared ownership of everything is not.
If everyone owns something, often nobody truly does.
Ownership should answer:
- who is responsible for the outcome
- who can make decisions
- who must be consulted
- who is affected
- when escalation is required
- 05
Mandate must match responsibility
Responsibility without authority creates frustration.
Authority without responsibility creates risk.
A clear mandate defines where a role or team can resolve ambiguity without waiting for permission.
Escalation should happen when ambiguity crosses boundaries, not when people lack confidence.
- 06
Roles are structural, not personal
Roles should describe what the organization needs, not merely what a person currently does.
People may hold multiple roles.
Roles may change as the system changes.
A healthy organization can discuss role clarity without turning every conversation into a personal judgment.
This makes change less political and accountability more precise.
- 07
Decisions must leave a trace
A decision should be recorded in a way that future people, teams, and AI systems can understand.
The artifact should clarify:
- what was decided
- why it was decided
- what alternatives were rejected
- what assumptions were made
- what constraints apply
- who owns the decision
- when it should be revisited
Alignment decays unless it is externalized.
Memory is not an operating model.
Artifacts are.
- 08
Ambiguity should be routed, not absorbed
People should not be rewarded for silently absorbing unclear ownership, contradictory priorities, or vague expectations.
Unclear work should be routed to the place where it can be resolved.
If ambiguity sits inside a person for too long, it becomes stress.
If ambiguity sits inside a team for too long, it becomes dysfunction.
If ambiguity sits inside an organization for too long, it becomes culture.
- 09
Structure should create flow, not permission-seeking
The purpose of structure is not control.
The purpose of structure is flow.
Roles, mandates, governance, rituals, and artifacts should help people act with confidence.
If structure makes everyone wait for permission, it has failed.
Good structure reduces dependency.
Bad structure institutionalizes it.
- 10
Accountability emerges from clarity
People can only be meaningfully accountable when ownership is clear, expectations are explicit, authority matches responsibility, constraints are known, feedback loops exist, and decisions are traceable.
Without clarity, accountability becomes blame.
With clarity, accountability becomes a normal part of how the system learns and improves.
- 11
Governance is how the organization changes itself
Governance should answer:
- who can change a role
- who can change a process
- who can change a decision rule
- who can create or remove a mandate
- who must be consulted
- what evidence is required
- how the change is recorded
- when it should be reviewed
Governance is not bureaucracy.
Good governance makes adaptation safe.
- 12
Debug the system before blaming the person
When something is not working, inspect the organization before assigning individual blame.
Are roles clear?
Are mandates explicit?
Are priorities coherent?
Are decision rights understood?
Are incentives aligned?
Are dependencies visible?
Are interfaces between teams working?
Are people operating with enough context?Individual accountability matters.
But it should come after the system has been inspected.
This is not softness.
It is precision.
Closing
The future belongs to organizations that can move quickly without becoming incoherent.
AI will make execution faster.
It will make artifacts easier to produce.
It will make prototypes cheaper.
It will make coordination look deceptively simple.
But the hard work remains human:
to clarify ownership,
to define mandate,
to make decisions visible,
to govern change,
to route ambiguity,
to design structure,
and to remain accountable for consequences.
The unambiguous organization is not a machine.
It is a legible human system.
It knows how work moves.
It knows where decisions live.
It knows who owns what.
It knows how uncertainty is handled.
It knows how the system changes.
In an AI-accelerated world, clarity is not overhead.
Clarity is infrastructure.
Clarity is infrastructure.