Taking the TeamFlow Assessment

By Kasper-Tanakrit Sermsuksan · Global Venture I: Playbook · Block B

You are here: B-03 · Block B · Understanding Yourself · article 3 of 8 · Form A+B · Next: B-04 The Personality Paradox

In short: The TeamFlow™ assessment is a free team-role test that takes about ten minutes: 60 short statements, shown one at a time in random order, each rated on an agreement scale. You need no account, and your result appears straight away — four scores, one for each role (Initiator, Aligner, Validator, Navigator), sorted into three bands. It is a development tool, not a selection tool: it helps a team balance itself, it does not label or pick people. Answer for how you actually behave in a team under pressure, then put your team's results next to your 4H archetypes to see what is covered, what is missing and who will step in.

Ten minutes. That is all the assessment takes.

What you do with the result is what takes the rest of the project.

Most people take a test like this, read the flattering paragraph, screenshot it, and move on. I would call that a waste of ten minutes.

The value of TeamFlow is not in learning your scores. It is in the conversation your team has once everyone's scores are on the table.

So here is how I would take it, read it, and use it to build a team that covers everything.

Try it in 10 minutes: take it now

This whole article is a tool, and the tool takes ten minutes. Find a quiet spot, open the assessment (step 1 of the next section), picture your last real team, and answer in one sitting. Read the rest of this page with your result in front of you.

How do I take the TeamFlow assessment?

1. Open the assessment: teamflow.seabridge.space. It is free and needs no account. (The Google Form used in earlier years is retired. If you took that earlier version, take this one.)
2. Give it ten quiet minutes. Not between classes, not on the train. One sitting.
3. Picture a real team. Think of the last project where something was at stake — a club event, a hackathon, a group assignment, a job. Answer for how you behaved there.
4. Rate each statement. There are 60, shown one at a time in random order. For each one, choose how much you agree. There are no right answers, and no statement is a trick — but some are worded the other way round on purpose, so read each one properly instead of clicking the same point every time.
5. Answer for who you are, not who you want to be. If you secretly wish you were the calm Navigator but you are the person who starts five things at once, say so. A flattering result is a useless result.
6. Go with your first instinct. Overthinking pushes your answers toward the "right" ones.
7. Save your result. It appears on screen as soon as you finish. Save or screenshot your four scores and bands, so you can open them with your team.
8. Take it early. I recommend doing it before your team forms, or before its first real piece of work. The result is most useful at the start of the team conversation, not the end.

What is a team role test — and what does TeamFlow measure?

A team role test asks how you behave when you work with others, and tells you which contribution comes most naturally to you.

It does not measure how smart or how good you are. I think of it as describing where your energy goes.

TeamFlow™ is the version we built at SEA Bridge, for venture teams. It measures four roles, and together they make the work cycle of an innovation team: start it, align people, check it holds, drive it home.

• Initiator — In one line: Moves first when the path is unclear — The three facets the statements cover: Ideation · Possibility framing · Momentum starting
• Aligner — In one line: Keeps a team understanding each other — The three facets the statements cover: Perspective taking · Translation · Cohesion repair
• Validator — In one line: Checks before the team commits — The three facets the statements cover: Assumption surfacing · Evidence seeking · Standard setting
• Navigator — In one line: Turns intent into a route and tracks it — The three facets the statements cover: Sequencing · Resource realism · Follow-through tracking

Each role has 15 statements, spread across its three facets. Your score for a role is the average of its 15 answers — on the six-point form, a number between 1.00 and 6.00.

That is why you get four scores rather than one type. Everyone does all four kinds of work to some degree.

It is built for founders and co-founders, family business successors, students and early-career professionals in fast-moving teams. It is not a personality test, and it is not a hiring screen.

And I want to be honest about where it stands:

TeamFlow is in active validation. It is a development tool, not a selection tool.

How do I read my TeamFlow results?

When I read a result, I go in this order.

Start with the three bands. Your four roles are listed in order, without numbers, in three groups:

• Where your effort goes furthest — your strongest role or roles. This is where you contribute most easily.
• Also strong — roles you can carry when the team needs you to.
• Where you'll want backup — the part of the cycle where you should pair with someone. Not a weakness grade. A note on who to ask.

