Two Years in Review: Navigating Process Debt and the Last Mile of Knowledge Work
Process Debt: Improving knowledge work processes to help you reach One Peace Flow.
Every new initiative starts as a prototype. Whether you are building a weekly podcast, launching a product, or cultivating a new habit, the first hurdle is simple: Can we technically execute this, and can we exercise some discipline?
When we launched The Process Debt Podcast two years ago, our goal was modest. We wanted to talk about the good, the bad, and the ugly of knowledge work, and help people reach what we call "One Piece Flow"—tackling one thing at a time and becoming a true craftsman in your work. But looking back at the past 24 months of publishing, building websites, and optimizing workflows, we realized something profound: every time you improve a process, you don't eliminate work; you simply uncover a new "last mile" problem.
The Asymmetry of Effort and the Last Mile Problem
In knowledge work, the definition of done is notoriously slippery. You think a task finishes with a meeting, but that meeting only leads to another meeting. As you tackle process debt, you inevitably run headfirst into the last mile.
Think about physical delivery. If you live right next to an Amazon distribution center, delivery is cheap and easy. If you live out in the mountains with no existing infrastructure, getting electricity hooked up or a package delivered is an entirely different beast.
Content creation and knowledge work share that exact same asymmetry of effort.
"As you tackle process debt, a lot of times it's fixing that last mile, right? And so... it's the most expensive part of delivering a package is really what the last mile is." — Chris
When we started, we thought publishing an episode was as simple as dropping an audio file into a distribution service and waiting for millions of listeners to knock down our door. Spoiler alert: they didn't.
Phase one was just proving we could do it. Phase two was making our work visible by setting up a LinkedIn page and a website. And that is where reality hit. None of us were professional marketers, webmasters, or designers. We were just two guys trying to fix things.
Moving From Isolation to Community
Trying to build everything in a vacuum is a trap. You can operate as a solo entrepreneur and figure out every tech stack under the sun, but you miss out on the genuine joy of doing hard things together in community.
For a long time, our website indexing was failing. Google couldn't see most of our pages because, quite frankly, we didn't know what we were doing. Bringing in experts—like our friend Josh Heideman from Stepwise, who pointed out our SEO blind spots—completely changed the game.
"It just lends to what's been cool in this path: to build stuff in community when you're working with other experts is actually stinking fun." — Chris
The lesson here applies to any corporate initiative or personal project: Don't worry, be crappy. Your first iteration does not need to be a masterpiece. It just needs to exist. Once you establish consistency, you can bring in the right people, leverage modern tools like AI and automation platforms, and streamline the back office so you don't get sucked down an infinite rabbit hole.
Embracing One Piece Flow in Daily Execution
Technology changes at a dizzying pace. Two years ago, the LLM boom was just finding its footing; today, multiple powerful models compete in the ecosystem. But regardless of how advanced tools become, the fundamental challenge of knowledge work remains personal focus.
How do we actually manage our attention amidst the chaos of notifications, meetings, and competing priorities? It comes down to committing to One Piece Flow.
"My One Piece Flow is I've been trying to write down what I'm working on, and I've been trying to intentionally just do one thing at a time." — Chris
We have started visualizing this literally—using task management markers that represent grabbing a piece of work from the bucket, finishing it, and sealing it before moving on. It sounds simple, and it is ridiculously hard in practice. Between the Pomodoro technique, time-blocking 90-minute deep-work sessions, and fighting off the daily game of Whac-A-Mole, slowing down enough to finish one thing is the ultimate competitive advantage.
Takeaway: Give Yourself Permission to Start
If you are looking at a messy workflow, a stalled project, or a massive mountain of process debt in your own organization, take a breath. You don't have to conquer the world on day one.
Start with a manageable cadence. Exercise the discipline to ship your version of a prototype. Lean on community, bring in experts when you hit the technical walls of the last mile, and find joy in mastering your craft—one piece at a time.



Comments