L2 of 4 · How people work together inside that structure

The Unambiguous Team Operating Manifesto

Written by Katrien Meijdam

We are uncovering better ways for teams to work together
in organizations where speed is increasing,
but trust, clarity, and accountability still determine results.

A team is not made effective by shared calendars, status meetings, or good intentions.

A team becomes effective when people trust each other enough to be honest, disagree clearly, commit visibly, hold each other accountable, and focus on shared outcomes over personal comfort.

Values

Values

While there is value in the items on the right, we value the items on the left more.

  1. Vulnerable trustoverprofessional theater

    A team cannot become unambiguous if people are hiding mistakes, doubts, risks, or disagreement.

    Trust is not politeness.
    Trust is the confidence that honesty will be used to improve the work, not punish the person.

  2. Productive conflictoverartificial harmony

    Avoiding conflict does not preserve alignment.
    It preserves ambiguity.

    Healthy teams disagree early, directly, and respectfully so decisions become stronger before execution begins.

    Conflict is not the enemy of teamwork.
    Unspoken conflict is.

  3. Clear commitmentoverpassive agreement

    A team does not need everyone to get their preferred option.

    It does need everyone to understand what was decided, why it was decided, who owns what, and what happens next.

    Commitment requires clarity, not enthusiasm.

  4. Peer accountabilityovermanagerial policing

    Accountability should not depend entirely on a manager noticing what is slipping.

    Strong teams make expectations visible enough that team members can challenge each other directly when commitments, behaviors, or standards drift.

    Accountability is not blame.
    It is respect for the shared work.

  5. Collective outcomesoverindividual optimization

    A team fails when personal goals, functional silos, status, or local efficiency matter more than the result the team exists to produce.

    The team’s outcome is the scoreboard.

    Individual contribution matters most when it improves the collective result.

  6. Captured workoverremembered work

    A team should not rely on memory, personality, or hallway conversations to stay coherent.

    Decisions, next actions, risks, assumptions, tensions, dependencies, and unresolved questions should be captured where the team can see and act on them.

    If it matters, it must leave a trace.

Principles

15 principles behind the values

  1. 01

    Trust is the foundation of clarity

    Without trust, ambiguity goes underground.

    People hide confusion.
    They soften disagreement.
    They avoid asking for help.
    They protect themselves instead of improving the work.

    A team that cannot tell the truth cannot become clear.

  2. 02

    The team should make uncertainty speakable

    Uncertainty is normal.

    The danger is not that people are unsure.
    The danger is that they pretend not to be.

    A healthy team makes it safe and expected to say:

    • I do not understand this.
    • I disagree.
    • I think we are making an assumption.
    • I need help.
    • I made a mistake.
    • I see a risk.
    • I do not think we are committed.
  3. 03

    Conflict is a design tool

    Conflict is how teams expose assumptions, constraints, trade-offs, risks, and weak reasoning.

    The goal is not to win the argument.

    The goal is to improve the decision.

    Teams should make conflict specific, grounded, and connected to the work.

  4. 04

    Silence is not alignment

    A quiet room does not mean agreement.

    It may mean confusion, fatigue, fear, resignation, or lack of psychological safety.

    Before important decisions, teams should deliberately surface disagreement and uncertainty.

    Alignment must be tested, not assumed.

  5. 05

    Decisions must create commitment

    A decision is incomplete until the team knows:

    • what was decided
    • why it was decided
    • what options were rejected
    • who owns the outcome
    • what the next action is
    • what constraints apply
    • when the decision should be reviewed

    Without this, teams leave meetings with different versions of reality.

  6. 06

    Every commitment needs a next action

    A goal without a next action creates fog.

    A decision without a next action creates false closure.

    A next action should be concrete enough that someone can do it without needing to reinterpret the conversation.

  7. 07

    Work should be captured outside people’s heads

    Open loops drain attention.

    A team should maintain trusted places for:

    • decisions
    • actions
    • waiting-for items
    • risks
    • assumptions
    • tensions
    • blockers
    • open questions
    • experiments
    • team agreements

    Capture is not bureaucracy.
    It is how teams protect focus and continuity.

  8. 08

    Tensions should be processed, not stored

    A tension is a gap between current reality and desired reality.

    When teams do not process tensions, people carry them privately.
    Private tensions become frustration, cynicism, side conversations, or disengagement.

    A tension should become one of four things:

    • a next action
    • a decision
    • a change to a role, agreement, or process
    • an explicit decision to do nothing
  9. 09

    Accountability should happen close to the work

    The longer accountability waits, the more political it becomes.

    Strong teams address drift early:

    • missed commitments
    • unclear ownership
    • low-quality handoffs
    • recurring blockers
    • unhelpful behavior
    • decisions being reopened without cause

    Accountability is healthiest when it is direct, timely, and tied to shared standards.

  10. 10

    Team norms must be explicit

    Every team has norms.

    The only question is whether they are visible.

    Teams should explicitly define how they:

    • make decisions
    • escalate issues
    • disagree
    • document work
    • review commitments
    • use meetings
    • involve stakeholders
    • use AI
    • handle missed expectations

    Implicit norms create uneven power.
    Explicit norms create shared expectations.

  11. 11

    Meetings are for interaction, not memory

    Meetings should be used for work that benefits from live participation:

    • resolving ambiguity
    • making decisions
    • processing tensions
    • creating options
    • confronting trade-offs
    • repairing trust
    • committing to action

    Status and context should be externalized whenever possible.

    The meeting is not the memory.
    The artifact is.

  12. 12

    Participation must be designed

    Open discussion often rewards the fastest, loudest, most senior, or most confident voices.

    Good teams design participation deliberately.

    They use silent thinking, structured rounds, small-group work, visible options, and explicit convergence to get better signal from the whole team.

    The goal is not endless inclusion.

    The goal is better thinking and stronger commitment.

  13. 13

    Results are the team’s scoreboard

    A team is not successful because everyone was busy, helpful, or individually productive.

    A team is successful when it produces the outcome it exists to create.

    When individual priorities conflict with collective outcomes, the team must make the conflict visible and resolve it.

  14. 14

    AI should accelerate the team’s clarity, not replace it

    AI can summarize, draft, prototype, analyze, compare, and generate options.

    But AI should not become a hiding place for vague intent.

    Teams should use AI to make work more explicit:

    • clearer decisions
    • sharper assumptions
    • better artifacts
    • faster prototypes
    • stronger options
    • more visible risks

    Humans remain accountable for judgment, commitment, and consequences.

  15. 15

    Teams should debug themselves before blaming individuals

    When a team is not working, inspect the system before assigning blame.

    Are expectations clear?
    Are commitments visible?
    Are roles understood?
    Are decisions stable?
    Are tensions processed?
    Is conflict healthy?
    Is accountability direct?
    Are people optimizing for the team result?

    Individual accountability matters.

    But it should come after the team has inspected the conditions it created.

Closing

An unambiguous team is not a team without tension.

It is a team that knows how to turn tension into clarity.

It trusts enough to be honest.
It disagrees enough to think well.
It commits clearly enough to move.
It holds itself accountable enough to improve.
It cares about results enough to put the shared outcome above personal comfort.

The unambiguous team does not depend on heroic memory, vague alignment, or managerial rescue.

It makes work visible.
It makes decisions traceable.
It makes commitments concrete.
It makes uncertainty speakable.
It makes accountability normal.

In an AI-accelerated world, the best teams will not be the teams that generate the most output.

They will be the teams that create the most clarity, trust, and collective progress.

Turn tension into clarity.