Resources
The diagnostic instruments I use inside engagements, organised so you can take a first read on your own operation. Each is free; one email gets you the download.
These are working instruments, not marketing collateral. Each one started life inside an engagement — the questions that open a diagnostic, the primer used to scope a first improvement project — and has been stripped of anything client-specific so you can run it yourself. They will not replace an embedded operating partner, and they are not meant to. They are meant to give you an honest first read on where your operation stands.
Who do they help? Founders and operators of companies that have outgrown improvisation, and the people who report to them — a chief of staff, a quality lead, an operations manager asked to take a first look at the model. You do not need a Lean Six Sigma background. The questions are plain, the scoring is simple, and the point throughout is to find the few places where the operating model is exposed, not to produce a grade.
The sections below explain how to apply each tool and what to read first, so the download is the start of something useful rather than another file in a folder. If what they surface is a problem you can fix internally, fix it. If it is the kind of problem that needs an operating partner, the diagnostic is the next step.
01Available now
Operations Audit Checklist
The structured checklist I use to take an evidenced first read on an operating model — the same questions that open a diagnostic, organised so you can run them yourself.
Inside
- The eight areas where operating models fail under scale
- Diagnostic questions for ownership, flow, quality and governance
- A simple scoring rubric to find your weakest link
Lean Six Sigma Quick-Start
A practical primer for using Lean and Six Sigma as engineering tools rather than a training programme — how to scope a first project that proves a real, measured gain.
Inside
- How to choose a first process worth transforming
- Measuring cycle time, rework and value-add without a toolkit
- Running the change as an experiment with a control
How to use the Operations Audit Checklist
Answer it with evidence, not impressions. The temptation is to score from memory; the value comes from checking. Where it asks who owns a process, find a recent decision and see whether ownership was actually clear. Where it asks about quality, look at the real first-pass numbers, not the final pass rate. Score honestly, even where it stings, then sort by your weakest area rather than your loudest one. The output is not a grade — it is a shortlist of the few places where the operating model is exposed, and where your attention will pay back most over the next quarter.
How to use the Lean Six Sigma Quick-Start
Pick one process that matters and is measurable, and resist the urge to fix everything at once. Measure how it runs today — cycle time, rework, and the share of steps that add value — before you change anything, so you have a baseline to argue from. Then change one thing and keep a control, so any gain is attributable rather than assumed. The quick-start treats Lean and Six Sigma as engineering tools, not a course to complete. The aim is a single, proven win you can point to. One clean result earns the credibility to take on the next, and the one after that.
What to read first
Start with the checklist; it is the wider lens. Once it points to a specific process worth fixing, the quick-start helps you scope the work. To put language around what either one surfaces, the glossary defines the terms plainly, and the frameworks show how the same instruments work inside an engagement. If you are still deciding whether you need outside help at all, the guide to what a fractional COO does is the place to start.
The eight areas the checklist examines
The audit is organised around the places an operating model tends to fail under scale: ownership, decision rights, how work flows, where it queues, how quality is defined and measured, how problems escalate, how the leadership team meets, and whether reporting is trusted. Most operations are strong in some and quietly exposed in others, and the exposed ones rarely announce themselves. The checklist exists to make the quiet weaknesses visible before they become expensive. Working through all eight, even the areas you assume are fine, is what separates a useful read from a comfortable one — the area you skip is often the one that matters.
What good output looks like
A well-run audit does not end in a score; it ends in a decision. The output you want is a short, ranked list: the two or three places the operating model is most exposed, each with a note on the evidence behind it and a first action. Resist the instinct to act on everything at once — capacity spent on the third-ranked problem is capacity not spent on the first. Fix the constraint, let the system settle, then re-run the relevant section to confirm the gain held. The same discipline applies whether you are running the checklist alone or walking through it inside a diagnostic: find the constraint, fix it, prove it, move on.
Turning a one-off read into a habit
A single audit is a snapshot. The operations that stay strong treat it as a recurring instrument — run lightly each quarter, in full once or twice a year. Operating models drift: a process that scored well last year quietly degrades as volume rises and the people who held it move on. Re-running the checklist on a cadence catches that drift while it is still cheap to correct, and it gives a leadership team a consistent way to talk about the operating model over time rather than only when something breaks. The quick-start works the same way — one proven improvement becomes a method you reach for again, not a project you finished once.
Common patterns these tools surface
Across very different companies, the same few weaknesses recur. Decisions that default upward because ownership was never made explicit. A quality number that looks healthy until you separate first-pass work from rework. Reporting that nobody fully trusts, so the leadership team argues with the figures instead of acting on them. A cadence that produces updates rather than decisions. None of these are effort problems, which is why working harder rarely fixes them. They are design problems in the operating model — exactly the things these instruments are built to expose, and exactly the things worth fixing first.
Questions about the resources
What these tools are, who they help, and how to get the most from them.
They are the working instruments from inside engagements, not marketing collateral. The Operations Audit Checklist is the structured set of questions that opens a diagnostic. The Lean Six Sigma Quick-Start is the primer used to scope a first improvement project that proves a measured gain. Both have been stripped of anything client-specific and organised so you can run them yourself. They will not replace an embedded operating partner, and they are not meant to. They are meant to give an honest first read on where an operation stands — enough to know what to fix first, and whether the problem is one you can solve internally.
Founders, CEOs and operators of companies that have outgrown improvisation — usually somewhere between fifty and five hundred people — and the operations leaders who report to them. They are equally useful to a chief of staff or a quality lead asked to take a first read on the operating model. You do not need a Lean Six Sigma background to use them. The questions are written in plain language and the scoring is deliberately simple. If you can describe how work moves through your business today, you can run these and learn something from the result.
Start with the Operations Audit Checklist. It is the wider lens — it looks across ownership, flow, quality and governance, and it shows you where the operating model is weakest. Once that points to a specific process worth fixing, the Lean Six Sigma Quick-Start helps you scope the actual project: what to measure, how to run the change as an experiment, and how to prove the gain held. In short: the checklist tells you where to look, the quick-start tells you how to act once you know. Running them in that order keeps effort pointed at the constraint rather than the symptom.
Answer it with evidence, not impressions. The temptation is to score from memory; the value comes from checking. Where the checklist asks who owns a process, find the actual decision and see whether ownership was clear. Where it asks about quality, look at real first-pass numbers rather than the final pass rate. Score honestly, even where it is uncomfortable, then sort by your weakest area rather than your loudest one. The output is not a grade. It is a shortlist of the few places where the operating model is exposed — the places where attention now will pay back most.
Pick one process that matters and is measurable, and resist the urge to fix everything at once. Measure how it actually runs today — cycle time, rework, and the share of steps that add value — before you change anything, so you have a baseline. Then change one thing and keep a control, so any improvement is attributable rather than assumed. The quick-start treats Lean and Six Sigma as engineering tools, not a training course: the goal is a single, proven gain you can point to, not a certificate. One clean win builds the credibility to take on the next.
No, and they are honest about it. A self-run checklist gives you a first read; a diagnostic gives you an evidenced, outside read with a written recommendation and a sequenced plan. The resources are the same questions, but the value of a diagnostic is in the judgement applied to the answers — knowing which weak signal is the real constraint, and what to fix in what order. Think of the downloads as the way to decide whether you need more. Many operators run them, fix the obvious things themselves, and only get in touch when the remaining problem is the one that needs an operating partner.
You get the resource as a PDF, sent to the address you provide. The email is used to deliver the download and, if you opt in, the occasional note when new operating tools or writing are published. It is not sold or shared, and you can unsubscribe at any time. There is no sales sequence waiting on the other side. If a resource prompts a question or you want a read on what it surfaced, you are welcome to get in touch — but the download stands on its own, and using it does not commit you to anything further.
Indirectly, yes. If running the checklist surfaces problems your team can fix on its own, you have your answer — fix them. If it keeps pointing at the same structural weaknesses, the ones tied to how decisions are owned and how the operating model is governed, those are the problems an embedded operating partner is built to solve. The resources are a low-commitment way to find out which situation you are in. They will not make the decision for you, but they will replace a vague sense that something is off with a specific, evidenced view of what it is.
Ran the checklist and want a read on what it surfaced?