The simplest way to make consulting honest is to name the engineer who will ship the work. Not the partner. Not the delivery lead. The person committing code, writing runbooks, and sitting in the incident review.
What changes in practice
The useful version is specific, measurable, and owned by one person. That is the difference between a page that looks finished and an operating practice that survives production pressure.
The operating test
We treat this as real only when it changes a dashboard, a runbook, and one named engineer’s weekly work. If the idea cannot survive those three places, it is probably just a slide.
The useful version is specific, measurable, and owned by someone who can say what changed after it shipped.
What we would do differently
- Instrument before changing architecture. The baseline decides whether the fix worked.
- Name the trade-off. Every improvement costs latency, money, complexity, or time somewhere else.
- Revisit it after 30 days. Production has a way of teaching what the workshop missed.