How We Work — Team Session Deck

Team Session · Generated by Team Mirror

How We Work
— the Product Team.

Eight people. Nine possible working styles. One shared language for how we do our best work together.

First, the frame

This is not a diagnosis.

These are conversation starters, not psychological evaluations. Everyone can confirm, reject, or edit their own result. The type is just the hook — the value is the conversation.

The team, mapped

Where we land.

Each node is a working style; bigger nodes mean more of us share it. We cluster on depth (Type 5) and authenticity (Type 4) — and we have a strong, direct voice in the room (Type 8).

Same-type pair

L Liz + S Sara

Both landed on Type 4 — authenticity, depth, creative ownership.

→ Does that feel true to either of you?
→ Where do you work alike, and where are you totally different?
→ What does “meaningful work” mean to each of you?

Tension pair · handle with care

J John · Type 8 ↔ M Maya · Type 9

One prefers direct action and a fast call. One prefers harmony and steadiness.

→ How do you two handle disagreement so it feels productive, not tense?
→ John: be direct with reasons. Maya: your silence isn’t always agreement — say the real thing.

Blind spots

The perspectives we’re missing.

No one here maps to Type 1 (the quality bar), Type 2 (the relationship glue), or Type 7 (the reframe).

→ What might we systematically miss because of that — and whose perspective should we deliberately invite into the next big decision?

Group activity · 30 minutes

Same-Type Huddles.

People with the same or adjacent type pair up. Prompt: “Where do we work alike, and where are we totally different?” Each pair reports one insight back to the room. Ten minutes in pairs, twenty to share.

The durable artifact

Our “How We Work” agreement.

DecisionsDefault to a fast call; flag early if you need think-time (we have a lot of Type 5s).
FeedbackBe specific and honest — no hollow praise. Acknowledge the person first.
DisagreementSay the real thing in the room. Silence isn’t consent. Direct, with reasons.
Async vs syncSend heavy topics ahead of time so the deep thinkers can prepare.
We’ll invite inAn outside “quality / relationship / reframe” voice when it matters.

Thank you

Now we have a
shared language.

Revisit this map next quarter, after the next hire, or whenever the team changes shape.