the jambot the sabernetics of software organizations

From map to motion.

evidence signal hypothesis investigation intervention
Fig. 2 — Same field, five readings 01/05
CONCENTRATION OBSERVED 61% · DERIVED 22% · INFERRED 12% · UNKNOWN 5% INTERVENTION · ONE DEPENDENCY
01 / Structural Genesis

The Representation

The organization as it describes itself. Org charts, roadmaps, team charters, operating models.

02 / Evidence Capture

Work Leaves Evidence

Every issue, pull request, comment, review, assignment, label, and approval creates an involuntary record of how work actually moves.

03 / Topology Render

The Hidden Topology

Follow the evidence and patterns emerge: knowledge concentration, coordination bridges, maintenance gravity, ownership gaps, rework loops.

04 / Confidence Audit

The Unreliable Narrator

Correlation is cheap. The same pattern supports multiple explanations. The work is knowing which one survives contact with evidence.

05 / Intervention

Intervention

Act on the structural constraint, not the symptom. One well-placed experiment beats a reorg.

The five stations

Route: evidence → signal → hypothesis → investigation → intervention. The challenge station is where most traverses turn back. That is the point of having one.

Epistemics

Never treat a derived metric as an observed fact.

Most organizational analysis fails at the epistemics: derived numbers are presented as observations, and inferences travel as facts. Every claim in a Jambot map carries its status.

Fig. 3 — Confidence overlay
OBSERVED DERIVED OBSERVED INFERRED UNKNOWN
Next

The six structural patterns →

What the Assess station is looking for, and what each pattern feels like from the inside.

Advisory

Run a reading on your organization →

A traverse takes a few weeks and ends with one intervention you can actually test.