What Your Strengths Assessment Won't Tell You

· Field CTO, Akamai · · 5 min read

Strengths frameworks sell the upside and bury the cost. Every strength is a default, and defaults misfire under load — here's how to read your results for the failure modes, not the flattery.

A strengths report is a flattering document. You answer a few hundred forced-choice questions, and a week later get back a tidy list of the things you’re naturally good at, written in the warm second person of a horoscope that happens to be right. Mine came back with a top five I recognised instantly, and a quiet sense of having been seen.

Then I noticed what the report doesn’t say out loud. Every one of those strengths is a default — a behaviour I run without choosing it. A default fires whether or not the situation calls for it. The report tells you what you reach for; it doesn’t tell you when reaching for it is the wrong move.

That second question is the useful one: read the same themes for their failure modes.

A strength is just a behaviour you stopped choosing

Take Strategic — the habit of seeing paths through a problem before anyone’s drawn the map. Genuinely useful when the terrain is unknown and someone needs to spot the three routes that don’t end in a wall. Also the reason I have, more than once, produced the eleventh option in a meeting that needed me to commit to the first one. The strength doesn’t switch itself off when the job changes from find the path to walk it. Past a certain point, more options aren’t insight — they’re a way of staying comfortable in the part I’m good at and avoiding the part I’m not.

Or Ideation — delight in a new connection for its own sake. It’s the engine behind anything I’ve made that was worth making. It’s also, on a bad day, indistinguishable from distraction. The new idea arrives precisely when the old idea needs finishing, and it always feels like progress, because generating is more fun than grinding. Nobody puts “will abandon a 90%-done thing for a shinier 0%-done thing” on a strengths report. That’s the same theme, seen from underneath.

And Learner — the one that looks unimpeachable. “I need to understand this properly first” is the most respectable procrastination there is. It’s diligence-shaped, so it survives scrutiny that laziness never would. Half the time it’s genuine rigour. The other half it’s a reason not to ship, and the two feel identical from the inside.

None of this means the strengths aren’t real. They are. It means a strength and its shadow are the same trait pointed at different problems — and the report only photographs it from the good side.

The useful artefact is the if-then, not the top five

The reframe that changed how I use mine is simple. “I’m Strategic” is a label, and a label does nothing under pressure. I need an if-then:

When the team has converged and is asking me to decide, my default is to open the question back up — and that is usually the wrong instinct in that moment.

That sentence is portable in a way the label never is. It travels into the meeting with me. It gives me something to catch myself doing. Read properly, the strengths report is a list of the specific moments I’m most likely to misfire, written in advance, in my own handwriting.

The exercise I’d recommend, if you’ve got a report sitting in a drawer: ignore the descriptions. For each theme, write the one situation where leaning into it costs you. You’ll learn more from those five sentences than from the forty pages of affirmation they came wrapped in.

Turn a theme into a decision rule 1. Strength Strategic sees paths through a problem 2. Default Open more paths the behaviour that fires without choosing it 3. Decision gate Team converged? name the condition where the default misfires 4. If–then guard Decide; do not reopen it interrupt the default The report supplies the theme. The useful work is naming the condition and the guard.
A strengths assessment names the default. Its practical value comes from identifying the condition that changes its usefulness, then deciding how to interrupt it.

Where this bites in technical leadership

This isn’t abstract for me. The work I do — sitting between deep technical detail and the decisions that get made on top of it — is built out of these defaults, which means it’s exposed to their shadows.

Pattern-matching is the obvious one. Years of seeing how systems fail means I can usually tell you, fast, which architecture is about to become someone’s incident. That speed is most of the value I bring. It’s also a liability the moment the problem is genuinely novel, because the pattern-match doesn’t announce that it’s guessing — it returns an answer with exactly the same confidence whether it’s seen this before or only something that rhymes with it. The strength that makes me quick on the familiar is the one that makes me overconfident on the new. Same trait. Different problem.

The point of knowing that isn’t to suppress the instinct — I can’t, and I’d be worse off without it. It’s to know the one condition under which to distrust it, and to have decided that in advance, on a calm afternoon, rather than in the room.

That’s where a strengths assessment earns its keep. Not the flattery. The forewarning. The report tells me what I’ll reach for without thinking. My job is to work out, before the moment arrives, when not to.