Insights
Not thought-leadership in the empty sense. Specific, first-hand pieces on the problems I am hired to solve — written so they are useful to operators, and citable by anyone serious about the subject.
What this writing is for
Most writing under the banner of “insights” exists to signal expertise without saying anything you could act on. This is meant to be the opposite. Each piece is drawn from work I have actually done and written to be useful on its own — to leave you with a sharper way of seeing a problem even if we never speak. The test I hold every piece to is simple: does a reader come away with something concrete to use or reconsider? If not, it has not earned its length. I would rather publish fewer pieces that pass that test than a steady stream written to feed a schedule.
The themes recur because they are the recurring truths of operating work. That quality has to be a property of the system, not of whoever happens to be careful. That throughput is usually a flow problem rather than an effort problem. That measurement without decision rights is just observation. That most processes are thick with steps which only compensate for an earlier failure — and that the hardest part of any improvement is making it hold. These are not abstract positions; they are patterns earned across nineteen years and many operations, set down so they are useful to someone facing them now. Read them looking for your own situation, because most operating mistakes are mistakes of diagnosis.
More writing
The single highest-leverage habit for a founder who has become the bottleneck — a weekly operating rhythm that turns scattered decisions into a system the business runs by.
Most leadership dashboards are ignored because nobody believes the numbers. Here is how to build a scorecard that reconciles, leads rather than lags, and gets steered by — not argued with.
Scaling rarely breaks because of effort or talent. It breaks because the operating model that worked at one size becomes the constraint at the next. Here is the failure pattern, and the governance that resolves it.
Your final pass rate looks healthy because it counts the rework. First Pass Yield exposes the hidden cost of getting things wrong the first time — and points straight at where to fix the system.
Where machine assistance genuinely raises the quality ceiling in operations, where it quietly lowers it, and how to deploy it without losing the one thing that matters — accountability.
How a three-step quality framework turned an invisible, recurring revenue leak into a controlled process — and what it teaches about catching delivery shortfalls before the client does.
A practical, first-hand guide to standing up a Business Excellence function that survives scale — the standard, the measurement, the governance, and the order to build them in.
The principles underneath
The single idea this writing returns to most is that good outcomes have to be built into how work is designed rather than left to depend on who happens to be careful that day. When a defect reaches a customer, the instinct is to find who let it through — an expensive instinct, because it teaches people to hide errors and leaves the real cause untouched. The durable move is to trace the failure to the operating model: the missing gate, the handoff with no owner, the metric nobody watched. Fix the system and the defect stops recurring. Blame the person and it simply waits for the next one. Several pieces work through what that shift looks like in practice.
When output plateaus, the reflex is to ask people to work harder or to hire more of them. The writing keeps making the same correction: in most operations, work spends far more time waiting between steps than being worked on, so throughput is capped by the flow between desks rather than by the effort inside them. You lift it by attacking the queues, not by demanding more speed. This is not a comfortable message — it implies the busyness everyone feels is not the same as output — but it is where the largest, cheapest gains usually hide, and it is why adding people to an unseen pipeline so often lowers output per head.
A recurring theme is that most companies build reporting and call it governance. A dashboard shows you numbers; governance decides what happens because of them — who acts when a metric crosses a threshold, what they are empowered to do, and how the decision is tracked to completion. The half almost everyone skips is the decision rights, which is why so many operations have beautiful dashboards and persistent problems. The writing argues, repeatedly, that the value is not in seeing the number but in having wired in advance what the organisation does about it. Until that exists, more measurement just produces more things to look at and not act on.
Improvement is not the hard part; permanence is. A score lifted for a quarter that drifts back the moment attention moves is a story, not an outcome. So a thread running through the writing is the unglamorous work that makes a gain stick: standard work, gates built into the flow, a metric on the operating review, an owner accountable for the number. Without it, every audit becomes an annual rediscovery of the same problems and every transformation quietly decays toward the old way. A gain you cannot hold is not a gain. Designing the causes out, rather than inspecting harder, is what makes the difference durable.
The writing is designed to change the diagnosis first, because that is where most operating mistakes are made. Start from a problem you can actually feel, find the piece that matches it, and use it to see the problem more sharply — where the waiting really is, whether your quality is measured or merely asserted, whether your numbers arrive in time to act on. Then, if it is useful, follow the link into the frameworks, which set the relevant method down precisely enough to apply. The essays are for understanding; the frameworks are for doing. And where you want a principle turned on your specific operation with measurement attached, that is what a diagnostic is for.
What readers most often ask about what these pieces are for and how to use them.
It is for operators facing the problems I am hired to solve, and for anyone serious enough about the subject to want the real version rather than the brochure version. Each piece is meant to be useful on its own — to leave you with a sharper way of seeing a problem even if we never speak. It is deliberately not thought-leadership in the empty sense, where the point is to signal expertise without saying anything you could act on. If a piece does not give a reader something concrete to use or reconsider, it has failed its purpose, and I would rather write fewer pieces that earn their length.
Founders and CEOs of companies that have outgrown improvisation, operations and quality leaders running work at volume, and the boards or operating partners who hold them accountable. You do not need a background in Lean Six Sigma or Business Excellence to follow them — the writing assumes intelligence, not jargon, and explains the discipline in plain terms. If you run an operation where quality, throughput and governance decide whether the business holds its shape, this is written for you. If you are researching whether a fractional operating model fits your situation, it is a good way to see how I think before any conversation.
A handful, repeatedly, because they are the recurring truths of operating work. That quality has to be a property of the system rather than of the people who happen to be careful. That throughput is usually a flow problem, not an effort problem. That measurement without decision rights is just observation. That most processes are thick with steps which only compensate for an earlier failure. And that the hardest part of any improvement is making it hold. These are not abstract positions; they are the patterns I have watched play out across nineteen years and many operations, written down so they are useful to someone facing them now.
The insights are essays — they argue a point, work through a problem, and are written to be read. The frameworks are reference pieces: precise, structured descriptions of specific methodologies, written to be implemented and cited. An insight might explore why quality drifts under scale; a framework sets down the exact staged-QA method you would follow to prevent it. One is for understanding, the other for application. They are linked deliberately, so a reader who wants the thinking behind a method and a reader who wants the method itself can each find what they came for.
When there is something worth saying, not on a content schedule. I would rather publish a smaller number of pieces that are genuinely useful than a steady stream written to feed an algorithm. Each piece is drawn from real work and takes the time it takes to be right. That means the library grows deliberately rather than quickly. If you want to know when something new appears, the most reliable route is to connect on LinkedIn, where I tend to note new pieces, rather than waiting for a newsletter cadence that would only pressure the writing toward volume over substance.
Yes, and they are written to be citable — specific, first-hand, and grounded in real numbers rather than borrowed statistics. If you are quoting a piece in your own work, an internal document, or a talk, a link back and clear attribution is all I ask. The writing is meant to travel and to be useful to people I will never meet; that is part of why it exists. What I would ask you not to do is reproduce a piece wholesale as if it were your own, but quoting, referencing and sharing it with credit is entirely welcome and the point.
Yes. Every piece is drawn from work I have actually done — running Business Excellence at the scale of 2,000+ campaigns and 450 clients, protecting more than USD 20 million in billings with a staged QA framework, compressing a billing cycle from two months to fifteen days. The principles are not theory collected from books; they are patterns earned in operations and tested under real pressure. Where I describe a client situation, confidential clients are characterised by role and scale rather than named, but the underlying experience is genuine. That first-hand grounding is exactly what is meant to make the writing worth your time.
Start by finding the piece that matches a problem you can actually feel, and use it to sharpen how you see that problem — where the waiting really is, whether your quality is measured or merely asserted, whether your numbers arrive in time to act on. The writing is designed to change the diagnosis first, because most operating mistakes are mistakes of diagnosis. If you want the principle applied to your specific operation rather than read in general, that is what a short diagnostic engagement is for: it takes the way of seeing in these pieces and turns it on your business, with measurement attached.
Reference library
The signature frameworks are written up as standalone, citable reference pieces.