Skip to content after assessment

Assessment loading

If the interactive assessment does not start, you can still read the methodology and evidence below, then try again later.

Browse all assessments

Chart Your Team Flow Profile

Your Team Flow Assessment

Chart Your Team Flow Profile

A 20-scenario self-report that groups your selected answer points across five editorial dimensions. It is not a validated measure of an underlying trait.

20 scenarios5 dimensions4 forced choicesno neutral option

Topic context from the cited source; it does not validate this questionnaire or its score thresholds.

— Edmondson (1999)

What your answers coverPsychological SafetyHow safe people feel to speak up, disagree or admit mistakes.Role ClarityHow clearly people know what they own and who decides what.Challenge-Skill CalibrationWhether people's work stretches their abilities without overwhelming them.Feedback EnvironmentHow regularly honest, specific feedback flows and gets acted on.Trust CapitalWhether people follow through on commitments and back each other up.

Team Flow Assessment: What's Blocking Your Team's Collective Performance?

Twenty forced-choice scenarios are summed into editorial answer-score bands; the result does not diagnose or measure an underlying trait.

~7-9 min · Item answers and results stay on this device · Share links and invite cards carry no scores

Answer for how your team actually works today, not the culture you're building toward.

A structured self-reflection — not a diagnostic.

This assessment is a structured self-reflection tool and educational resource — it is not a validated diagnostic and is not a substitute for clinical or professional evaluation, including occupational psychology or organisational consulting. Every dimension insight references peer-reviewed literature for educational context only. If you have concerns about your team's functioning, consult a qualified professional. Self-report instruments of this kind have no validated retest interval; the four-to-six-week Second Reading is a sensible practice, not a clinical standard.

Welcome back — you have a profile in progress.

Your profile

0 / —

Profile

Dimension profile

The Reading

Strongest dimension

Learn more →

Open the full dossier

Dimension log

This assessment is a structured self-reflection tool and educational resource — it is not a validated diagnostic and is not a substitute for clinical or professional evaluation, including occupational psychology or organisational consulting. Every dimension insight references peer-reviewed literature for educational context only. If you have concerns about your team's functioning, consult a qualified professional.

Your answers

Team Flow Assessment: What's Blocking Your Team's Collective Performance?

This literature-informed structured self-reflection adds up what you select about how you see your team's psychological safety, role clarity, challenge-skill calibration, feedback loop speed, and trust capital. It does not measure your team or predict its performance — it reflects your own perception only.

Interactive scoring requires JavaScript. You can still read every question and answer option below.

