Notes from the lab.
Workflow craft, not launch decks.

From the article

Most process pain has nothing to do with effort. Smart people work hard around a system that was never designed to carry the work, and everyone mistakes the symptom for the cause. This piece is about lab asset inventory audit: a practical operator guide, and specifically about an off-the-shelf tool that fits the brochu…

From the article

Most process pain has nothing to do with effort. Smart people work hard around a system that was never designed to carry the work, and everyone mistakes the symptom for the cause. What follows is a practical take on email handoffs vs task systems for approvals, built around a single sore spot: a handoff that no one has…

From the article

Almost every operational fire traces back to a step that runs on a person instead of a system. It stays invisible right up until that person is out for a week. What follows is a practical take on client portal vs internal portal: what to build first, built around a single sore spot: role confusion where everyone sees e…

From the article

Buying more software feels like progress. A new subscription feels like a decision, a new shared sheet feels like order, a new status call feels like control. None of them prove that work is actually flowing. The focus here is how to audit a manual process before automation. More precisely, it is about an exception tha…

From the article

The most expensive part of most operations is invisible on any invoice. It is the hour someone spends every week making two numbers agree. The focus here is reporting that executives trust without reconciliation. More precisely, it is about a weekly pack that takes half a day to assemble from four exports. This is for…

From the article

Almost every operational fire traces back to a step that runs on a person instead of a system. It stays invisible right up until that person is out for a week. The focus here is how to map handoffs before buying another saas tool. More precisely, it is about a tool that fits the demo and not the messy exception. Before…

From the article

The question that exposes a shaky process is simple: what would stop working tomorrow if one specific person stopped doing one manual thing. The answer is usually uncomfortable. This piece is about decision framework for a first-version internal tool, and specifically about a handoff that no one has formally agreed to…