A few weeks into a new environment, I found myself watching a conversation and feeling fairly certain I understood what was happening.

Subscribe now

Someone pushed back on an idea.

The response felt slightly sharper than necessary.

It was brief, but fit together neatly enough for me to understand.

Or so I thought.

I them learned a little more of the story.

The people involved had worked together for years. There was context I hadn’t lived through. Decisions that had already been debated. Problems that had previously surfaced.

The meaning of the interaction changed almost immediately.

Not because what I saw was inaccurate.

It was just incomplete.

This has been on my mind lately.

How easy it is to forget that when you enter a new environment, you’re not arriving at the beginning.

You’re arriving somewhere in the middle.

People were there before you. As were their relationships, and whatever the culture had already become.

Even the things that seem obvious have roots that disappear beneath the surface long before you arrive.

But that’s not how it feels.

It feels like you’re looking at reality directly.

Someone says something. A process exists. A decision gets made.

And the mind immediately begins making sense of it.

Not because we’re careless.

But because orientation is how we move through the world. We need a map, even when we’ve only seen a small piece of the territory.

I’ve noticed this tendency in myself.

A process feels inefficient. A conversation feels tense.

And almost automatically, the explanations begin to form. Maybe this is the reason. Maybe that’s the problem.

Sometimes they turn out to be right.

But often they change as more of the story becomes visible.

A process that seemed unnecessary turns out to protect against a problem you didn’t know existed.

A decision that felt shortsighted turns out to have been shaped by constraints you couldn’t see.

What felt personal at first turned out to be more historical.

The facts don’t always change.

The context does.

And context changes the meaning.

This is one of the hidden challenges of entering any new system.

Not learning what is happening.

Learning what happened before you arrived.

Most environments have been shaped for years before you experience them in their current form.

What you encounter on the surface is often the consequence of decisions and adaptations that occurred months or years earlier.

You’re seeing the current shape.

Not the forces that shaped it.

Not yet, at least.

There’s a humility in that.

Not because your observations aren’t valuable.

But because they’re late to the party.

You’re inheriting context. Stepping into chapters you didn’t live through, about relationships whose beginnings didn’t involve you.

The longer I spend in new environments, the less interested I become in arriving with answers.

And the more interested I become in the story that was already unfolding before I got there.

Every system has a history.

Every relationship has chapters you weren’t there for.

The challenge isn’t holding back your opinions.

It’s remembering that you may have walked in halfway through.

If any of this resonates with you, I’m glad you’re here.

– Maxwell

Subscribe now

There was a moment last week when I caught myself about to speak, and didn’t.

Subscribe now

I’d been working closely with someone for nearly a month. Not long. But long enough that impressions had begun to form. Strengths I’d noticed. Thoughts about where they might grow.

When they asked me for feedback, I felt the usual machinery start to move.

The instinct to be useful.
To deliver something clear.
To meet the expectation in the way I usually would.

But underneath it was something I hadn’t felt in a long time.

I wasn’t sure.

Not unsure of what to say.
Unsure of whether what I’d say was really true.

So I paused, and the moment passed without me filling it.

That pause has stayed with me.

Not because anything visible happened, but because of what I noticed inside myself in the second before it.

A pull, quiet but insistent.

To resolve.
To deliver.
To do the thing I usually do well.

I’m starting to think a surprising amount of human behavior is actually an attempt to escape that feeling.

Not uncertainty in the abstract.

The kind that enters quietly.

A shift in tone.
A conversation that feels different than it did a week ago.
A relationship becoming harder to read.
A team losing some feeling of ease.

And almost immediately, something starts happening inside people.

The atmosphere tightens.
Pressure builds.
Movement begins before clarity arrives.

There are moments where I can feel my mind wanting to stabilize things quickly.

What’s effective.
What matters.
What needs attention.
Where things are working and where they aren’t.

Not because I understand all of it yet, but because unresolved ambiguity creates tension.

And tension rarely stays still for long.

What’s harder to admit is that the pull isn’t only about the environment.

It’s about me.

I’ve spent a long time being someone who, after many years in one environment, could read a room and respond. Form a take. Offer direction.

That instinct has been useful for a long time, and over time it quietly became part of how I understood my value.

But in an environment I don’t yet understand, that same instinct can fire too early.

