Chapter 3

Architecture in the Wild

Moving to California opened a different chapter.

It was less institutional and more experimental.

TRL had been an extraordinary run, but the landscape was shifting fast.

Post-9/11 New York was changing.

Audience behavior was changing even faster.

Ratings were slipping, crowds were thinning, and the ways people consumed media were evolving faster than most organizations could keep up.

I had seen signals like this before. This time, I decided to move before the disruption made the decision for me.

So I went west.

I became bi-coastal, working across independent projects, startups, broadcast, and branded entertainment.

My work moved between San Francisco startups, MTV Los Angeles, and pilots for Dickhouse Productions.

This was a period defined by constant motion, shifting formats, changing clients, and new environments that demanded adaptation.

It was also where I began relying less on institutions and more on systems I could build myself.

The Structural Shift

The most significant evolution happened in San Diego.

As Final Cut Pro began making serious inroads into post-production, traditional models were starting to fracture.

Avid was still the industry standard for large scale jobs, but the systems were massive and massively expensive.

Smaller post houses and independents were shifting toward leaner, more flexible models.

Through agency work, I became involved in building shared media and collaborative production systems inside that transition.

What began as solving practical production problems quickly became a specialization.

The Inflection Point

Once I was being hired specifically for that skill, I realized it was bigger than a technical niche.

Suddenly, the opportunity was no longer simply to edit inside workflows...

It was to help design the workflows themselves.

This was where "systems builder" stopped being something I did and became part of how I worked.

I moved from creative operator to creative architect.

I learned something equally important about leverage during this time period.

If I built the system, I was often expected to stay close enough to support it.

The most effective way to do that was to embed myself inside the system operationally, often by taking an editing role within the very workflows I designed.

That made me more available to clients, increased trust, and created a model where systems design and execution reinforced one another.

It also, pragmatically, created two revenue streams instead of one.

Much of the integrated strategy I deploy today traces back to a realization formed in that period:

The system is often the most powerful tool in the room.

Build the right system, and better work becomes possible.

← Chapter Menu | Next Chapter →