Skip to content
Playbook
Cristiano RonaldoPublished· 6 min read

Cristiano Ronaldo Wasn't Always Cristiano Ronaldo

Potential is not the same as performance. What deliberate, sustained skill-building looks like inside a career — and inside a company.

The Cristiano Ronaldo who joined Manchester United in 2003 was a teenage winger known for step-overs and inconsistent finishing. The one who left for Real Madrid in 2009 had just won a Ballon d'Or and scored more than 40 goals in a season. Same person, six years apart.

Documented fact: his league goal return in his first season at United was low single figures, and by 2007/08 he scored 31 in the Premier League alone. He then scored prolifically in Spain and Italy. Whatever is argued about his career, that progression is a matter of public record.

The reason this matters to anyone running a team is uncomfortable. If you had assessed that 18-year-old on his first season's output, you would have concluded he was a flair player with a finishing problem. You would have been right about the present and completely wrong about the person.

The people question this raises

We hire for potential and then evaluate on performance, as though the two were the same measurement. Potential is a hypothesis about what someone could become. Performance is what has already happened. When we use one year of performance to settle the hypothesis, we close the door on the only people who were ever going to grow dramatically.

There is a body of research behind this. Anders Ericsson's work on deliberate practice found that expert performance develops through specific, effortful, feedback-rich repetition rather than through general experience — time served is not the variable. Carol Dweck's research on mindset found that beliefs about whether ability is fixed change how people respond to difficulty. Put those two findings next to a performance system that scores people annually on output and you can see the design flaw: it rewards what is already built and is nearly blind to what is being built.

Where this shows up at work

  • A promising hire is labelled 'not senior material' in their first year and never again gets the assignments that would produce contrary evidence.
  • Development plans list courses and conferences instead of the one specific skill that is actually blocking the person's results.
  • Feedback describes traits — 'needs more polish', 'lacks gravitas' — rather than behaviours anyone could practise on a Tuesday.
  • The people who improve most get no credit, because the rating measures level, not slope.
  • Nobody has written down what the next level looks like, so improvement is aimed at a target only the manager can see.
The quiet cost of an early verdict

Once a person is privately filed as 'capped', the assignments, the stretch projects and the airtime stop arriving. Their performance then confirms the original judgement. This is not talent assessment; it is a self-fulfilling loop, and it is invisible in your data because the inputs changed along with the outputs.

A framework for turning potential into performance

The one-skill quarter
  1. 1
    Name one skill, not five
    Pick the single capability that would most change this person's results over the next year, and write it in plain language they would recognise. Five development goals is the same as none, because nothing gets enough repetitions to change.
  2. 2
    Define what better looks like
    Describe the observable behaviour at the next level in two sentences — what they would say, write or decide differently. Progress must be visible without waiting for a rating.
  3. 3
    Build reps into real work
    Attach practice to live commitments: a weekly section of the team meeting they run, a customer call they lead, a document they own end to end. Practice that sits outside the job gets cancelled by the job.
  4. 4
    Coach on the reps, monthly
    Fifteen minutes of specific feedback on a thing that actually happened, twelve times a year, outperforms one annual verdict by a wide margin.
  5. 5
    Re-decide at the end
    At quarter end, either keep the same skill for another cycle or promote a new one. Deciding explicitly stops development plans from quietly dying.

A worked example

A support analyst is technically strong and repeatedly overlooked for a team-lead role. Her manager's feedback for two years has been 'needs more confidence'. Under the one-skill quarter, they replace that with something practisable: leading a conversation with an unhappy enterprise customer without escalating to a manager. Better looks like — she states the situation, offers two options, commits to a date, and follows up in writing the same day. The reps are three live calls a month, with her manager listening, then eight minutes of feedback afterwards. By the third month she handles the calls alone. The development note now reads as evidence rather than an adjective.

Hiring for trainability

  • Tell me about a skill you deliberately built that did not come naturally. How did you practise it?
  • What feedback changed how you work? What did you do differently the following week?
  • Describe something you were visibly bad at six months ago and are competent at now.
  • Who gave you your hardest feedback, and what did you do with it?
  • What are you practising at the moment, and how would you know it is working?

The method matters more than the outcome in those answers. Someone who can describe how they built a skill has a transferable process; someone who can only describe results may have had a good environment.

What readers often get wrong about this

  • It does not mean everyone can become elite. Very few people become the best in the world at anything, and no development plan changes that. It means that one year of output is weak evidence about a five-year trajectory.
  • It does not mean effort alone explains transformation. Coaching, role changes, teammates, physical development and opportunity all contributed in Ronaldo's case. Attributing improvement entirely to individual work ethic is the most common misreading of this story.
  • It does not mean you should never make a negative decision. Sometimes the fit is wrong and an honest conversation is kinder than a development plan nobody believes in. The rule is that the decision should follow real reps and real feedback, not a first impression.

Interpretation, not established fact: reading his progression as primarily a story about deliberate practice is a popular framing and an incomplete one. The documented part is the improvement itself and the timeline over which it happened.

First 30 days

  1. List everyone on your team who has not had a genuinely stretching assignment in the last year. That list is your real potential-blind spot.
  2. For each direct report, write one sentence naming the single skill that most limits their results right now.
  3. Convert every trait-based phrase in your last round of feedback into an observable behaviour.
  4. Book a recurring monthly 15-minute coaching slot per person and protect it as you would a customer meeting.
  5. Pick one person you had privately written off and give them one honest quarter of reps before you conclude anything.

Common questions

How long should I wait before deciding someone cannot grow into a role?

Long enough that they have had the assignments, the feedback and the coaching the role actually requires — in most professional roles that is two to three quarters of deliberate reps, not one review cycle. If you cannot point to the reps you gave them, you are assessing your own system rather than the person.

Isn't it unfair to invest heavily in one person's development?

Targeted investment is not favouritism if the criteria are public. Publish the skill map and the route to the next level so anyone can opt in, and the investment follows demonstrated effort rather than the manager's preference.

What if the person does not want to practise?

That is useful information, and it should be received without judgement. Not everyone wants to move levels, and a team of steady, reliable operators is a legitimate team. The failure mode is assuming disinterest without ever having offered a real, well-defined opportunity.

References

Over to you

Who on your team was written off early? What would it take to give them one honest quarter of deliberate practice — and would you be willing to change your mind in public if it worked?

Talent Development