Principles Library / Visible Conditions

Visible Conditions

Making System Conditions Visible Enables Timely, Informed Decisions

Act

Showing all 7 practices. Answer the Diagnose questions and the most relevant come first.

Make the real work and risks visible

Make queues, dependencies, risks and uncertainty visible, and get bad news surfacing early.

Start by asking your team: What do we know now that leadership can't see, and where does reported status differ from what people experience?

Avoid · You’ll know it’s working when

Avoid

  • Flooding leaders with data instead of insight

You’ll know it’s working when

Risks known on the ground reach the people who can act, and teams raise problems before they escalate.

Design reporting that shows real conditions

Design reports to show real system conditions, and keep what people disclose apart from how they're evaluated.

Start by asking your team: What incentives discourage people from surfacing bad news?

Avoid · You’ll know it’s working when

Avoid

  • Using transparency as a tool for micromanagement
  • Expecting openness without psychological safety

You’ll know it’s working when

Status reports match what people actually see, and outcomes and reports move together.

Set traceability requirements before go-live

Before a system runs, decide what must be recorded, at what level of detail, and for how long.

Start by asking your team: What would a regulator be unable to answer if they reviewed our current decision records?

Avoid · You’ll know it’s working when

Avoid

  • Adding audit trails after a compliance failure instead of designing them in from the start
  • Treating traceability as a compliance checkbox instead of an operational need

You’ll know it’s working when

Reviews can name the decision behind a failure, and a failed agent pipeline can be replayed step by step.

Record the reasoning behind each decision

Design decision records that capture the inputs, the governing policy and the reasoning along with the output.

Start by asking your team: Who could reconstruct the reasoning behind the last few significant decisions this system made?

Avoid · You’ll know it’s working when

Avoid

  • Treating logs as traceability: logs record what happened, traceability records why

You’ll know it’s working when

Post-incident reviews name the decision that caused a failure, and accountability follows who decided.

Separate facts from assumptions

Label which signals are facts and which are interpretation or assumption, and make key inputs and trade-offs traceable.

Avoid · You’ll know it’s working when

