Diagnostic Workflow – From Observation to Structural Hypothesis¶

⚠️ ATTENTION: This workflow ends at the Structural Hypothesis Contract.
HCS is a diagnostic instrument. It does not manage execution. Once the contract is generated (Step 4), custody transfers to your delivery framework (e.g., Agile, 3SF, Management).

The HCS Diagnostic Workflow is a small loop that turns the Core Model into a usable lens.

It provides a structured way to trace observable issues in cooperation back to their systemic root causes in the Matrix and Pyramid — and ends with a rigorous, falsifiable Structural Hypothesis.

Most improvement efforts fail because they start with practice changes (Level 4) rather than asking:

“At which level of cooperation is this actually unstable?”

This workflow keeps analysis grounded and ensures each corrective action strengthens the right layer of the system.

Why This Workflow Exists¶

The workflow exists to:

move from vague problem labels (“communication issue”, “planning is bad”) to specific matrix cells and levels;
respect the Level Rule (stabilize lower levels before adjusting higher ones);
avoid jumping straight into tools and methods without understanding what function they are supposed to serve.

It focuses on the Core Model first:

Conditions × Needs → Functions (Matrix)
Levels 1–5 (Pyramid)

Extended Human Dynamics and System Modes are layered on after this basic structural pass.

When to Use the Diagnostic Workflow¶

Use this workflow when:

you observe recurring friction, not one-off incidents;
multiple people describe the same issue in different words;
you are tempted to “roll out a new practice” but cannot clearly say which function it solves;
a previous intervention failed to stick.

The 4-Step Workflow¶

Step 1: Observation¶

Goal: Separate what happened from what you think it means.

Most diagnoses fail here because people skip to "stories" (e.g., "They don't care about quality").
You must strip the story away.

The Video Camera Rule¶

Only write down what a video camera could record.

Bad: "The team is lazy." (Story/Judgment)
Good: "Three tasks were moved to 'Done' without passing the test suite." (Fact)
Bad: "They are hostile." (Story)
Good: "When I asked for the roadmap, they did not reply to the email for 5 days." (Fact)

Output: A neutral, factual statement of the pattern.

Step 2: Matrix Mapping¶

Goal: Locate the friction in the 25-cell Matrix.

Ask: "Which structural condition or human need is breaking here?"

The Symptom Compass¶

Use this cheat sheet to find the neighborhood:

If the friction is about...	Look at this Matrix Column/Row
"Why are we doing this?"	Common Purpose (Row 1)
"Who is doing what?"	Distribution of Roles (Column 4)
"We are surprised by bad news."	Feedback Loops (Column 3)
"I'm waiting on them."	Interdependence (Row 2)
"I don't feel safe to talk."	Trust / Safety (Row 4 / Column 3)

Output: A specific cell (e.g., Interdependence × Role Distribution = Coordination).

Step 3: Level Check (The "Stop Sign")¶

Goal: Apply the Level Rule.

Look at the cell you identified in Step 2. Ask:
"Is the level below this cell stable?"

The Level Rule Check¶

You want to fix: Coordination (Level 3).
Check Level 2: Do they even want to coordinate? (Mutual Commitment).
Check Level 1: Do they actually need each other? (Interdependence).

STOP: If Level 1 or 2 is unstable, do not fix Level 3.
You cannot "coordinate" people who don't share a purpose. Move your diagnosis down.

Output: The Lowest Unstable Level (e.g., "It looked like a Process issue (L3), but it's actually a Purpose issue (L1)").

Step 4: Structural Hypothesis Contract (The Exit Gate)¶

Goal: Define the structural parameters of the intervention and "sign" the contract.

Do not jump straight to "We will use Jira."
First, identify the Structural Move required to fix the function.

The 5 Structural Moves¶

Before picking a practice, select the Move:

Decouple: Break a dependency to reduce coordination cost. (Encapsulation).
Couple: Create a dependency to force alignment. (Integration).
Explicate: Write down a hidden norm or rule. (Clarity).
Sanction: Attach a consequence (positive/negative) to a boundary. (Accountability).
Dampen: Reduce the frequency or noise of a signal. (Focus).

These moves define the type of structural change required, not the action that implements it.

The SHC Artifact (Template)¶

You must fill this out to complete the HCS diagnosis.

The Structural Hypothesis Contract

Structural Claim: "Function [X] is unstable because Condition [Y] is unmet."

Observable Signal: "We know this because we see [Video Camera Fact]."

Structural Move: "We need to [Decouple / Couple / Explicate / Sanction / Dampen] this interaction."

Falsification Criteria: "We will know our diagnosis is WRONG if [Specific Metric/Signal] does not improve within [Timeframe]."

The Validity Protocol (Mandatory)¶

Rule: If ANY of the 4 fields above are missing or vague, the diagnosis is INVALID.
Action: You must not proceed to practice selection. Go back to Step 1.
The Structural Cost: If you skip this step, your intervention is just an opinion. HCS disclaims all reliability for interventions without a signed SHC.

Output: A valid, signed SHC.

The Practitioner's Inner Loop (Self-Correction)¶

Expert practitioners do not just run the 4 steps once. They run a continuous micro-loop in their heads to avoid bias.
Before you propose any intervention, run this 10-second mental check:

The Evidence Check: "Did I actually see this happen (Video Camera), or am I assuming intent?"
If assuming: Stop. Go back to observation.
The Level Check: "I am trying to fix [Level X]. Is [Level X-1] solid?"
If unsure: Stop. Test the lower level first.
The Projection Check: "Am I prescribing this tool because the team needs it, or because I like this tool?"
If I like it: Stop. Name the missing function first.
The Safety Check: "Will my intervention make people feel unsafe?"
If yes: Stop. Switch to Conflict Mode to build safety first.

Summary Table¶

Step	Action	The "Quality Check" Question
1. Observation	Record Facts	"Would a video camera agree with this?"
2. Matrix Mapping	Find Cell	"Is this about Meaning, Roles, or Feedback?"
3. Level Check	Apply Level Rule	"Is the foundation under this problem solid?"
4. Structural Contract	Define Move & Exit	"Are all 4 fields defined? If yes, sign and exit."

Essence¶

Every cooperation issue can be traced through the same Core Model lens.
HCS owns the diagnosis; You own the execution.

[HCS Zone: Observation → Matrix → Level → Structural Hypothesis] ➔ [Execution Zone: Practice → Learning]

This workflow does not replace judgment, System Modes, or Extended Human Dynamics.
It provides a stable structural backbone for all of them — a way to keep diagnosis grounded while you decide how to act.