Review season. Every deck carries the same slide, in one phrasing or another: double down on your strengths. The strongest problem-solver gets the harder problems. The strongest communicator gets the stage. The team's weakest area, the one every initiative actually waits at, goes unowned for the third consecutive year.
The advice on the slide is not wrong. It is misaddressed. Strengths strategy is career advice. It optimizes the market value of one person. A team is not a portfolio of personal brands. It is a production chain, and chains reward a different investment logic entirely.
Two correct theories, one addressing error
The strengths doctrine says: your edge is your differentiator, marginal hours spent there compound, hours spent shoring up weaknesses buy you mediocrity at best. For an individual career, this is close to airtight. The market prices scarcity, scarcity lives at the extreme, and the extreme is where your cheapest improvement in market value sits.
A team executes as a chain. As Teams Ship at Their Weakest Area, Not Their Average lays out, every initiative passes through five stations in sequence: it must be understood, survive its collisions, be pushed through indifference, cross team boundaries, and be converted into a repeatable system. In a serial process, the constraint's capacity is the team's capacity. Marginal hours spent on the strongest station improve a number nobody ships at. Marginal hours spent on the weakest station raise the actual output.
Both theories are correct at their own scale. The failure is applying the individual's portfolio logic to a chain. It is an addressing error, not a reasoning error, which is why smart teams keep making it. Nobody argued badly. They just mailed the advice to the wrong recipient.
Where should a team's training budget go?
To the lowest station, with a name attached.
The reasoning is plain arithmetic wearing a management costume. If behavior, the cross-team station, is the team's weakest area, then every initiative pays the handoff tax every time. Funding a workshop for the strongest problem-solvers raises the quality of work that will then wait, longer, at the handoff. You have improved the queue's contents, not the queue.
There is a political layer, because there always is. Praising strengths is socially cheap. Everyone enjoys it. Naming the team's weakest area requires a room that can hear a diagnosis without converting it into blame. Many rooms cannot, so the weakest area goes unnamed, and the budget follows the praise. That is an incentive problem dressed as a development strategy, and it rhymes with Incentives Are the Hidden Architecture of Bad Decisions: the budget is not flowing to development at all. It is flowing to whatever the room finds comfortable to fund.
The error compounds quietly. Strong areas get stronger, more visible, and more celebrated. The weak station keeps its tax on every initiative. Over a few years the team becomes extremely good at the parts of the work that were never the constraint, and the gap between the scorecard and the shipped year widens until nobody trusts the scorecard.
What this is not
Not an argument against specialization. Specialists are precisely how a team buys coverage at each station. The claim is about the marginal training dollar at the team level, not about what individuals should become. Depth is the unit of coverage; the chain decides where the next unit is bought.
Not a claim that individuals should fix their weaknesses. An individual's growth plan is a career document, and the strengths doctrine remains good career advice there. Keep two budgets and two conversations: the person's growth plan follows their edge. The team's training budget follows its lowest station. Confusing the two budgets is the original sin.
And not a mandate to publicize individual scores. The weakest area belongs to the team as a system, not to whichever person happens to sit closest to the gap.
The move
- Separate the two budgets this cycle: individual growth plans follow strengths. Team training money follows the weakest of the five stations.
- Attach a name and a quarter to the weak station. A weakest area without an owner is a subscription, not a priority.
- Re-scan quarterly. When the station improves, the constraint moves, and the money should move with it.
Take-home
- Find the slide in your last review deck that says amplify strengths. Correct address, wrong recipient: it belongs to careers, not to the team budget.
- Put the team's training money on the lowest of the five stations for one quarter and measure what changes at the waiting points.
- Keep individual growth plans strength-based. The person is a portfolio. The team is a chain. Each gets the advice that fits its shape.
Related reading:
- Teams Ship at Their Weakest Area, Not Their Average
- The Bottleneck Keeps Moving
- Incentives Are the Hidden Architecture of Bad Decisions
- Small Teams, Real Owners, Fast Executives
- A Demotivated Quarter Looks Like a Capability Problem
If your development budget keeps flowing to the strengths that demo best while every initiative waits at the same unfunded stage, the advice is addressed wrong. If you want help splitting the two budgets and funding the actual constraint, book a discovery call.
FAQ
Should teams focus on strengths or weaknesses?
Neither rule applies universally because the two words belong to different scales. Individuals should double down on strengths, because careers are portfolios and scarcity lives at the extreme. Teams should fund their weakest area, because teams execute as a chain and a chain delivers at its minimum station. Applying individual logic to the team budget is the common failure.
Why does strengths-based development fail for teams?
Because it optimizes the visible and celebrated stations rather than the constraint. In a serial process, improving a strong station raises a number the team never ships at, while the weakest station keeps taxing every initiative. The budget flows to wherever praise is comfortable, not wherever the waiting is.
How should a team allocate its training budget?
Fund the lowest of the five stations, intellect, personality, motivation, behavior, or experience, with a named owner and a quarter-long window. Re-scan afterward, because once the weakest station improves, the constraint moves and the budget should follow it.
Is it ever right for a team member to work on a weakness?
Yes, when the person volunteers because the gap blocks their own growth path. That is a career conversation funded by the individual growth budget. The team budget stays pointed at the chain's constraint. The mistake is not working on weaknesses. It is spending chain money on portfolio goals.