Your team isn't short on effort.
Something their work depends on is closed — and it's rarely the thing they've been working on.
Teams that backslide usually aren't short on skill or goodwill. Something their work depends on is closed — and it's rarely the thing they've been working on.
Half of these conditions are human: whether people raise the inconvenient thing, whether the person who has to live with a decision can make it. The other half are informational: whether the team shares one version of where the work stands, whether what gets raised ever comes back resolved.
Our programs read both sides, identify which condition is binding, and hand the team the instrument so they can read themselves again in six months.
A note on the word "gate." We use it throughout. In Growth Geometry, a gate is an operating or flow condition — the circumstance required for work to move from one part of the system to the next. Twelve of them, six on each side.
Why the gains don't hold
Most team work produces a good two months. People are more candid, meetings run better, the room feels different. Then it drifts back.
The usual explanation is that the habits didn't stick — so the answer is a refresher, and the cycle repeats. But a habit that requires continuous effort to maintain is usually compensating for something structural. The team was working around a missing condition, and the workaround was expensive. When attention moved elsewhere, the workaround stopped.
That's why we read conditions before we build habits. If something required is absent, no amount of skill or goodwill substitutes for it — that's what makes it a condition rather than a factor. And if it's present but thin, more training isn't the remedy either.
Actionable understanding
The program is named for a tension, not a destination.
Actionable pulls toward coherence, commitment, and getting on with it. Understanding pulls toward variation, possibility, and looking again. Both are right. Teams don't resolve this one — they hold it, and the holding is the work.
It matters because the two failures look nothing alike from inside. A team weak on both is visibly struggling and usually knows it. A team excellent at one and blind to the other feels effective, moves fast or deliberates well, and is the more common and less visible failure.
Twelve questions. Six minutes. Alone, before anyone compares.
Rate your team as it operates today, not as you'd like it to be. One is really bad, four is OK, seven is ideal.
And the scale keeps going. Eight is a bit too much. Nine is over the top — because every condition here can be underdone, and every one can be overdone, and those are different problems with opposite remedies.
Four of the twelve
The right-hand column is the part most instruments leave out. A team that scores a nine on candor is not a healthy team — it's a team where everything is aired and nothing gets settled. Scoring it as excellent would hide that.
What the answers mean
Thin and Closed score the same in any arithmetic — below the line is below the line. We report them separately because they call for opposite work. Thin is a dosing problem: the condition exists and there isn't enough of it. Closed is structural: it isn't there, and more effort won't produce it.
This is a pre-read, not a reading. It identifies candidate constraints — the conditions most likely to be binding, based on twelve questions. Confirming one requires a completed field card and a demand profile for your team's actual work. We'd rather tell you that than hand you a result we can't stand behind.
Why balanced teams still get stuck
There's a tension underneath several of the twelve: quality of focus against quality of relationships.
Weight focus too heavily and the team stops raising things that slow the work. Weight relationships too heavily and things get raised gently enough that nothing changes. From outside, both look identical — a team that doesn't correct itself — for opposite reasons.
Here's the part worth knowing. A team can be perfectly balanced on that tension, genuinely candid and genuinely kind, and still fail to correct — because raising something and closing it are different conditions, and the second one lives on the evidence side. If nothing carries a raised issue back to the person who raised it, the candor was real and it went nowhere.
That's the case for reading both sides. A team-development program that only works the human side can produce a more open team that corrects no better than before.
After the pre-read
A conversation about the spread
The interesting result is rarely the average. It's where your team disagrees with itself — four people rating the same condition at 3, 5, 7 and 9 is a finding in its own right, and usually the most useful one.
ATP
Our team program, built around accurate self-awareness, team awareness, and shared direction. Scoped to the condition that's actually binding rather than run as a standard curriculum — which is why the pre-read comes first.
Then the levers
Once a binding condition is addressed, the work shifts from removing constraints to building range — including the emotional-intelligence work that helps a team hold a tension under pressure rather than defaulting to its preferred move. That's the second half, and it doesn't work in the other order.
What you won't get
No composite score. A single number lets a strength hide the thing that's actually stopping you. That's the arithmetic of an average, and it's the opposite of what a constraint is.
No ranking against other teams. Whether a condition is thin depends on what your team's work demands of it. Two teams at the same number aren't in the same position, so we don't pretend the comparison means something.
No personality typing. This reads conditions in how a team operates, not traits in the people on it.
If you'd rather talk it through first — what your team keeps getting stuck on, and whether any of this fits — that's a fine place to start.
Team Effectiveness is the team-level entry read for Growth Geometry, AgilEdge's framework for finding what's holding an organization's ceiling down. Instrument version: GGM v1.1.1.