Part of Practical Integration - Which layer do you want to investigate?
Feedback as a learning layer
A feedback experiment helps you recognize what your system actually takes in after a small step. Not only what happened, but which feedback your system uses to confirm, soften or update old predictions.
You are not only investigating whether an experiment “worked.” You are investigating which feedback your system received, which meaning it gave to that feedback and whether the old prediction became stronger, softer or less absolute.
Core sentence: the experiment is not only what you do. The experiment is mainly what your system learns afterwards.
Learning from return signals
A feedback experiment is a small, safe way to investigate what your system actually learns after an action. You do not only look at what you did, but at what came back: calm, tension, confirmation, confusion, relief, rejection, repair or more choice space.
The goal is to recognize whether your system receives update feedback, threat feedback or moves back into old predictions.
HSP question: what does my system actually learn after this small step?
Not the action alone
A small action does not automatically change the system. What happens afterwards matters just as much. The system compares the new experience with the old prediction.
If the old prediction was: “If I pause, rejection will follow”, the feedback after the pause is crucial. Did rejection actually appear? Did connection remain? Did more calm appear? Did tension increase?
Feedback experiments help you see whether your system receives useful new information, or mainly information that strengthens the old protection.
Reading the return signal
Feedback experiments make visible how output and feedback form a loop together. You do not only see what you do, but also what meaning your system gives to what happens afterwards.
This helps you read feedback not only as content, but as system information.
Update, threat or noise
Not all feedback helps the system in the same way. In HSP, you can roughly distinguish three kinds.
A feedback experiment does not help you make everything positive. It helps you see more precisely what kind of feedback your system received.
Keep it small
A feedback experiment quickly becomes too vague when you try to understand everything at once. Choose one question.
The art is not to get the perfect outcome. The art is to make the feedback small enough to read.
Ordinary return signals
Feedback experiments are often simple. Precisely because they are small, you can see what actually comes back.
The experiment is not only the action. The experiment is mainly what you learn afterwards.
New experience
A small return signal can have a large effect when it touches an old prediction precisely. If your system expects pause to be dangerous, one safe pause can already provide new information.
That does not mean one experience changes everything. But several small experiences can build confidence: I can influence something in the loop, I can read feedback, I do not have to move straight into the old output.
Small feedback builds confidence: behavior feels less fixed when your system notices that small adjustments create noticeable differences.
After the output
In feedback experiments, the emphasis is on what happens after the small step.
The HSP Rollback Review fits well here when the system moves back into old output after an experiment.
Information is progress
A feedback experiment is successful when it provides information. That can be a visibly different outcome, but it does not have to be.
Even when old output returns, the experiment can still be successful. It has shown where the loop became too fast, too large or too unsafe.
Do not conclude too quickly
Sometimes feedback is mixed. Someone responds kindly, but your body remains tense. Or the outside world gives calm, while your system still feels shame or guilt.
That does not mean the experiment failed. It may mean that external feedback and internal feedback are not saying the same thing yet.
Make the next experiment smaller. Choose one return signal to read: the other person’s response, your body state, the old prediction, or your choice space afterwards.
Safety first
Some feedback is too heavy, threatening or unsafe to use as an experiment. Think of violence, coercion, intimidation, stalking, serious unsafety or situations where dependency is being misused.
In those situations, the goal is not to learn to read feedback better, but to create safety, support, distance or practical help.
Feedback becomes useful for learning only when the system is safe enough to process the information.
Next layer
Feedback experiments often sit at the end of a small learning route. They help you see what your system took from an input experiment, capacity experiment, boundary experiment, prediction experiment, activation experiment or relationship experiment.
If the feedback shows that input is strongly influencing the system, move to input experiments. If you notice that the step asked too much, look at capacity. If feedback mainly brings up guilt, pressure or relational tension, boundaries or relationships may be the next layer.
The question remains: which layer now needs a smaller, safer test?
What does the system learn?
Feedback experiments make visible what actually happens after a small step. They help you not only change behavior, but mainly recognize which information your system uses to confirm, soften or update old predictions.
When you learn to read feedback smaller and more precisely, confidence grows. Not as positive thinking, but as experience: I can influence something in the loop, I can learn from return signals and I do not have to automatically follow every old prediction.
This makes change less abstract. Small feedback can show that behavior is not fixed output, but influenceable output.