The expensive problems happen between two people.
Throughline maps every working pair on a team, not every individual — so you can see which frictions are structural, and which are about something that happened in March.
- Pair guidance from two people up
- Team read from about four
- Every combination, not a sample
- Mutual by construction
A report describes one person. The problem is usually a pair.
Hand a team eight PDFs and you've given them eight descriptions and twenty-eight unanswered questions. The useful unit isn't “Marta is deliberate” and “Yusuf is decisive” — it's what happens on Thursday when Marta wants another day on the estimate and Yusuf has already told the client it's fine.
Where it works
Every pair has a genuine complementarity, and it's usually the thing neither person notices because it costs them nothing. Naming it is most of what a team offsite is trying to do.
Where it slips
And a predictable failure. Not a personality clash — a difference in pace, or in how much cushioning each person expects, compounding across a hundred small exchanges.
The tell
The observable early signal, so you can catch it in week two rather than at the exit interview. For most pairs it's something small and specific, like a colleague going quieter over a month.
The thing your team has too much of is hard to see from inside.
A team of similar styles feels easy, agrees quickly, and fails in one predictable direction. The read names the direction before it costs you a quarter.
Three of your five profiles sit low on assertiveness. In a disagreement this team will reach agreement quickly, and it will not always be real agreement.
Evidence
- The strength that becomes a blind spot
Source
Over-represented
Consented profile
One person is doing the reconnection work after every disagreement. It isn't in anyone's objectives, it's invisible in a review, and it's the first thing to go when they're stretched.
Evidence
- The person absorbing what nobody assigned
Source
Carrying the gap
Consented profile
A team's worst week is usually predictable from its mix.
Four shapes, and the specific way each one comes apart. Most teams recognise themselves in one within about ten seconds.
Decision-rich, follow-through-poor
Plenty of decisions, made fast, several of them contradicting each other. Nobody wants the unglamorous half of the work, and the decisions quietly stop meaning anything.
Who on this team will actually do the follow-through, and have we asked them?
Everything is exciting until Thursday
Wonderful at the start of a problem. The energy leaves the moment the shape is settled, which is exactly when the work begins.
What did we commit to three weeks ago that nobody has mentioned since?
Nobody says the difficult thing
Pleasant, durable, and slowly accumulating unsaid objections. The problem arrives fully formed, months after it could have been fixed cheaply.
What does this team agree about in the room and disagree about afterwards?
Each of the six mixed pairings has its own read, with moves for both sides — every pairing mapped.
See how you work in six minutes
Free, no sign-up. Then bring your team in, free for five people.
A team map your team will trust.
Composition guidance shows you how the team is shaped and where it is likely to strain, so you can act early. It describes the team rather than ranking the people in it, which is exactly why people are willing to be in it.
How we keep it trustworthy- No ranking of team members against each other
- No “you need one of each” composition rules — the evidence doesn't support them
- No hiring or staffing recommendation
- No profile for anyone who hasn't opted in; the team read says so rather than guessing
What people ask before they try it.
Two, for pair guidance — which is where most of the value sits. The team map needs about four before its observations mean anything, because below that it's describing a coincidence rather than a shape.
You don't need full coverage, and pushing for it tends to produce compliance rather than consent.
Also worth reading
Bring the pairing that's been grinding for months.
Twenty minutes, live, on a demo team. Most “personality clashes” turn out to be a pace difference with a ten-minute fix.
See pricingTell us what you’re working on.