I saw this ridiculous quote today:

“A fool complains about his torn pocket, but a wise man uses it to scratch his balls.”

I laughed.

Then I thought: Son of a bitch. There's actually a management lesson in there.

We spend an enormous amount of time complaining about the things we don't have.

Not enough people. Not enough budget. Wrong tools. Bad processes. Legacy technology. Impossible deadlines. A client who won't make decisions. A senior executive who wants champagne outcomes on a tap-water budget.

And sometimes every complaint is completely legitimate.

But legitimate complaints don't deliver outcomes.

At some point, leadership requires us to stop describing the hole in the pocket and figure out what the hell we're going to do with it.

The Constraint Isn't Going Away

This is where I think some managers get stuck.

They believe acknowledging a constraint means accepting defeat. It doesn't.

You can simultaneously say: “This situation is unacceptable.” and “Until it changes, here's how we're going to operate.”

Those are not contradictory positions. That's leadership.

A good manager escalates the structural problem while helping the team navigate today's reality. A bad manager escalates the problem and then sits around waiting for somebody else to fix it.

You don't need to like the constraint to learn how to operate within it.

Think About an IT Service Desk

Imagine a Service Desk supporting 40,000 users.

Volumes are increasing. Headcount is frozen. The knowledge base is garbage. Automation funding has been pushed into next year. Average Handle Time is climbing. First Contact Resolution is falling. Abandonment is increasing. Employees are frustrated and customers are getting pissed off.

The manager has every right to complain. In fact, they should escalate the capacity problem.

But Monday morning still arrives. Forty thousand users still need support.

So what happens next?

One manager spends the next six months showing everyone the staffing gap. Another asks:

Where are the contacts coming from? What are our top ten call drivers? Which incidents should never reach a human being? Which tickets are being transferred unnecessarily? Where are analysts wasting time searching for information? Which approvals add no value? Which problems keep generating incidents because nobody owns Problem Management? What can we eliminate before asking people to work harder?

Now something interesting happens.

Maybe 18% of contacts are password and access issues. Maybe another 12% come from three badly designed applications. Maybe analysts spend two minutes per call searching six different knowledge repositories. Maybe one resolver group rejects 30% of assignments because the routing rules are wrong.

Suddenly the staffing problem hasn't disappeared. But the operating problem has changed.

Resourcefulness isn't doing more with less. It's finding the waste that was hiding when you had more.

And that distinction matters.

Don't Turn Resourcefulness Into Exploitation

There is an ugly version of this philosophy.

Executives sometimes say: “Look how much the team accomplished with fewer people. Apparently we didn't need those positions after all.”

No.

That's how organizations punish ingenuity.

If employees find a way to survive a broken operating model, don't institutionalize the broken operating model.

If somebody figures out how to scratch his balls through a torn pocket, that doesn't mean we should stop buying pants without holes.

There. I said it.

The objective isn't to glorify scarcity. It's to refuse to become paralyzed by it.

Fix the pocket. But until somebody brings you a needle and thread, you've still got a business to run.

Key Takeaways

  • Constraints are real. Paralysis is optional.
  • Escalate structural problems while optimizing today's operation.
  • Don't confuse resourcefulness with permission to underfund teams.
  • Look for waste, friction and unnecessary demand before demanding more effort.
  • The strongest managers ask, “Given what we have right now, what can we make possible?”