All Posts

We joke that “this meeting could’ve been an email,” but Charlie Munger would flip that logic on its head. In most organizations, the real failure mode isn’t too many meetings — it’s hiding work inside emails no one ever truly acknowledges. A good meeting, with a shared agenda and a visible workflow, creates something email never can: confirmation, context, and community. Reduce your emails by having better meetings. That’s how you start paying down process debt.

There is no such thing as an idealized user. We're all distracted, temporarily disabled, with lots of things competing for our attention and if there's one thing we've learned through decades of building software, it's that we have to design around that reality, not in spite of it." — Jon Yablonski

"In software, you test your code before it ships. In life, you're testing in production. And when there's a bug that was in prod. You can't roll it back." — Dr. Adam Link

Here's the thing about a process that's working well: you don't see it. Nobody walks up to you and says, "Hey, great email triage today." The outcome shows up — but the process itself is invisible. Which means it's also easy to mess with, because there's no obvious cost to changing something nobody's watching.

There's a joke that goes: how do you sell a deaf person chickens? You just ask really, really loudly. It's a bad joke. It's also, somehow, the default communication strategy in most workplaces. When we're not being understood, we repeat ourselves more emails, more meetings, more bold text. And still, everyone walks out of the room with a completely different idea of what just happened. More volume was never the answer.

Most SaaS tools present as the easiest solution to all your problems. For a single user, that might even be true. But get a team involved — without a clear process and the right people at the table — and you've just handed everyone a bucket of 300,000 Legos and walked away. In this episode, Toby and Chris break down the requirements trap, the hidden cost of anchoring to your old system, and why pushing people into the tool before defining the process is sometimes exactly the

Most clients walk into a consulting engagement expecting magic. What they get instead is a mirror. In this episode, Toby and Chris unpack why technology implementations so often disappoint not because the software is wrong, but because the process underneath it was never examined. From the "kitchen analogy" to the AI cuteness trap, they lay out what process debt actually costs and what to do before you ever call in outside help.

We’ve been conditioned to think 'boring' means stagnation, but in operations, boring is your ultimate competitive advantage. Just like sleep hygiene, a business without rhythm isn't an operation—it’s just noise. If you want to scale, you have to stop chasing complexity and start embracing the predictable. Because if a process isn't boring, it isn't ready to be automated.

In the physical world, a carpenter who wastes 70% of his wood gets fired. In the digital world, we call that same waste "Process Debt" and ignore it. Digital scrap is invisible, it’s the "zombie" systems, muted channels, and skipped foundations that erode your team's sanity. The truth? You don’t lose to bad technology; you lose to skipping the boring foundations that make good technology usable.

The most expensive mistake you can make isn't buying the wrong software. It’s paying for a transformation while demanding a mirror. If you force a new system to mimic a 20-year-old legacy workflow, you haven't upgraded your business; you've just moved your Process Debt into a more expensive neighborhood. To find the ROI, you have to be willing to be a rookie again.

Middle managers are the 'glue people'—the vital translators between executive vision and frontline reality. As companies look to AI to trim the fat, are they accidentally cutting the air cover that keeps teams productive? We explore why the 'middle' is the primary target for automation and why history proves these roles are harder to delete than they look.

Is the person saving the day actually the one who started the fire? In this episode of the Process Debt podcast, we dive into the world of prediction markets and why most businesses fail to evaluate the quality of their decisions. From "corporate pyromaniacs" who thrive on chaos to the mastering statistical bias. Learn why psychological safety is the missing ingredient in risk management and how a simple calendar trick can reveal if you’re actually a good leader—or just lucky

“Hey, what’s up Toby? We made it another week.” And if your week included insane weather, unhinged headlines, and a football game that made you question your life choices… welcome to the club. But here’s the thing. When the news gets loud, it’s easy to get pulled into the politics of it all. This week, I want to do something different. I want to look underneath the argument and ask the question we ask on this podcast every week: What process produced the outcome we’re starin

If your work constantly feels urgent, reactive, and exhausting, the problem probably isn’t effort, it’s process debt. This episode digs into why solving for stress is easy, solving for service is hard, and how small shifts can radically reduce long-term friction.

Most automation doesn’t fail because the tools are bad. It fails because companies automate before they understand the business objective—and before they do the boring, foundational work that makes automation possible. The fastest wins aren’t usually robots. They’re often the obvious fixes the frontline has been asking for all along.

We tend to judge ourselves by our intentions and everyone else by their actions. It’s a subtle bias that feels harmless, but it quietly creates process debt everywhere from missed emails to failed system implementations. It it time to unpack why intentions feel productive, why actions are uncomfortable, and how time, habits, and learning curves expose the gap between the two. Turns out, most treadmills don’t fail we just never turn them on.

Distraction is the most convincing fake work in modern business. It feels urgent, but it’s usually just reaction disguised as productivity. In knowledge work, without clear constraints or clear strategy, we confuse motion with meaning. This episode explores how reaction, ambiguity, and shifting priorities create process debt—and why clarity is the only antidote to constant distraction.

Blame is the fastest reflex in business. A quick way to dodge discomfort without fixing anything. But real process health comes from slowing down, understanding the work, and building boring-but-powerful rituals that prevent chaos. When we value clarity over reaction, the fires stop before they start.

Lately, when people talk about AI, I think they believe they are buying Rosie. But we are not building Rosie. Not yet. And chasing Rosie too early is how you quietly pile up a whole new layer of process debt. AI is not doing your dishes In the real world, the direction of AI right now is information, not activity. It can summarize meetings, draft emails, write status updates, brainstorm project plans. It can churn through data at a scale that used to require an army of analys

Collaboration in the modern workplace frequently falters before actual work starts. This week’s Process Debt story highlights how a simple profile update request turned into a 20-minute ordeal of password resets and confusion. It demonstrates how invisible process friction can disrupt even the simplest tasks, not due to individual failure, but because our systems impose unnecessary obstacles.