the jambot / visual systems
A working catalog of visual metaphors for reading work, forecasting consequences, and making hidden systems easier to discuss.
Most of these came from somewhere else.
A heat map from a trading desk. A flow tracker from logistics ops. A consequence ring from how military planners visualize second-order effects. A constellation map from the way a good coach reads a defense before the play develops. I did not invent these metaphors. I borrowed them from domains where misreading the field has an immediate, visible cost. The bet is that if they work where the stakes are that obvious, they should work where the stakes are just as real but harder to see: inside a product team, a planning cycle, a twenty-five person meeting where everyone walked out thinking they communicated.
I am constantly looking for better ways to talk about this work and to make it visible. This catalog grew from that restlessness. Every metaphor here started as an attempt to explain something I was watching happen: coordination breaking down, demand accumulating in silence, velocity slipping without anyone being able to say exactly why. The visuals are not the insight. They are the thing I reach for when the words stop working.
When I am trying to understand what is happening inside a team, product, or organization, I often sketch the system before I try to explain it.
The usual tools matter. Roadmaps, org charts, status reports, strategy decks: they all have their place. But they tend to show the formal version of the work: what we planned, what we named, what we said was happening.
The harder questions usually live underneath that surface.
These visual metaphors are some of the instruments I use to reason about those questions. They work alongside the common tools. I reach for them to forecast what may be happening, explain what I am seeing, and build a shared picture when the conversation goes too abstract.
Some of these metaphors help read the work as it exists today. Others help test whether a team, workflow, or organization is ready for automation or agentic systems.
A working catalog: borrow, adapt, challenge, remix.
Two shapes, two topologies: the org chart as designed, the demand constellation as operated. The space between them is where misalignment starts costing.
A backlog tells you what exists. A flight tracker tells you what is moving, what is waiting, and what is grounded. The useful question is not how much work exists; it is where work is losing altitude.
Backpressure, queue depth, and flow rate reveal where value moves or stalls. Development is often where hidden demand becomes visible; the question is whether the queue is a normal constraint or a system-wide signal.
| SKILL / CAPABILITY | INTAKE | ANALYSIS | DEVELOPMENT | REVIEW | DEPLOYMENT | TOTAL |
|---|
Intensity shows where demand is concentrated. Hot zones signal capacity gaps; cold zones signal missing context. The heat marks where the conversation should start.
The demo shows what the agent can do. What follows is what the organization must absorb: second and third-order consequences that no capability review catches in advance.
The demo proves what the agent can do. It does not prove what the organization can absorb. Consequence analysis is the readiness threshold most teams skip.
Organizational readiness determines the operating mode. Agent capability sets the ceiling; the system's readiness sets the floor. Deploying autonomous behavior before the system is ready raises the blast radius, not the maturity.
The agent does not just change the organization. It reveals it. The hidden dependencies, weak interfaces, and unclear ownership were already there; the agent makes them harder to ignore.
One weak readiness dimension sets the effective operating mode. Readiness is the shape of the system around the agent, not an average of its parts.
Most teams jump from capability to deployment. The safer path is to map the workflow, analyze the consequences, assess readiness, and only then decide the operating mode.
One ambiguous phrase ("dependency on Azure") can spawn seven weeks of cascading meetings that each feel necessary but collectively produce nothing. The tax is the compounding cost of coordination without a shared map; no single meeting is the problem. A 25-person meeting at $200K average fully-loaded cost runs roughly $2,500 an hour. Do it weekly with no decision reached, and you have spent more than $100K in a quarter on institutional confusion.
Match the starting point to where confusion is sharpest. Misalignment between teams: the constellation. Work that won't move: the tracker or pipeline. Demand that feels uneven: the heat map. An agent that looks capable but an organization that feels uncertain: the consequence and readiness views. And if things are simply taking longer than they should (and nobody can say exactly why), start with the coordination drift. That is usually where the tax is hiding.