The Team Trade-Off Matrix
What this does: Shows you, on one page, where putting people together makes your organization smarter and where it makes it dumber. Most leaders only see one side of that equation.
The business outcome: You stop guessing about why a team’s underperforming and start seeing the specific dimensions where combining people created problems — so you can fix the right thing instead of restructuring blind. This saves you on re-hiring, re-training, and consultants.
Quickstart
Pick any team, department, or cross-functional relationship in your organization. For each of the three rows (See, Understand, Reach), ask: did combining these people expand, shrink, or reshape the organization’s capability on that dimension? Fill in the matrix. The cells that surprise you are where the diagnostic value lives. For detailed instructions see “How to use it” below.
Template
| Contracted (lost by combining) | Neutral | Expanded (gained by combining) | |
|---|---|---|---|
| What we can SEE | |||
| What we can UNDERSTAND | |||
| What we can REACH |
Fill each cell with specific observations, not general impressions. “We lost visibility into customer sentiment because field reports get summarized before they reach product” is useful. “Communication is bad” is not.
You can (and should) have multiple items in each cell, so you can choose the most impactful.
A note on reshaping: Sometimes a combination doesn’t clearly expand or contract — it changes the shape of the capability. A committee of specialists gains depth but loses generalist breadth. When this happens, you’ll see entries in both the Contracted and Expanded columns for the same row. That’s reshaping — it’s not a problem to fix, just a trade-off to be aware of.
How to use it
Step 1: Pick the combinations you want to diagnose. This works at any scale — a two-person partnership, a department, a cross-functional team, the whole company. Start with whatever’s causing you the most pain.
Step 2: Walk each row.
What we can SEE (expanded / contracted / reshaped):
- What information does this group receive that no individual member could get alone? That’s expansion.
- What information do individual members have that the group somehow can’t access? That’s contraction. This is the “sales knows but product doesn’t” pattern — the signal exists inside the organization but doesn’t reach the people who need it.
- What information reaches the group in a different form than it reaches individuals? That’s reshaping — not clearly better or worse, just different. Note it in both the Contracted and Expanded columns.
What we can UNDERSTAND (expanded / contracted / reshaped):
- What can this group figure out that no individual could? That’s expansion. A team that solves problems none of its members could solve alone.
- Where is the group’s collective understanding worse than its best individual? That’s contraction. Groupthink. Decisions by committee that are dumber than what the smartest person in the room would have decided alone.
- Where does the group understand differently — deeper in some areas, shallower in others? That’s reshaping.
What we can REACH (expanded / contracted / reshaped):
- What can this group do that no individual could? That’s expansion. A company that can build and sell a product because it combines people who can build with people who can sell.
- Where is the group’s ability to act less than its best individual’s? That’s contraction. Diffusion of responsibility. Nobody acts because everybody assumes somebody else will.
- Where does the group’s reach have a different shape? That’s reshaping. Specialists who gained depth but lost generalist flexibility.
Step 3: Look at the contraction cells. These are where intelligence is getting trapped. For each one, ask: is this a See problem (the signal isn’t arriving), an Understand problem (the signal arrives but nobody can make sense of it), or a Reach problem (everyone understands but nobody can act)?
Step 4: Check whether the contractions are actually problems. Not every contraction is bad. If your sales team’s individual customer relationships get compressed into a summary report before reaching the product team, that might be deliberate filtering — not every customer request should drive the roadmap. The question isn’t “is there a contraction?” It’s “is this contraction hurting us?”
Example
A CEO runs the Team Trade-Off Matrix on his executive team — the five VPs who report to him. He expects to find the problems in his engineering department, where a recent project missed its deadline. Instead, the surprising finding is at the C-suite level itself.
| Contracted | Neutral | Expanded | |
|---|---|---|---|
| SEE | Each VP gets the same board reports, same financials | The exec team collectively covers five domains — sales, product, engineering, ops, finance — that no single VP could monitor alone | |
| UNDERSTAND | Each VP defers to the others’ domains without checking. The VP of Sales doesn’t question the VP of Engineering’s timeline estimates. The VP of Engineering doesn’t question the VP of Sales’ pipeline forecasts. Each assumes the other has it covered. The collective understanding of cross-functional risk is worse than what any individual VP would produce if forced to evaluate the whole picture alone. | The group can evaluate strategic decisions that require multiple domain perspectives — but only when explicitly forced to by the CEO | |
| REACH | Cross-functional decisions require consensus, which means the group’s ability to act quickly is less than any individual VP’s. Each VP can make fast decisions in his domain; the group can’t make a fast decision across domains. | The exec team can commit the whole company to a strategic direction — something no individual VP can do |
The CEO expected the problem to be in engineering. The matrix shows the problem is in his own leadership team. The Understand contraction — each VP deferring to the others without checking — means nobody on his team is modeling cross-functional risk. The missed engineering deadline wasn’t an engineering failure; it was an exec team failure to catch that the engineering timeline depended on a sales commitment that the VP of Sales knew was shaky but never flagged, because he assumed the VP of Engineering had accounted for it.
The fix isn’t firing anyone or restructuring the org chart. It’s a coupling fix at the exec level: a monthly cross-functional risk review where each VP is explicitly asked to pressure-test the others’ assumptions. The intelligence was inside the room the whole time. It was trapped because the team’s structure encouraged deference instead of challenge.
Where to learn more
Other tools:
- The Trapped Intelligence Diagnostic — Once you’ve found a contraction, use this to pinpoint exactly where the intelligence is stuck.
- The Franz Ferdinand Check — If a Reach expansion is making you nervous (more authority than understanding), this diagnoses the blast radius.
- The Capability Reality Check — If you suspect the team doesn’t know what it’s capable of, this finds the gap.
Vocabulary: Composition, Trapped Intelligence, Capacity, Realized