When something goes wrong in your team, how is it typically handled?
- Mistakes are punished or publicly criticised — people work to conceal them
- Blame tends to surface, and people become guarded afterward
- Most issues handled matter-of-factly, though visible failures carry some tension
- The team treats failures as shared learning events and moves forward without blame
How easy is it for team members to challenge a decision or contradict a colleague's view, even when it might be unwelcome?
- Too risky — team members stay quiet rather than bear the social cost
- Uncomfortable — concerns are generally watered down or held back
- Usually fine, though a few topics or people make candid pushback feel risky
- Easy — people routinely challenge ideas and raise concerns without fear of looking bad
When your team faces something genuinely new or uncertain, what does the honest response tend to look like?
- We project confidence — the team moves forward decisively and doesn't dwell on what we don't yet know
- We tend to default to what's worked before rather than risk being seen fumbling with something unproven
- We're fine trying new things and admitting gaps when the stakes are low, but hold back when more is riding on it
- We say plainly when we don't know something, and trying unproven approaches is a normal part of how we work
How does your team treat each other when under pressure or tight on time?
- Pressure regularly triggers contempt, dismissal, or scapegoating
- Tension often affects interactions — voices get sharp and contributions get dismissed
- Mostly fine, though some people become short or cut off discussion under stress
- Pressure does not change the quality of respect — the team stays direct without becoming dismissive
When you describe how work and ownership are divided on your team, which comes closest to the honest answer?
- We stay flexible — nobody is locked into a fixed lane, so people pitch in wherever they're needed at the time
- Ownership is loose enough that the same items get picked up by whoever notices them, or get left for someone else
- Most areas have a clear owner, though a handful of things still get quietly re-negotiated each time they come up
- Every area has a single named owner, and people rarely need to check who is responsible before acting
How clearly does each team member know what excellent performance looks like in their specific role?
- Unclear — team members are unsure what they are actually accountable for delivering
- Vaguely — people know their tasks but not what separates good work from excellent
- Mostly — the general standard is understood, though the specifics blur in some areas
- Very clearly — each person knows the concrete standard their role is judged against
How often do team members face conflicting demands — expectations from different sources that pull in opposite directions?
- Chronically — most team members carry persistent, unresolved conflicting expectations
- Often — people frequently face competing demands they cannot easily reconcile
- Occasionally, though the team has informal ways of resolving them
- Rarely — when conflicts arise, they are resolved quickly and cleanly
How clearly does your team know who can make which decisions without escalating?
- Very unclear — decisions are frequently delayed, avoided, or made by the wrong person
- Unclear — decision-making often stalls while people check who has authority
- Mostly clear, with some grey zones that occasionally slow things down
- Very clearly — decision rights are understood well enough to act quickly within each role
How well does the difficulty of your team's work match the collective capabilities of the team?
- Severely mismatched — the work is chronically beyond or well below what the team can manage
- Poorly matched — the team is regularly either bored, overwhelmed, or split between the two
- Mostly matched, though some roles or tasks are either too easy or too demanding
- Well matched — the work is stretching but achievable, with a genuine sense of shared effort
How does your team typically decide who does what kind of work?
- We rotate people through different kinds of work on principle, so nobody gets typecast into just their strongest area
- Assignments tend to follow whoever's available more than who is actually strongest at the task
- Most work goes to whoever is best suited for it, though a few people are still regularly asked to cover work that doesn't play to their strengths
- Work consistently goes to whoever is genuinely strongest in that domain, even if it means the same person does that kind of work most of the time
How well does the work each person is assigned match their actual capability — stretching them without overwhelming?
- Poorly matched — assignments rarely land in anyone's productive stretch zone
- Often mismatched — several people are stuck in work well below or well above their level
- Mostly matched, though a few are routinely under-stretched or over-stretched
- Well matched — most people work at a level that stretches them without overwhelming them
How often do people on your team feel genuinely stretched by their work — rather than coasting on routine or drowning in overload?
- Rarely — the team mostly oscillates between boredom and overwhelm
- Occasionally — people more often feel under-used or over-loaded than well-stretched
- Fairly often, though spells of routine or overload interrupt it for some
- Regularly — most people feel productively stretched most of the time
How regularly do team members give each other honest, useful feedback on their work?
- Almost never — the team is effectively operating in a feedback vacuum
- Only in formal reviews — scheduled feedback happens, but honest in-the-moment input is rare
- Sometimes — feedback happens but mainly in structured settings or when prompted
- Regularly — useful feedback flows naturally without waiting for formal reviews
When feedback is given in your team, does it name concrete behaviours — or does it stay at the level of impressions and general results?
- Rarely useful — feedback is either absent, generic, or too personal to act on
- Often vague or evaluative — 'good job' or 'not quite right' without much guidance
- Mostly helpful, though it can be vague or focus more on results than behaviour
- Very specific and useful — feedback names concrete behaviours and gives people something to act on
How quickly does your team act on feedback — does information about what is not working reach people fast enough to influence the work in progress?
- Near-absent — feedback rarely translates into adjustment at all
- Slow — feedback is collected but changes are infrequent or arrive long after the relevant work
- Moderate — there is often a meaningful lag before feedback changes behaviour or direction
- Fast — feedback reaches people and influences work within days, not weeks or months
When you're unsure how your work is landing, what's the honest description of what you do?
- I trust my own read on the work — asking around for input feels like it undercuts my own judgment
- Asking for feedback feels a little exposing, so I mostly wait and see how things land on their own
- I'll take feedback if it's offered, but I don't often go looking for it myself
- I regularly ask people directly how my work is landing, without waiting for a formal review
When team members commit to something, how reliably do they follow through?
- Poorly — it is common to assume commitments will not be kept without tracking
- Inconsistently — follow-through is unreliable enough that people regularly factor it in
- Mostly — occasional missed commitments but they are acknowledged and recovered
- Very reliably — commitments are kept and people do what they say they will
When someone on your team is falling behind or struggling, what's the honest norm?
- We respect people's independence — everyone is trusted to manage their own workload without others stepping in uninvited
- People generally focus on their own work; pitching in for someone else isn't really the norm
- People will help, but it tends to depend on who's struggling and how visible it is
- People jump in and cover for each other without being asked, even before anyone raises a hand
When a colleague makes an unexpected or unfavourable decision without explaining it, how do team members tend to respond?
- Default to suspicion — unexplained decisions are read as bad faith
- Often assume self-interest or carelessness before knowing the reason
- Mostly give benefit of the doubt, though some quietly assume the worst at times
- Assume good reason — people extend benefit of the doubt and ask before judging
How well does your team hold each other accountable — naming when something is not working, constructively and without blame?
- Poorly — accountability is either absent or, when it surfaces, damaging to relationships
- Inconsistently — difficult conversations are avoided and performance gaps often go unnamed
- Mostly, though accountability is easier to apply to low-stakes issues than high-stakes ones
- Well — the team can name problems directly and hold each other to standards without drama

