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

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…

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 scope an mvp internal tool without overbuilding. More precisely, it is about a step that only runs while one person is awake. The good…

From the article

AI is useful when it has a clear job. It is much less useful when it is added to a workflow nobody understands. For many businesses, the first step is not "add AI." The first step is to map the process: what starts it, who touches it, where data moves, what decisions repeat, and what output matters. Once that is clear,…