Understanding and updating - Models

TA Through the Lens of HSP

Transactional Analysis shows how people repeat patterns, scripts, games and racket feelings. HSP looks at the system architecture underneath.

Within Human System Protocol™, TA concepts are not used as labels, but as signals of operating rules, activation patterns, protective behavior and feedback loops.

Why TA fits HSP

Connection

Transactional Analysis describes how people communicate, react and repeat interaction patterns.

HSP adds system language to that.

TA can show which pattern is playing out.

HSP then asks:

Which interpretation, rule, activation and feedback loop produces this pattern?

Not therapy, but system observation

Boundary

TA originally developed as a therapeutic and communication model.

Within HSP, we do not use TA to diagnose or label someone.

We use TA as an observation framework:

  • which role becomes active?
  • which old rule is running?
  • which emotion is being repeated?
  • which interaction keeps the pattern alive?
  • which feedback confirms the old prediction?

This keeps the work practical, clear and behavior-focused.

Ego states through the lens of HSP

Ego states

TA describes ego states such as Parent, Adult and Child.

Through the lens of HSP, these can be seen as temporary system modes.

  • Parent mode: rules, norms, control, criticism or care become active.
  • Adult mode: observation, reality testing and conscious choice are available.
  • Child mode: old emotions, needs, adaptation or protection become active.

An ego state is not identity.

It is a temporary configuration of interpretation, activation and behavior.

The question is not: “Which ego state am I?” The question is: “Which system mode is active now?”

Scripts as old system configurations

Scripts

In TA, a script refers to an early-formed life pattern or internal scenario.

Within HSP, a script can be seen as an old system configuration.

A script often contains:

  • old interpretations
  • learned expectations
  • operating rules
  • protective behavior
  • repeated feedback
Early experience
Meaning
Rule
Script

A script remains active as long as the system keeps predicting that this old configuration is needed.

Examples of script rules

Operating rules

A script becomes practical when the underlying rule becomes visible.

  • If I am not strong, I will not be respected.
  • If I ask for help, I am weak.
  • If I show myself, I will be rejected.
  • If I succeed, I will lose connection.
  • If I relax, I will miss danger.
  • If I say no, I am selfish.

These rules are usually not consciously chosen.

They become active when the system recognizes a situation as similar to the past.

Games as feedback loops

Games

TA describes games as recurring interaction patterns with a predictable outcome.

Within HSP, games can be seen as feedback loops between two or more systems.

Trigger
Role
Other response
Old rule confirmed

A game stays alive because both systems keep producing something familiar.

Not because someone consciously wants to “be bad”, but because the pattern regulates tension, confirms meaning or activates old roles.

Why games are so persistent

Pattern repetition

Games are persistent because they produce something in the short term.

  • tension is discharged
  • a familiar role is confirmed
  • uncertainty is replaced by predictability
  • an old belief receives new evidence
  • responsibility is shifted or avoided

The result may be painful, but to the system it feels familiar.

A game is often not a rational choice. It is a repeated feedback loop that keeps old rules active.

Racket feelings as familiar emotional output

Racket feelings

TA uses the term racket feeling for a familiar, repeated feeling that often replaces a deeper or more vulnerable feeling.

Within HSP, a racket feeling can be seen as familiar emotional output.

The system does not always choose the most accurate feeling. It often chooses the most familiar or most permitted feeling.

  • anger instead of sadness
  • guilt instead of anger
  • shame instead of need
  • control instead of fear
  • irritation instead of vulnerability

The racket feeling is not a fake feeling.

It is a system route that has been used before.

Racket feelings and operating rules

Emotional rules

Behind racket feelings, there are often rules about which emotions are safe or allowed.

  • If I feel sadness, I am weak.
  • If I become angry, I lose connection.
  • If I show need, I will be rejected.
  • If I feel fear, I lose control.
  • If I feel guilt, I stay socially safe.

The system does not choose freely between emotions.

It follows the emotional route that once seemed safest.

The drama triangle through the lens of HSP

Drama triangle

TA describes roles such as Rescuer, Persecutor and Victim.

Within HSP, these roles can be seen as protective behavioral strategies.

  • Rescuer: regulates tension by taking over responsibility.
  • Persecutor: regulates tension through control, attack or judgment.
  • Victim: regulates tension through helplessness, dependency or withdrawal.

These roles are not fixed identity.

They are output of a system trying to regulate threat, tension or relational uncertainty.

From role to rule

Role to rule

The practical HSP question is not only: “Which role am I playing?”

The stronger question is:

Which rule makes this role logical for my system?

Examples:

  • Rescuer: “If I do not help, I lose value or connection.”
  • Persecutor: “If I do not attack, I lose control.”
  • Victim: “If I take responsibility, I will fail or be left alone.”

When you see the rule, the role becomes changeable.

Transactions as system exchange

Transactions

TA looks at transactions: the way communication between people unfolds.

Within HSP, communication is also system exchange.

Every interaction contains:

  • input
  • interpretation
  • activation
  • operating rules
  • behavioral output
  • feedback
My output
Input for you
Your output
Feedback for me

This turns communication from an exchange of words into a feedback loop between systems.

Why communication derails

Communication

Communication often does not derail because of the words alone.

It derails because systems add meaning.

A sentence may be interpreted as:

  • criticism
  • rejection
  • control
  • abandonment
  • dominance
  • unsafety

After that, people no longer respond to the words, but to the predicted meaning.

Many communication problems are not language problems, but interpretation and activation problems.

How HSP makes TA practical

Application

HSP makes TA practical by asking the same system questions repeatedly:

  • Which input activated the pattern?
  • What meaning did the system assign to it?
  • Which operating rule became active?
  • Which role or game emerged?
  • Which racket feeling appeared?
  • Which feedback kept the pattern alive?
  • Which small safe update is possible?

This turns TA from a description of patterns into a route for system observation and behavioral change.

From game to system

The shift

Not:

“Why am I playing this game?”

But:

“Which rule, role and feedback loop makes this pattern logical?”

And then:

“Which safe update makes a different transaction possible?”

That shift moves you from self-judgment to system observation.

Where TA connects within HSP

Diagnosis

TA concepts can point to several HSP system layers:

  • Scripts: old interpretations and operating rules.
  • Games: repeated feedback loops between systems.
  • Racket feelings: familiar emotional output.
  • Ego states: temporary system modes.
  • Drama triangle: protective behavioral strategies.
  • Transactions: input-output-feedback between systems.

This makes TA not a separate model beside HSP, but a useful observation framework inside the HSP architecture.

TA shows how relational patterns repeat.

The next step is understanding how conscious communication can make meaning, need and request more explicit.

Read NVC through the lens of HSP →

Games, scripts and racket feelings are not proof that you are wrong. They are patterns that reveal which system rules are still active.

View the HSP system scan Back to models and methods