The Work Behind the Work

The Part People Usually See

Most people judge work from the surface.

They see the finished website, the polished presentation, the clean design system, the brand refresh, the well-structured document, or the tool that suddenly makes a frustrating process easier. They see the result because that is the part meant for people to see. It is the most visible layer, and in a lot of cases, it is the only layer people ever think about.

That makes sense. Finished work is what shows up in the world.

What is easier to miss is everything underneath it. The questioning, the false starts, the learning curve, the revisions, the troubleshooting, the restructuring, the decisions about what matters and what does not, the time spent understanding the problem deeply enough to build the right solution instead of the fastest one. That is the work behind the work.

Groundwork Is Not Decoration

This idea sits at the center of how I think about almost everything I do.

If you are building a house, the foundation matters long before anyone notices the walls, the windows, or the finish. A stronger foundation does not just help the structure stand. It determines what the structure can carry, how well it holds up, and how much confidence you can have in what comes next.

Creative work is not all that different.

A brand can look good and still feel weak if the thinking underneath it is vague. A system can appear functional and still create friction if nobody took the time to understand how the parts actually connect, and a process can move quickly and still fail later because it was built on shortcuts instead of understanding.

That is why I care so much about groundwork. I am not interested in weak understanding. I do not want to build something on top of assumptions I have not tested, or deliver a clean result that only works because no one has pushed on it yet.

What the Hidden Work Actually Includes

When I talk about the work behind the work, I mean all of it.

I mean strategy, structure, systems, questioning, learning, revision, troubleshooting, documentation, audience thinking, experimentation, and the discipline required to stay with a problem long enough to understand it instead of reacting to it too quickly. I mean the internal discipline of building patience, trusting the process, and resisting the pressure to answer in the moment before the answer is ready.

That matters more than people think.

A lot of what looks clean and efficient from the outside exists because someone did a messy amount of invisible effort to make it that way. On the outside, it can look fast, calm, and obvious. On the inside, it often involves uncertainty, stress, rethinking, and a series of decisions that never make it into the final artifact. The cleaner the result, the easier it is for people to assume it was simple.

It usually was not.

Why I Invest So Much in Learning

Part of this philosophy comes from how I approach tools.

I have never been satisfied with learning only the surface of something. My instinct is usually not, “How do I use this?” It is, “How does this function?” and “Why does it work the way it does?” That shift matters because it changes how quickly you can adapt. If you understand the logic underneath the tool, you can learn new tools faster, move between disciplines more easily, and build better systems for yourself and for other people.

That is one reason I have always invested so heavily in learning. Cameras, publishing, art, software, programming languages, automation, systems, documentation, workflow design, all of it adds range. The bigger the arsenal, the more options you have. The more options you have, the more capable you become when the work gets complicated. Psychologist Anders Ericsson spent his career studying this exact pattern. His research on deliberate practice found that experts are made through sustained, focused effort, not born with some rare gift.

This is still part of the work behind the work.

Investing in your skills is not separate from execution. It is preparation for it. Designing a better workflow for yourself is not procrastination. It is a way of setting up better work before the project is under pressure.

How This Shows Up in Practice

This way of thinking shows up everywhere I go, even when the output changes.

It shows up when I create style guides during a brand refresh, because a good visual system should not depend on memory, taste, or guesswork. It should give people structure they can actually use. Budgeting tools carry it too, because clarity and consistency matter just as much in accounting as they do in design. And it shows up when I write HR documentation standards, manage projects, troubleshoot messy workflows, or step into a problem nobody has fully defined yet.

On the surface, those things can look unrelated. They are not.

In every case, I am doing some version of the same thing. I am trying to understand what is really happening, what is missing, what is creating friction, what needs to be repeatable, and what kind of system would make the work stronger after I am done. Sometimes that means designing a better path. Sometimes it means designing a better tool so other people can follow the path more easily.

That is why I am often the person people come to when something is hard to figure out. My brain tends to move in the other direction. I can usually see that there is a path to clarity, even when it is buried under a lot of noise.

The Hidden Work Matters Most at Scale

This becomes especially important when the volume of work increases.

Anyone can muscle through one difficult project with enough effort and improvisation. That is not the same thing as building a repeatable way to handle complexity well. When you are refreshing a brand, launching a new website, planning an event, setting up a trade show, and trying to keep teams aligned at the same time, visible effort alone will not save you. You need structure, workflows, and standards, and you need a way to make quality repeatable under pressure.

That is where the hidden work makes the biggest difference.

A strong system can make impossible-looking work manageable. Not easy, just manageable. It creates leverage and gives people a common language, a clear process, and a better chance of staying aligned when the pressure rises.

What Frustrates Me About How People Value Work

One thing that has always bothered me is how casually people draw the line between creative work and logical work, as if one side is mysterious talent and the other side is teachable discipline.

I hear people say, “I’m not good at that,” as if that ends the conversation. I do not really have that luxury. Creative projects have always asked more of me than taste or aesthetics. It has asked for logic, systems thinking, budgeting, communication, structure, and the ability to explain why something works, not just make it look good.

That road should go both ways.

If creative people are expected to understand process, systems, and business logic, then other people can also learn more of the creative side than they often give themselves credit for. Patience, skill, understanding, and better judgment can all be developed. Most of the invisible strengths people admire in finished work did not arrive as magic. Somebody built them.

The Shift

The finished piece matters. Of course it does. That is the part people use, remember, and react to.

But strong work does not begin at the surface. It begins underneath it, in the foundation you build for yourself long before anyone sees the result. It begins in the time you spend learning, questioning, testing, failing, improving, and designing a better way forward before the pressure to deliver starts closing in.

That is the work behind the work.

It may be invisible to most people. It is still the reason the visible part holds up.