observe-guidance

name	observe-guidance
description	Guide a person in systematic observation of systems, patterns, or phenomena. Coaches neutral attention, field notes methodology, pattern recognition, hypothesis formation, and structured reporting. Use when: a person wants to understand system behavior before intervening; someone keeps jumping to conclusions and needs observation discipline first; preparing evidence-based reports; studying team dynamics or process effectiveness through direct observation. Do NOT use when: the person needs immediate intervention or quick fixes; the task is data analysis of existing logs/metrics without live observation; the scope is a simple one-time check with obvious outcomes; the person needs technical instruction rather than observational methodology.
license	MIT
allowed-tools	Read
metadata	{"author":"Philipp Thoss","version":"1.1","domain":"esoteric","complexity":"intermediate","language":"natural","tags":"esoteric, observation, field-study, pattern-recognition, debugging, guidance, methodology"}

Observe (Guidance)

Guide a person in systematic observation of a system, phenomenon, or pattern. The AI acts as a field study coach — helping frame the observation target, prepare a protocol, sustain neutral attention, record findings with field notes, analyze patterns, and report observations with clear separation of data and interpretation.

When to Use

• A person wants to understand a system's behavior before intervening (debugging by observation rather than trial and error)
• Someone is conducting research or gathering evidence and needs structured observation methodology
• A person keeps jumping to conclusions and needs to develop observation discipline before interpretation
• Someone is preparing a report that requires evidence-based findings, not opinions or assumptions
• A person wants to understand team dynamics, user behavior, or process effectiveness through direct observation
• After meditate-guidance has cultivated sustained attention, the person wants to direct that attention toward a specific system

When NOT to Use

• The person needs immediate intervention or quick fixes — observation takes time and delays action
• The task is data analysis of existing logs/metrics without any live observation component
• The scope is a simple one-time check with obvious outcomes that don't warrant systematic study
• The person needs technical instruction on how to do something rather than observational methodology for understanding something
• The observation target is inaccessible, illegal, or violates privacy/ethics boundaries
• A more specific skill exists (debug-guidance, research-guidance, user-study-guidance) that matches the exact context

Inputs

• Required: What the person wants to observe (a system, process, behavior, codebase, team dynamic, natural phenomenon)
• Required: Why they are observing (debugging, research, audit, curiosity, improvement)
• Optional: Time available for observation (single session vs. multi-day study)
• Optional: Prior attempts to understand the system (what has already been tried)
• Optional: Specific questions or hypotheses they want to test
• Optional: Tools available for recording (notebook, screen capture, logging, metrics)

Procedure

Step 1: Frame — Define the Observation Target

Help the person set up a clear, bounded observation frame.

1. Ask what they want to observe: "What system or behavior are you trying to understand?"
2. Help them narrow the scope: "What specific aspect of that system interests you most?"
3. Identify the observation purpose: understanding, debugging, improvement, evidence-gathering, or pure curiosity
4. Set boundaries: what is in scope and what is not (prevents observation from expanding endlessly)
5. If they have a hypothesis: state it explicitly, then set it aside — "We will look for evidence both for and against this"
6. Choose the observation stance:
   • Naturalist: observe without interfering (best for understanding behavior)
   • Controlled: change one variable and observe the effect (best for debugging)
   • Longitudinal: observe over time (best for detecting trends)

Expected: A clear observation frame with defined target, scope, purpose, and stance. The person knows what they are looking at and what they are not looking at.

On failure: If the person cannot narrow their focus ("I want to understand everything"), help them pick one entry point: "What is the one behavior you find most confusing?" If they are already committed to a conclusion ("I just need to prove X"), gently challenge: "What would we need to see to disprove that? Let's look for both."

Step 2: Prepare — Set Up the Observation Protocol

Help the person establish a systematic approach to recording what they observe.

1. Choose the recording method based on the observation type:
   • Codebase/system: file paths, line numbers, timestamps, log entries
   • Behavior/process: time-stamped notes with actor, action, and context
   • Team/communication: quotes, speaker identifiers, non-verbal cues
   • Natural/physical: sketches, measurements, environmental conditions
2. Create a simple recording template:

Field Notes Template:
┌─────────────┬────────────────────────────────────────────────────────┐
│ Timestamp   │ When the observation occurred                          │
├─────────────┼────────────────────────────────────────────────────────┤
│ Observation │ What was seen/heard/measured (fact only)               │
├─────────────┼────────────────────────────────────────────────────────┤
│ Context     │ What was happening around the observation              │
├─────────────┼────────────────────────────────────────────────────────┤
│ Reaction    │ Observer's response (thoughts, emotions, surprises)    │
├─────────────┼────────────────────────────────────────────────────────┤
│ Hypothesis  │ Tentative interpretation (kept separate from fact)     │
└─────────────┴────────────────────────────────────────────────────────┘

3. Emphasize the separation: "The observation row is fact. The hypothesis row is interpretation. Never mix them."
4. Set a minimum observation count: "Aim for at least 10 observations before drawing any conclusions"
5. If applicable, set up monitoring tools: logging, metrics, screen recording

