Field Service · Fleet · Multi-Site Operations

OPERATIONS
SYSTEMS ARCHITECT

20 years of leadership — from General Manager to Director — turning operating chaos into measurable, ownable systems across 18 restaurants, two cloud kitchens, and a 35-person field service organization with a 34-vehicle fleet.

Goals set direction. Systems create repeatable results. The work below shows the operating architecture behind the outcomes: finite queues, decision rules, capacity visibility, and finance-ready recommendations.

Executive Impact

The numbers behind the systems

Every metric below is the output of a specific operating design, not a one-time push — each is broken down in the case studies further down the page.

“Goals set direction. Systems create repeatable results.”

The work samples that follow show the operating architecture behind the outcomes: finite queues, decision rules, capacity visibility, management cadence, and finance-ready recommendations.

Selected Work

Six systems, six problems solved

Click a lane to open the case study — the same problem / design / outcome structure used to brief every one of these to leadership.

Operating Philosophy

Three ideas that repeat across every system

A hiring quiz, a prioritization matrix, a training curriculum, a handoff procedure — different artifacts, built from the same three habits of mind.

01

Cultural musts ≠ technical musts

Fit and skill fail for different reasons and get fixed by different systems. I build separate, explicit standards for each — one never quietly excuses the other.

02

Systems outrank goals

A goal describes the destination. It says nothing about Tuesday when the plan is inconvenient. Every improvement I've led became real once it was an owned, scheduled system.

03

One inventory, every responsibility

Selection → Standards → Training → Coaching → Execution. Execution itself: learn the system, teach it, run it consistently, then innovate on top.