System Scan & tools

HSP — PRACTICAL

Practical tools for making visible what appears to be happening in a concrete situation, pattern or team.

The tools are not diagnoses and do not define who you are. They help you observe, organise and ask better questions.

Choose a tool → Start with the System Scan →

Choose the tool that fits your question

HSP tools

The tools are not tests that determine who you are. They help you examine what is happening now and where influence may exist.

HSP System Scan

A snapshot of the layers where your system currently appears most constrained or under pressure.

View the System Scan →

HSP Observation Map

Map what you detect, what happens internally and what output follows.

Use the Observation Map →

HSP System Map

Place the main system elements of one concrete situation next to each other.

Use the System Map →

HSP Pattern Map

Examine a pattern that keeps returning across different situations.

Use the Pattern Map →

HSP Trigger Map

Examine which signals trigger activation and what changes afterwards.

Use the Trigger Map →

HSP Input Filter

Examine which framing, assumptions and other input gain influence before you respond.

Use the Input Filter →

HSP Rollback Review

Review a relapse without treating it only as failure.

Use the Rollback Review →

Which tool, when?

Practical choice

I do not yet know where I get stuck

Start with the System Scan.

I want to unpack one situation

Use the Observation Map or System Map.

The same thing keeps returning

Use the Pattern Map.

Something activates me immediately

Use the Trigger Map.

I am questioning the input itself

Use the Input Filter.

I fell back into old behavior

Use the Rollback Review.

For teams and Agile/Scrum

Team tools

A team is not the sum of individual scores. Team tools are used to make patterns in collaboration, pressure, rules and capacity discussable.

For Agile and Scrum teams there is the Agile/Scrum Quick Scan: a short snapshot that can be used for intake, workshop opening, pre-retro reflection or before-and-after comparison.

View the Agile/Scrum Quick Scan →

A tool is a starting point, not a conclusion

No diagnosis

A score or map does not define who you are and does not prove a cause.

Use the result as a working hypothesis: which layer appears to have influence now, what do we see in concrete situations and what happens when we change something small?

Not getting further on your own?

Next step

Sometimes a tool makes enough visible for you to continue on your own. Sometimes it mainly gives you a better question.

Start with your question   See how coaching works →