Before You Automate Anything, Draw the Blueprint

I’ve been away from serious work for a couple of weeks.

Traveling. Coming home. Getting back into my normal routine.

This morning I woke up knowing it was time to get my ass back to work.

And I didn’t need another productivity app to do it.

I didn’t need to punish myself for being away, and I didn’t need to work twice as hard to catch up.

I needed to do something I learned decades ago, standing on construction jobs with a set of plans I barely understood.

Pull out the blueprints.

Figure out where the hell I am.

The Trees Were Already on the Plans

I learned that lesson when I was a third-year electrical apprentice working on the Roybal Federal Courthouse in Los Angeles.

At that point, I was still just trying to understand electrical work.

Then I started looking through the complete drawing set for the project, and it was a different world.

There were electrical drawings, obviously.

But there were also structural drawings.

• HVAC
• Plumbing
• Steel
• Engineering

All these different sets showing different parts of the same building.

Half of it might as well have been written in another language.

I barely understood my own trade, let alone what the plumbers, ironworkers, HVAC guys, engineers, and everybody else were doing.

But there was one set of drawings that blew my mind.

The landscaping plans.

We were still building the fucking building.

The structure was going up.

And somebody had already decided where the trees were going to go.

Where the plants would sit.

What the outside of the place would eventually look like.

If I remember right, those drawings were already two or three years old.

Which meant somebody had been thinking years beyond the stage I was physically seeing.

The building wasn’t finished.

People hadn’t moved in.

And someone already knew where a tree was eventually going to stand.

I remember thinking:

Obviously, things changed.

Construction drawings always change.

But somebody had thought through the finished product—not just the building, but the trees around it—years before we ever showed up.

That changed the way I thought.

What if I did that with my life?

Around 1990, I started treating my life more like a construction project.

I began with three questions:

• Where am I?
• How did I get here?
• Where do I want to go?

Over the years, a fourth question became obvious:

What’s the blueprint that gets me from here to there?

Knowing the Destination Isn’t Enough

Knowing where you want to go isn’t enough.

You need some sense of how the pieces fit together.

What has to happen first?

What depends on something else?

What can happen at the same time?

What needs to be finished before something gets built over it?

What should you ignore because you’re not ready for it yet?

Who do you need?

What resources do you need?

And only then:

What tools will make the work easier?

A blueprint isn’t fortune-telling.

I didn’t predict exactly what my life would look like thirty years in the future.

Plans change.

Life changes.

Priorities change.

Reality shows up and laughs at some of your assumptions.

But a blueprint gives you direction.

It gives you sequencing.

It gives you reference points.

It gives you something to compare reality against.

There’s a huge difference between changing the blueprint because you’ve learned something new and wandering around the jobsite because you never had a blueprint in the first place.

The Blueprints Kept Getting Better

Something else happened during my construction career.

The blueprints got better.

A lot better.

Years after Roybal, during the dot-com boom in the early 2000s, I worked on what you might broadly call data-center infrastructure today.

It wasn’t one of these enormous purpose-built campuses we talk about now.

It was essentially a floor in a downtown Los Angeles building packed with the systems needed to keep servers running.

• Battery backup
• Generator backup
• Cooling
• Power
• Network equipment
• Redundancy everywhere

And for the first time, I remember seeing our conduit laid out precisely in three dimensions.

That was another leap.

It wasn’t:

“There’s electrical shit somewhere up there. Figure it out when you get there.”

They could show us where the conduit was supposed to go in space before we started installing it.

And here’s why that matters.

When coordination is loose, construction requires slop.

Everybody needs room because nobody knows exactly where the conflicts are going to appear.

The electrician needs space.

The plumber needs space.

The HVAC guy needs space.

The fire-sprinkler guy needs space.

Structural steel occupies fixed space and doesn’t care about any of you.

When those conflicts are discovered in the field, somebody has to move.

Something gets rebuilt.

Labor gets wasted.

Materials get wasted.

Space gets wasted.

Schedules get affected.

Good coordination doesn’t eliminate every problem.

But it lets you discover a lot of those problems while they’re still lines on a drawing instead of installed material that now has to be torn out.

That’s cheaper.

That’s faster.

That’s leverage.

Better Planning Changed How We Built

Years later at LAX, I saw an even more sophisticated generation of the same idea.

The specific software isn’t important, there are many, Bluebeam was one of them.

What mattered was that the major trades could increasingly coordinate their systems in detailed shared space before installation.

Electrical goes here.

Plumbing goes there.

HVAC goes there.

Structural components occupy this space.

This system can’t run through that system.

You could identify conflicts before somebody was standing on a ladder looking at another guy’s pipe running directly through the spot where his conduit was supposed to go.

And once the planning became precise enough, another thing became possible:

Prefabrication.

Instead of fabricating everything piece by piece on the jobsite, more assemblies could be built under controlled conditions and brought to the field ready to install.

Fewer wasted field hours.

Fewer mistakes.

Less rework.

Faster installation.

More repeatability.

Better use of space.

I spent thirty-five years as a union electrician, so I’m not talking about eliminating skilled labor.

