Book contents

Chapter 12

The talent-dense company

PDF page 116
In this chapter
  1. Dependable is a contribution
  2. Skill travels, but conditions may not
  3. Hire for the gap in the team
  4. Fit must leave room for difference
  5. Measure the work you hoped to improve
  6. Strong teams need enough capacity

The coordinator in our worked example is not there to become the agency's most impressive strategist. The role exists because missed hand-offs and scattered requests are taking account managers away from their work. A dependable person who keeps commitments visible, follows up and raises a risk early can make that whole team more effective. Calling their contribution merely adequate would miss the reason for hiring them.

That is the question behind talent density: what can this group do well together, and what does the next person help it do better? It asks more of a hiring decision than whether a vacancy has been filled. It also asks more of the employer than collecting people with impressive records and expecting them to work it out.

Reed Hastings and Netflix helped popularise the term.1 I use it as a way to think about team capability, not as a percentage of people I would label stars. The aim is a team with the skills, judgement and working relationships its work requires. Some contributions will be conspicuous. Others will be valuable because they make reliable work possible without demanding attention.

Dependable is a contribution

PDF p. 117

There is an important difference between harmful conduct, a person who cannot meet a role's requirements and somebody who does their job well without constantly exceeding it. If we put all three in a category called mediocre, we lose the ability to decide what to do.

Harmful conduct needs a response to the conduct. An unmet requirement needs a clear account of the gap, its cause and whether support or a change can address it. Dependable work needs to be valued against what the role exists to provide. A team does not become stronger because everybody is made anxious about being the least exceptional person in the room.

If somebody meets expectations but you are disappointed, examine the expectations. Perhaps the role now needs a capability it did not need before. Perhaps you wanted more initiative but never gave the person authority to act. Perhaps the work is simply less visible than the work you tend to celebrate. These possibilities call for different decisions.

I still want a high standard. That means being specific about the standard and willing to act when it is not met. It does not mean turning every stable contributor into a problem. The person who prevents an avoidable error may contribute more than the person praised for fixing it later. A senior specialist should not have to prove their value by holding on to routine work that somebody else could own well.

The coordinator example helps make this concrete. If the role eventually gives account managers more reliable time for client work, the benefit is partly in what those colleagues can now do. If the coordinator creates another layer of approval without resolving the delays, the hire may have added cost without solving the problem. You need to inspect that contribution. Neither the person's title nor how busy they look will answer it.

Skill travels, but conditions may not

PDF p. 118

What will this team need to provide for the next person to do the work well? Look at how their previous results were achieved, the support they had and what will be different here, alongside evidence of the capability itself.

Groysberg, Lee and Nanda studied the portability of star securities analysts' performance. Analysts who changed firms experienced an average decline in their rankings, especially when moving alone or to firms with weaker capabilities. The researchers found no statistically significant decline for those moving with colleagues or to stronger firms.2 That does not prove the effect was zero, and an observational study of analyst rankings is not a universal rule for every job. It gives us a good reason to investigate the resources and relationships behind a record of success.

Ask what the previous team supplied that your team would have to replace. A candidate may have worked with a specialist who checked their technical decisions, a strong manager who settled priorities or established systems that made the work predictable. You might be able to provide those conditions. You might instead need somebody with evidence of working effectively without them. Either answer is more useful than deciding that impressive experience must travel intact or cannot travel at all.

The same applies to a person whose previous results were modest. A different environment may help them, but that possibility is not proof of hidden excellence. Look for evidence of the capability you need and be honest about the support you are prepared to provide.

Hire for the gap in the team

PDF p. 119

Before deciding what the next person should add, identify where the current work becomes difficult. Look at recent decisions and hand-offs. Where does work wait? Where is it redone? Which questions reach the founder because nobody else can answer them? Which important capability depends on one person always being available?

Write down the contribution in terms somebody else could recognise. Then decide what evidence would support it. If the team needs better challenge of assumptions, ask candidates to examine a relevant decision and explain where the evidence is weak. If it needs reliable coordination, inspect how they handle dependencies and commitments. Avoid replacing these requirements with labels such as confident, high energy or entrepreneurial. Those words can cover very different behaviour.

You are not asking the new person to repair everything. Specify what belongs to the manager and existing team too. If people regularly make promises without consulting delivery, hiring a coordinator does not remove their responsibility to change. A role designed to absorb everybody else's unresolved habits will be difficult to keep working, however capable its occupant.

