Victim Versus Player
Diagnose whether someone takes agency, then coach them across the line with one question.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 93%
Fred Kofman introduces the model with how small children report bad news: 'the coat is at school,' 'the toy is broken' — never 'I broke it.' The adult version is 'the report was not written… Lucy owes me her notes.' The player version of the same situation is: 'completely my fault, I planned to get it to you by 5, I prioritised an emergency and didn't tell you — can I get it to you at 5 today?' Ownership plus renegotiation. The coaching move is a single question — 'what could you have done differently?' — followed by silence long enough to be uncomfortable, then a non-judgmental list of options (help Lucy write the notes, set an earlier internal deadline, put the deadline in a visible tool). At scale, unchecked victim thinking mutates into empire building: 'if it's not under my direct control I'm not responsible,' so leaders demand more scope to satisfy the accountability checkbox.
Origin
Fred Kofman's framework, taught to Claire Hughes Johnson in Google's Axialent leadership bootcamps and carried through her career at Google and Stripe.
Core principles
- 01Language reveals agency: 'the report was not written' versus 'I didn't write it.'
- 02A player renegotiates; a victim explains why someone else made it impossible.
- 03Agency is coachable early in a career and close to fixed late in one.
- 04Blaming dependencies is the adult version of 'the toy is broken.'
- 05Visible shared accountability is a disinfectant for blame.
How to run it
- 1
Listen for the grammar of blame
In status updates, note whether the person owns the miss or narrates it as something that happened to them because of a dependency.
Pro tip The tell is a named third party who is 'slow' or 'bad at deadlines.'
- 2
Ask what they could have done differently
One open question, aimed at their own action set, not the other person's failure.
Watch out Do not answer it for them.
- 3
Hold the uncomfortable silence
Some will push back with 'what do you mean?' Stay in the discomfort rather than rescuing them.
Pro tip The silence is the intervention — filling it hands the agency back to you.
- 4
Build the option list together, without judgment
Enumerate concrete alternatives: help the dependency do their part, set an internal deadline ahead of yours, make the action item visible in a shared tool.
Pro tip Sunshine is a great disinfectant — a public task board makes the dependency accountable without you arbitrating.
- 5
Go to the balcony on the pattern
If it repeats, name it: 'I see this pattern where you're waiting for other people. Why do you think that's happening?' then walk down into specific examples and run the five whys.
Pro tip 'Be that as it may' is the phrase that acknowledges their excuse without accepting it, and keeps the inquiry moving.
Watch out Don't voice your own left-hand column theory (e.g. 'Lucy dislikes you because you blame her') — they'll shut down and stop learning.
- 6
Make the fit call
Signal clearly that you will not let them off the hook. If they cannot get into a player mindset after real coaching, they are not right for the team.
Watch out Later-career people are often unaware of the pattern because it has been rewarded — expect low coachability.
In the wild
A report is late. The victim says: let me tell you about that report — Lucy owes me her notes, I can't finish without them, and Lucy is super slow, so I don't know when you'll get it. The player says: completely my fault, I'd planned to get it to you by 5pm yesterday, an emergency came up, I prioritised that and didn't tell you — can I get it to you at 5 today? Same facts, opposite posture. The coaching then runs: what could you have done differently? Helped Lucy write it. Set a deadline with her ahead of yours. Put the action item somewhere visible.
→ The person usually concedes the list is fair, and implicitly admits they weren't collaborating well.
A senior leader reasons: if it's not under my direct control, I'm not responsible. So they ask for the infrastructure teams, then more scope, then more headcount — each grab framed as the precondition for accountability. Some organisations comply, and the person fails upward with an expanding org they still don't take responsibility for.
→ Scope inflation without ownership; the accountability gap widens as the org grows.
Common mistakes
Rescuing them from the silence
Suggesting the alternatives yourself keeps the person passive. The list has to come out of their mouth for the mindset to move.
Rewarding the excuse with more resources
Granting scope so someone can 'finally be accountable' teaches the org that control is a precondition for responsibility.
Judging the options as you list them
Evaluating each alternative turns a learning exercise into a verdict and shuts the conversation down.
Is it for you?
Best for
Managers assessing and developing accountability in early- and mid-career reports.
Not ideal for
Late-career leaders whose victim mode has been rewarded for years — the pattern is deeply ingrained and rarely coachable.
From the transcript
“how young children when something has happened that they know is bad will not take responsibility so they will say things like the coat is…”
“the easiest coaching move you do... you say to them what could you have done differently and you have to let uncomfortable silence”
“well if it's not under my direct control then I am not responsible and so they become Empire Builders”
From the episode
#724: Claire Hughes Johnson — How to Take Responsibility for Your Life, Create Rules That Work, Stop Being a Victim, Set Strong Boundaries, and More