Appendix · Method & evidence Leadership · Case file

How this instrument works

This is a 20-item structured self-assessment of your team flow profile, read across 5 dimensions: Psychological Safety; Role Clarity; Challenge-Skill Calibration; Feedback Environment; and Trust Capital. Each item is a concrete scenario with four forced-choice responses — no neutral midpoint, so every answer commits to a direction — and response order is shuffled on every run to vary position; this implementation has not been tested for bias reduction. 5 of the 20 items are reverse-keyed — the attractive-sounding response is the structurally weak one — with wording intended to challenge socially desirable framing; this design has not been tested for bias reduction.

Scoring combines an overall reading with a per-dimension profile. Cascade flags compare configured dimension totals with editorial thresholds. They do not establish a compound risk and may not reflect the item-level pattern. The result bands are editorial guidance, not clinical thresholds: they organise the reading, they do not describe.

Every dimension insight cites peer-reviewed literature, and most answer reveals do — 8 sources back this instrument, each with DOI metadata supplied at build time; source relevance and claim interpretation remain editorial judgments. Compiled by the High Performance Culture editorial team. Instrument v1.1 · August 2026.

Read the full assessment methodology →

Items: 20
Dimensions: 5
Format: Forced choice, 4 options
Sources: 8
Instrument: v1.1 · August 2026

The 5 editorial answer groups

Psychological Safety

Strength here looks like treating errors and uncertainty as shared information — members openly raise concerns, admit mistakes, and experiment, because the interpersonal climate makes it safe to do so.

The vulnerable pattern: managing interpersonal risk before contributing openly — self-censoring in meetings, filtering feedback, and defaulting to safe positions rather than honest ones.

Sample itemWhen something goes wrong in your team, how is it typically handled?

First structural move: At the next team retrospective, name a recent mistake openly and frame it as a shared learning event — model the response you want, and watch others begin to follow.

Go deeperGlossary: Psychological Safety →Glossary: Groupthink →

Role Clarity

Strength here looks like operating with clear, uncontested ownership — each person knows their scope, their decision authority, and whose expectations to prioritise when demands compete.

The vulnerable pattern: navigating competing expectations and unowned territory — spending coordination effort on 'who owns this?' rather than on the work itself.

Sample itemWhen you describe how work and ownership are divided on your team, which comes closest to the honest answer?

First structural move: List the five most frequently confused ownership questions in your team. Assign each to a single owner before the next sprint — specificity, not a policy, is what clears ambiguity.

Go deeperGlossary: Delegation →Glossary: Accountability →

Challenge-Skill Calibration

Strength here looks like deploying people at work that stretches but does not overwhelm — goals are shared and understood, capabilities match responsibilities, and the team regularly reaches a state of collective absorption.

