The programs I’m proudest of, and how I ran them.

A field failure mode was traced back to our component after years of investigation. I led the root-cause work, including live teardowns with the customer on-site. Every confirmed failure meant an engine pulled off the wing for repair. That was real, direct cost, and very little patience from the operators flying those business jets.

Eighteen months was the honest estimate for the redesign. Due to the critical nature of the failure, the cost of repair, and the implications for the customer, it was imperative to deliver the program as efficiently as possible. The customer requested a critical design review four months from kickoff, and stayed engaged throughout the program to accelerate the review process, including an engineering manager who came on-site three to four times, more than his role would normally call for.

I mapped the real critical path myself. The bottleneck wasn’t the engineering. It was long-lead test parts and review cycles that had been built in from a slower prior experience with this customer. Rather than absorb that quietly, I was transparent about where their own review cycles were adding time.

I chose to qualify by similarity and analysis over new physical testing wherever it was defensible. That meant reconstructing evidence from sparse, disorganized legacy documentation, but it kept the schedule honest instead of padding it with tests we could justify avoiding.

Six months of daily customer meetings. Every workstream ran in parallel: testing, documentation, procurement, manufacturing. I was doing the engineering and the program management at the same time.