I’m talking about using expensive skilled labor where it creates the most value instead of burning hours solving problems that better planning could have prevented.

The crews didn’t suddenly become twice as strong.

They didn’t become twice as hardworking.

The blueprint got better.

And because the blueprint got better, everybody could go further, faster, with less waste.

That’s leverage.

The Tool Is Not the Blueprint

These days I’m building something I call Chuck OS.

I’m pulling together what I’ve learned from construction, martial arts, business, productivity, and almost sixty-one years of fucking things up and occasionally getting things right.

And there’s a trap hiding in the middle of all of this.

We have more tools than we’ve ever had.

• Software
• Apps
• AI
• Automations
• Calendars
• Project-management systems
• ​CRMs​
• Templates
• SOPs
• Dashboards
• Agents

Everybody wants to sell you another one that will save time, organize your life, grow your business, or automate everything.

But construction taught me something those sales pitches often skip.

The tool is not the blueprint.

A drill doesn’t know where the hole belongs.

A conduit bender doesn’t know where the conduit should run.

A lift doesn’t know which work has to happen first.

Hand somebody a powerful tool without a good plan and you’ve simply given him the ability to make a much bigger mistake, much faster.

Tools multiply execution.

They don’t provide direction.

That’s why I’ve become a believer in being intelligently lazy.​

I don’t want another app because it’s impressive.

I don’t want an automation because I can automate something.

I don’t want another dashboard simply because something can be measured.

I want to know:

What part of my blueprint does this help me execute?

If I can’t answer that, why the hell am I adding it?

Destination → Blueprint → Process → Tool → Automation

Over time, the order has become pretty simple.

Destination. What am I actually trying to build?

Blueprint. How do the pieces fit together?

Process. What actually has to happen?

Tool. What creates leverage against that process?

Automation. What can now happen with less repeated human effort?

Not the other way around.

Know where you’re going.

Design how you’re getting there.

Understand the work.

Choose the leverage.

Then automate.

Because if you automate a bad process, you’ve automated stupidity.

And if you become more efficient while heading in the wrong direction, congratulations.

You’re getting lost faster.

Software Can’t Decide What You’re Building

That’s how I think about business software too.

Take a CRM.

A CRM can help me remember who I talked to.

• What we talked about
• Who needs a follow-up
• What the next action is
• Where someone sits in the process
• Who might be falling through the cracks

That’s useful.

I’ve followed HubSpot for years because they’ve put out a lot of useful free information and resources for businesses.

But HubSpot—or any CRM—can’t decide what business you should build.

It can’t decide who you should serve.

It can’t tell you what your values should be.

It can’t decide what kind of relationship you want with your customers.

And it can’t tell you whether the process you’re putting into the software is actually a good one.

Putting a shitty process into software doesn’t make it a good process.

It just helps you run the shitty process more consistently.

You figure out what you’re trying to build first.

Then the tool gives you leverage.

Pull Out the Plans

That’s what I needed this morning.

I’d been away from serious work for about a week.

The answer wasn’t to punish myself.

It wasn’t to cram ten days of work into one.

It wasn’t a new productivity system.

And it sure as hell wasn’t another app.

It was to pull out the plans and answer the questions.

• Where am I?
• How did I get here?
• Where do I want to go?
• What’s the blueprint for getting there?
• What changed?
• What’s the next piece of work that actually needs to happen?

Only after that do the tool questions make sense.

What can I eliminate?

What can I delegate?

What can I template?

What can I automate?

What tool would reduce the effort?

What would give me leverage?

In that order.

The Trees Are Still on the Plans

When I was a third-year apprentice looking at those landscaping drawings at the Roybal Federal Courthouse, somebody had already decided where a tree would eventually stand.

More than three decades later, that idea still matters to me.

You don’t need to know exactly what your life will look like five years from now.

You don’t need to predict every problem.

Your plans will change.

But there’s an enormous difference between changing a blueprint because reality handed you new information and wandering around the jobsite because there was never a blueprint at all.

The tools keep getting better.

The software keeps getting better.

The automation keeps getting better.

AI keeps getting better.

But none of it can answer the one question that actually matters:

What the hell are you trying to build?

Figure that out.

Draw the blueprint.

Then pick up the tools.

⚔ The Dojo Drill

Today’s training:

The Priority Stack

List the 10 things competing for your time.

Circle the top 3.

Ignore the rest today.

📚 Leader’s Library

​Factfulness by Hans Rosling​

Why?

Because this book is a great reminder that the world in our heads is not always the world that actually exists.

We naturally notice dramatic stories, divide things into simple categories, and give more weight to bad news than slow improvement.

Rosling shows how easily those instincts can distort our judgment—and how looking at the data can change the picture.

For leaders, that matters.

Better decisions begin with seeing reality more clearly, not merely believing the story we’ve already told ourselves about it.

P.S. Know a martial arts gym owner who’s stressed about money or student numbers?

Do them a favor: send them to The Leader's Dōjō, my website where I help owners get more students and keep them longer with simple systems.

One forward from you could change their gym: The Leader's Dōjō​

Chuck