Expected: The person has a recording method ready and understands the critical distinction between observation and interpretation. They feel prepared to begin.

On failure: If the template feels too formal, simplify to: "Just write down what you see, and separately write what you think it means." If they resist recording ("I'll remember"), explain that unrecorded observations are subject to memory bias — the act of writing makes observation more accurate.

Step 3: Observe — Practice Sustained Neutral Attention

Guide the person through the actual observation session.

1. Remind them of the stance: "You are a naturalist studying a new species. Do not interfere — just watch"
2. For the first 5 minutes: encourage pure observation without recording — just attend
3. After initial immersion: begin recording using the template
4. Coach neutral language: "Instead of 'the system crashed,' try 'the system stopped responding at 14:32 after processing the 47th request'"
5. Watch for interpretation creeping into observation: "That is an interpretation — record it in the hypothesis row"
6. Encourage noting surprises: "What surprised you? Surprises often contain the most valuable data"
7. Periodically check the frame: "Are you still observing what you set out to observe, or has your attention drifted?"
8. If they want to intervene: "Note what you want to change and why, but do not change it yet — keep observing"

Expected: The person generates at least 5-10 concrete observations with specific evidence. They experience the difference between observing and interpreting, and find it harder than expected to maintain neutral attention.

On failure: If they keep interpreting instead of observing, try this exercise: "Describe what you see as if explaining it to someone who has never seen this system. Only use verifiable facts." If they run out of things to observe quickly, they are looking at too high a level — guide them to zoom in on details: timing, ordering, edge cases, exceptions.

Step 4: Record — Capture Findings with Field Notes

Help the person organize their raw observations into structured notes.

1. Review their recorded observations together
2. Check for completeness: does each observation have enough context to be understood later?
3. Check for factual accuracy: are statements verifiable, or do they contain hidden assumptions?
4. Group similar observations: "Do you see any patterns forming?"
5. Note frequencies: how often did each pattern appear?
6. Note absences: "What did you expect to see that was not there?"
7. Help them separate strong observations (clear evidence) from weak observations (ambiguous data)

Expected: A set of organized field notes that cleanly separate observation from interpretation. The notes are detailed enough that someone else could verify the observations independently.

On failure: If the notes are too vague ("things seemed slow"), help them add specifics: "How slow? Compared to what? In which conditions?" If the notes are too detailed (recording everything), help them identify which observations relate to the original frame and which are noise.

Step 5: Analyze — Identify Patterns and Generate Hypotheses

Guide the person from observations to structured analysis.

1. Lay out all observations and look for patterns:
   • Repetition: "This happened multiple times — is it systematic?"
   • Correlation: "X always happens alongside Y — are they related?"
   • Sequence: "A always precedes B — could A cause B?"
   • Absence: "X never happens in condition Z — why?"
   • Anomaly: "Everything follows pattern P except this one case — what is different?"
2. For each pattern, ask: "Is there an alternative explanation?"
3. Generate 2-3 hypotheses that explain the major patterns
4. Distinguish between correlation and causation: "Observing that A and B co-occur does not prove A causes B"
5. Identify which hypotheses are testable and what test would confirm/refute them
6. Note confidence levels: which hypotheses are well-supported, which are speculative?

Expected: The person moves from raw observations to structured hypotheses while maintaining the discipline of separating data from theory. They have at least one testable hypothesis for their original question.

On failure: If they jump to a single explanation immediately, challenge it: "That is one possibility. What is another?" If they see no patterns, the observations may be too few — suggest continuing observation before analysis. If every observation seems to point to the same conclusion, they may be filtering — ask: "What evidence would contradict your current theory?"

Step 6: Report — Share Findings with Clear Structure

Help the person communicate their observations effectively.

1. Structure the report:
   • Context: What was observed, when, why, under what conditions
   • Method: How the observation was conducted (protocol, tools, duration)
   • Findings: Key observations with evidence (data, not interpretation)
   • Analysis: Patterns identified, hypotheses generated, confidence levels
   • Recommendations: Suggested next steps (further observation, testing, intervention)
   • Limitations: What the observation did not cover, potential biases
2. Help them write findings in neutral language that separates fact from interpretation
3. Review for hidden assumptions or unsupported claims
4. If the observations are for debugging: translate hypotheses into concrete tests
5. If the observations are for a report: ensure the evidence is cited specifically
6. If the observations are for personal understanding: summarize the key insights and remaining questions

Expected: A clear report that communicates observations, patterns, and hypotheses while maintaining the distinction between what was observed and what was inferred. The reader can evaluate the evidence independently.

On failure: If the report buries observations in interpretation, restructure: "Put all the facts in one section, all the theories in another." If the report lacks confidence levels ("this is definitely because..."), help them calibrate: "How sure are you? What would change your mind?"

Output Contract

After using this skill, the person must have:

1. Observation Frame: A clearly defined target, scope, purpose, and stance (naturalist/controlled/longitudinal)
2. Recording Protocol: A chosen method and template for capturing observations
3. Field Notes: At least 5-10 concrete observations with timestamps, context, and clear separation of fact from interpretation
4. Pattern Analysis: Identified patterns (repetition, correlation, sequence, absence, anomaly) with alternative explanations considered
5. Hypotheses: 2-3 testable hypotheses explaining the patterns, with stated confidence levels
6. Structured Report: Clear documentation separating findings (data) from analysis (interpretation) with recommendations and limitations

