Why Work Doesn't Work

A manifesto, of sorts

Most work doesn’t work.

Not in the catastrophic sense. The lights stay on, the customers get served, the quarterly numbers get hit often enough to keep everyone employed. But beneath that surface, an enormous amount of effort produces an embarrassing amount of output. Training programs that change nothing. Strategies that get announced and abandoned. Processes that everyone follows and nobody believes in. Meetings about meetings about the meeting we should have had instead.

If you work inside a real organization, you already know this. You’ve sat in the room. You’ve watched the slide deck. You’ve nodded along to the rollout. You’ve gone back to your desk and quietly figured out how to do your actual job around the official version of how it’s supposed to be done.

This publication is for you.

I came to this work the long way around. I spent years as a criminal investigator before I became a performance consultant, and the transition was less of a leap than it sounds. Investigators and consultants are doing the same job in different rooms. Something happened. Something is wrong. The obvious explanation is probably incomplete. The official story is definitely incomplete. The people closest to the problem know more than they’ve been asked. Your job is to find out what’s actually true.

The investigator’s mindset is the most underused tool in organizational work.

We hire consultants who arrive with answers.

We need people who arrive with questions.

We celebrate frameworks that promise certainty.

We need methods that tolerate the ambiguity of real situations.

We treat performance problems as moral failures—people aren’t trying hard enough, leaders aren’t visionary enough, culture isn’t strong enough—when they’re almost always structural.

This is the first thing I want you to take from this publication, and I’ll keep saying it until it sounds obvious:

The system is working exactly as designed—just not for you.

The dysfunction isn’t a bug. It isn’t a sign that someone forgot to fix things. It’s the predictable output of incentives, structures, and histories doing what they were built to do. The official story claims the organization is trying to produce one thing; the actual outputs reveal what it was actually built to produce. If you don’t like the output, investigate the system.

That’s the work. I take problems that get blamed on people and look at them as problems of design. Training that fails because the job didn’t need training in the first place. Processes that drift because nobody owns the gap between the documented version and the lived version. Transformations that stall because the org never actually agreed on what it was transforming into. Capability gaps that aren’t capability gaps at all—they’re authority gaps, or incentive gaps, or attention gaps, wearing a capability costume.

But seeing the system clearly is only the first move. The second is harder, and it’s where most organizational conversations fall apart:

Definitions matter.

If you and I can’t agree on what we’re looking at, we can’t possibly agree on what to do about it. Most meetings about dysfunction are actually multiple meetings happening in parallel, each participant solving for a slightly different problem under the same name. “We have a training problem” means six different things to the six people in the room, and nobody notices, because nobody asked. The work of definition isn’t bureaucratic throat-clearing. It’s the precondition for any shared action. Skip it and you’ll spend a year solving a problem that was never collectively defined.

Which brings me to the third thing, the line I’ll repeat most often, because it’s the one the entire industry violates:

Treatment without diagnosis is malpractice.

A doctor who prescribed without examining would lose their license. In organizational work, prescribing without examining is the entire business model. Frameworks arrive before facts. Solutions arrive before problems. Five-step plans arrive before anyone has asked what’s actually happening. This publication takes the opposite stance: the diagnosis is the work. If a post ends without a tidy action list, that’s not a failure—it’s the contract.

A few things I believe, stated plainly so you can decide whether to keep reading:

The gap between how things should work and how they actually do is the most important territory in any organization. It’s where the truth lives. Most management is an effort to pretend the gap doesn’t exist. Most good work is an effort to close it.

People are almost always smarter than the system they’re operating in. When work doesn’t work, the failure is usually upstream of the people doing it. Blame travels downward; causation travels upward. Investigate accordingly.

Frameworks are useful until they aren’t. The job isn’t to apply the framework. The job is to understand the situation. The framework is scaffolding, not the building.

Evidence beats opinion. Including mine. Especially mine. If I tell you something here and your experience contradicts it, trust your experience first and write to tell me what I’m missing.

You don’t need permission to start. Most of the people inside broken systems are waiting for someone with authority to fix the system. The people who actually improve things don’t wait. They investigate, they define, they document, they share what they learn. Authority follows clarity more often than clarity follows authority.

Here’s what you can expect:

Posts that take a specific problem and work it the way I’d work a case. Some will be short observations from the field. Some will be longer investigations. Some will be arguments staked plainly, with no hedge. All of them will try to tell you something true about how work actually works, rather than how we pretend it does.

I will be wrong sometimes. When I am, I’ll say so. I’d rather be useful than impressive.

I won’t write to fill a content calendar. I’ll write when I have something worth saying (at least once a week, but more likely two times). The trade-off for less frequency is that what arrives in your inbox should be worth opening.

I won’t sell you a course. I won’t sell you a certification. I won’t tell you that five steps will fix your culture. If I tell you something is hard, it’s because it’s hard. If I don’t tell you what to do about it, it’s because we haven’t finished diagnosing it yet.

If you’ve read this far, you’re probably the reader. Subscribe, and let’s see what we find.

Together, we can figure out what the fuck is happening. Let’s investigate.

—Ari