The one who moves first
Fire · Vermilion Bird 朱雀You see what could be, not only what is. When a team is stuck, you are usually the one who puts a new option on the table, or simply starts something rough so there is a thing to react to.
You are comfortable acting before the picture is complete. Most people are not. That is the contribution.
Early. Before the direction is set, when the team is circling and nobody wants to be wrong first. You break inertia at a cost other people find high and you find low.
Also: when the obvious answer is available and nobody has asked whether there is a better one.
You can over-generate and under-finish. New ideas are more interesting to you than the one you had last week, and a team can only carry so many open threads.
Watch for the moment when starting something new is a way of avoiding finishing something old. It rarely feels like avoidance from the inside. It feels like momentum.
Also watch: your speed can read as dismissal. When you move past someone's concern quickly, they do not experience it as confidence. They experience it as not being heard.
Fire ignites, and fire consumes. The same property that lets you start things without certainty is the one that leaves things half-burned when your attention moves. The discipline is not to burn less. It is to choose where.
Do not just spark the idea. Light the path.
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.
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.
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.
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.