OLD SCRIPT DETECTED
“I grab the hardest ticket so I still feel useful”
Try this response:
“The hardest ticket doesn't need me. It needs whoever's turn it is to get harder.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“I grab the hardest ticket so I still feel useful”
YOUR RECORDED RESPONSE
“The hardest ticket doesn't need me. It needs whoever's turn it is to get harder.”
ONE PRIVATE MOVE
Before your next grooming call, privately write down which teammate you'd assign the hardest ticket to and the one thing they'd need to succeed — without opening the tracker.
The Reconciliation Bug Nobody Else Touches
The Cursor Hovers Over Assign-to-Self
Grooming call, ten tickets left on screen. Most are routine — copy fixes, a config change, a flaky test. Then the payment reconciliation bug, three weeks old, notes from two engineers who bounced off it. Your chest tightens before you've finished reading the description. Your cursor is already on the assignee field. Nobody asked you to take it. You just can't watch it sit there unclaimed.
The Queue That Only Moves Through You
Three sprints later, every hard ticket in the backlog still routes to you by habit, not decision. Your calendar has one-on-ones and a roadmap review, then two hours blocked at 9pm to actually touch the code. The easier tickets your team closes fine on their own. Nobody has gotten visibly better at debugging the gnarly stuff, because the gnarly stuff never reaches them — you're standing in front of it.
The Ticket You Left for Someone Else
Next grooming call, before you touch the assignee field, open a private note instead. Write the name of the teammate you'd give the hardest ticket to, and one specific thing — a doc, a pairing session, a Slack thread — they'd need to not drown in it. Don't send it. Just sit with the ticket unassigned to you for ten minutes and notice what that discomfort is actually about.
TRACE · 01/04
How this script runs you
- In grooming, your cursor moves to assign-to-self before you've finished reading the ticket's description.
- You privately rank the backlog by difficulty, and the hardest one becomes yours by pattern, not by decision.
- A sprint where the ticket you claimed turned out easy leaves you oddly unsettled, like you didn't earn the week.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Player Reflex
Only the hardest, ugliest ticket proves I still belong on this team. Anything I could hand off is admin work that doesn't count toward earning my keep, so I keep the worst one for myself to settle the question.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- The hardest ticket doesn't need me. It needs whoever's turn it is to get harder.
- My name in the assignee field isn't proof of anything except a habit I haven't questioned.
- Handing over the ugly ticket is the actually difficult part of this job now.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“I grab the hardest ticket so I still feel useful”
I say
“The hardest ticket doesn't need me. It needs whoever's turn it is to get harder.”
Then I do one thing
Before your next grooming call, privately write down which teammate you'd assign the hardest ticket to and the one thing they'd need to succeed — without opening the tracker.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "I grab the hardest ticket so I still feel useful". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
What if I genuinely am the fastest person on the hardest tickets?
Being fastest today explains why you're capable of taking it, not why you must. Speed at the task and necessity of the assignment are two different questions — the second one is worth answering separately each time, not by default.
What if the hard ticket just sits unclaimed for days if I don't grab it?
A ticket sitting unclaimed for a few days is visible information for the team — about capacity, about priority, about who needs support. Absorbing it silently removes that information instead of surfacing it.
What if my manager expects me to personally close out the gnarly bugs?
That expectation, if it exists, is worth checking directly rather than assuming. Many managers who promoted you for judgment are surprised to learn you're still measuring yourself by ticket difficulty instead of by what the team can now handle without you.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- Becoming the Boss — Hill, Harvard Business Review, 2007
- Why People Crave Feedback — and Why We're Afraid to Give It — Abi-Esber, Abel, Schroeder & Gino, HBS Working Knowledge / JPSP, 2022
- Are your employees avoiding you? Closing the feedback gap — Detert et al., Academy of Management Perspectives, 2004