Results, not transformation theatre.

My own engagements, with context, baseline and verification — from aerospace, automotive and heavy industry to the AI systems running my own operation. Company names are confidential; the numbers were internally audited.

Aerospace · Flow & Accountability

From a 30-day verification backlog to next-day flow

Situation

A tier-1 supplier network feeding a major European aircraft manufacturer was drowning in verification backlog. Parts sat for weeks waiting for quality disposition.

What was at risk

Programme milestones, penalty discussions on every late shipment, and the credibility of the entire verification chain.

Baseline

Verification lead time of up to 30 days; delays escalating to programme level; no single owner of a part’s waiting time.

What I changed

  • Mapped the verification chain end to end — 80% of the delay was routing and ownership, not inspection time.
  • Redesigned routing so every part had one accountable owner and a clock that never stopped silently.
  • Standardised quality gates so decisions happened at the gate — not in escalation meetings after it.

Measured result

97%verification lead-time reduction (30 days → next-day)
0programme milestones missed after stabilisation

How the result was verified

Lead-time KPIs tracked before and after in the programme’s own reporting; internally audited within the quality organisation.

What remained after handover

The routing verification KPIs and gate discipline stayed in daily use — no new software or headcount was needed to sustain them.

Similar backlog on your floor? →

Automotive · Quality Recovery

From permanent firefighting to 18 months without a customer escalation

Situation

A metal-forming supplier to major automotive OEMs was in permanent escalation: recurring complaints, special status with two OEMs, audit findings piling up faster than they were closed.

What was at risk

Existing business with the OEMs, new-programme awards, and a leadership team consumed by customer calls instead of running the plant.

Baseline

Special status with two OEM customers; a year of recurring escalations; 8D reports closed on paper but not in the process.

What I changed

  • Rebuilt the complaint-to-root-cause discipline: every 8D closed with evidence, not paperwork.
  • Installed a VDA 6.3–based internal audit programme run as coaching, not policing.
  • Negotiated directly with OEM supplier-quality engineers to reset expectations and rebuild trust with a visible roadmap.

Measured result

0customer escalations for 18 consecutive months
OEM special status lifted, standard status restored

How the result was verified

Escalation status is the customer’s own scorecard — both OEMs formally lifted the special statuses. Complaint and audit trends were tracked in the plant’s QMS.

What remained after handover

The audit programme and complaint discipline survived after I left — escalations end when the customer sees the same defect never twice, and that takes a system, not heroics.

In escalation with a customer? →

Heavy Industry · Hidden Cost

From fragmented loss data to more than €2M in verified annualised savings

Situation

Scrap, rework and warranty were treated as separate line items owned by nobody. Individually each looked tolerable; together they were quietly consuming millions — the classic invisible factory.

What was at risk

Margin erosion with no single owner, and improvement budgets impossible to justify because the loss was never visible in one place.

Baseline

No consolidated cost-of-poor-quality model; loss drivers unranked; no owner, target or review cadence on any of them.

What I changed

  • Built a single Cost of Poor Quality model consolidating scrap, rework, sorting, warranty and expedited freight.
  • Ranked the top 10 loss drivers and assigned each an owner, a target and a monthly review cadence.
  • Trained line leadership to read and challenge the numbers themselves.

Measured result

€2M+verified annualised savings
10/10top loss drivers with named owner and trend

How the result was verified

Quality and finance built the model together, so finance owned the numbers from day one. Savings were verified against the P&L, not a quality-department estimate.

What remained after handover

The CoPQ model and the monthly ownership rhythm outlived the project — when CoPQ hits the P&L review, improvement funds itself.

Suspect an invisible factory? →

AI Systems · My Own Operation

An autonomous AI company and a private company model — built, run and measured on my own operation

Situation

Before recommending AI-enabled operating models to clients, I built one for real: Velin, an autonomous AI company that runs my own operation — agents that propose, execute and verify work under human authority.

What was at risk

Credibility. An advisor who has never run AI in production is selling slides. This system is the proof that the governance I recommend actually works under load.

Baseline

A one-person operation with knowledge trapped in files and history — the same institutional-memory problem every complex company has.

What I changed

  • Built an agent workforce with separation of duties, independent verification and a permanent journal.
  • Added Velin Sovereign: a private model on my own infrastructure, answering from the company’s own record with a source under every sentence.
  • Applied quality-system discipline throughout: human GO on anything that matters, audit trail, kill switch.

Measured result

5,812fragments of company record the private model reads
10/10acceptance evaluation · 0 invented answers on trap tests

How the result was verified

Every answer the system gives is recorded, sourced and reviewable. The acceptance run included deliberate trap questions about things never written down — all answered with “I don’t have that” rather than an invention.

What remains in operation

The system runs my operation daily and is demonstrable live — not a lab demo. See Velin · Ask Sovereign a question

How I build AI for companies →

Client names withheld under confidentiality. All figures were internally audited results of programmes I led or co-led.

SECONDARY · PUBLIC EVENTS, NOT CLIENT WORK

Public case analyses — how complex systems fail

Beyond my own engagements: famous, publicly documented quality failures dissected one case file at a time — what broke, why, and which discipline would have caught it.

Jack in the Box: how a temperature spec cost four children their lives
Food & Beverage

Jack in the Box: how a temperature spec cost four children their lives

In aerospace, when I rate a failure mode as Severity 10 on a PFMEA, the next question is not "can we work around this." The question is "what engineered control eliminates the failure mode." If a…

Case file #39·August 4, 2026·6 min readRead case →
IKEA Malm: how ignored misuse caused a 17-million-unit recall
Consumer Products

IKEA Malm: how ignored misuse caused a 17-million-unit recall

Hierarchy of controls. Elimination, substitution, engineering controls, administrative controls, and at the very bottom — the warning label. A leaflet stuffed in a flat-pack box is an administrative…

Case file #38·August 3, 2026·5 min readRead case →
Sony: how particle contamination ignited a 9-million-unit battery recall
Consumer Products

Sony: how particle contamination ignited a 9-million-unit battery recall

A microscopic metal particle caused Sony's 2006 recall of 9 million batteries. A case study showing defect cost is driven by system scale, not particle size.

Case file #37·August 2, 2026·6 min readRead case →
Theranos: how bypassing APQP and validation built a $9bn fraud
Medical & Pharma

Theranos: how bypassing APQP and validation built a $9bn fraud

A quality professional examines how Theranos scaled process bypass and ignored validation to a $9bn valuation—putting real patients at risk.

Case file #36·August 1, 2026·5 min readRead case →
De Havilland Comet: how a window shape dictated aerospace fatigue testing
Aerospace

De Havilland Comet: how a window shape dictated aerospace fatigue testing

The gap between "strong enough on paper" and "strong enough after the three-thousandth pressurisation cycle" is the gap that killed fifty-six people. I think about this every time a junior engineer…

Case file #35·July 31, 2026·6 min readRead case →
Ariane 5: how unvalidated software reuse doomed a maiden flight in 40 seconds
Aerospace

Ariane 5: how unvalidated software reuse doomed a maiden flight in 40 seconds

Ariane 5's maiden flight self-destructed in 40 seconds due to inherited Ariane 4 software that couldn't handle higher velocities—a $500M lesson in unvalidated code reuse.

Case file #34·July 30, 2026·5 min readRead case →

Browse all 39 case files →

Similar problem in your company?

A focused conversation costs nothing and usually locates the constraint in under an hour. No slides, no pitch — an experienced pair of eyes on your situation.

Discuss Your Company
I reply within one business day. US and European time zones supported.