Mason James Gray

Senior Operations Leader · Writer

Mason James Gray.

Fifteen years building and fixing operations at companies scaling faster than their processes could handle. Multi-site field ops, national programs, director-level ownership of programs north of $100M.

Mason Gray

Selected work

What the fifteen years actually look like.

Three chapters that shaped how I think about operations. Each one broke differently, and each one taught something the others could not.

01

National Program Management

Built a 30-plus person program management organization from nothing for a last-mile segment north of $100M. Senior managers, program managers, analysts, and a service advisement team, national in scope.

02

A Four-State Turnaround

Took over an underperforming West Coast region and rebuilt it. Inventory variance from north of 20% to under 2%. Regional billability to 94%. A leadership bench developed and promoted out of the technician ranks.

03

Systems That Outlast The Operator

Operating models, SOPs, standardized intake, and the reporting that makes performance legible. The work that keeps running after the person who built it moves on.

Background

Where the depth actually is.

I started in the field and worked up through it. Vendor management, then a four-state region, then national program management. These are the areas I have spent the most time in and have the most to say about.

  • Operating models and governance design
  • Enterprise program management and PMO structure
  • Operational excellence and continuous improvement
  • Span of control and org design
  • Multi-site field operations
  • Forecasting and capacity modeling for staffing
  • KPI reporting and operational visibility
  • Fleet, automotive, and last-mile logistics
  • Regulatory and DOT compliance programs
  • Developing first-time operations leaders
Mason Gray at work

15yrs

in operations

Operations, in practice

Operations backed by real-world experience.

My first operations job was a two-bay diesel shop where I drove the tow truck and answered the phone. It grew into a ten-bay facility with a towing division, and I learned the whole business from underneath it.

Since then I have run operations at nearly every scale. Teams of ten. A four-state region. National programs with hundreds of people across dozens of sites, and director-level ownership of scopes north of a hundred million dollars.

The pattern was always the same: companies scale, processes break, and people fill the gaps with workarounds until the workarounds are the process. I got very good at finding those gaps and closing them.

$100M+

Programs led

Multi-Site

National scope

Director

Level

Frequently asked

Questions, answered.

What kind of operations have you run?

Multi-site field operations, a four-state region, and national program management — mostly in fleet, last-mile logistics, and complex services businesses. Director-level ownership of programs north of $100M. Fifteen years of it, and most of that time the business was growing faster than the process could hold.

What do you actually write about?

The gap between how an operation is designed and how it actually runs. Span of control, cadence, accountability, decision quality under pressure. Frameworks I have used, and the ones I got wrong first.

What is The Operating Lane?

A weekly essay on operations leadership at mid-market companies. Frameworks, audits, observations from a 15-year operator. Tuesday morning, in your inbox and on LinkedIn. No fluff, no engagement bait.

What industries do you know best?

Fleet and last-mile logistics, multi-site field services, automotive, and complex services operations. The operational primitives travel — span of control, cadence, accountability — but the depth is strongest where the work happens in the field, across many sites, with a real ops team running it.

How do you think about AI in operations?

AI is downstream of process. If the process is broken, AI accelerates the broken thing. Most AI projects fail at the audit phase, not the build phase. Fix the operating model first, then decide what to automate.

Where else do you publish?

Long-form on this site and on LinkedIn Newsletter. Shorter notes a few times a week on LinkedIn.

In conversation

If any of this lands, let's talk.

I write for operators working through the same problems. If something here is useful, or you think I have it wrong, I read every message.