Avoid

    You’ll know it’s working when

    Groups work from one shared view of the system, and reports mark which claims are assumptions.

    Make agent decisions observable and auditable

    In AI-augmented systems, make automated decisions, their inputs, actions, exceptions and outcomes observable and auditable.

    Start by asking your team: As execution speeds up, which signals and decision paths must never be filtered, delayed or left unrecorded?

    Avoid · You’ll know it’s working when

    Avoid

    • Believing agent systems are too complex to make traceable
    • Accepting opacity as unavoidable

    You’ll know it’s working when

    Leaders can see why an agent produced an output, and agent assumptions are open to inspection.

    Rehearse an incident before deployment

    Before deployment, simulate an incident and confirm the causal chain can be rebuilt without relying on anyone's memory.

    Start by asking your team: If something went wrong today, could you trace the decision that caused it to a specific point, input and governing policy?

    Avoid · You’ll know it’s working when

    Avoid

      You’ll know it’s working when

      After a simulated incident, the team traces the cause to a specific decision, input and policy.

      Overview

      Principle intent

      Make the conditions shaping system performance visible, and build the ability to trace decisions to their causes before a system operates, not after a failure.

      Read the full intent

      Decisions grounded in shared, traceable evidence produce better outcomes than decisions grounded in assumptions, filtered reporting, or records reconstructed from memory after a failure. Visibility should extend beyond progress and status to include workload, dependencies, risks, uncertainty, constraints, decision assumptions, quality signals, and emerging outcomes.

      When it holds: what it does for you

      Problems surface earlier

      Risks and bad news reach the people who can act while there are still options.

      Decisions rest on evidence

      Leaders decide from shared, traceable facts instead of filtered reports or assumptions.

      Incidents teach something

      When something fails, you can trace it to the decision that caused it and fix that.

      When it is ignored: from early signs to a lasting condition

      Early warning signs · Visible now, cheap to fix

      • Important risks are known locally but hidden from the people who could act.
      • Status reports stay positive while outcomes get worse.
      • Post-incident reviews say what happened but can't name the decision that caused it.

      What happens over time · Accumulates, costly to reverse

      • Problems surface late, options are already limited, and crisis mode is normal.
      • People stop trusting reported status and steer by their own local numbers.
      • Incident learning stays shallow and the same failures keep coming back.

      The condition it becomes

      Intent Drift · Secondary

      The team built exactly what was asked. It is no longer what is needed.

      How this principle feeds it

      confident leaders keep commitments running against assumptions that no longer match reality.

      Quality Fragility · Secondary

      Customers find defects before the team does.

      How this principle feeds it

      problems found late are found after they are cheap to fix.

      Strategic Volatility · Secondary

      Every quarter starts over. Nothing compounds.

      How this principle feeds it

      each late crisis forces a replan, so commitments are dropped before they finish.

      Local Optimization Bias · Secondary

      Every team hits its targets. The product still misses.

      How this principle feeds it

      without a trusted shared view, each group optimizes the numbers it can see, and end-to-end value fragments.

      Attribution Failure · Primary

      We know what happened. Nobody can explain why.

      How this principle feeds it

      outcomes are recorded but cannot be traced to the decisions that produced them.

      Oversight Erosion · Secondary

      The review process still runs. It stopped meaning anything.

      How this principle feeds it

      review continues while the volume and opacity of agent decisions outrun it.

      Implementation Drift · Secondary

      The agents are building. Nobody is sure it still matches the plan.

      How this principle feeds it

      untraced agent substitutions become the new baseline without anyone flagging the divergence.

      Where is your system on this path?

      Diagnose

      Diagnose

      AI signs are on by default. Use the AI switch to exclude them.

      1. Which of these early warning signs are you seeing?

      • Important risks are known locally but hidden from the people who could act.
      • Status reports stay positive while outcomes get worse.
      • Leaders hear about issues only after escalation or a crisis.
      • Teams hold back from raising problems early.
      • Post-incident reviews say what happened but can't name the decision that caused it.
      • After a failure, accountability follows proximity instead of decision authority.
      • Different groups work from very different views of the same system.
      • Dashboards track activity and status but not the assumptions behind the plan.
      • Leaders see what an agent produced but not which data, rule or model drove it. (AI)
      • Agent actions are accepted as final because tracing them to policy takes too long. (AI)
      • When an agent pipeline fails, nobody can rebuild the sequence of decisions. (AI)
      • Agent assumptions and rules sit in configurations leaders can't inspect. (AI)

      2. Over the last few months, have you noticed…

      For each consequence: Not seen / Sometimes / Persistently / Not sure.

      • Leaders make decisions with a confidence the facts don't support.
      • Problems surface late, options are already limited, and crisis mode is normal.
      • People stop trusting reported status and steer by their own local numbers.
      • Incident learning stays shallow and the same failures keep coming back.
      • Records fall short of traceability requirements, so audit and regulatory risk grows.
      • Automated decisions build up unseen risk faster than oversight can catch it. (AI)

      3. The condition it becomes

      Based on your answers, recognize at most two conditions: No / Partly / Yes, that is us.

      Intent Drift: The team built exactly what was asked. It is no longer what is needed.

      Quality Fragility: Customers find defects before the team does.

      Strategic Volatility: Every quarter starts over. Nothing compounds.

      Local Optimization Bias: Every team hits its targets. The product still misses.

      Attribution Failure: We know what happened. Nobody can explain why.

      Oversight Erosion: The review process still runs. It stopped meaning anything.

      Implementation Drift: The agents are building. Nobody is sure it still matches the plan.

      Take your Diagnosis to the next level by invoking AI Diagnostic Coaching tool.

      What else have you observed? Optional. Shared only if you choose to start coaching.

      Start a Diagnosis session: review and edit a draft containing your note, conditions you recognized in Step 3 (including whether they match partly), warning signs and consequence ratings before sending it. No scores or principle files are sent.

      See what practices will help you