The muscle still wants to move.
The identity still wants to deliver.

And steadiness, I’m learning, sometimes means letting the muscle rest even when it’s ready.

Relief and understanding are not the same thing.

Something can feel more stable without actually becoming clearer.

And once relief enters a system, people often stop tolerating the discomfort that deeper understanding requires.

The system begins organizing itself around the need to feel certain again.

Not necessarily around what’s true.

I think this is part of why uncertainty changes environments so quickly.

People begin reacting to the tension itself.
Trying to stabilize it before they actually understand it.

And systems absorb that tension fast.

Especially from people with influence.

The longer I work with people and environments, the less I believe steadiness comes from always knowing.

More often, it comes from being able to remain grounded while reality is still unfolding.

Not frozen.
Not passive.
Not avoiding responsibility.

Just steady enough that uncertainty doesn’t immediately distort the system around you.

There’s a difference between creating clarity and forcing certainty.

One emerges from deeper contact with reality.
The other usually emerges from discomfort.

A lot of systems become unstable this way.

Not because people stop caring, but because unresolved reality becomes emotionally difficult to tolerate.

And when that pressure builds, people begin reaching for anything that restores a feeling of stability.

Even if the movement comes too early.
Even if the certainty is incomplete.

For most of my career, the skill I developed was reading the room fast, and accurately so.

I’m starting to think the next one is knowing when not to.

If any of this resonates with you, I’m glad you’re here.

– Maxwell

Subscribe now

A few days into a new role, I made a suggestion to another leader.

It was a tool built around problems I’d understood intimately in my last role. Based on what I’d observed, I thought it might help here.

I was kindly but firmly redirected.

And the redirect was right. Not because the suggestion itself was necessarily wrong. It might still turn out to be useful. The issue was simpler than that. After one day of observations, I hadn’t spent enough time in this environment to truly understand it.

I had a read. I didn’t yet have understanding.

What struck me afterward wasn’t the suggestion. It was how quickly I’d moved from observation to recommendation. How little space there had been between the two.

It’s a pattern I keep noticing.

Something feels slightly off, and almost immediately, a story forms.

Communication is strained. People aren’t aligned. Standards are slipping. Leadership is disconnected.

Sometimes those explanations are right. A lot of the time, they’re just the first explanation that makes the uncertainty go away.

It happens so quickly it barely feels like a process at all. You notice something, and almost instantly you feel like you understand it.

But observation and understanding are not the same thing. There’s a space between them, and most of the time, we collapse it too quickly.

I notice how fast this happens in myself. Energy shifts. A conversation feels tense. A team feels less connected than it did a week ago. Before I realize it, my mind is already building a story around why.

Not intentionally. Almost automatically.

The difficult part is that the original signal is usually real. Something has changed. But the explanation attached to it may not be.

Once a story forms, it starts shaping everything afterward.

You stop observing openly. You start filtering. The moments that confirm the story stand out. The moments that complicate it fade.

Ambiguity disappears. Not because reality became clearer. Because interpretation did.

The first explanation quietly becomes the thing that prevents deeper understanding.

Sitting with not-knowing is uncomfortable. There’s a pull to act, to help, to solve. An incomplete explanation gives you something to move on. Even when moving is exactly what the moment doesn’t need.

But understanding takes longer than interpretation. It requires context. Repeated exposure. Contradiction. Time.

Sometimes what you’re seeing only makes sense after you’ve lived alongside it long enough.

That’s part of what’s been on my mind in this new environment. New role. New city. New systems. New people.

I can feel how quickly the mind wants to stabilize uncertainty into explanation. What matters. Who’s effective. What should change. What’s working and what isn’t.

Some of those early reads will eventually prove true.

But right now, I’m trying to resist the urge to decide too quickly what everything means. To spend more time understanding before interpreting. To let reality reveal itself before putting a story on it.

Because the first explanation is often incomplete. Once it hardens, it becomes difficult to see past it.

A lot of problems compound this way. Not because people fail to notice what’s happening, but because they become too certain too early about what it means.

From there, decisions get made. Feedback changes. Behavior changes. Systems start reacting to an interpretation that may not be true.

The signal wasn’t the problem. The speed of interpretation was.

