Product Team

Participants: 7 / 8 invited · Session date: 22 September 2026

What stands out this round

Participants split most clearly on: Process–outcome balance, Risk appetite.
Shared lean: Pace under uncertainty (Data first), Stance in disagreement (Harmonise), People–task focus (Protect people).
2 perception gaps: most participants chose one option but most predicted this team's majority would choose the other.

Pace under uncertainty

Shared lean

Data firstMove fast

The team leans towards waiting under uncertainty: fixing decision dates up front helps avoid missed windows.

Stance in disagreement

Shared lean

HarmoniseAddress directly

The team leans towards harmonising: a regular, safe channel for objections keeps issues from piling up.

Decision ownership

Centred

ConsultOwn the call

The team gathers around the middle on this axis; no notable tension.

Process–outcome balance

Split

Process & fairnessOutcome & speed

The team is split between following rules and prioritising results. Which rules can't flex, and how are exceptions shared?

Risk appetite

Split

Safe optionBold option

The team is clearly split between safe and bold options. In which areas do we agree to experiment?

People–task focus

Shared lean

Protect peoplePrioritise the task

The team leans towards protecting people: discussing critical goals and their reasons openly prevents work from slipping.

Bars show head counts; who is where is never shown.

NNormSignal·Norm Check-up · Team snapshot

Confidential — team-level aggregate, no individual data

Perception gaps

Most participants chose one option, yet most predicted that most of this team would choose the other. This is a gap between choices and predictions in this session; it doesn't show why it isn't voiced, or that it is a lasting team norm. It is a starting point for a team conversation.

Pace under uncertainty

You're about to roll a new workflow out to the whole team. Early pilot feedback is positive, but you only have one week of data.

100%

actually chose: Wait a week

86%

thought most would choose: Roll out now

People–task focus

While the team is worn out, a client sends a last-minute extra request. Delivering it means working the weekend.

100%

actually chose: Negotiate scope/time

86%

thought most would choose: Accept and deliver

Discussion questions for the team meeting

1.The team is split between following rules and prioritising results. Which rules can't flex, and how are exceptions shared?
2.The team is clearly split between safe and bold options. In which areas do we agree to experiment?
3.Most of us chose "Wait a week", yet most of us predicted the team's majority would pick "Roll out now". Where do you think that gap comes from?
4.Most of us chose "Negotiate scope/time", yet most of us predicted the team's majority would pick "Accept and deliver". Where do you think that gap comes from?

Method and limits

—7 team members (of 8 invited) answered the same 18 dilemmas in their own time within a week. Each dilemma also asked 'which one would most people in this team choose?'. Results are participants' answers that week and may not represent those who didn't take part.
—Results are shown only with at least 5 participants and only in aggregate; who chose what never appears on any screen. 5 is a publishing threshold — not a guarantee of scientific validity or full anonymity; in small groups people can be guessed with outside knowledge.
—Each axis is measured by three dilemmas. This is screening-level, not a precise measurement or a personality diagnosis.
—The tool's own validity and reliability study has not been done; the axes and thresholds haven't been expert-reviewed yet. It makes no claim to predict job performance.
—No camera, voice, facial, CV or social media analysis. Only the choices made are used.