# The same ten problems, dressed up for thirty years.
In 1997 I watched a warehouse manager print out a spreadsheet every morning, highlight the rows that mattered, and walk the floor with it on a clipboard. In 2024 I watched a warehouse manager open a $400,000 WMS, export a filtered view, paste it into a spreadsheet, highlight the rows that mattered, and walk the floor with it on a tablet.
Twenty-seven years of technology. Same clipboard. Better screen.
I don't say this to be cynical. I say it because it's the most useful thing I know. The problems don't change. They get new clothes. And if you can recognize the shape underneath the outfit, you can save yourself — and everyone around you — an enormous amount of time and money.
Experience isn't knowing more solutions. It's recognizing the same problem faster, even when it shows up wearing a different hat.
The ten problems
I've been keeping a list. It's not literally ten — it's more like eight to twelve depending on how you count — but "ten" feels right, and precision would imply a certainty I don't have. Here's the gist:
**1. The handoff gap.** Work crosses a boundary — between teams, between systems, between shifts — and something gets lost. Context, urgency, ownership. Every generation reinvents the handoff, and every generation loses something in it.
**2. The accountability vacuum.** Everyone assumes someone else is responsible. The task sits in a gap between two job descriptions. Both people can make a credible case that it's not theirs. Meanwhile, the customer waits.
**3. Information asymmetry.** The person making the decision doesn't have the information. The person with the information doesn't have the authority. They're connected by a chain of telephone, email, Slack, or meetings, and by the time the signal arrives, it's stale.
**4. The hero dependency.** One person holds a critical process in their head. Everyone knows this is a risk. Nobody does anything about it because that person is too valuable to interrupt long enough to document what they know.
**5. Measurement theater.** The dashboard shows green. The operation is on fire. The metrics were designed for a board presentation, not for running the business. The people closest to the work don't recognize the numbers.
**6. Process debt.** A procedure was created for a good reason five years ago. The reason is gone. The procedure remains. Nobody remembers why it exists, but everyone follows it because removing a rule feels riskier than keeping a useless one.
**7. Tool worship.** The organization buys a platform expecting it to solve a problem that's actually about people and incentives. The platform is implemented. The problem persists. The organization concludes they need a better platform.
**8. The calendar trap.** People spend their days in meetings discussing the work instead of doing the work. The meetings exist because the system doesn't make status visible, so humans have to manually synchronize. Remove the information gap and half the meetings evaporate.
**9. Premature optimization.** Someone automates a process that nobody fully understands yet. The automation faithfully reproduces every mistake and bottleneck, just faster. Now you have efficient dysfunction.
**10. The fear of simplicity.** The solution is obvious and straightforward, but it feels too simple. So the organization adds complexity — approvals, layers, systems — until it feels appropriately serious. The complexity creates new problems. Those problems feel real. The original simple solution is forgotten.
Why this matters
If you've been doing this for thirty years like I have, pattern recognition is most of the job. Not because the solutions are always the same — they aren't — but because the diagnosis is faster when you've seen the symptoms before.
A company calls me because their dispatch operation is chaos. I listen for about forty-five minutes. Somewhere in that conversation I'll hear one of the sentences: "only Marcus knows how that works" or "the numbers in the system don't match what's actually happening" or "we have a meeting every morning to figure out the day." I know where this is going. The companies are different. The failure patterns aren't.
The costume changes
What *has* changed in thirty years is the costume. The accountability vacuum used to live in filing cabinets and voice mails. Now it lives in Slack threads and shared drives. The hero dependency used to be the guy with the Rolodex. Now it's the person whose browser bookmarks are load-bearing infrastructure. The measurement theater used to be a printed report nobody read. Now it's a real-time dashboard nobody trusts.
The technology changes. The architecture of the failure doesn't.
When someone tells me their problem is unprecedented, I believe them about the specifics and doubt them about the shape.
This isn't arrogance. It's just mileage. A mechanic who's seen a thousand engines doesn't need to understand your specific engine from scratch. They listen to it run for thirty seconds and they know where to look. That's not magic. That's Tuesday, times a thousand.
What experience actually buys you
It doesn't buy you answers. It buys you faster questions. Instead of spending three months analyzing a broken dispatch operation to discover it's a handoff problem, you hear it in the first conversation. That means you can spend those three months actually fixing it instead of figuring out what's wrong.
The most expensive thing in any engagement is the time between "something's not right" and "oh, it's *this* kind of not right." Thirty years of dressed-up problems buys you a shorter version of that sentence. And a shorter sentence means the money goes toward building instead of diagnosing.
That's the trade. The problems aren't new. But the willingness to see that clearly — and to act on it — is still surprisingly rare.