I’ve delegated the blame. Please return the credit
Michael Scott’s Golden Ticket idea changes from disaster to success, and ownership changes with it. A comic look at credit, blame and delegation.
Becoming a Leader · Mistakes & Course Correction · Delegation
You can learn a lot about a manager by watching their pronouns during a project failure. At launch, it is my vision. During delivery, it becomes our initiative. When the costs arrive, it is your decision. If the customer renews, memory improves and the manager becomes available for interviews.
This article reflects on fictional events in the US version of The Office. The workplace examples outside the programme are imagined illustrations, not accounts of real people, companies or events.
In “Golden Ticket”, Michael Scott launches a promotion inspired by Willy Wonka. Discount tickets placed in paper shipments end up benefiting the same major customer, creating a much bigger discount than he intended. Faced with the apparent disaster, he wants Dwight to take responsibility for the idea.
Then the customer’s response changes the commercial picture. The promotion has helped win more business. Suddenly, the idea is brilliant and Michael has a pressing intellectual-property concern: someone else is being congratulated for it.
His position is unusually clear. “I do want the credit without any of the blame.” Most managers would take longer to explain this and include a slide about empowering others. Michael saves everyone the preparation time.
Ownership, subject to favourable results
The funny part is how quickly the meaning of responsibility changes. When the idea looks costly, Dwight can demonstrate loyalty by owning it. When it looks clever, loyalty would involve handing it back. The task has not changed. The audience has.
Imagine a quieter version at work. A manager approves an ambitious launch date after the team raises several concerns. They agree to proceed with a reduced scope. For a week, everyone works towards the same plan. Then a senior stakeholder asks why something important is missing.
At this point, the manager explains that the team was given considerable autonomy. This is technically adjacent to something that happened, which makes it particularly useful. The approval meeting has become difficult to remember, while the team’s independence is suddenly available in impressive detail.
Now imagine the stakeholder loves the focused release. The manager describes the strategic discipline required to protect the scope. Same calendar, same decisions, entirely different documentary. The team sits beside them discovering which version of its responsibilities has been commissioned.
That uncertainty would make ownership difficult to trust. If I cannot tell whether a decision will remain mine once somebody important reacts to it, I have a good reason to keep asking for permission. The manager may then wonder why nobody takes initiative. Perhaps everyone is waiting to learn who will be responsible for having had it.
The people quietly collecting receipts
One imagined consequence is an office where every agreement acquires a long email trail. A conversation that could have ended with a clear decision instead produces a careful recap, two attachments and an unusually prominent reference to who approved what. The team is documenting the work, but it is also preparing for the possibility that the work develops amnesia.
I would be cautious about treating that behaviour as needless bureaucracy. Sometimes people are protecting themselves against something they have learned to expect. Asking them to become more trusting would be an ambitious response from the person whose memory depends on the result.
There is a distinction here between sharing credit and pretending the manager contributed nothing. Leaders make decisions, secure support, remove obstacles and sometimes have the original idea. It is reasonable to name that contribution. It is also reasonable to examine the team’s mistakes when something goes wrong.
What I would want is an account that survives both outcomes. If I approved the risk before the launch, that remains part of the story after a complaint. If a colleague found the solution, their contribution remains part of the story when I present it to my own manager. The facts should not need changing because the meeting has better chairs.
A version of events that stays put
Michael’s dilemma gives us an unusually clean test. Could he describe the golden-ticket decision in the same way before and after learning that the customer likes it? He could explain the idea, the assumptions and the unforeseen consequences. The emotional experience would change considerably. The author would not.
In the imagined launch, I would want to say that I agreed the scope with the team, that we knew which risks we were taking and that we now needed to understand the effect. If I had ignored a concern, that would belong in the account too. It would be uncomfortable, but it would save everyone the work of correcting the history privately afterwards.
That does not require absorbing every mistake made by anyone who reports to me. Turning the manager into a ceremonial blame sponge would make it harder to learn what actually happened. People still need responsibility for their judgement and follow-through. They also need to know that their manager will describe their own part accurately.
The most useful conversation might happen before the outcome arrives. What can the person decide? Which risks have we accepted together? When should they involve me? That gives both of us something firmer than a retrospective debate about who sounded most enthusiastic in the meeting.
I like the ridiculous honesty of Michael’s confession because it removes the language that can hide the same temptation. Of course I would prefer praise to criticism. The question is whether that preference changes the account I give of somebody else’s work. Before presenting the result, I would want to check whether the story would still sound like this if the result had gone the other way.
Continue exploring
- Article
When ownership is agreed in the room and lost afterwards - AI Skill
Delegation Planner - Free resource
Handing over the decision