The vulnerable pattern: operating with misaligned roles, unclear goals, or chronic over- and under-challenge — preventing the collective engagement that makes team performance more than individual output.

Sample itemHow well does the difficulty of your team's work match the collective capabilities of the team?

First structural move: Ask each team member privately to rate current work challenge on a 1–10 scale this week. Share the distribution — anyone above 8 or below 4 is a calibration priority.

Go deeperProtocol: The Flow Triggers Protocol →Glossary: Flow State →Glossary: Yerkes-Dodson Law →

Feedback Environment

Strength here looks like giving and seeking specific, timely feedback as a natural part of work — so the team corrects course continuously rather than waiting for formal reviews to identify what is not working.

The vulnerable pattern: operating with a thin or slow feedback loop — people work without the adjustment signal they need, and the gap between 'something is off' and 'something has changed' stretches across weeks.

Sample itemHow regularly do team members give each other honest, useful feedback on their work?

First structural move: Introduce a two-minute feedback exchange at the end of every team meeting: one thing a colleague did that worked, one thing to adjust. Consistency matters more than depth.

Go deeperProtocol: The Radical Candor Protocol →Glossary: Radical Candor →Glossary: Difficult Conversations →

Trust Capital

Strength here looks like operating with high mutual reliability and honesty — commitments are kept, gaps are covered without being asked, struggle is surfaced without penalty, and performance gaps are named directly.

The vulnerable pattern: managing the cost of distrust — checking others' work, avoiding honest conversations, and absorbing problems that the team as a whole should be solving together.

Sample itemWhen team members commit to something, how reliably do they follow through?

First structural move: When you next notice a team member is overloaded, step in without being asked — and make it visible. One unprompted act of genuine backup sets a stronger norm than any values statement.

Go deeperGlossary: Five Dysfunctions of a Team →Glossary: Social Capital →

Questions, answered

Is this a diagnosis?

No. This assessment is a structured self-reflection tool, not a validated clinical instrument. Its result bands are editorial guidance, not clinical thresholds — they organise your answers into a readable profile; they do not describe a condition. If you have concerns about your health or wellbeing, speak to a qualified professional.

How were the questions designed?

Each of the 20 items presents a concrete scenario with four graded responses and no neutral midpoint, so every answer commits to a lean. Items were authored against the peer-reviewed literature listed in the evidence file on this page, and citation metadata is supplied at build time; source relevance and claim interpretation remain editorial judgments. Response order is shuffled on every run to vary position; this implementation has not been tested for bias reduction.

What happens to my answers?

Assessment answers stay on this device. Unfinished progress expires after 30 days. A completed profile and optional comparison history remain until you delete local assessment data or clear browser data. If you opt into email, your email address is sent; item answers are not. If you share a result link, total and dimension scores are included in the URL and may appear in browser, server, CDN, or analytics logs.

How often should I retake it?

The instrument keeps your previous reading and sets the two side by side when you retake — the Second Reading. There is no validated retest interval; repeat only if a raw answer-point comparison would be useful, and do not treat it as confirmed underlying change.

Why bands instead of percentiles?

Because this assessment does not collect a population score set, there is no reader population to rank you against — and we will not invent one. The 5-dimension profile groups selected answer points for editorial display; it is not a validated structural or decision-utility model.

Where does the evidence come from?

Every dimension insight cites peer-reviewed research, and most answer reveals do — 8 sources stand behind this instrument, each with DOI metadata supplied at build time; source relevance and claim interpretation remain editorial judgments. A few reveals are straightforward editorial reasoning from the same evidence base and carry no citation by design. The full list, with DOIs, is in the evidence file below.

The evidence file

8 peer-reviewed sources stand behind this instrument's items and insights.

