Eric Nelson, MSPM

Operator | Execution & Systems Leader

I’ve spent my career in environments where execution actually matters.

In the Army Reserve, as a logistics officer, there’s no room for ambiguity. You either move resources where they need to go, or the system breaks. Clarity, ownership, and timing aren’t concepts. They’re requirements.

In the private sector, I saw something different.

The problems weren’t a lack of intelligence or effort. Most teams were capable. Most plans were solid.

But execution still struggled.

Not all at once.
Step by step.

Ownership would blur.
Decisions would stall.
Work would move, but not in a way that actually produced results.

And the more complex the environment, the worse it got.

Over time, I found myself getting pulled into those situations.

Programs that were behind.
Teams that were stuck.
Workstreams that looked fine on paper but weren’t actually delivering.

Not to manage more activity.

To fix how execution was working.

Across both the military and enterprise environments, the same pattern kept showing up.

Execution wasn’t failing because people didn’t know what to do.
It was failing because no one was operating the system that controlled how work moved.

So, teams compensated.

More meetings.
More tracking.
More coordination.

And the system slowed down even more.

That’s what led me to write The Unchained Operator.

Not as another project management book, but as a way to define what was actually happening underneath execution, and how to take control of it.

My background reflects that path.

I hold a Master of Science in Project Management from the University of Southern California and was elected to the Phi Kappa Phi Honors Society through USC. I serve as a Field Grade Logistics Officer in the United States Army Reserve, and I’ve worked inside large-scale enterprise programs where execution has real consequences.

But the common thread across all of it is simple.

I operate inside systems where things need to work.

If you’re responsible for making things happen inside complexity,
you’ve likely seen the same problems.

This work is built for that.