Part of HSP Tools
HSP · START
You reacted differently than you wanted to. Maybe faster, harder, quieter, more defensive or not at all.
Afterwards, you may know exactly what you wish you had said or done. But in that moment, that option apparently was not or was barely available.
This short HSP exercise helps you look back at one concrete situation: what came in, what your system made of it, what it seemed to expect, how much activation appeared and how much choice space remained.
No test. No diagnosis. You do not need to understand HSP first. One moment, step by step.
Not: “Why did I do that?”
First: “What happened between input and behavior?”
07 · CHOICE SPACE
In hindsight we are often brilliant. The more useful question is: what actually felt available in that moment?
How much choice space felt available?
almost nonelots of room
What was less available?
What you can think of afterwards was not automatically available during activation.
08 · OUTPUT & FEEDBACK
Now look at the visible output. What did you say? What did you do? What did you not do? Then briefly look at what followed immediately.
What did that reaction do in the short term?
Behavior is the visible output, not the whole story. What happens next can reinforce the route. Understanding is not the same as excusing.
10 · LOOK AGAIN
Look at the same reaction again. Not only as something you did, but as visible output from a route that started earlier.
Maybe you can see that...
This is not a search for the one hidden cause. You are making a workable map of what becomes visible in this one situation.
11 · DO NOT FIX IT YET
You do not have to “react differently” immediately. First look for where the route narrowed and where something else might create more room.
This is enough for a START exercise. You do not yet need to know exactly which learned system logic, capacity, need or output function is underneath it.
Want to work through the same situation in more depth? The HSP Observation Map adds those layers.
HSP · START · EXPLANATION
You did not explain or judge one reaction. You slowed it down so you could look at the route before, during and after the visible behavior.
For this START exercise, we deliberately use a short chain:
The full HSP architecture is richer. Detection — what your system picks up as relevant in the first place — is implicit here between input and meaning. Learned system logic, resource allocation, capacity, output function and other constraints are also not mapped separately in this first exercise. That is deliberate: first learn to see one scene, then add more layers.
What you eventually said, did or did not do is the visible part. A lot may already have happened before that: something captured attention, received meaning, became linked to a possible next outcome and changed activation. As activation or load rises, the available choice space can become smaller.
That is why knowing afterwards what you “should have done” is not the same as having that option available in the moment. Sometimes deliberate choice was still there, but narrower. Sometimes part of the reaction was already underway before deliberate choice was fully available.
A reaction may do something for the system in the short term: reduce tension, stop conflict, create distance, increase control or try to preserve connection. HSP calls this a possible output function. It is not an excuse and it does not prove that the behavior was desirable.
HSP uses the question to make responsibility more precise: what happened in the system, what was available at the time, what impact did the output have, and what now requires repair, a boundary, a different choice or further practice?
What happened after the reaction matters. If a route immediately reduces tension, stops criticism or restores control, the system may keep treating that route as useful — even when the longer-term cost is high. Different feedback can instead help make a new route more credible and more available.
This map does not prove that events unfolded exactly this way. You are building a working hypothesis from one situation. That is enough to ask better questions without turning one reaction into a trait, diagnosis or fixed story about yourself.
Want to investigate the same situation in more detail? The HSP Observation Map makes Detection, assumptions, learned system logic, capacity, output function, costs, need and ownership more explicit.
TOOL IN CONTEXT
What Just Happened? is the HSP START exercise for the moment when your main question is: “Why did I react like that?” You do not need to know the full model yet. You first investigate one scene using a deliberately simplified system route.
If that gives you enough insight, stop there. Not every situation needs to be fully unpacked.
If you want to look further at what your system may have assumed, which learned logic was involved, how much capacity was available, what function the output had, what it cost, what you needed and what is yours to own, continue with the HSP Observation Map.
In the HSP Core Protocol: OBSERVE → MAP
Continue with the HSP Observation Map Back to System Scan & tools