Case notes

Work that taught me something.

Selected notes on the operating work behind the essays: what the situation was, what I built, and what I would carry into the next business.

These notes describe the work and the lesson. They are not audited client results, and they leave out confidential details.

Service operations

Shoo Lab: the handoff between sale and production

The situation

A growing shoe care service was taking orders through WhatsApp and paper. The team could sell the work, but the handoff into production was where details got lost.

What I built

A clearer intake, quality checkpoints and a way for the team to see where each pair was in the process.

What I learned

The constraint was not demand. It was the handoff. Once ownership was visible, the team could handle more without the founder in every conversation.

Customer conversations

A central support system for customer enquiries

The situation

Customer messages arrived through WhatsApp, Facebook, Instagram, ads and staff follow-up. Management could not see who owned what or what happened next.

What I built

One operating view, simple stages, routing rules and a weekly review loop.

What I learned

A shared inbox is not a system. The system is the ownership and the follow-up rule behind it.

Read the full case note

Remote teams

Remote agency operations: documentation is not the hard part

The situation

A distributed team across four countries was delivering client work with inconsistent handoffs and little shared context.

What I built

Documented workflows, async communication standards and clearer role expectations.

What I learned

Documentation only works when someone owns the process and the team can see whether it was followed.

If you are working through a handoff, ownership or reporting problem, the useful conversation usually starts with what is breaking.

Start there