Speaking
Systems, diagnostics, and the judgment required when the easy story is incomplete.
Talks for engineering conferences, leadership events, and technical teams, grounded in real work across software delivery, architecture, AI, diagnostics, and organizational systems.
Representative talks
Sessions can be adapted to the audience and format.
The emphasis is practical: how people reason about complex systems, what evidence changes a decision, and how engineering structures can reduce avoidable failure.
-
01
Systems · Keynote
The Diagnostic Mindset: How to See What Others Miss
A cross-domain approach to separating symptoms from system behavior and finding the evidence that changes the diagnosis.
Discuss this talk -
02
Failure · Keynote
Failure Has a Pattern
What software incidents, operational failures, and other complex systems teach about drift, coupling, incentives, and early warning signals.
Discuss this talk -
03
Architecture
Architecture as a System of Constraints
Why architecture is less about diagrams than about making dangerous choices difficult and desirable behavior easy to preserve.
Discuss this talk -
04
Engineering
How to Read a Codebase Like a Detective
A forensic approach to code, tests, names, structure, history, and the organizational decisions embedded in a system.
Discuss this talk -
05
AI · Judgment
AI Adoption That Preserves Judgment
How to use AI to compress work and ambiguity without quietly outsourcing accountability, evidence, or domain authority.
Discuss this talk -
06
Leadership
Decision-Making Under Pressure
A practical model for acting with incomplete information, distinguishing reversible from irreversible moves, and updating as evidence changes.
Discuss this talk
Speaker bio
Engineering leadership informed by systems thinking and cross-domain diagnostics.
Kevin M. Miller is an engineering leader, systems strategist, and founder of Echelon Foundry. His work focuses on modernization, explicit system design, diagnostics, AI adoption, security, and technical decision-making under constraint.
He has led engineering organizations and enterprise platform work for more than 25 years and writes about how systems fail, how teams reason under uncertainty, and how architecture can preserve judgment instead of hiding it.