Fired Over a $2 Cookie: Why Jumping to Conclusions Costs More Than You Think
Aug 18, 2026Kurt Kromm had worked as an electrician at Ford's Kentucky Truck Plant for 11 years. Until he got called into the labor office and told he was being fired - for stealing a $1.95 pack of cookies.
In this week's video, I share his side of the story: his blood sugar dropped during an overnight shift, he went to the vending kiosk, swiped his card, got an error, swiped again - and thought it had gone through. A week later, supervisors reviewed the footage, decided he hadn't paid, and fired him on the spot, with no chance to explain first.
Kromm went back through his bank records, and provided a notarized statement to prove it (and if you've gotten something notarized recently, you know that takes effort). Ford eventually offered to reinstate him with roughly $33,000 in back pay. He turned it down - because, as he put it to the New York Post, "I can’t come back to a company that just fired me like this and not give me any chance to show I paid."
You may have seen the headlines: "Ford fires worker over $2 cookie." And that kind of story gets headlines, because it sounds too ridiculous to be real. But if you work in HR or manage people, the specific headline isn't the lesson - it's the common pattern behind it.
See the breakdown in the video - and keep reading for what to consider as a leader to make sure your decisions don't end up in the headlines.
This Happens More Than the Headlines Suggest
It's easy to read this and think, "We'd never do that over a cookie!" Fair. But the actual mistake Ford made wasn't about the cookie - it was making a final decision before giving someone a chance to respond. And that mistake shows up frequently at work - just usually in smaller, less headline-worthy ways:
- A teammate gets accused of having missed a deadline, when their manager hadn't checked their inbox.
- A customer complains that an employee was rude, and they get written up before anyone asks what happened on the call.
- A senior leader tells a manager that their team member was unprepared in a meeting, when no one told that team member they were going to present.
- Two people give conflicting accounts of the same situation, and whoever spoke first gets believed.
None of these might end up in the news - but all of them shape whether your team trusts you.
Why We Skip the Conversation
Rarely is someone - including a leader - unfair on purpose. It's usually about assuming that when you hear information, it's the full story. Once you think you already know what happened, asking a question can feel unnecessary, or even like you're second-guessing evidence sitting right in front of you. So you skip straight to the decision.
This is where the Pause-Consider-Act framework I write about can be a lifesaver. Not as another step that slows you down, but as a habit check before you make a call. Pause before reacting, so you're deciding on the facts and not out of frustration or a push to move fast. Consider what you actually know versus what you're assuming, and how you'd want to be treated if you were the one being accused. Then act, but only after you've done the first two steps. If you want a full breakdown of this framework with examples in different roles, I wrote about it here: The 3 Things Every Manager Must Consider Before Making Any Decision.
What This Sounds Like in Practice
The fix can be straightforward and simple. It's one question, asked before making a conclusion instead of after: "Here's what I'm seeing/hearing - walk me through what happened on your end."
That's giving both an observation and an open door, so you're not backtracking after an accusation. It can take thirty seconds. It doesn't slow down real accountability - if someone genuinely dropped the ball, you'll still deal with it. But it means you're deciding based on a fuller picture instead of the first version you heard, or the version that happens to confirm what you already suspected. And if it turns out you were wrong, better to find that out in the conversation than in an exit interview, a Glassdoor review, or a letter (or lawsuit) from an attorney.
Ford is learning that lesson the expensive way: having their $33,000 in back pay offer rejected, and headlines that will follow the company for a while. And, as Kromm said, it was never really about the cookie. It was about the real impact of being treated like a thief before anyone bothered to ask if he was one.
You probably won't fire someone over a snack. But you will, at some point, be tempted to act on the first version of a story instead of the full one. When that moment comes, the pause costs you almost nothing. Skipping it can cost a lot more than $2.
If you're in HR: A big part of your job is making sure managers ask before they assume - and that those conversations get documented, so no one's stuck relying on memory when something gets disputed later. If you want a tool that helps your managers build that habit consistently, take a look at Manager Method's leadership platform.
If you're a manager: This exact moment - deciding what to do about a mistake, a complaint, or a rumor about someone on your team - is one of the most common and most avoidable ways managers lose trust. Manager 101 helps you build skills and confidence to decide exactly what to say and do before you make the call.