Part of HSP Tools
HSP · PRACTICE
One reaction can become much more understandable when you look not only at what you did, but at the full system route that came before it.
What actually came in? What was detected? Which meaning and prediction emerged? Which learned system logic became active? What happened to activation, capacity and choice space?
The HSP Observation Map helps map one concrete situation in more detail including behavior, possible function, feedback, costs, need and what is actually yours to own.
Not to label yourself. To see which system conditions made the reaction understandable.
Behavior is what you can see. The Observation Map helps investigate what came before it and what the system learned from it.
Use
Use the HSP Observation Map when you want to understand why your system produced something: a reaction, block, people-pleasing, withdrawal, anger, procrastination, control, overthinking or other behavior that later did not fit what you actually wanted.
The map is not a diagnosis and not a test. Use the layers as observation points. You do not need to know everything perfectly. One visible layer can already make a reaction feel less personal and more understandable.
Not: “What is wrong with me?”
But: “Which system conditions made this reaction understandable?”
New to HSP? You can first use the shorter START exercise What Just Happened?.
What you enter in the fields below is not submitted or stored by this page.
03 · Predictive interpretation
HSP separates predictive interpretation into three steps. They can happen very quickly and largely automatically.
An assumption does not have to be wrong. The point is to see that your system was working with it.
06 · Capacity & choice space
The question is not only what was theoretically possible. The question is what your system actually had available in that moment.
How much choice space felt available?
almost no rooma lot of room
What was less available?
Afterwards there is often more choice space than during activation. That difference is information.
09 · Need & ownership
The Observation Map is not an excuse. Understanding which layer was active can actually make responsibility more precise: what is yours to acknowledge, repair, protect, communicate or update?
Which system condition may have been missing?
What is yours to handle consciously?
Responsibility does not mean condemning yourself. It means exploring what is yours to handle consciously.
10 · The whole Observation Map
Summarize each layer in one short line. The goal is not completeness but visibility: where did the route change?
| Input | |
|---|---|
| Detection | |
| Meaning | |
| Prediction | |
| Assumption / system logic | |
| Activation | |
| Choice space | |
| Output | |
| Function | |
| Feedback / cost | |
| Need / ownership |
This summary could later be filled automatically from the earlier fields; for the first version you can summarize it manually.
11 · Hypothesis, not truth
The Observation Map is meant to slow things down, not lock you into a new analysis. Every layer is a hypothesis. Maybe your first interpretation is correct. Maybe not.
Not: “Which explanation sounds smart?”
But: “Which observation makes the system more understandable and creates more room to investigate?”
System chain
HSP views behavior as system output. That means behavior usually does not appear on its own. A chain comes before it: input, predictive interpretation, activation, capacity / choice space, operating rule / learned system logic, output function and feedback.
| Layer | What do you observe? | Helpful question |
|---|---|---|
| Input | What came in through words, tone, body language, timing, media, memory, body signal or situation? | What exactly did my system receive? |
| Predictive interpretation | What did the system detect, what meaning did it assign, and what did it predict might happen next? | What did my system predict this meant? |
| Assumption | Which conclusion was treated as true before it was fully examined? | What did I assume without knowing for sure? |
| Body signal | Which physical signals appeared: tension, pressure, heat, cold, restlessness, fatigue, contraction or numbness? | What did my body show? |
| Emotion / activation | Which emotion or state came online: fear, anger, guilt, shame, urgency, confusion, shutdown or alertness? | Which activation came online? |
| Operating rule / learned system logic | Which implicit rule, threshold, default route or learned strategy seemed to direct the output? | Which learned logic became active? |
| Capacity / choice space | How much room was still available for clear thinking, feeling, choosing, slowing down or setting a boundary? | What was still available or unavailable? |
| Output | What did the system produce: attacking, defending, explaining, pleasing, avoiding, blocking, controlling, saying yes or going silent? | What became visible as output? |
| Output function | What did the output do in the system: reduce tension, prevent conflict, protect connection, create clarity, set a boundary, restore control or avoid an unwanted experience? | What function did this output have? |
| Feedback | What happened immediately after the output? Did tension drop, conflict get avoided, control return or connection stay intact? | What did my system learn from this? |
| Cost | What did this output cost over time: energy, honesty, connection, calm, boundaries, self-trust or autonomy? | What was the price of this output? |
| Need | Which system condition may have been missing: safety, time, clarity, rest, support, boundary, information or recovery? | What did my system need? |
| Ownership | What is yours to acknowledge, repair, protect, communicate or update? | What is mine to take with me? |
Example
The Observation Map becomes clearer when you apply it to a concrete pattern. For example: you say yes to a request while internally feeling no.
| Layer | Possible observation |
|---|---|
| Input | Someone asks something with urgency, expectation or disappointment in their tone. |
| Predictive interpretation | My system detects pressure, gives it meaning — “If I say no, I disappoint them” — and predicts distance, conflict or rejection. |
| Assumption | “Disappointment means I am doing something wrong.” |
| Activation | Guilt, tension, urgency or restlessness comes online. |
| Operating rule / learned system logic | “Protect connection by adapting.” |
| Capacity / choice space | Pausing, feeling and setting a clear boundary are temporarily less available. |
| Output | I say yes, explain, soften or make myself smaller. |
| Output function | The output lowers guilt, prevents possible conflict and protects connection in the short term. |
| Feedback | The tension drops immediately. The system learns: saying yes keeps things safe. |
| Cost | Later, fatigue, irritation or loss of self-trust appears. |
| Need | Time, space, permission to pause and a safe boundary. |
| Ownership | I can practice slowing down: “I will come back to this later.” |
From judgment to observation
Without observation, the system often jumps straight into self-judgment:
HSP looks differently. A reaction is not automatically identity. A reaction is often system output under specific conditions.
| Self-judgment | HSP observation |
|---|---|
| I am weak. | My system had low capacity / choice space and produced automatic output. |
| I am exaggerating. | My system detected meaning, threat or an old prediction. |
| I should have just said no. | No may not have been available enough in that moment. |
| I keep doing the same thing. | The old learned route may still receive feedback that it is needed. |
| I understand it, so why can’t I change? | Insight is available, but the system update is not yet integrated into choice space and output. |
From observation to direction
The Observation Map helps give language to what happened in your system. After that, other HSP tools can help choose a fitting next step.
Use the tools in this order:
Input Filter → inspects the input.
Observation Map → explores the system response.
System Scan → helps locate the active system area.
This makes the System Scan more concrete. You are not exploring a vague problem, but a visible system chain.
Core
Self-awareness is not only knowing what you feel. It is seeing how input becomes predictive interpretation, learned system logic, activation, choice space, output, output function and feedback.
The HSP Observation Map helps make that chain visible. Not to label yourself, but to understand your system more clearly. When the chain becomes visible, there is more choice space for responsibility, repair and safe updating.
You are not your first activation. But you can learn to understand which system conditions made that activation logical.