This doesn’t mean ignoring what you feel. Many of the most important things begin as signals that are difficult to explain. But there’s a difference between noticing something, forming an early read, and fully understanding it.

Sometimes the most important thing you can do is stay with the tension long enough for the deeper pattern to emerge. Long enough for the read to catch up to reality.

Not every feeling is correct. Not every explanation is either.

The question is whether you can stay open long enough to tell the difference.

In my last post, I wrote about a moment in a café that didn’t feel quite right. Everything looked fine, but something was off in a way I couldn’t yet explain.

There’s a part of that moment I didn’t understand at the time. Not just what I was seeing, but what I was part of.

When something feels off, the instinct is often to fix it. Even if you can’t fully explain it yet. Especially then.

That’s where things go wrong. Not in missing the signal, but in acting on it before you understand what’s actually happening.

What I thought I was seeing

At the time, I thought I was observing a team that wasn’t fully aligned. Communication felt thin. Energy felt slightly constrained. Something wasn’t moving the way it should.

Nothing obvious. But enough to make me want to step in.

If I had acted on that, I would’ve tried to correct what I thought was off. Push for more communication. Address what felt like hesitation. Tighten standards.

It would have looked like a reasonable response. It also would have been wrong.

Because what I didn’t understand yet was simple:

The system included me. What I was seeing wasn’t separate from me. It was, in part, a response to my presence.

The shift I wasn’t accounting for

The energy shifted when I walked in. Not dramatically. Just enough.

Conversations tightened. Movements became more deliberate. People checked themselves in ways they hadn’t a moment before.

At the time, I read that as something missing. In reality, I was part of what was changing.

That’s easy to miss, because it doesn’t feel that way. It feels like you’re a bystander, or silent observer of an unfolding environment, from the outside.

But you’re not on the outside. You never really are.

The moment you enter a room, you change it. People adjust. They pay attention to different things. They hold themselves differently. They respond to what they think you’re looking for, even if you haven’t said a word.

So what you’re seeing isn’t neutral. It’s shaped by your presence, even with minimal interaction. And if you don’t account for that, you misread what’s actually happening.

What the signal actually points to

A team that feels tense might not be tense in your absence. A conversation that feels guarded might not usually be that way. What feels like a system problem might be a moment.

That doesn’t make the signal less real. But it does change what it points to.

If I had moved too quickly, I would have solved for the surface, and made the underlying dynamic worse.

This is the part that’s easy to skip. Because waiting doesn’t feel like progress. And accounting for yourself is harder than diagnosing others.

But until you understand what you’re part of, you’re not in a position to change anything.

The question that actually matters

This isn’t just true in a café. It shows up in conversations. In meetings. In relationships. Even in small, everyday interactions.

So the question shifts.

Not: What’s wrong here?

But: What am I changing just by being here?

If any of this resonates with you, I’m glad you’re here.

– Maxwell

I remember a moment from years ago, not long after I became a district manager.

I walked into a café I had been in many times before.

By that point, I knew exactly how a café should operate. I knew what to look for. It had become second nature.

And as I looked around, everything you’d expect was in place.

Drinks were being made promptly. The bar was in order. Equipment was working. Staffing was right.

Nothing obvious was wrong.

And yet, something didn’t feel quite right.

People were barely speaking to each other. Movements felt slightly out of sync. There was a kind of quiet tension that did not belong.

If I had gone strictly off my checklist, I could have said everything was fine and moved on.

But it didn’t feel the way it was supposed to.

I just couldn’t fully explain it.

But everyone could feel that something was off.

For a long time, I treated moments like that as something to come back to later, or worse, ignore.

Something I’d figure out once I had more information.
Once I could explain it clearly.

But over time, I realized those moments aren’t something to move past.

They’re where the real information is.

The problem is, they show up quietly.

Before you can justify them.
Before you have language.
Before you can point to something concrete and say, “this is the issue.”

It’s just a feeling.

And it’s easy to move past.

What does that actually look like?

It’s rarely something obvious you can immediately prove.

It shows up in shifts.

A change in how people speak to each other.
A slight hesitation where there used to be clarity.
Energy that feels just a little off.
Something that used to feel easy now taking more effort.

You can notice each of these.

But you can’t easily defend any one of them on its own.

So you move past it.

Even though, taken together, they’re telling you something has changed.

Not fully broken.

