How telemetry finds the right mental shape and predicts team performance
Team Topologies and Axiom Cortex
How the two systems work together
Team Topologies gives us a map for how teams should be shaped, and Axiom Cortex gives us a way to read the people who fill those shapes, so the two systems work best when they run side by side. One system draws the box, and the other system finds the person who actually fits inside the box. Most companies draw the box and then shove anyone into it, and that is why so many teams feel off, feel slow, feel stuck. When you match the shape of the team to the shape of the person, the team starts to move on its own, without being pushed, without being nagged, without being saved.
The four team shapes
Team Topologies says every team fits into one of four types, and each one needs a different kind of mind, a different tolerance for noise, and a different relationship with change. The table below shows what each shape is, what it does, and the kind of person who fits inside it.
Team Type
What It Does
Mental Shape Needed
Person Who Fits
Stream-aligned
Ships features close to the user, every day
Steady focus, fast bounce-back, calm under noise
Handles small fires, switches tasks easy
Platform
Builds tools used by other teams
Deep focus, long memory, patient with slow feedback
Wants quiet, wants depth, hates chopped days
Enabling
Teaches and coaches other teams, then moves on
Social range, teaching instinct, low ego on handoff
Likes to explain, likes to leave teams stronger
Complicated-subsystem
Owns the hard math, the tricky engine
Long attention, comfort with confusion, stubborn
Loves hard problems, stays with them for weeks
How Axiom Cortex reads people
Signals from real work
Axiom Cortex does not use surveys, does not use self-reports, does not use vibes. It reads real telemetry from real work, the kind of work people do every day without thinking about being watched. The signals stack up into a shape, a kind of fingerprint of how a person actually works, not how they say they work, and the shape stays pretty much the same across weeks, even when the topic changes, and that is what makes it useful for matching.
The table below shows the main signals the engine reads, what each one measures, and what it tells us about the person behind the keyboard.
Signal from Telemetry
What It Measures
What It Tells Us About the Person
Commit cadence
How often code gets pushed
Rhythm of thought, delivery style
Review depth
Length and quality of pull request comments
Level of care, depth of thinking
Message latency
Time between message and reply
Focus mode, interrupt tolerance
Context-switch frequency
How many topics in a day
Breadth vs depth preference
Recovery time
How fast someone bounces back from a blocker
Resilience, problem-solving agility
Written reasoning style
How they write in tickets, docs, chat
Architectural instinct, clarity of mind
Matching people to team shapes
Once the person shape is read and the team shape is known, the match becomes easy to see on paper. The table below shows the main person shapes, the teams they fit best, the teams they fit worst, and what actually happens when someone lands in the wrong seat.
Person Shape
Best Fit Team
Poor Fit Team
What Happens in the Wrong Seat
Deep focus, long writer
Platform / Complicated-subsystem
Stream-aligned
Burns out from interruptions, goes quiet
Fast switcher, live talker
Stream-aligned / Enabling
Complicated-subsystem
Feels starved of feedback, drifts into other teams' work
Teacher, social bridge
Enabling
Platform
Gets bored, leaves, or turns into a silent bottleneck
Stubborn problem chewer
Complicated-subsystem
Enabling
Feels interrupted, never finishes deep work
Why the match predicts performance
Friction is the real cost
Most team pain is not about skill, is not about effort, is not about attitude, it is about friction, and friction comes from putting the wrong shape in the wrong slot. A deep-focus person dropped into a stream-aligned team will burn out from interruptions, will start missing small signals, and will slowly go quiet, and the telemetry shows this drift weeks before the person says anything. A high-switching person dropped into a complicated-subsystem team will feel starved of feedback, will start poking into other teams' work, and will slowly drift into distraction, and the telemetry shows that drift too, in the same quiet way.
Measuring the gap
Axiom Cortex lines up the shape of the person against the shape the team actually needs, not the shape the org chart says the team needs, and the gap between those two shapes is the thing that predicts performance. The table below turns the gap score into a simple action map.
Gap Size
What It Means
Predicted Outcome
Recommended Action
Small
Person shape matches team shape
Growth in place, compound output
Leave alone, give scope
Medium
Some drift between shapes
Friction at first, can recover
Coaching, pairing, stretch tasks
Large
Wrong team type for the person
Burnout, drift, silent damage
Move the person, not the process
How the two systems divide the work
Team Topologies and Axiom Cortex answer different questions, and neither one can answer the full question alone. The table below shows where each system does the heavy lifting and where they hand off to each other.
Question
Team Topologies Answers
Axiom Cortex Answers
What shape should the team be?
Yes, with four named team types
No, not its job
What shape is this person?
No, not its job
Yes, read from real telemetry
Do these two shapes match?
Partly, through cognitive load
Yes, with a gap score
Will the team perform?
Sets the right conditions
Predicts outcome before damage
The bigger idea
Team design and people design are the same problem, and treating them as two different problems is why most reorgs fail, why most hiring plans miss, and why most performance reviews feel unfair. Team Topologies gives you the grammar of team shapes, Axiom Cortex gives you the grammar of human shapes, and the match between the two is where performance actually lives.
When the shapes line up, the team moves without being pushed, the work flows without being managed, and the output compounds without being forced, and that is what people mean when they say a team has clicked. When the shapes do not line up, no process saves the team, no tool saves the team, no amount of effort saves the team, because the friction is baked into the structure and the structure is invisible until you measure it. The signal is always sitting there in the telemetry, waiting to be read, and the job of the system is to read it early enough to act before the drift turns into damage.