Four manifestos · One stack

AI makes execution cheap. It does not make it clear.

These manifestos describe how to stay unambiguous at every layer, from how an organization governs itself to how its software feels in someone's hands. Each one is short enough to read in one sitting and specific enough to argue with.

The stack, top to bottom

  1. L1OrganizationHow the organization is structured and governed
  2. L2TeamHow people work together inside that structure
  3. L3Systems-FirstHow the software those teams build is designed
  4. L4Experience-FirstHow that software feels to everyone it touches

What we value

Every manifesto makes a trade. We say out loud what we choose.

There is value in the items on the right. We value the items on the left more.

L1 · Organization
  • Explicit ownershipoverimplied responsibility

  • Clear mandateoverdistributed authority

  • Defined rolesoverinformal expectations

  • Decision artifactsovermeeting-driven alignment

  • Visible ambiguityoverhidden uncertainty

  • Adaptive governanceoverstatic process

L2 · Team
  • Vulnerable trustoverprofessional theater

  • Productive conflictoverartificial harmony

  • Clear commitmentoverpassive agreement

  • Peer accountabilityovermanagerial policing

  • Collective outcomesoverindividual optimization

  • Captured workoverremembered work

L3 · Systems-First
  • SystemsoverSolutions

  • ClarityoverSpeed

  • StandardsoverCustom Plumbing

  • Human AccountabilityoverAlgorithmic Output

L4 · Experience-First
  • ExperiencesoverFeatures

  • Customer ControloverProduct Control

  • ClarityoverCleverness

  • End‑to‑End JourneysoverIsolated Interfaces

Writing

Notes from putting it into practice

All writing

Research · Open invitation

How does your team stay on the same page? We'd like to hear about it.

Talk with us

Want these principles working inside your organization, not just on the wall?

Visit unambiguous.build