← All thoughts

What happens when you actually map a business's workflow on a whiteboard

Composite, drawn from patterns across engagements, not one specific client.

Most process problems get discussed in the abstract: “our handoffs are messy,” “things fall through the cracks.” Those descriptions are true and useless at the same time, because nobody can fix a problem stated that vaguely. The fix starts with something much less glamorous: an actual whiteboard.

What the exercise looks like

Every step a piece of work goes through, from request to delivery, gets written as a literal box, with an arrow to the next box, and a name next to each arrow for who’s responsible for that handoff. Not a flowchart tool, an actual whiteboard, because the friction of drawing it by hand forces precision that a template lets you skip.

What it usually reveals

In one engagement, this exercise for a fifteen-person services business surfaced eleven handoffs. Four of them had no named owner, work just “ended up” moving forward, usually because someone noticed it was stuck and pushed it manually. Two boxes existed that nobody in the room could actually explain, steps that had been added years earlier for a reason nobody remembered, and never removed.

That’s the real value of the exercise: it turns “our process is messy,” a feeling, into “these four specific handoffs have no owner,” a fixable fact.

What changed after

Each of the four ownerless handoffs got a named owner, in writing. The two unexplained steps got tested by removing them for two weeks, nothing broke, they were quietly cut for good. Total time to run the exercise: about two hours. Total time the business had been losing to the gaps it revealed: years.

The lesson, generalized

Most operational pain isn’t inside any single step, it’s in the gaps between steps, and gaps are invisible until someone draws the whole thing out loud, in front of the people who actually do the work. This is close to the cheapest diagnostic available to any business, and one of the most underused.