Framework & playbook design

A method that only works when you're in the room isn't really a method yet.

Most experienced practitioners — founders, consultants, senior leaders — build a way of working over years. They can walk into a stuck room and get it unstuck. They can diagnose a broken process on sight. They know exactly how they do it, but only in their own hands.

This service is about turning that instinct into structure. A shareable framework, a repeatable playbook, or a working method other people can pick up and run — without needing you in the room every time.

- You have a way of working that clients or colleagues keep asking about, and you keep re-explaining it from scratch.
- You're scaling from doing all the work yourself to bringing others in, and the handover keeps breaking.
- You want to codify your consulting methodology, teaching approach, or internal process so it can be trained, licensed, or replicated.
- You have a proprietary model living in a slide somewhere that never quite makes sense to anyone else.
- You're building a book, a course, or a productised service and need the underlying framework structured properly before you build around it.
- A first conversation to understand what the method is, who it's for, and what "usable by others" actually needs to mean.
- Extraction sessions with you — usually two or three. My job is to ask the questions that surface what you're actually doing when you do the work, especially the invisible bits.
- A structural draft — the framework mapped as its parts, its logic, and its sequence. Before any visual polish, we agree it's right.
- Framework design — turning the structure into something legible: a diagram, a set of stages, a decision tree, a playbook layout, or whatever the format actually needs to be.
- A companion guide if useful — short written notes on how to use the framework, common pitfalls, and worked examples.
- A named, structured version of your method that other people can pick up.
- A clean visual or document that explains it without you having to be there.
- Language for talking about your approach with clients, hires, and audiences.
- A foundation you can build training, licensing, content, or productised offers on top of.
- A version of your practice that can travel further than your own calendar.

Recent example
A founder-led business setting up a new design function asked me to build the operating layer around it — not the creative work itself, but everything the department would need to run properly from day one. Mapping how the team would take a brief, run it, review it, and deliver it. Producing the internal documents and templates that make that repeatable. Structuring the server and file system so nothing gets lost between people. Writing down the workflows and processes so the first hires arrive into a way of working rather than having to invent one. The idea is simple: give the discipline a shape before the volume shows up, so the department scales on structure rather than on the founder's memory.

Talk to me.

If there's a method in your head that keeps proving itself but hasn't been made shareable yet, let's talk.