Quality Gates:

• Observations contain specific, verifiable details (not vague generalizations)
• Facts and interpretations are never mixed in the same statement
• Each hypothesis has a stated confidence level and a test that could confirm or refute it
• The report includes explicit limitations and potential observer biases

Stop Conditions:

• The person cannot define an observation target after 3 attempts → pivot to clarify-guidance
• The person refuses to record observations and insists on immediate action → acknowledge and exit
• The observation reveals safety or ethics concerns → stop and escalate appropriately
• The analysis produces only confirmation of pre-existing beliefs → challenge and extend observation period

Validation

• The observation target was framed before observation began (not free-form wandering)
• A recording protocol was established and used consistently
• Observations were recorded as facts, separate from interpretations
• At least 5 concrete, evidence-backed observations were captured
• Patterns were identified through analysis, not assumed from the start
• Hypotheses are testable and have stated confidence levels
• The person experienced the discipline of observing before interpreting

Failure Handling

If the person cannot narrow their focus

• Symptom: "I want to understand everything" or scope keeps expanding
• Response: "What is the one behavior you find most confusing right now?" Force a single entry point.
• Escalation: If still unable to focus after 3 attempts, pivot to clarify-guidance to define the problem space first.

If the person is already committed to a conclusion

• Symptom: "I just need to prove X" or dismisses contrary evidence
• Response: "What would we need to see to disprove that? Let's look for both confirming and disconfirming evidence."
• Escalation: If they refuse to consider alternatives, acknowledge the bias explicitly and ask if they want to continue with that limitation noted.

If the template feels too formal

• Symptom: Resistance to structured recording
• Response: Simplify to: "Just write down what you see, and separately write what you think it means."
• Escalation: If they resist all recording, explain memory bias risk once, then proceed with their preferred method but document the limitation.

If they keep interpreting instead of observing

• Symptom: "The system is broken" instead of "The system stopped responding at 14:32"
• Response: Use the exercise: "Describe what you see as if explaining it to someone who has never seen this system. Only verifiable facts."
• Escalation: If persistent, ask them to record observations verbatim for 5 minutes before any analysis is allowed.

If they run out of things to observe quickly

• Symptom: "There's nothing else to see" after minimal observation
• Response: Guide them to zoom in: timing, ordering, edge cases, exceptions, environmental conditions.
• Escalation: If the system is genuinely simple, conclude observation early and move to analysis.

If notes are too vague

• Symptom: "Things seemed slow" without specifics
• Response: Ask: "How slow? Compared to what? In which conditions? Can you measure or timestamp it?"

If notes are too detailed

• Symptom: Recording everything indiscriminately
• Response: Help identify which observations relate to the original frame and which are noise; prioritize observations that answer the original question.

If they jump to a single explanation immediately

• Symptom: "It's obviously because of X"
• Response: "That is one possibility. What is another explanation that could also fit the data?"

If they see no patterns

• Symptom: Random-looking data with no discernible structure
• Response: Suggest continuing observation (more data may reveal patterns) or checking if the frame is too narrow.

If every observation points to the same conclusion

• Symptom: Unanimous data supporting one theory
• Response: Check for filtering: "What evidence would contradict your current theory? Have you looked for it?"

If the report buries observations in interpretation

• Symptom: Facts and theories mixed throughout
• Response: Restructure: "Put all the facts in one section, all the theories in another."

If the report lacks confidence calibration

• Symptom: "This is definitely because..." without uncertainty acknowledgment
• Response: Help calibrate: "How sure are you on a scale of 1-10? What would change your mind?"

Common Pitfalls

• Observation as confirmation bias: Observing only things that support a pre-existing belief. The frame should include "look for evidence against your hypothesis" as an explicit instruction
• Intervention urge: Seeing a problem and wanting to fix it immediately. Premature intervention often masks the root cause — observe first, then intervene with full understanding
• Recording fatigue: Detailed observation is mentally taxing. Suggest breaks and realistic session lengths (30-60 minutes of focused observation is substantial)
• Overcomplicating the protocol: For simple observations, a notebook and timestamps are sufficient. The protocol should serve the observation, not replace it
• Confusing observation with surveillance: In interpersonal observation, ethical boundaries matter. Observe behavior that is visible, do not spy. If observing people, transparency is usually better than secrecy
• Skipping the frame: Without a clear observation target, attention scatters and findings are unfocused. Even a rough frame is better than none

Next Steps

• After observation is complete and patterns identified: Use learn-guidance to turn observations into structured understanding and knowledge
• If the observation reveals a specific technical problem: Use debug-guidance to systematically resolve the identified issue
• If the observation involves understanding people or communication: Use listen-guidance for focused attention on speakers and dialogue patterns
• If the person needs to sustain attention for extended observation: Use meditate-guidance to cultivate the neutral attention capacity first
• For self-directed AI observation across systems: Use observe (the AI-directed variant of this skill)