A piece of scrap metal sat in the road for hours because everyone thought “not my job.” Here’s what it takes to fix that, for good.
“Not My Job”: Why Randy Crossed the Road
Randy was driving between campsites on Alaska’s North Slope when he noticed something odd. Ten or fifteen vehicles ahead of him were swerving, all avoiding the same spot in the road. When he got there, he found a large piece of twisted metal sitting in the middle of the roadway, the kind of hazard that could blow a tire or worse at highway speed. A dozen or more drivers had already seen it and driven past. Every one of them had the same two words available as an explanation: not my job.
Randy pulled over, safely removed the hazard, loaded it in the bed of his truck, and drove straight to a leadership meeting he had that morning with twenty-two colleagues. He walked in, set the disfigured chunk of metal on the table in front of his seat, and told the room he’d explain later. That lasted about four minutes before the questions started.
“Not My Job”: The Answer Every Driver Had Ready
Once Randy told the story, he asked the room a simple question. “What do you suppose all those drivers were thinking as they swerved around it?”
The answers came back fast, and every one of them landed on the same idea. “Not my job. Someone should take care of that.”
Randy let that sit for a second. Then he pointed out the obvious. “We tell everyone up here every single day that safety is job one. We spend millions training people. We’ve got signage everywhere, processes, systems, a safety meeting to start every shift. So why did a dozen people drive right past an actual hazard sitting in the middle of the road?”
Nobody had an answer. Randy had one. Of the roughly ten thousand people working that operation, exactly one department had “safety” written into their job description, and everyone else had quietly outsourced it to them.
The Fumble Every Team Leaves on the Field
Randy made his point with a football analogy that landed with the room. “If I’m a wide receiver, say Doug Baldwin, and there’s a fumble on the field, do I stand there and say, not my job, that’s on our fumble recovery guy?”
Recovering a fumble isn’t in a wide receiver’s contract. He does it anyway, because the result the team needs in that moment matters more than the boundaries of his position. Randy’s point was that safety works exactly the same way. The only reason anyone has a job on that team at all is that someone decided, at some point, that hiring them would help the operation achieve what it needed to achieve. Nobody gets hired just to stay busy inside a narrow lane.
A Twelve-Year-Old Made the Same Mistake
The story that gave Randy the language for this actually started at home. After a busy day getting the house ready for company, a father let his kids pick where to go for dinner as a reward. They came back to find a gust of wind had blown papers across the kitchen floor from an open window.
His twelve-year-old son stepped carefully around every single page on his way to the fridge. “Zack, help pick up these papers,” his dad said. The answer came back immediately. “That’s not my job.”
After a breath, the dad gave him the only answer that actually mattered. “You’re right. It’s not written on your birth certificate that you have to pick up papers off the kitchen floor. It’s not written on mine either. But you know we like this house clean. So when you see something like this, it’s your job, because you’re part of this family.”
That’s the whole idea, told twice, once with a kid and papers, once with ten thousand employees and a piece of scrap metal in the road. Job descriptions tell you what you’re required to do. They were never meant to tell you what you’re allowed to ignore.
Why “Job One” Needs an Owner, Not Just a Slogan
Most organizations already say the right words. Safety is job one. Quality is everyone’s responsibility. Culture matters. The words cost nothing, which is exactly the problem. Randy’s operation had said “safety first” for seven years and their safety numbers hadn’t moved, because saying it and everyone actually owning it are two different accomplishments.
When people focus only on their job description, the blame-game becomes almost logical. If safety, or quality, or the customer experience isn’t technically written down as theirs, they have a legitimate-sounding reason to let it be someone else’s problem when it breaks. The fix isn’t a new training module or another round of signage. It’s getting an entire organization, from the truck drivers to the cooks to the executives, to define their job as the result the team needs, not the four bullet points on their offer letter.
Randy didn’t have a clause in his contract requiring him to remove hazards from an Arctic access road. He stopped anyway, because he’d internalized something a lot of well-trained, well-intentioned employees never get told directly: the job was never the task. It’s the result. Everything else is just where you happen to be standing when you notice it needs doing.
If this resonated, Achieve with Accountability goes deeper into what it takes to build shared, organization-wide ownership like this on purpose, not by accident.
Curious where your own team or organization stands against the five capabilities that hold up under real pressure? Take the Kryptonite Scorecard, about 15 minutes.