SELECTED WORK

Case studies built around operating systems, not just job titles.

These samples translate the public resume into portfolio-grade proof: how problems were framed, what decisions changed the delivery system, and where measurable movement came from.

Client names are intentionally omitted and some implementation detail is generalized, but the operating patterns map directly to the environments I have led.

Open Résumé

WHAT THESE PAGES PROVE

  • Portfolio control: I can turn a messy set of dependencies into a repeatable operating rhythm.
  • Cross-functional translation: I connect field teams, executives, technical leads, and outside stakeholders without losing speed.
  • Outcome discipline: Every example centers on throughput, risk, timing, or governance quality rather than activity volume.

Clean Energy Operations

Solar Program Acceleration

How a portfolio-level reset shortened handoffs, clarified readiness, and improved throughput across a high-volume solar program.

  • Reset handoffs across design, permitting, utility coordination, and install readiness.
  • Built a five-day notice-to-proceed target for standard-ready projects.
  • Made aging exceptions and owner clarity visible at portfolio level.

Focus: phase-gates, utility coordination, portfolio visibility

Read Case Study

Enterprise Operations

Enterprise Device Ops

A governance-driven operations model for device lifecycle, recovery readiness, and exception management at enterprise scale.

  • Standardized lifecycle language and exception ownership.
  • Improved readiness for recovery exercises and executive reviews.
  • Reduced noise by separating routine flow from true escalation work.

Focus: service operations, lifecycle controls, resilience

Read Case Study

Defense Delivery

Defense Program Delivery

Stabilizing execution across a defense portfolio by tightening schedule integrity, risk burn-down, and decision cadence.

  • Unified milestone reporting across cross-functional workstreams.
  • Turned risk reporting into a weekly decision mechanism.
  • Improved executive confidence through cleaner escalation rules.

Focus: IMS discipline, reporting rhythm, change control

Read Case Study

Read these as operating-system resets. Each case shows the delivery pressure, the mechanism that changed, and the evidence that the system moved.

Solar Program Acceleration

Clean Energy Operations

Pressure
High project volume with fragile handoffs between contract close and field readiness.
Reset
Phase-gates, a dedicated exception lane, and a five-day readiness target for standard-ready work.
Evidence
~50 percent faster PTO cycle time with calmer queue management.
Open case

Enterprise Device Ops

Enterprise Operations

Pressure
Large installed-base operations with fragmented language, stale exception ownership, and slow resilience prep.
Reset
Shared lifecycle taxonomy, exception review cadence, and named pre-drill readiness criteria.
Evidence
Exception backlog down by roughly one-third with inventory variance pushed below five percent.
Open case

Defense Program Delivery

Defense Delivery

Pressure
Parallel workstreams with fragile milestone confidence and risk debates eating executive time.
Reset
One integrated milestone view, weekly burn-down accountability, and earlier escalation thresholds.
Evidence
Overdue risks reduced by about 40 percent across $66M+ in managed scope.
Open case

REPEATABLE DELIVERY PATTERNS

Reset the handoffs

Most schedule pain starts at the seams. I define exit criteria, owner clarity, and escalation rules before asking teams to move faster.

Make risk visible

I treat risk reporting as an operating mechanism, not a slide. Teams move better when exposure, aging, and decisions are easy to read.

Design for the next operator

Repeatability matters. The goal is a system that still works when volume increases, staffing changes, or leadership turns over.