Case Study · Technical Program Management
Changing
the Engine
in Flight
How I took full ownership of release governance across a 60 stakeholder enterprise program and delivered 100% on time, zero severity incidents, zero compliance findings — across 30+ production deployments.
A Mission Critical Platform.
No Shared Definition of Ready.
A healthcare enterprise was running 30+ production deployments per year across an SAP S/4HANA platform supporting $100M+ in regulated revenue. Every release touched multiple engineering teams, compliance windows, and integrated systems that required zero unplanned downtime.
The release process lacked a shared standard. Each team operated with its own definition of ready. Go/No Go decisions were made reactively, often by whoever happened to be in the room. Executive stakeholders were regularly learning about issues they should have been informed about weeks earlier. SOX audit exposure was real. The cost of an unplanned outage ran $50,000 to $100,000 per hour.
“Changing the engine in flight” describes this operating condition precisely. The platform served active business operations around the clock. Every change had to work on the first attempt, under full production load, with no rollback window.
The work required wasn't coordination. It required someone to own the outcome — design a system that didn't exist, earn the credibility to operate it across teams with no formal authority, and hold the standard even when timelines were under pressure.
Took Full Ownership and Built
the Operating Model from Scratch
-
Owned the governance design end to end
Built readiness reviews, Go/No Go decision frameworks, and runbooks from scratch. Every document was written to be executable by any team lead under any condition, so execution quality depended on the system design, regardless of who was available.
-
Built a program health metrics framework with real executive signal
Defined schedule variance, change failure rate, and release quality as the three core indicators, reported weekly to leadership. The goal was to give executives genuine visibility into risk so they could make informed decisions rather than react to surprises.
-
Created a live dependency map across all 8 to 12 engineering and infrastructure teams
Cross team conflicts were surfaced and resolved before each release window opened. The dependency map became the shared source of truth every team referenced going into a cutover.
-
Established command center execution protocols for every high risk go live
Named owners for every integration. A clear escalation path everyone had agreed to in advance. Real time status visible across all teams. When an in flight decision was needed, the decision path was already established and the right people were already in the room.
-
Ran structured retrospectives that actually changed how the next cycle ran
After every release, facilitated a focused retrospective, documented specific process gaps, and updated the runbooks before the next window opened. Improvements compounded quarter over quarter because learning was built into the operating rhythm.
Measurable Impact Across
Every Dimension That Matters
These are verified outcomes from programs I owned end to end, measured and reported to executive leadership across full delivery cycles.
Executive stakeholders shifted from reactive surprise to proactive confidence — because the data was already in front of them before they asked.
The Technical Environment
This program ran inside a heavily regulated enterprise technology stack. The tools and systems listed here are the actual environment I operated in across regulated enterprise programs.
The Culture Fit,
Culture Fit and Skill Match
The programs I ran were built on candor and direct communication. I surfaced hard risks before they became leadership surprises, pushed back on scope when it was the right call, and earned trust through consistency over time, through credibility built across every cycle.
The governance model in this case study was built from credibility and adopted because it made engineering teams more effective. I take full ownership of outcomes, including the things outside my formal scope, and I move on fixing problems before anyone asks.
I use GenAI tools daily to accelerate program planning, automate status reporting, and surface risk signals at a speed that manual review cannot match. I built the Program Health Pulse tool — a free program health diagnostic — which reflects the same frameworks used inside high performing engineering organizations.
Beyond the Program,
Giving Back
Program management is about unlocking the potential in people — including the systems that are human. This is how I apply that same work outside of my professional role.
I designed and facilitate a free, five-session program for underprivileged high school students in Indianapolis. Using CliftonStrengths, Holland Code, and DISC assessments, students identify their natural academic strengths, map those strengths to subject choices, and build a personalized college readiness plan. Every session is structured, strength-based, and delivered at no cost to the student or their family.
The same skills that make me effective managing a 60-person enterprise program — facilitation, structured frameworks, clear communication across different audiences — are the skills that make this program work for a 16-year-old who has never been told they are good at anything.
View Catalyst Edge →Ready to build something together?
Open to the right opportunity. I’d welcome a direct conversation.