How I See My Craft

I've always been interested in what makes things work.

Not just whether a business is growing, a team is performing, or a strategy is succeeding, but why.

What actually produced the result? What matters most here? What are we overlooking? What happens next if we make this decision? And are we solving the real problem, or just the most visible part of it?

Those questions have become the foundation of how I work.

I've learned that what we see on the surface is rarely the whole story.

A successful launch may trace back to a decision made months earlier. What looks like a people problem may actually be people adapting to the environment around them. A strategy that works beautifully at one stage of a business can become the thing holding it back at the next.

The longer I've worked in business, the less interested I've become in simple explanations.

Businesses are complicated because people are complicated. Markets change. Priorities compete. Information is incomplete. Good people disagree. A decision that solves one problem can create another somewhere else.

Sometimes there isn't a perfect answer.

There is simply a situation to understand, tradeoffs to weigh, and a decision to make.

I think that's where judgment matters.

I didn't learn that from a textbook. I learned it by doing the work — building things, leading people, working alongside founders and executives, making decisions with incomplete information, watching businesses grow, seeing good ideas fail, seeing unlikely ideas work, and getting things wrong myself.

Experience has made me slower to assume and faster to ask questions.

When something isn't working, I want to understand what's producing it before trying to fix it. When people keep making the same mistake, what about the way we're working makes that mistake easy to make? When a strategy is succeeding, what's actually driving the success, and which parts are merely along for the ride?

I've found that asking better questions often matters more than having faster answers.

The same is true of systems.

I believe deeply in clear ownership, useful processes, good information, aligned incentives, and thoughtful communication. Those things can transform the way a business operates.

But systems have limits.

You cannot process your way out of every problem. You cannot build a dashboard that eliminates uncertainty. You cannot create enough rules to account for every situation people will encounter.

Eventually, someone has to think.

That's why I believe the purpose of a good system isn't to remove judgment. It's to make good judgment easier.

The best systems give people enough clarity to act without constantly asking permission. They put useful information in the hands of the people who need it. They make ownership clear without making collaboration rigid. They catch predictable problems without getting in the way of solving unpredictable ones.

And importantly, they leave room for people to be people.

Because a business isn't a machine.

It's a group of human beings trying to accomplish something together.

They bring ambition, fear, intuition, experience, ego, creativity, insecurity, generosity, exhaustion, and judgment into the room with them. Pretending those things don't exist doesn't make a business more rational. Understanding them makes you better equipped to lead one.

I've also become increasingly interested in what happens after a decision.

It's easy to ask whether something will work.

I also want to know:

What happens if it does?

If we reward this, what behavior will we get more of?

If we optimize for this number, what might people stop paying attention to?

If we solve the problem this way, where might the pressure move next?

If this works at twice the scale, does it still work?

Those questions have taught me that good decisions aren't only about immediate results. They're about understanding consequences.

And even then, you won't see everything coming.

You can think carefully and still be wrong. You can make the best decision available and still get a bad outcome. You can build something that works for years and eventually outgrow it.

Changing your mind isn't necessarily evidence that your earlier thinking was poor. Sometimes you've learned something. Sometimes the circumstances changed. Sometimes you're simply seeing more of the picture than you could before.

I think good leadership requires enough conviction to make a decision and enough humility to revisit it.

Earlier in my career, I probably thought leadership meant solving more problems.

Now I think part of leadership is creating an environment where fewer problems require you to solve them personally.

That means giving people real ownership. Making expectations clear. Sharing context instead of just instructions. Allowing people to make decisions differently than you would. Letting small mistakes become information instead of treating every mistake like a failure of control.

The goal isn't to make yourself indispensable.

It's to help build something capable.

A capable team can disagree without falling apart. It can make decisions without waiting for the most senior person in the room. It can recognize when something isn't working and adjust. It can operate with structure without becoming dependent on it.

And a capable leader knows that different moments require different things.

Sometimes you need to move quickly. Sometimes you need to wait.

Sometimes you need more data. Sometimes you have enough.

Sometimes consensus matters. Sometimes somebody has to make the call.

Sometimes the right thing is to build a system. Sometimes the right thing is to trust a person.

Knowing the difference is the craft.

That's probably the simplest way I can describe how I see my work now.

I try to understand what is actually happening.

I look for the few things that matter most.

I think about what today's decision makes more likely tomorrow.

I try to build structures that help people do good work without making those structures the work itself.

And I try to leave things more capable than I found them.

Not more dependent on me.

More capable.

Because the work I'm proudest of isn't necessarily the work with my fingerprints all over it.

It's a team that knows how to think.

A leader who trusts their own judgment.

A business that can change without losing itself.

A decision that still makes sense after the excitement wears off.

Something that keeps working when nobody remembers who originally built it.

That's what I want my work to create.

And maybe that's what legacy is, too.

Not what you built.

But what you left behind that continues to build after you.