Operating Pressure
Throughput under constraint
Used phase-gates, queue-age visibility, and an exception lane to keep solar work moving without hiding blockers.
Signal: 80+ projects per year with PTO cycle time cut roughly in half.
See the solar caseMy work sits where cross-functional execution gets messy: solar operations, defense programs, and enterprise-scale technology environments. I bring structure, risk discipline, and calm stakeholder management so teams can ship real outcomes.
The portfolio below turns resume bullets into confidentiality-safe case studies focused on the operating mechanisms behind the results.
Sectors served: Renewable Energy, Defense, and Enterprise IT. Delivery style: clear ownership, early risk visibility, and measurable movement instead of status theater.
Operating Pressure
Used phase-gates, queue-age visibility, and an exception lane to keep solar work moving without hiding blockers.
Signal: 80+ projects per year with PTO cycle time cut roughly in half.
See the solar caseGovernance Reset
Standardized lifecycle language and exception ownership so enterprise operations could make decisions from one clean operating picture.
Signal: exception backlog down by about one-third in a 100k+ device environment.
Open the enterprise caseExecutive Cadence
Connected schedule integrity, risk burn-down, and escalation thresholds so leaders could act earlier instead of debating status.
Signal: overdue risks reduced by about 40 percent across a $66M+ defense portfolio.
Review the defense caseCross-Domain Pattern
The same approach repeats across clean energy, defense, and enterprise ops: define readiness, age exceptions, and make ownership obvious.
Signal: the portfolio reads as systems thinking, not a disconnected set of job titles.
Browse all case studiesClean Energy Operations
Portfolio-level controls that reduced PTO cycle time, tightened readiness, and helped sustain 80+ projects per year.
Enterprise Operations
A lifecycle-governance reset for a 100k-plus device environment where resilience and clean reporting mattered.
Defense Delivery
Execution controls for a $66M-plus portfolio where schedule integrity, burn-down rhythm, and decision speed all mattered.
I start where work gets stuck: handoffs, decision rights, and definitions of ready. Most schedule slip hides there before it appears in a dashboard.
My preferred lens is schedule integrity, aging exceptions, and risk burn-down. Teams need live operating signals more than decorative status decks.
Strong systems survive growth, turnover, and pressure. I aim for operating models that still make sense when the volume doubles.
Program governance, risk and issue management, field-to-office coordination, stakeholder reporting, enterprise operations, and delivery-system design.
Background includes U.S. Army CW2 (Ret.), renewable energy, defense, and large-scale IT environments.
Program or project leadership roles where scope, accountability, and stakeholder complexity are real.
Discuss a roleShort engagements focused on delivery-system cleanup, governance cadence, or execution visibility.
Scope advisory fitProgram execution, AI-enabled operations, stakeholder trust, and scaling delivery in transition-heavy environments.
Ask about availability