Illustrative sample. A fictional 5-person team, real report structure. Every real team map is generated from each member's own answers and stays private.
IndividualCouplesBusiness OwnerTeams
S
Stronghold Team Map

The Operations Team

Teams edition · Sample team · 5 members · Led by Trevor Lane
"Five people who out-work anyone in the building — and never tell each other they're drowning."
Team size
5 assessed
Led by
Trevor Lane
Team archetype
The Engine Room
Under pressure
Drive & go quiet
Measures scored
1,150+
How a team report works

Five people. One map.

Every member takes the full Stronghold assessment on their own. Then the reports are read together — not as five profiles side by side, but as one living system: who collides, who completes whom, and where it will break.

The roster

Who is on this team.

Each person, read in full first. Their archetype is how they are wired — not a box, a starting point.

Leader
T
Trevor Lane
VP, Operations
The General
Lion · drives
Decisive, intense, unshakable in a crisis. Leads from the front.
 
D
Dana Reyes
Operations Manager
The Shepherd
Retriever · absorbs
Holds everyone together. Takes on the stress and never says so.
 
P
Priya Shah
Senior Analyst
The Strategist
Owl · withdraws
Deep, precise, quiet. Processes alone before she will speak.
 
J
Jordan Brooks
Team Lead
The Flame
Otter · pursues
High energy, thinks out loud, runs on recognition.
 
S
Sam Okafor
Project Lead
The Fortress
Beaver · carries it
Reliable and private. Will not ask for help until it is late.
The team, as one system

What this team is.

Add the five together and a single character emerges — with one strength that carries it and one blind spot that will cost it.

Team archetype
The Engine Room

This team is built to produce. Three of the five default to action or output; the other two are a deep analyst and the glue that holds morale together. They will out-work almost anyone in the building.

But under pressure the wiring turns on itself: the drivers push harder, the thinkers go quiet, and the carer absorbs it all — so problems stay buried until they break. This team's risk is not effort. It is silence.

The strength

Relentless execution and real capability. They finish what they start and stay calm when it counts.

The blind spot

Nobody surfaces a problem early. Four of five cope by pushing, withdrawing, or absorbing — only one speaks up, and he is not always heard.

How they act with each other

The collision map.

The relationships that run hot, run cold, and run well — the part a manager feels every day but could never quite name.

Trevor & Dana
Collision
He steamrolls; she absorbs. Dana nods, takes it on, and burns out silent — you will lose her before you see it coming. The single most important relationship to fix on this team.
Priya & Jordan
Collision
He thinks out loud and fills every silence; she needs quiet to form a thought. In meetings he talks and she disappears — and the team loses its sharpest analysis right when it needs it.
Trevor & Sam
Friction
Two high-output people who both refuse to ask for help. They respect each other — and neither surfaces a problem until it is on fire. The team's key-person risk lives right here.
Trevor & Jordan
Friction
Jordan's energy sells Trevor's vision to the floor. But Jordan runs on recognition Trevor never gives — so the team's best connector is also its top flight risk.
Dana & Priya
Fit
Dana's warmth makes it safe for Priya to speak. Put them together and the quiet genius actually talks. This is the team's hidden asset — use it on purpose.
The operating manual

How to reach each one.

The same practical layer the individual report gives — now for all five. How they each need to be approached, so the message actually lands.

Person
Reach by
How to work with them
Trevor
In person
Be fast and specific. Bring a plan, not just a problem. Don't bury the point.
Dana
In person
Open warm, ask what she needs, and mean it. Don't pile on — she will not say no.
Priya
Email first
Send it ahead so she can prepare. Never put her on the spot in the room.
Jordan
Face to face
Let him talk it out, then name the win. Recognition is oxygen for him.
Sam
Written, direct
Respect his autonomy. Offer help as a teammate, not a rescue.
Burnout radar

Who is closest to the edge.

The assessment reads strain across the team — and the person most at risk is almost never the one raising their hand.

Dana ReyesShepherd · silent over-functioner
High
Sam OkaforFortress · carrying it alone
Elevated
Trevor LaneGeneral · driving everyone, himself included
Elevated
Priya ShahStrategist · withdraws to cope
Moderate
Jordan BrooksFlame · flight risk, not exhaustion
Watch

The two people most likely to leave — Dana to burnout, Jordan to a place that values him — are also the two least likely to tell anyone first. That is the report's whole point: see it early.

The leader 360

How the team experiences Trevor.

One layer of a team map is the leader 360 — the leader's self-view next to how the team actually receives him. The gap is the blind spot he cannot see alone.

How Trevor sees himself How his team experiences him
DelegationWide gap
He sees himself as hands-off; the team feels every decision routed back through him.
Recognition & appreciationWide gap
He believes he appreciates the team; they rarely feel it land. This is what puts Jordan at the door.
ApproachabilityWide gap
"My door is always open." The team reads the intensity and stays out — so problems don't reach him.
Composure under pressureAligned
A real strength — the team trusts him in a crisis, even more than he trusts himself.

His blind spots line up exactly with the team's frictions: the delegation gap is why everything routes back to him, and the recognition gap is why his best connector is a flight risk. Fix the leader, and three of the collisions ease at once.

How this helps

From an engine running hot to a team that lasts.

The point is not the diagnosis. It is the change. Here is what the work actually moves for this team.

Where the team is now
  • Problems stay buried until they break
  • Dana absorbs until she's gone
  • Priya's best thinking never reaches the room
  • Jordan is updating his résumé
  • Everything routes back through Trevor
Where the work takes it
  • Problems surface while they're still small
  • Dana's load is seen and shared
  • The quiet analyst is actually heard
  • The connector feels valued and stays
  • The leader delegates; the team owns it
What the practitioner sees

The team, read for coaching.

The intelligence layer for team work — where to start, what to protect, and what to watch. This stays with the practitioner.

Where to start

  • Protect Dana first: she is the retention risk nobody is flagging. Move here before anything else.
  • Build a problem-surfacing ritual: the team's silence is structural — give it a forced, safe outlet.
  • Coach Trevor's delegation + recognition: both gaps are driving the team's frictions at once.
  • Pair Dana with Priya: the cheapest win on the board — it unlocks the analysis.

Brief & cautions

  • Don't "fix" the drivers: Trevor and Sam are the engine — channel them, don't dampen them.
  • Jordan is the canary: when the team's loudest voice goes quiet, the team is already in trouble.
  • Sam won't raise his hand: check on him directly; he will say "fine" until he isn't.
  • Expect resistance to slowing down: tie every change to output — the thing they actually care about.

Team early-warning forecast

Where this team tends to head without intervention.

Losing Dana to silent burnout
High
85% confidence
Problems surfacing too late
High
80% confidence
Jordan flight risk
Elevated
74% confidence
Drop in execution
Low
61% confidence
5
Full assessments, read as one team
1,150+
Measures scored across the team
1
Map of how they actually work together

Five individual reports are useful. One map of how they collide, complement, and communicate is what changes a team.

This is one team. Every team's map is different.

Trevor's team is fictional. Each real team map is generated from each member's own answers and stays private to the team and its practitioner.