Aligner
The one who keeps a team a team
Wood · Azure Dragon 青龍What you do
You build shared understanding. You notice when two people think they agree and do not, and you say so. You restate an idea in words a different person can act on. When friction shows up, you make sure it actually gets resolved rather than left running.
This is not niceness. Done well it involves saying uncomfortable things earlier than other people would.
Where your effort goes furthest
When a team is forming, when it is under stress, and at every handover. Anywhere meaning gets lost between people.
Also: when the team is about to make a decision that half the room understands differently from the other half. You are usually the only one who has noticed.
Your edge
You can over-accommodate and under-direct. Holding a group together is real work, and it can become a way of avoiding a position of your own.
Watch for the meeting where you spoke about everyone's view except yours. And watch for agreement you engineered rather than reached — a team that agrees because you smoothed it will not hold under pressure.
Also: you carry things. Tension you absorbed and never named has a cost, and it is usually paid later and by you.
What to ask for
- From a Validator: whether the agreement you built is actually sound
- From an Initiator: a bolder position than the one the group settled on
- From a Navigator: the sequence, so alignment turns into movement
Questions worth sitting with
- What do I actually think, separate from what the team needs?
- Whose stress am I carrying that is not mine?
- Which conversation am I avoiding to keep things comfortable?
The elemental note
Wood grows toward whatever light it finds, which is how it connects everything, and how it ends up spread thin. Growth in every direction is not growth. Pick a direction.
Connection is power. Clarity has to lead it.
Reading your four scores
Your scores are not a type
You get four numbers, not a label. Read the shape, not the winner.
A wide spread — one score clearly above the rest — means you have a pronounced default. Useful to know, and worth deliberately covering the low end.
A narrow spread — all four close together — means you adapt to what the team needs rather than running one style. That is genuinely different information, not a failed result.
If your top two are close
Your report will say so when the gap between your top two is smaller than the measurement error. That is not hedging. It means those two would plausibly swap if you took this again next week.
Read them as a pair. People whose top two are close usually recognise both descriptions, and the interesting question is which one the current team is pulling out of you.
On taking it again
Working styles shift with context. If you take this in a season where you are leading rather than building, or building rather than shipping, you should expect the shape to move.
That is the instrument doing its job. A measure of what you do in teams ought to respond to which team you are in.
Using this with your team
The report is for one person. Most of the value is in the conversation between four.
Map it together. Put everyone's top two on one page. Look for functions nobody covers.
Name the gap out loud. A gap is not a verdict on the team. It is a job nobody has picked up. Decide who covers it deliberately, knowing it is not their default and will cost them more effort.
Use it before conflict, not after. The language is most useful when nobody is annoyed yet. Once a team is in conflict, role labels become ammunition.
Do not use it to allocate work permanently. “You are the Navigator, so you do the plan” is how people get trapped in the thing they are already good at. The point is coverage, not casting.
TeamFlow is in active validation. Your four scores are calculated correctly and describe how often you report doing each set of behaviours. What they predict about team performance has not yet been established. Treat this as a starting point for a conversation, not a verdict.