# Observe Clarity starts with **signals**. Not "what do we think is happening?", but: - what did we see - what changed - what are we waiting on - what's surprising Observation is where you reduce drama and increase truth. ## Start here if - You feel the room is full of stories and certainty. - You need to separate what changed from what we assume. - You want to reduce blame by focusing on signals. Try next: - [[Signal Log]] - [[07_Tools/Show Your Work Checklist (10 min)]] - [[System Mapping Operators Map]] ## Run one small move - If you're stuck: [[Complaint-to-Probe (25 min)]] - If learning is disappearing: [[Golden Extraction (30 min)]] - If the system feels stuck on hidden blockers: [[Probe a Dependency (10 min)]] - If the room is quiet: [[Safety Signals Check (10 min)]] ## What "good" looks like You can write 5–10 bullets of reality that most people can agree with. When you can do that, go to [[Frame]]. ## Signals and system reading The core move in Observe is separating what is happening from what we are inferring. - [[Signals over Stories - Why It Happens]] — why teams default to narrative and how to return to observable data - [[Common Cause vs Special Cause]] — distinguishing systemic patterns from one-off events; the Deming lens that prevents over-reacting to noise - [[Signal Log]] — a running record of observed signals, not interpretations - [[From Raw Complaint to Signal (Example)]] — a worked diagnostic: how to translate a presenting complaint into an observable signal worth acting on - [[Cynefin Framework]] — situating signals in the right domain before interpreting them; what kind of system are you observing? ## Culture and safety diagnostics What you can observe in a room tells you a great deal about the conditions underneath it. - [[Westrum Culture Typology]] — three culture types (pathological / bureaucratic / generative) and their observable markers - [[Psychological Safety Signals - Deep Dive]] — what psychological safety looks like in practice; signals that it is present or absent - [[Belonging Cues]] — the micro-behaviours that signal inclusion or exclusion; observable in real time ## Failure modes to recognise Some patterns are hard to see from inside them. Naming them makes them interruptible. - [[The Heroism Trap]] — when the system rewards individual fire-fighting over structural improvement; what it looks like from outside - [[Optimism as Avoidance]] — when positive framing is a defence against uncomfortable signals - [[Workarounds as System Intelligence]] — workarounds are not laziness; they are diagnostic data about where the formal system is failing - [[What Generative Culture Produces]] — the positive counterpart; observable markers of a system that is working well ## System structure Some signals only become legible when you can see the shape of the system producing them. - [[System Boundary Sketch (15 min)]] — draw what's in scope before diagnosing what's wrong - [[Feedback Loop Scan (20 min)]] — identify one reinforcing or balancing loop that explains the pattern - [[Stakeholder Tension Map (20 min)]] — who has interests in this situation, and where do they pull against each other? - [[Leverage Points Scan (15 min)]] — once the system is visible, find where a small change creates a large shift ## Time and rhythm as observational lenses How a team relates to time is itself an observable signal — not just what they are doing, but when and at what pace. - [[Temporal Imagination Map]] — noticing time, pace, rhythm, and urgency as observational lenses - [[Where Time Goes (10 min)]] — a fast audit of where time is actually spent vs where the team believes it goes - [[Waiting Column Audit (20 min)]] — making queue time visible; what is sitting and for how long ## The inference backbone A lot of "disagreement" is actually people standing on different rungs of inference. Owlery makes those rungs visible so the loop stays adult-adult. - Lens: [[Ladder of Inference]] - Quick reset: [[Ladder Check (7 min)]] ## References - Donella H. Meadows, Thinking in Systems (overview): https://donellameadows.org/archives/thinking-in-systems/ - Karl E. Weick, sensemaking (summary): https://en.wikipedia.org/wiki/Sensemaking ## See Also - [[Sensemaking Map]] — the closely related map; once you have signals, sensemaking is the interpretive step before framing - [[Knowledge Sharing Map]] — what you observe needs to travel; this map handles making observation actionable for others - [[Psychological Safety Map]] — the full cluster for diagnosing and designing safety conditions - [[Queues and Waiting - Deep Dive]] — one of the core observational domains; where work stacks up, why, and what it reveals about the system - [[Temporal Imagination Map]] — noticing time, pace, rhythm, and urgency as observational lenses