The People Analyst Guide to Nine Lies About Work. Format: what the book argues → what the research actually says → how you run it → the analysis you can run → the AI-era turn → what to do Monday. No reproduction of the book's text; the substance is ours. Research anchors verified on read.
What the book argues
The fourth lie is "the best people are well-rounded." The book's counter is that excellence is spiky: the people who are genuinely great are great at a few things and unremarkable — sometimes bad — at the rest, and the corporate instinct to assess everyone against a balanced wheel of competencies and coach the low spokes upward sands the spikes down to a competent, forgettable average. Build around strengths, it argues, and manage around the weaknesses; don't manufacture roundedness.
What the research actually says
Here the Guide has to be more careful than the book, because this is its most over-sold chapter. Two things are true and the book blurs them.
True and well grounded: person–job fit beats generic roundedness. Narrow, role-relevant abilities predict performance in that role better than a balanced competency profile, and assessing people against a context-free competency wheel measures the wrong thing — it scores breadth when the job rewards a specific spike. The well-rounded ideal is mostly an artifact of generic assessment, not a finding about performance.
Over-sold, and worth flagging: the broader "strengths" movement — the claim that developing strengths and ignoring weaknesses is the path to excellence — has mixed and contested empirical support; the popular version outruns the evidence. And roundedness genuinely matters for some roles (general management, integrative work that rewards breadth), while some weaknesses are fatal and have to be fixed, not routed around. So the honest version isn't "strengths good, weaknesses ignore." It's: match the spike to the role. Define what the role actually requires, assess the person's real shape against that, and stop grading everyone against an average no job actually needs.
That reframing is, conveniently, exactly what a job architecture is for.
How you run it
Make the role the yardstick, not a generic wheel. Specify what this role at this level actually requires — the few abilities that drive performance in it — and assess the person's spike against that specific requirement profile. Manage around non-fatal weaknesses; fix the fatal ones; don't chase roundedness the work doesn't reward.
The analysis you can run
A role-fit / KSA-profile analysis — job-family-agent (the canonical job architecture: each
function × level carries its real knowledge/skills/abilities) with performance-validity — that scores a
person's spike against the role's actual requirements instead of a context-free competency model. The job
architecture supplies the "what does this role require"; the assessment supplies the "what is this person
great at"; fit is the overlap. (This is the JobFrame substrate doing double duty.)
The AI-era turn
AI competency-scoring is the well-rounded ideal's most efficient new vehicle: feed it a résumé or a transcript and it will happily rate someone across a generic competency wheel, confidently, at scale — re-imposing exactly the roundedness this chapter warns against. Point it at role fit instead (spike vs. the role's requirements), and reliability-test it like any rater (Lie 6). The tool is fine; the target — generic roundedness vs. role-specific spike — is the whole question.
What to do Monday
- Retire the generic competency wheel as the assessment of record; it scores breadth the job doesn't need.
- Define the role's required spike (top few KSAs at this function × level) and assess against that.
- Distinguish fatal vs. non-fatal weaknesses — fix the first, manage around the second.
- Be honest that strengths-only is over-sold: fit, not strengths-evangelism, is the defensible lever.