Edmondson (1999) — Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly. DOI: 10.2307/2666999 ✓ Crossref‑verified
Kim et al. (2020) — How Psychological Safety Affects Team Performance: Mediating Role of Efficacy and Learning Behavior. Frontiers in Psychology. DOI: 10.3389/fpsyg.2020.01581 ✓ Crossref‑verified
van den Hout et al. (2018) — The Conceptualization of Team Flow. The Journal of Psychology. DOI: 10.1080/00223980.2018.1449729 ✓ Crossref‑verified
Slemp et al. (2018) — Leader autonomy support in the workplace: A meta-analytic review. Motivation and Emotion. DOI: 10.1007/s11031-018-9698-y ✓ Crossref‑verified
Katz et al. (2021) — Feedback environment: A meta-analysis. International Journal of Selection and Assessment. DOI: 10.1111/ijsa.12350 ✓ Crossref‑verified
De Jong et al. (2016) — Trust and team performance: A meta-analysis of main effects, moderators, and covariates. Journal of Applied Psychology. DOI: 10.1037/apl0000110 ✓ Crossref‑verified
Humphrey et al. (2007) — Integrating motivational, social, and contextual work design features: A meta-analytic summary and theoretical extension of the work design literature. Journal of Applied Psychology. DOI: 10.1037/0021-9010.92.5.1332 ✓ Crossref‑verified
Jackson & Schuler (1985) — A meta-analysis and conceptual critique of research on role ambiguity and role conflict in work settings. Organizational Behavior and Human Decision Processes. DOI: 10.1016/0749-5978(85)90020-2 ✓ Crossref‑verified

Neuroscience of Discipline Habits & Behavioral Design

Willpower Test: How Strong Is Your Self-Control Architecture?
July 17, 2026August 24, 2026 Neuroscience of Discipline, Habits & Behavioral Design

A 20-scenario, evidence-based profile that maps five structural dimensions of your self-regulation – and reveals whether you are winning through habits and environment, or relying on effortful resistance, which the evidence suggests is the least durable self-control strategy.

Dive Deeper Willpower Test: How Strong Is Your Self-Control Architecture?
Leadership & Social Dynamics Team Flow

What Is Quiet Quitting? Disengagement vs Healthy Boundaries, Scored | HPC Trend Breakdown
June 18, 2026September 2, 2026 Leadership & Social Dynamics, Team Flow

Assessment loading If the interactive assessment does not start, you can still read the methodology and evidence below, then try again later. Browse all assessments This page renders as a standalone Trend Science Breakdown.

Dive Deeper What Is Quiet Quitting? Disengagement vs Healthy Boundaries, Scored | HPC Trend Breakdown
Vagus Nerve & Nervous System Regulation Brain Health & Bio-Performance

Vagal Tone Assessment: How Resilient Is Your Nervous System?
July 17, 2026August 24, 2026 Vagus Nerve & Nervous System Regulation, Brain Health & Bio-Performance

A 20-scenario, evidence-based assessment that maps how well your autonomic nervous system recovers from stress – identifying the specific habits, practices, and patterns that shape your vagal tone across five measurable dimensions.

Dive Deeper Vagal Tone Assessment: How Resilient Is Your Nervous System?
Leadership & Social Dynamics Team Flow

Tuckman’s Stages: Definition and the Forming-Storming-Norming-Performing Model
June 18, 2026September 2, 2026 Leadership & Social Dynamics, Team Flow

Tuckman’s Stages is a five-phase model of group development that helps leaders diagnose team maturity and adapt their leadership approach for each phase.

Dive Deeper Tuckman’s Stages: Definition and the Forming-Storming-Norming-Performing Model
Trust Relationship Neuroscience

Trust Architecture Quiz: How Well Do You Build and Sustain Trust?
August 18, 2026August 24, 2026 Trust, Relationship Neuroscience

This evidence-based profile evaluates how you build and maintain trust across five behavioural dimensions: how you initiate trust through vulnerability, signal competence honestly, maintain a consistent track record, repair breaches when they occur, and calibrate how far and to whom you extend trust.

Dive Deeper Trust Architecture Quiz: How Well Do You Build and Sustain Trust?
Leadership & Social Dynamics Executive Presence

Transformational Leadership: Bass’s Definition and the Four-I Model
June 18, 2026September 2, 2026 Leadership & Social Dynamics, Executive Presence

Bass’s Four-I model of transformational leadership: definition, mechanisms, performance evidence, and how to measure and develop it.

Dive Deeper Transformational Leadership: Bass’s Definition and the Four-I Model