Strengths Spotting
'What's X really good at?' is the format. 'What's X's strength?' is a 360. The room can tell the difference in three seconds.
Each teammate names what each other teammate is concretely good at — with a specific verb and a recent example. Surfaces hidden expertise the team's been benefiting from without naming. The grammar is the format; performance-review adjacency is the failure mode.
When to use
Teams that have worked together at least a quarter — you need shared evidence to spot strengths from. Useful at end-of-quarter reviews, mid-project check-ins, or after a project where strengths showed up clearly. Skip it for teams under three months together; you don't have the evidence yet. Skip it on teams where the framing will read as evaluation — the format collapses into theatre. Use Personal Map instead when the goal is connection rather than capability mapping.
How it runs
Set the grammar before you start
'What is X really good at?' is the work format. 'What is X's strength?' reads like a 360 review. State the framing out loud and hold it. The grammar choice isn't pedantic — it's load-bearing. The first prompt produces concrete capability; the second produces evaluative platitudes.
Make consent explicit
Some people don't want their colleagues publicly enumerating what they're good at. Tell the team they can opt out of receiving without explanation. Forced strengths-spotting is worse than skipped — it weaponises the format.
Silent write, one round per teammate
For each person, every other person writes one to three things that person is really good at — with a specific verb and a recent example. 'Priya is really good at debugging concurrency — she found the race condition in the queue last sprint' is the format. 'Priya is technical' is the failure mode.
Read the strengths to each person, one at a time
One person at a time, the others read what they wrote. The person receiving doesn't need to respond. Don't ask 'how does that make you feel?' — that's the performance-review move. Read the data, move on.
Act on the output
A list of strengths is data; routing the work to where the team already says the expertise sits is the artefact. 'Three people said Priya is great at concurrency debugging — let's route the queue rewrite to her.' The activity earns its place in the routing decision, not the read-aloud.
Why it works
Most teams have hidden expertise they've been benefiting from without naming. Strengths-spotting forces a public, specific naming — and the specificity is what protects the format from collapsing into 'great communicator' filler. The grammar choice ('really good at' rather than 'strength') keeps the room out of performance-review register, which is what kills the format on every team that conflates them. Run on a team with shared evidence and you produce a routing map; run without it and you produce a wishlist.
Variations
- Anonymous variant: each person writes their notes for the team via a private form, facilitator reads them aloud without attribution. Lower-pressure for teams uncomfortable with direct feedback.
- Strengths-pairs: each person picks one other person and shares one specific strength. Less data per person; faster. Useful for teams over eight where round-robin tax is high.
- Quarterly with action: tie strengths-spotting to the next quarter's work allocation. The activity becomes a routing exercise, not just a kindness ritual.
- Async first: spread the silent-write phase over a week in a private channel; live session for read-aloud only.
Facilitator notes
Police the grammar. Every 'great communicator' or 'team player' gets pushed back: 'name a recent moment.' Two pushes per round is enough to set the bar; three becomes lecturing. Watch the distribution — some people will get five mentions, some will get one. Don't redistribute. The asymmetry is data; the response is to look at why and what to do, not to manufacture parity.
Pitfalls
- Asking 'what's X's strength?' and getting evaluative platitudes back. Wrong grammar; the format collapsed.
- Letting 'great communicator' or 'team player' stand. Either name the moment or strike the entry.
- Running it on a team under three months together. No shared evidence; the room defaults to compliments.
- Listing strengths and stopping there. The output isn't the list; the routing decision is.
Remote tips
Async-first works well — give the team a week to write notes for each colleague in a private form, then run a 30-minute live session for the read-aloud. Live writing on a video call produces thinner notes; the time pressure pushes people to platitudes. For the read-aloud, share screen and read the notes flat — don't ad-lib.
Example outputs
- 'Priya is really good at debugging concurrency — she found the race condition in the queue last sprint, three days after we'd given up on it.'
- 'Tom is really good at writing code review feedback that lands without making the author defensive — the auth PR last month was a textbook example.'
- 'Ana is really good at explaining the system to new joiners — both new hires this quarter said her onboarding 1:1 was the most useful day of their first week.'
- Filler-version (don't accept): 'Priya is technical.' 'Tom is a great communicator.' 'Ana is friendly.' Send back, ask for the verb and the moment.
FAQ
- Strengths-Spotting or Personal Map?
- Personal Map is 'who are you outside work?' — a connection tool, works on day one. Strengths-Spotting is 'what are you good at inside work?' — a capability tool, requires shared evidence (a quarter of working together at minimum). Different bonds, different timing. Don't substitute one for the other; you'll get a thin version of whichever you swapped for.
- Why does the grammar matter so much?
- Because the room can hear the difference. 'What is X really good at?' points at concrete capability and produces specific verbs. 'What is X's strength?' points at evaluation and produces 360-review language. Once the room reads the activity as evaluative, every subsequent answer turns careful — you've stopped collecting strengths and started collecting performance-review filler.
- What if the strengths are unevenly distributed?
- Don't redistribute. The asymmetry is data: some people are visible in their work, some aren't. The response is curiosity, not parity-engineering. If the quiet senior engineer got one mention and three people got five, that's the conversation worth having — quietly, not by manufacturing extra mentions in the room.