Then check whether your top two are close. If the difference between your top two scores is within the assessment's measurement error, your result says so: "Your top two are close enough that they may swap on a retake."

My advice: read both as your strengths. Do not argue with yourself about which one is "really" you.

Then read your strongest role's shadow, and its opposite. Roles opposite each other on the cycle — Initiator and Validator (generate versus test), Aligner and Navigator (people versus process) — are the pairs that most need each other.

• Initiator · Fire — What it is not: Risk appetite, extraversion, optimism — Under pressure, watch for…: jumping between ideas, starting more than the team can finish — Its opposite on the cycle: Validator — tests what you generate
• Aligner · Wood — What it is not: Agreeableness, niceness, conflict avoidance — Under pressure, watch for…: smoothing over a disagreement instead of repairing it — Its opposite on the cycle: Navigator — turns shared understanding into a route
• Validator · Metal — What it is not: Pessimism, negativity, disagreeableness — Under pressure, watch for…: testing so long that the team never commits — Its opposite on the cycle: Initiator — gives you something worth testing
• Navigator · Water — What it is not: Conscientiousness in general, rule-following, doing the work personally — Under pressure, watch for…: holding the route too tightly, or doing the work yourself instead of resourcing it — Its opposite on the cycle: Aligner — keeps the people with the plan

The elements (Fire, Wood, Metal, Water) are a memory aid, not part of the score. The full role definitions are in TeamFlow™ — Your Best Role in the Innovation Team.

Here is the one thing I ask everyone to do with the result. Mark one facet of your strongest role that is uncomfortably accurate, and one that does not sound like you at all.

Those two lines are worth more than the rest.

What should I not do with my result?

• Do not use it as an excuse. "I'm a Validator, so I criticize" is not insight. It is a shadow with a label on it — and a Validator is not a critic anyway.
• Do not use it to select people. It is a development tool, not a selection tool. TeamFlow helps mix teams; it never decides who is in or out. Do not pick, reject or rank teammates by their scores.
• Do not treat it as fixed. It shows today's tendencies. Your scores can shift with experience and practice.
• Do not trust it alone. Every self-report reflects how you see yourself today. Ask one teammate: does this match the person you work with? If they disagree, treat the result as a hypothesis, not a verdict. (The Personality Paradox explains why that question matters.)
• Do not translate an old result. If you took the earlier version, its roles do not map one-to-one onto these. Retake the new version.

What should I write down after the assessment?

In my experience, a result you never write about is a result you forget. I recommend writing four things, while it is fresh:

1. Your four scores and your bands — and, if your result says your top two are close, both roles.
2. One facet that felt uncomfortably accurate, and one real situation where you saw it — once where it helped a team, once where it caused friction.
3. Your "backup" role, and who could back you up — a teammate, a classmate, a mentor.
4. Once your team is formed: the team's coverage around the cycle, and the name next to each gap.

How do I use TeamFlow to form and balance a team?

TeamFlow tells you how each person works. The 4H Founder Archetypes tell you what each person brings — Hustler, Hacker, Hipster or Hunter.

In my view, you need both to see a team clearly.

1. Put everyone's results on one page. Name, the role(s) in "Where your effort goes furthest", the role(s) in "Where you'll want backup", primary H.
2. Check TeamFlow coverage around the cycle. Does every part — start it, align people, check it holds, drive it home — sit in at least one person's top band? Which role appears twice? Which is missing?
3. Check 4H coverage. Same question for Hustler, Hacker, Hipster and Hunter.
4. Look for collisions. Two strong Initiators will compete for direction. Two strong Validators can stall every decision. Plan for it.
5. Decide who covers each gap. Look first for someone who has that role in "Also strong". Otherwise someone stretches into it on purpose, or you borrow it from outside the team (a mentor, a classmate, a friend from another field). Write the name down.
6. Put it in your team agreement — the roles, time and ownership conversation in Team Formation Science.
7. Revisit it halfway through. Has anyone drifted into a role that is burning them out?

