*Architect of Predictability*
I stabilize engineering organizations by eliminating drift, restoring clarity in execution, and building systems that behave predictably—even amid AI‑generated complexity.
My discipline, EMI (Engineering Maturity Institute), introduces a new class of verification primitives that expose silent AI logic failures long before they destabilize delivery. I help teams move from ambiguity to confidence by aligning hardware, firmware, software, and product groups around truth‑based engineering, predictable execution, and disciplined reasoning‑path verification.
The Discipline: EMI
EMI is a new engineering discipline built for the AI era. It introduces primitives that detect drift, expose unstable reasoning paths, and restore predictable system behavior.
The first primitive, Code‑Probe‑IF, identifies AI‑generated IF‑condition failures that traditional testing cannot see.
What I Do
I lead cross‑functional engineering organizations through clarity, maturity, and disciplined execution. My work focuses on stabilizing ambiguous, high‑complexity environments — especially those impacted by AI‑generated logic — and transforming them into predictable, teachable systems that teams can execute with confidence.
I operate at the intersection of hardware, firmware, software, and safety, where rigor, calm leadership, and reasoning‑path discipline matter most.
Selected Leadership Stories
I’m a systems‑driven Technical Program Manager with deep experience in safety‑critical software, Standards maturity (including ASPICE), and cross‑functional engineering alignment. My work focuses on transforming ambiguous, high‑complexity environments into predictable, teachable systems that teams can execute with confidence. I operate at the intersection of hardware, firmware, and software, where clarity, rigor, and calm leadership matter most.
Across my career, I’ve helped organizations elevate engineering discipline, strengthen their safety posture, and deliver reliably under pressure. Whether coaching teams through ASPICE 4.0, driving system readiness in autonomy programs, or building frameworks that outlast my tenure, I focus on creating sustainable, repeatable patterns that raise the entire organization.
I’m confident in any space because I bridge the gap between specialists — and I know how to get the right upstream and downstream people involved for the system's greater good.
⭐ Selected Leadership Stories
1. Stabilizing a Global ASPICE Compliance Assessment
On Day 1 of an external ASPICE Compliance assessment — after six months without a software ASPICE lead — I stepped into a worldwide engineering organization with no preparation or alignment in place. What followed was a week of real‑time stabilization and a six‑month uplift effort that rebuilt training, processes, design practices, testing strategies, and cross‑functional reviews across global teams. The result was a 20–30% improvement in the next assessment.
2. Broadcast Engineering / FIFA World Cup Delivery
In a mission‑critical broadcast environment powering the industry’s core production systems, I led a cross‑functional engineering effort to deliver the end‑to‑end platform for the first HD‑televised FIFA World Cup. I built and led the IV&V function, operationalized a system‑level validation framework, and ensured critical failures surfaced early and were regressed across every build… enabling a flawless global broadcast under immovable deadlines.
3. The Global Training & Organizational Uplift Story
I designed and delivered a global training program that aligned engineering teams across continents on process maturity, safety expectations, and system behavior. This work improved compliance, reduced friction, and created a shared language that accelerated collaboration across the organization.
4. The Critical Bug Discovery / Trust‑Building Story
During a complex integration cycle, I uncovered a subtle but high‑impact defect that had evaded multiple teams. Instead of escalating blame, I used the moment to build cross‑team trust, establish a repeatable debugging workflow, and strengthen relationships among development, QA, and systems engineering.
5. Full‑Scale Validation With Scarce Hardware
When the 1024×1024 routing system reached integration, we didn’t have enough production boards to populate even a single rack. Hardware provided a limited number of early pilot boards that they manually updated to match the latest manufacturing run. Using those scarce, hardware‑modified boards, I designed a rotation‑based validation strategy that allowed us to exercise every critical path — HD, NTSC, PAL, audio, timing, arbitration, and inter‑rack links — across the full fabric. This approach validated the system under real conditions and became the standard method for multi‑rack firmware validation.