Skip to content
Playbook
Cristiano RonaldoPublished· 5 min read

How Does One High Performer Change an Entire Team?

High performers reset what normal looks like — in both directions. Managing the spillover deliberately.

When Ronaldo joined Real Madrid in 2009 for what was then a world-record fee, the expectations around the club moved. When he joined Juventus in 2018, the same thing happened — a club that already dominated its domestic league publicly reframed its ambition around the Champions League.

Documented fact: both transfers happened, both were record or near-record deals for their moment, and both were followed by publicly raised expectations. Whether the results justified them is a separate argument.

The people question this raises

One person changes what 'normal' means for a group, in both directions at once. High performers reset the reference point for effort, quality and speed. They can also make competent colleagues feel replaceable, or give quieter contributors permission to coast because the outcome is now covered by someone else.

Research on star performers describes both effects. Spillover studies find that proximity to a high performer can raise the productivity of peers, particularly when knowledge is transferable and the star has reason to share it. Other work finds the opposite where status and credit concentrate: peers reduce effort, or leave. The determining variable is usually not the star's talent but how the work, credit and teaching responsibilities are arranged around them.

Where this shows up at work

  • A senior hire's standard silently becomes the new baseline and three solid performers disengage without ever saying why.
  • All the team's hardest output routes through one person, so nobody else stretches and your risk concentrates.
  • Peers copy the new person's habits: reviews get sharper, documents get shorter, meetings start on time.
  • A capable mid-level person starts job-hunting because the path above them now looks occupied.
  • Leadership's attention follows the star, and everyone else's work becomes invisible.

Managing the spillover deliberately

Four moves when a star joins
  1. 1
    Say what is changing, out loud
    Tell the team explicitly what the new standard is and what it is not, so nobody has to infer it by comparing themselves to one person's output.
  2. 2
    Give the star a teaching remit
    Make raising others an explicit part of their scope and their objectives from week one — not a favour you ask for in month six when problems appear.
  3. 3
    Protect the middle
    Restate what good looks like for solid performers, in writing. Without this, 'not the star' quietly reads as 'not valued', and your steadiest people leave first.
  4. 4
    Watch the flow of work
    If every difficult task lands on one desk, you are building dependency rather than capability. Route at least one hard problem a quarter deliberately elsewhere.
Two ways a strong hire lands
Six weeks inHealthy patternWarning pattern
Work allocationHard problems spread across three or four peopleEverything difficult queued behind one person
Peer behaviourOthers copy specific habits and ask questionsOthers stop volunteering for stretch work
CreditWins are described as the team'sWins are described as one name's
Middle performersClear on what good looks like for themComparing themselves to the star and losing
The starTeaching, with time allocated for itOverloaded and becoming a bottleneck

A worked example

A ten-person product team hires a highly experienced designer. Within two months, design quality is visibly better and two designers have stopped presenting their own work in reviews. The manager makes three changes: the new designer's objectives now include running a fortnightly critique and pairing with one colleague per cycle; the team writes down what a strong, shippable design looks like at mid-level so the bar is a document rather than a person; and the next two high-visibility projects are deliberately assigned to the existing designers with the new hire as reviewer. Quality holds. Participation recovers. The star is still the strongest designer and is no longer the only one.

Check the second-order effect at six weeks

Six weeks after a strong hire, ask two solid performers how their job feels different. That one question surfaces disengagement months before it appears in output, and long before it appears in a resignation.

What readers often get wrong about this

  • This is not an argument against hiring excellent people. It is an argument against assuming the benefit is automatic and needs no management.
  • Star effects are not symmetric across functions. Where work is interdependent and knowledge is shareable, spillover tends to be positive; where reward is relative and zero-sum, it tends to be negative.
  • The star is not the problem. Most negative spillover comes from how credit, workload and attention are distributed by managers, not from the high performer's behaviour.
  • The football comparison is limited: a squad has a fixed number of starting places, so one arrival demonstrably displaces someone. Most teams at work are not zero-sum in that way — but they feel that way if promotion slots are scarce and credit is concentrated.

Interpretation, not established fact: linking a transfer to a club's internal standards is my reading of public events. Clubs change coaches, squads and strategies simultaneously, and untangling one cause is not possible from the outside.

First 30 days

  1. Look at the last quarter's hardest pieces of work and count how many went to the same person.
  2. Write down, in one paragraph, what strong performance looks like for a solid mid-level member of your team, and share it.
  3. Add a teaching or enabling objective to your highest performer's goals, with time allocated for it.
  4. Ask two steady performers what has changed about their work since the strong hire arrived.
  5. Assign the next visible project to someone other than the obvious choice, with review support.

Common questions

Won't asking a star to teach slow down their own output?

Yes, somewhat, and that is the trade you are making deliberately. If their individual output is the only thing you are optimising, you are accepting key-person risk and capping the rest of the team. Reduce their delivery load to match the teaching remit rather than adding it on top.

What if the star does not want to develop anyone?

Some people genuinely do not, and that can be a legitimate senior specialist role — but then the teaching has to come from somewhere else, and you should not pay a leadership premium for a role that excludes it. Make the choice explicit rather than hoping it resolves itself.

How do I keep solid performers engaged next to an exceptional one?

Separate the standard from the person. Define good work in writing at each level, recognise it specifically and publicly, and make sure at least some visible opportunities are reserved for people who are not the strongest performer in the room.

Over to you

When a high performer joined your team, who thrived and who quietly stepped back — and did anyone ask them about it at the time?

Performance ManagementCulture & Strategy