But no longer working the way it should.

It’s easy not to stay with that.

To look for something you can explain.
To go back to what you know how to check.

And if nothing clearly fails that test, it’s natural to assume everything is fine.

That’s how a team that feels slightly off still gets labeled as “working.”

Because there isn’t a clear problem to point to.

It’s also how a leader can walk into a room and change how a team feels, without realizing the impact they’re having.

Nothing obvious breaks.

But something shifts.

And that shift matters.

It’s also how something that clearly worked gets copied, but only at the surface level.

The visible parts translate easily.

The underlying conditions don’t.

So you end up recreating the appearance of something that worked, without the substance that made it work in the first place.

Over time, you start to see how often this gets missed.

Not because people aren’t paying attention.

But because what matters shows up before it can be explained.

Before it can be defended.
Before it can be measured.

And if you don’t stay with it, you move past it.

You default back to what you can point to.

What you can prove.
What you can justify to someone else.

But by then, you’re not just late to understanding what’s actually happening.

You’ve already started making decisions based on the wrong read of the situation.

You’re off track.

In that moment, I didn’t move on.

I stayed with it.

Over the next few days, I spent time in the café. I paid attention. I asked questions. I watched more closely.

And what I eventually understood was simple.

The team wasn’t off.

They were nervous.

Their new district manager had just walked in.

Me.

What I was feeling wasn’t random.

It was a real response to something in the environment.

I just didn’t understand it yet.

But it was there the entire time.

Most of the time, what matters shows up earlier than we expect.

The question is whether you stay with it long enough to understand it.

Or move past it because you can’t explain it yet.

Pay attention to what you feel.

Then take the time to understand what’s actually real.

If any of this resonates with you, I’m glad you’re here.

– Maxwell

Why do some things work and others don’t?

Why some teams just work
Why certain places feel alive
Why some leaders create energy while others drain it
Why a café, a company, or even a community can feel either deeply human or somewhat hollow.

I didn’t have language for it at first. Just a sense.

A lot of that curiosity has been shaped by the past decade of my life working inside and helping lead through many iterations of Compass Coffee.

Different seasons. Different challenges. Different versions of what we were trying to build.

Some things worked. Some didn’t. Some only worked for a while.

But across all of it, I kept coming back to the same questions:

What actually makes something work?
And just as importantly, what breaks it?

Over time, I started to notice patterns.

The way people are treated
The standards that are set
The systems behind the scenes
The small decisions no one talks about, but everyone feels

Most things aren’t broken by accident.

They’re built that way.

And if that’s true, then the opposite must also be true.

Things that work, really work, are built with intention.

That sits at the center of this project.

I’m calling it Built Well.

Not as a statement. More a question.

What does it actually mean to build something well?

A team
A company
A body
A life

This is, in many ways, a way for me to synthesize what I’ve experienced and continue to explore what comes next.

I’m not trying to provide answers.

If anything, this is me working through the questions in public.

Pulling from things I’ve experienced firsthand
Leading teams, working inside a company, watching things succeed and fail in very real ways
And also from what I’m studying across health, systems, leadership, technology, and environments

Because they do connect.

You can’t separate the way someone works from how they feel
You can’t separate a company’s outcomes from how its people are treated
You can’t separate performance from environment

Everything compounds.

A lot of what we talk about sits at the surface.

Tactics
Advice
Hot takes
Frameworks without context

That’s not what I’m interested in.

I’m more interested in what sits underneath:

What actually drives behavior
What sustains performance over time
What creates trust
What breaks it
And how all of that shows up in real life

Built Well will live across a few core areas:

People
Work
Health
Technology
Systems

And maybe most importantly, how all of those come together.

I don’t think building well is about perfection.

It’s about alignment.

Between what you say and what you do
Between what you build and what people experience
Between short term pressure and long term thinking

This will be a mix of things.

Longer essays like this
Shorter observations
Ideas pulled from books, conversations, and real environments
Things I’m testing
Things I’m getting wrong

Over time, I want this to become more than just writing.

A body of work
A set of principles
Maybe even something people can use

For now, it’s simple.

I’m paying closer attention
Trying to understand what matters
And documenting it as I go

Subscribe if you want to follow along.

If any of this resonates with you, I’m glad you’re here.

– Maxwell

Subscribe now