Selected results
Each of these is a real engagement, told in full — the challenge as it was, the intervention as it happened, and the outcome as it was measured. Where a client name is held in confidence, the numbers are not.
How to read these case studies
The number at the top of each case is the least interesting part of it. A newsroom’s throughput quadrupled to roughly 400 stories a day; more than USD 20 million in billings was protected; a quality score moved from 95% to 99% across 2,000+ campaigns and 450 clients; a billing cycle fell from two months to fifteen days across 75 entities. Those figures tell you the work succeeded. They do not tell you how, and the how is what you are here for. So each case is written as a sequence — the challenge as it actually was, the intervention as it happened, the outcome as it was measured — and the value for a reader is in the middle section, the reasoning, not the headline.
Read them looking for your own situation rather than for the biggest number. The sectors differ — media, advertising, shared services, multi-entity enterprise — but the failure modes recur: work queueing where no one can see it, quality asserted rather than measured, processes thick with steps that only compensate for an earlier failure. If one of these challenges sounds like your business, the way that problem was diagnosed and unpicked will be far more useful to you than the specific figure it produced. The figure is evidence the method works. The method is the thing you can actually use.
How these outcomes hold up
Why measured proof beats a confident claim
Operations is a field crowded with assertion. “We improved efficiency” and “we raised quality” mean nothing without a baseline, a number and a method. A measured result can be examined, questioned and trusted: a cycle time that fell from roughly two months to fifteen days is a claim you can interrogate; “we made billing faster” is not. Everything on this page is reported the harder way, against a figure, because that is also how the work was done. The discipline of measurement is not a reporting style applied afterward — it is the method that produced the outcomes in the first place.
The metric is defined before the work begins
The most common way to fake a result is to redefine the target after the fact. I work the other way: the measure is agreed up front, in precise terms, so the outcome cannot be moved by quietly changing what was being counted. A throughput figure is stories produced at a sustained run-rate, not a single good day. A quality score is measured against a fixed standard across thousands of campaigns, not a flattering sample. A cycle time is the real elapsed time across every entity in scope. Defining the measure first, then proving the change against it, is the core of the Lean Six Sigma discipline — it is what separates a genuine, sustainable gain from seasonal noise.
Why confidential clients are anonymised, not embellished
Senior operating work reaches deep into a company’s processes, finances and weak points, and discretion is part of the role. So where a client is held in confidence, I describe the organisation by role and scale — a global advertising network, an enterprise media operation, a multi-entity enterprise — and leave it unnamed. What I never do is soften the numbers to compensate. Anonymising a client protects a relationship; altering the figures would defeat the entire purpose of a case study. A reader should be able to trust that the proof is real even when the name is withheld, and that is the line these cases hold.
A result that does not hold is not a result
The hardest part of any improvement is not achieving it but keeping it. A score lifted for a quarter that drifts back the moment attention moves is a story, not an outcome. So the engagements behind these numbers did not end at the result — they ended at the structure that holds it: standard work, gates built into the flow, a metric on the operating review, an owner accountable for it. The quality lift from 95% to 99% mattered because the systemic causes were designed out, so the gain did not unwind. When you read these cases, the durability is the quiet point. The number is only worth reporting because it stayed.
What this means for your operation
Most operations carrying real volume have a number like these hidden in them, unmeasured: a billing cycle nobody has timed end to end, a quality rate expressed as a comforting percentage that hides a large absolute figure, a process thick with approvals that compensate for an earlier failure. The honest way to find it is not to assume your business will repeat someone else’s figure — every operation is different — but to measure where the biggest, most provable gain is actually sitting. That is what a short diagnostic is for. The result a case study reports belongs to that business; the method that found it is what I would bring to yours.
Questions about these results
What people most often want to know about how these outcomes were produced, measured, and reported.
Because senior operating work goes deep inside a company’s processes, finances and weaknesses, and discretion is part of the job. Where a client is held in confidence, I describe the organisation by role and scale — a global advertising network, an enterprise media operation, a multi-entity enterprise — rather than naming it. What is never softened is the measurement: the numbers, the volumes and the outcomes are reported exactly as they were. Anonymising the client protects a relationship; changing the figures would defeat the entire point of a case study. The proof has to be real even when the name is withheld.
Read each as a sequence, not a headline. Every case is told in three parts: the challenge as it actually was, the intervention as it happened, and the outcome as it was measured. The number at the top — 4×, USD 20M+, 95% to 99%, two months to fifteen days — is only the result. The value for you is in the middle: how the problem was diagnosed and what specifically changed. A company recognising its own situation in the challenge section will learn far more from how the intervention was reasoned than from the figure it produced. The figure tells you it worked; the narrative tells you why.
Because operations is a field crowded with assertion. “We improved efficiency” means nothing without a baseline, a number and a method. A measured result — a cycle time that fell from roughly two months to fifteen days, a quality score that moved from 95% to 99% across 2,000+ campaigns — can be examined, questioned and trusted. It also reflects how I work: every engagement agrees its measures up front and proves the gain against them, rather than declaring success in adjectives. The discipline of measurement is not just how these results are reported; it is how they were produced in the first place.
They are real engagements chosen because each illustrates a distinct discipline — throughput, quality governance, staged QA, process compression — not because they are unrepeatable peaks. That said, no honest advisor promises that a specific number will recur; every business is different, and the figure a given engagement produces depends on where the operation starts and how much slack is in it. What does transfer is the method. The reason to show these is to demonstrate how the work is reasoned and what kind of change is possible, so you can judge whether the same discipline would find a number like these, still unmeasured, in your own operation.
Against an agreed baseline, with the metric defined before the work began so the result could not be moved by redefining the target afterwards. A throughput figure is stories produced at a sustained run-rate, not a single good day. A quality score is measured against a fixed standard across thousands of campaigns, not a flattering sample. A cycle time is the real elapsed time across all the entities in scope. Defining the measure up front, then proving the change against it, is the core of the Lean Six Sigma discipline I apply — it is what separates a genuine, sustainable gain from seasonal noise or a temporary push.
Often, yes — most operations carrying real volume have a number like these hidden in them, unmeasured. A billing cycle nobody has timed end to end, a quality rate expressed as a comforting percentage that hides a large absolute figure, a process full of approvals that compensate for an earlier failure. The honest way to find out is a short diagnostic: a low-commitment window that measures how your work actually moves and identifies where the biggest, most provable gain is sitting. The result a case study reports is specific to that business; the method that found it is what I would bring to yours.
It varies with the scope, and the cases describe the arc in each instance. As a rule, an early, visible win comes relatively quickly — relieving the tightest constraint in a pipeline, or settling the definitions behind a number nobody trusts. The deeper, durable change builds over the following weeks and months as the new operating model beds in. The sequence is deliberate: deliver a tangible improvement early, then install the structure that makes the gain permanent rather than a temporary push that fades once attention moves elsewhere. A result that does not hold is not a result; it is a story about last year.
Where a client is named and willing, a reference can sometimes be arranged at the appropriate stage of a conversation — but I do not publish contact details or trade on relationships, and confidential clients remain confidential. The more useful early step is usually a diagnostic of your own operation, which tells you far more about whether the working relationship fits than a reference call ever could. The case studies are written in enough detail that you can interrogate the reasoning directly; that transparency about method is deliberately the substitute for asking you to take the outcomes on trust.