An illustrative example. A four-person team finds it has an Initiator-Hunter, a Validator-Hacker, an Aligner-Hustler and a second Initiator who is a Hipster. Nobody has Navigator in their top band.

The Validator-Hacker has Navigator in "Also strong" and agrees to stretch into it for the first four weeks, with a shared task board so the route and the deadlines are visible. The two Initiators agree that one owns product direction and the other owns brand.

The gap is named, owned and dated. To me, that is a balanced team — not a perfect one.

That is how I would make a mixed team work. TeamFlow helps you mix a team well; it never decides who is in or out.

Frequently asked questions

How do I take the TeamFlow assessment?
Open the assessment, give it about ten quiet minutes in one sitting, rate the 60 statements for how you actually behaved in a real team, and save your result.

Is the TeamFlow team role test free?
Yes. It is free, needs no account, and shows your result as soon as you finish.

What if my top two roles are close?
Your result will say so: they may swap on a retake. Treat both as your strengths, and read both role descriptions.

Can I retake it?
Yes, but not to chase a "better" answer. Retake it later to see whether how you work in a team has shifted. If you took the earlier version, retake the new one — the old results do not map onto the new roles.

Is TeamFlow used to pick teams?
No. TeamFlow is not a selection tool. The result is one input to the team conversation — it helps a team balance itself, and it never decides who is in or out.

✦ A Note for Global Venture I Students · Block B: Understanding Yourself · Form A+B

Take the assessment in Week 1 and bring your result. Teams are confirmed in Week 2 (8-week format) or by Week 4 (16-week format), and the first team conversation starts from these pages.

Your result is not graded. What you do with it is: your reflection on it is part of Form A+B, which is graded with your other block forms. In Form A+B, write the four points in "What should I write down after the assessment?" above. The team's coverage and the name next to each gap also go in your team's Venture Log.

Teams are mixed by design, and the balancing steps above are how you make a mixed team work. If you want to request your own project with your own team, bring your one-page TeamFlow and 4H summary with your request. Revisit it at the mid-point.

Do this before class:

1. Take the TeamFlow assessment (teamflow.seabridge.space) and save your four scores and bands.
2. In Form A+B, write the four points in "What should I write down after the assessment?" above.
3. Venture Log: once your team is confirmed, add the team's TeamFlow and 4H coverage and the name next to each gap.

Pre-class check (in Form A+B):

1. What does your strongest role do well, what is it not, and what does it do under pressure?
2. Which role sits opposite yours on the cycle — and who on your team could be that person for you?
3. Why should a team check TeamFlow and 4H coverage together?

AI: write your reflections in your own words. If AI helped with anything, say what in the form's "AI used for:" field.

Your progress: Team readiness to level 3: name your team's skills, gaps and a plan to fill them. How we measure progress

Skills you practice: Motivation and self-awareness · self-awareness and self-efficacy · working with others.

Keep reading

• TeamFlow™ — Your Best Role in the Innovation Team — the framework behind the assessment
• The Personality Paradox — next in Block B: why your result is only half the picture
• The 4H Founder Archetypes
• Team Formation Science

All articles in Block B · Understanding Yourself

• B-01 The Global Entrepreneurial Mindset
• B-02 TeamFlow™
• B-03 Taking the TeamFlow Assessment (you are here)
• B-04 The Personality Paradox
• B-05 FISHE Capital™ × CSTO™ (Personal Edition)
• B-06 The 4H Founder Archetypes
• B-07 The Culture Map
• B-08 Team Formation Science

Further reading

• Marks, M. A., Mathieu, J. E., & Zaccaro, S. J. (2001). A temporally based framework and taxonomy of team processes. Academy of Management Review, 26(3), 356–376. https://doi.org/10.2307/259182 — the team-process research behind the 2027 version.
• Belbin, R. M. (2010). Team roles at work (2nd ed.). Butterworth-Heinemann. — a different, widely used team-role model, if you want to compare.

About the author: Kasper-Tanakrit Sermsuksan is the Founder of SEA Bridge and a Visiting Lecturer in Computer Engineering and Digital Technology at Chulalongkorn University's Faculty of Engineering. Learn more →