Skip to main content
The Hard Parts.dev
FM-33 leadership FM Failure Modes
Severity high Freq common

Weak Governance Structures

Governance exists as meetings, forums, or approval paths, but authority, accountability, and escalation are too weak to change outcomes.

Severity
high
Frequency
common
Lifecycle
planning · build · operate
Recovery
hard
Confidence
high
At a glanceFM-33
Also known as

ceremonial governanceauthority fogdecision governance gap

First noticed by

engineering managerstaff engineerprogram lead

Mistaken for
inclusive decision-making
Often mistaken as
healthy stakeholder alignment

Why it looks healthy

Concrete external tells that make the pattern read as responsible behavior.

  • The right people appear to be in the room
  • Agendas, notes, and approval steps exist
  • Decisions are discussed in structured forums
  • No single person appears to dominate

Definition

What it is

Blast radius decision quality delivery flow team accountability risk management

A governance structure that consumes attention but cannot make clear decisions, assign ownership, price trade-offs, or resolve conflict.

How it unfolds

The arc of the pattern

  1. Starts

    A team needs shared oversight, so it creates a steering group, architecture council, approval board, or operating forum.

  2. Feels reasonable because

    The problem involves multiple teams, and a shared forum feels fairer than unilateral decision-making.

  3. Escalates

    The forum discusses issues repeatedly without naming a decision owner, a risk owner, or a forced trade-off. People leave with different interpretations.

  4. Ends

    Teams route around governance, decisions soften into advice, and unresolved conflicts reappear as delivery misses or architectural drift.

Recognition

Warning signs by stage

Observable signals as the pattern progresses.

EARLY

Early

  • Nobody can name who owns a key decision.
  • Meeting notes record discussion but not decision rights.
  • Escalation paths depend on personal relationships.

MID

Mid

  • The same decision returns to the same forum several times.
  • Proposals get softer after review instead of clearer.
  • Teams comply with process while privately ignoring the outcome.

LATE

Late

  • Governance is feared or bypassed but not respected.
  • Risks are acknowledged without being assigned.
  • Leadership cannot explain which controls changed actual outcomes.

Root causes

Why it happens

  • Organizations confuse representation with authority
  • Leaders avoid naming decision rights because it creates conflict
  • Forums are created faster than operating principles
  • Accountability is social but not observable
  • Governance artifacts substitute for governance choices

Response

What to do

Immediate triage first, then structural fixes.

First move

Pick one recurring decision and write down who decides, who advises, who is consulted, and who is accountable for consequences.

Hard trade-off

Accept visible disagreement instead of preserving the appearance of alignment.

Recovery trap

Creating a higher-level committee that inherits the same unclear authority.

Immediate actions

  • Name the decision owner for the next disputed decision
  • Write down what the forum can decide, advise, block, and escalate
  • Separate risk acceptance from general discussion

Structural fixes

  • Align authority with accountability
  • Create clear escalation rules for unresolved decisions
  • Retire governance steps that do not change decisions
  • Review governance outcomes, not governance attendance

What not to do

  • Do not add another forum to compensate for unclear authority
  • Do not use consensus language when a DRI decision is needed
  • Do not call governance successful because artifacts are complete

AI impact

How AI distorts this pattern

Where AI-assisted workflows accelerate, hide, or help with this failure mode.

AI can help with

  • AI can summarize decision histories, extract unresolved questions, and compare governance artifacts against actual decision outcomes.

AI can make worse by

  • AI can produce polished decision logs that make unclear ownership look settled.
  • AI can compress dissent into neutral summaries that hide unresolved trade-offs.

Relationships

Connected patterns

Causal flows inside Failure Modes, and related entries across the site.

Easy to confuse with

Nearby patterns and how this one differs.

  • Consensus trap is the behavior of seeking broad agreement. Weak governance structures are the missing decision rights that let the trap persist.

  • Stakeholder capture gives too much power to one group. Weak governance gives too little usable power to anyone.

  • Ticket theater makes process look like delivery. Weak governance makes governance look like control.

Heard in the wild

What it sounds like

The phrase that signals the pattern is about to start, and who tends to say it.

Heard in the wild

We need everyone aligned before we move.

Said bysenior stakeholder or committee chair

Notes from practice

What experienced people notice

Annotations from engineers who have worked this pattern before.

Best momentWhen intervention actually changes the trajectory.
When a forum is created or when a recurring decision keeps returning unresolved
Counter moveThe specific action that breaks the pattern.
Name what decision is being made and who is allowed to make it after consultation.
False positiveWhen this pattern is actually the correct call.
Some decisions need broad consultation; the failure mode is consultation without decision rights.