Validator
The one who checks before the team commits
Metal · White Tiger 白虎What you do
You test whether an idea holds up. You name what the plan is taking on faith. You ask what evidence would show whether this works, and you look for the information that would prove the team wrong rather than right.
When the group agrees quickly, you are the one who asks what everyone is assuming.
Where your effort goes furthest
Just before commitment. After the excitement and before the money, time, or reputation is spent. That window is short and you are the one who uses it.
Also: when standards are quietly slipping and everyone has stopped noticing because they see it every day.
Your edge
You can over-critique and under-build. Finding the flaw is faster than proposing the fix, and a team can absorb only so much friction before it stops bringing you things early.
Watch for the pattern where you are consulted last, on purpose. That is not people avoiding rigour. That is people protecting momentum from a cost they have learned to expect.
Also: your work is invisible when it succeeds. The problem you caught never happened, so nobody saw it. That is genuinely unfair, and it is worth naming rather than resenting.
What to ask for
- From an Initiator: the version of this that is worth the risk
- From an Aligner: how your point will land, and how to make it land better
- From a Navigator: what “good enough to ship” looks like this week
Questions worth sitting with
- Have I offered clarity, or only critique?
- What does “good enough for now” look like here?
- Am I protecting a standard, or holding on to control?
The elemental note
Metal sharpens, and metal cuts. The same edge that finds the flaw in an idea finds it in a person if you are not paying attention. Sharpen the work. Not the room.
Excellence matters. Progress needs room too.
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.