Fit must leave room for difference

PDF p. 119

There is a risk in any method that asks who fits. We can quietly redefine fit as familiar: somebody who speaks like us, approaches problems as we do and makes the interview feel easy. Benjamin Schneider's attraction-selection-attrition framework describes how the people attracted to, selected by and remaining in an organisation can make it increasingly alike.3 It is a useful warning about how a team reproduces itself, not a formula for choosing its next member.

Make the missing contribution explicit instead of searching for a different personality. A team that commits quickly may need somebody who is good at testing whether a promise is feasible. That is a work requirement you can assess. It does not mean choosing somebody because you have decided they belong to a cautious personality type. The same person might act quickly when the evidence is clear and pause when it is not.

Use comparable tasks and questions to examine that contribution. A candidate who disagrees with your first answer may be doing exactly the work you need. Look at how they make the disagreement useful: what they noticed, what evidence they sought and how they helped the group reach a decision. The aim is neither automatic agreement nor disagreement as a performance.

Also examine who can reach the process. Referrals alone can reproduce the same networks. An unnecessarily narrow experience requirement can hide relevant work done elsewhere. An assessment format may make it harder for someone to show a capability that the job itself does not require them to demonstrate in that way. These are reasons to inspect access and criteria, rather than assume a welcoming sentence in the job ad has resolved the issue.

People should not have to resemble the founder to meet a clear standard of work. Nor should one person be hired as a symbol of difference and then expected to carry every challenge the group avoids. The manager has to make room for the contribution they said they wanted.

Measure the work you hoped to improve

PDF p. 121

I cannot give you a single validated talent-density score. It would hide too many different things inside one number. That does not make measurement useless. Without it, a founder's feeling that the team is getting better can become as hard to challenge as an automated ranking.

Choose a small set of measures connected to the reason for the hire, and interpret them alongside the conversations. Record the starting point where you can. Keep the period, definition and missing information visible so that a better-looking number does not quietly mean something different.

Question Evidence worth keeping Limit to remember
Is the work becoming more reliable? Agreed commitments met, avoidable rework and the reasons for missed hand-offs. The volume and difficulty of work may have changed.
Has a bottleneck eased? Time waiting for an agreed decision and who had authority to make it. A faster decision is not necessarily a better one.
Is the new role enabling others? Work returned to its intended owner, with examples of how that time was used. Moving a task is not a benefit if the problem was merely passed on.
Were promises kept? Agreed support, hours and authority compared with actual experience. Staying in the role does not itself establish satisfaction.
What happened after hiring? Start dates, dated reviews, departures and unknown follow-up. A small record cannot prove what caused the outcome.

Measures need to show improvements alongside unresolved problems. Otherwise you risk expanding a role too soon or overlooking a useful change and choosing the wrong remedy.

A short record reviewed with the people doing the work may be enough to inform the next decision, including the uncomfortable one that the hire did not address the original problem.

Strong teams need enough capacity

PDF p. 122

The appeal of a small, highly capable team can become an excuse to keep loading work onto people who are already stretched. Better coordination may remove waste. It cannot create unlimited hours or make every responsibility safe to concentrate in one person.

When you review the team's needs, include cover for absence, time to learn and space to improve how work is done. If one person must always rescue a deadline, investigate why. Sometimes the answer is a missing capability. Sometimes it is too much work, a promise the business should not have made or an approval rule that keeps creating emergencies.

Hiring another person can be the right response. So can reducing the work or changing a commitment. Talent density should help you make that choice thoughtfully. It should not make a larger team seem like a failure or a smaller team seem efficient before you examine the result.

The people in the team have a stake in this too. They need work they can do well, reasonable conditions and colleagues whose contribution they can rely on. A role that helps the business while repeatedly breaking its promises to the person doing it is not a durable achievement. Neither is a pleasant role whose necessary work is continually left to others.

Where this breaks: Team contribution can become an excuse for vague personal judgement. If you cannot name the work, the effect on others and the evidence behind your concern, pause before labelling somebody a poor fit. At the same time, clear harm or an unmet essential requirement should not be ignored because the person is well liked. The standard needs to be specific enough to support both decisions.

Reader edition - October 2026. Full contents