“What problem are we actually trying to solve?”

It sounds obvious, but it’s surprising how often the room goes quiet.

Not because people don’t know what they’re working on. They do.

They’re trying to modernize marketing.

Improve campaign performance.

Implement AI.

Reduce operational complexity.

Launch a new operating model.

Those are all important initiatives.

But they’re not always the problem.

Over the years, I’ve realized that organizations spend an incredible amount of energy trying to improve execution without ever questioning the assumptions behind it. We become so focused on doing things better that we rarely stop to ask whether we’re solving the right problem, or whether the environment we’re operating in has fundamentally changed.

That’s where many transformation efforts stall.

Not because people aren’t capable.

Not because the technology isn’t ready.

Because everyone is still operating from the same assumptions.

The Assumptions We Stop Seeing

Every organization develops ways of working that eventually become invisible.

They’re the assumptions no one questions anymore.

“This is how approvals work.”

“This is how campaigns get built.”

“This is how teams collaborate.”

At one point, those assumptions probably made perfect sense. They reflected the environment the organization was operating in at the time.

But environments change.

Markets evolve.

Customers change.

Technology changes.

The organization changes.

The assumptions don’t always change with them.

That’s why some of the most persistent problems aren’t caused by poor execution. They’re caused by applying yesterday’s operating assumptions to today’s environment.

A Lesson From the Battle Room

I’m a lifelong science fiction fan, so it probably won’t surprise anyone that one of the most influential leadership lessons I’ve ever encountered came from Ender’s Game.

In the Battle Room, Ender and the other students are no longer operating in gravity. But when they first enter that space, they continue to behave as though they are.

They orient themselves the way they always have. They look across the room at the enemy’s gate as though they’re standing on a floor, preparing to cross a battlefield.

They’re in a zero-gravity environment.

But they’re still thinking in gravity.

Then Ender reframes the entire room with one sentence.

“The enemy’s gate is down.”

That changes everything.

Once the enemy’s gate becomes “down,” the team stops thinking about crossing the room and starts thinking about dropping through space. They aim their feet toward the enemy, presenting only the bottoms of their feet as targets instead of exposing their entire bodies. Their movement changes. Their strategy changes. Their understanding of the environment changes.

The room didn’t change.

The rules didn’t change.

Gravity had already stopped applying.

The only thing that changed was their orientation to the environment they were actually in.

A simple shift radically changed the game because, for the first time, they were solving the problem that actually existed instead of the one they assumed they were facing.

Marketing Has Its Own Gravity-Based Thinking

I see organizations do this every day.

They step into entirely new environments while continuing to operate with assumptions built for the old ones.

They introduce AI but continue relying on tribal knowledge instead of making decisions explicit.

They replace platforms while rebuilding the same operational bottlenecks that frustrated them in the previous system.

They reorganize teams but preserve the same approval paths, ownership questions, and decision-making patterns they’ve always had.

From the outside, it looks like transformation.

From the inside, very little has actually changed.

The technology is different.

The environment is different.

The thinking isn’t.

That’s why I love the phrase, “The enemy’s gate is down.”

To me, it isn’t just about perspective.

It’s about recognizing when the assumptions you’ve carried with you no longer match the environment you’re operating in.

That’s a very different leadership skill.

Seeing the Invisible

One of the things I’ve learned over the years is that the most valuable person in a transformation isn’t always the one with the best technical solution.

It’s often the person willing to ask the uncomfortable question.

“What assumption are we making?”

Not because assumptions are bad.

Because assumptions have expiration dates.

The longer an organization has been successful, the easier it is to mistake long-standing assumptions for permanent truths.

They’re not.

They’re simply ideas that worked well in a particular environment.

Great leaders recognize when that environment has changed.

The Takeaway

The older I get, the less interested I become in frameworks, methodologies, and silver bullets.

I’m much more interested in helping organizations recognize the assumptions they’ve stopped seeing.

What constraints no longer exist?

What rules are we still following because they once made sense?

What if the environment changed years ago, but our thinking never caught up?

Those questions have unlocked more meaningful transformation than any process I’ve ever introduced.

That’s why “The enemy’s gate is down” has stayed with me for so many years.

Not because it’s a memorable line from one of my favorite books.

Because it’s a reminder that transformation rarely begins with a new answer.

It begins with recognizing that you’re still solving a zero-gravity problem with gravity-based thinking.

I’ve spent a lot of time over the last several years helping organizations modernize their marketing technology. Sometimes that means replacing a platform. Sometimes it’s introducing AI into marketing operations. Sometimes it’s connecting systems that have grown independently over the course of a decade.

No matter what the initiative is called, I keep running into the same challenge.

It usually isn’t the technology.

The technology is often the easiest part.

The difficult part is untangling years of business decisions that have quietly become trapped inside the technology itself.

At first, everything looks straightforward. A workflow works. A campaign launches. An automation fires exactly when it’s supposed to. Then someone asks what seems like a simple question.

“Why does it work that way?”

The room gets quiet.

Someone remembers it was added years ago because of a unique business situation. Someone else thinks it was tied to a legal requirement. Another person believes it was a customer experience decision. Eventually someone says, “Let’s go look at the workflow.”

That’s usually the first sign that the software has become the only place your organization remembers how it operates.

When Software Becomes the Expert

One of the biggest shifts in my own thinking has been realizing that we’ve unintentionally blurred the line between business knowledge and technical implementation.

Workflows, automation rules, scripts, and platform configurations are often treated as though they are the business. They aren’t. They’re simply one expression of how the business has chosen to operate.

The decision always comes first.

The technology comes second.

That distinction matters because business decisions typically outlive the software used to execute them. Platforms change. Vendors change. AI capabilities evolve. The business, however, still needs to decide who receives an offer, when a message should be suppressed, what qualifies a customer for a particular experience, and which exceptions should always be honored.

Those decisions belong to the business, not the platform.

Business Rules Are Just Data

At some point I realized something that now seems incredibly obvious.

Business rules are just data.

Not “like” data.

They are data.

They’re information about how your organization chooses to operate. They deserve to be treated as organizational assets that can be defined, governed, versioned, and shared across systems instead of quietly disappearing into the configuration screen of whichever platform happened to be implemented first.

When we don’t treat them that way, every transformation project starts with the same challenge. Before we can build something new, we have to rediscover how the business already works.

That isn’t transformation.

That’s archaeology.

A Hospitality Example

Consider something I see frequently in hospitality marketing.

A business decides that guests shouldn’t receive promotional messages while they’re actively staying at one of its properties. That’s not a technical requirement. It’s a customer experience decision. The business has decided that there are moments when serving the customer is more important than selling to them.

But somewhere along the way, that decision gets embedded inside campaign logic.

For years, everything works exactly as expected.

Then another platform is introduced.

Or another channel.

Or another team needs to apply the same rule.

Now someone has to recreate that business decision somewhere else.

Maybe they interpret it slightly differently. Maybe they forget one of the exceptions that accumulated over time. Maybe they don’t even realize another implementation already exists.

Nothing about the business changed.

Only the implementation did.

Before long, one business rule has quietly become five different technical implementations.

The One Ring Problem

There’s a Michele-ism I use a lot in meetings: “One Ring to rule them all.”

Usually I’m talking about having one canonical brief or one source of truth, but I think it applies here too.

Somewhere along the way, we handed one application responsibility for remembering how the business operates.

It worked beautifully until we needed another platform.

Or another channel.

Or another acquisition.

The software wasn’t just executing business rules anymore.

It had become the only place those rules existed.

That’s a risky position for any organization to be in.

Why This Matters More Than Ever

This way of thinking becomes even more important as organizations begin exploring AI.

Everyone wants AI to make smarter decisions, but AI can only reason over what the organization has actually represented. It needs to understand the conditions that influence decisions, the policies that should always be respected, the exceptions that matter, and the business principles that remain true regardless of which technology happens to be executing them.

Those aren’t prompts.

They’re business rules.

If those rules only exist as custom scripts scattered across half a dozen systems, AI has very little organizational intelligence to work with. Every modernization effort begins by rediscovering decisions the company already made years ago simply because those decisions were never represented independently from the software executing them.

A Different Way to Think About It

I’m not suggesting we create more documentation for documentation’s sake.

I’m suggesting we start treating business rules the same way we treat customer data or product information.

Give them names.

Define them clearly.

Assign ownership.

Represent them in a way that every platform can understand.

Sometimes that means metadata. Sometimes it’s a semantic layer. Sometimes it’s a governed taxonomy or a shared decision model. The implementation matters far less than the principle.

The business should own the rule.

Technology should consume it.

The Takeaway

I suspect this will become one of the defining characteristics of mature marketing organizations over the next decade.

It won’t be the size of their technology stack.

It won’t be how quickly they adopt AI.

It will be how intentionally they’ve separated business knowledge from technology.

Because technology will continue to change.

Your business shouldn’t have to rediscover itself every time it does.

Business rules were never software.

They were always organizational knowledge.

The smartest organizations simply choose to represent that knowledge as data instead of hiding it inside the tools they happen to use today.

One-to-one personalization.

The vision sounds compelling.

Every customer receives a unique message.

Every interaction is tailored.

Every experience is customized to the individual.

The technology industry loves this idea.

Marketing technology vendors love it even more.

The promise is always the same.

More data.

More content.

More personalization.

Eventually, a perfectly individualized customer experience.

But I’ve started to wonder if we’re solving for the wrong thing.

Not because personalization doesn’t matter.

Because I don’t think customers experience personalization the way marketers define it.

The same content can feel completely different

Think about the last time a message felt genuinely relevant to you.

Not because it used your first name.

Not because it referenced something you purchased.

Because it showed up at exactly the right moment.

Maybe you were researching a problem.

Maybe you had just encountered a challenge.

Maybe something had changed in your life or your business.

The content itself may not have been unique.

Thousands of other people may have received the exact same message.

But it felt personal because the context made it meaningful.

The same content delivered a week earlier might have been ignored.

A month later, it might have felt irrelevant.

The content didn’t change.

The context did.

Marketers tend to focus on the message

Customers experience the moment.

That’s an important distinction.

When we talk about personalization, we often focus on content variation.

How many versions can we create?

How many audience segments can we support?

How many dynamic rules can we build?

Those are all useful capabilities.

But customers rarely evaluate personalization based on how much effort went into creating the content.

They evaluate it based on whether it mattered to them when they encountered it.

Relevance is experienced.

Not engineered.

The industry may have confused customization with personalization

Customization is about changing the content.

Personalization is about changing the experience.

Those are not the same thing.

A company can create hundreds of content variations and still deliver an experience that feels disconnected.

At the same time, a single piece of content can feel remarkably personal if it arrives when it is needed most.

That doesn’t mean content doesn’t matter.

It means context matters more than we often acknowledge.

More content isn’t always the answer

One of the reasons organizations struggle with personalization is that they assume scale requires more content.

More variants.

More journeys.

More assets.

More complexity.

The result is often a content operation that becomes increasingly difficult to manage.

Meanwhile, customers are still asking a simpler question.

Is this relevant to me right now?

That question is often answered by timing, intent, and context far more than by content variation.

Context is the real personalization engine

This is where I think the conversation needs to evolve.

The future of personalization is not creating an infinite number of messages.

It’s understanding the circumstances that make a message meaningful.

What does the customer already know?

What are they trying to accomplish?

What has changed?

What signals suggest they’re ready for something different?

Those questions create relevance.

And relevance is what customers experience as personalization.

A different question to ask

Instead of asking:

“How do we personalize this content?”

Maybe we should be asking:

“What context would make this content meaningful?”

The answer often leads to a very different strategy.

One focused less on producing endless variations and more on understanding the conditions that shape customer decisions.

The takeaway

I don’t think customers are asking for a unique message every time.

I think they’re asking for relevance.

The industry has spent years chasing one-to-one personalization.

The better goal might be one-to-one understanding.

Because when context is understood, personalization becomes much easier.

And when context is ignored, no amount of content variation will make the experience feel personal.

Campaigns are running.

Meetings are full.

Work is constantly moving.

But activity is not the same as progress.

Why busy often signals a system problem

When systems lack clarity, teams compensate with effort.

More coordination.

More follow-ups.

More manual work.

The organization appears productive.

But much of that effort is spent navigating friction.

What effective systems look like

Effective systems reduce unnecessary effort.

Work moves predictably.

Decisions happen without escalation.

Teams focus on outcomes, not coordination.

The difference is not talent.

It is how the system supports the work.

The shift leaders need to make

Leaders often measure output.

How much work was completed.

More useful is understanding throughput and outcome.

How efficiently work moved.

What impact it created.

Progress is reported through updates.

Status is communicated through meetings.

Visibility depends on conversations.

This creates a pattern.

Leaders ask questions.

Teams provide updates.

Decisions get delayed.

Not because leaders lack direction.

Because they lack visibility.

Visibility vs control

Many organizations try to solve this by increasing oversight.

More check-ins.

More reporting.

More structured updates.

This creates control.

But it does not create clarity.

Visibility works differently.

It allows leaders to understand how work is progressing without needing to ask.

What changes when visibility exists

When systems provide visibility, leadership shifts.

Leaders stop chasing updates.

Teams spend less time explaining status.

Decisions happen faster.

The system becomes more self-sustaining.

Why this matters more than strategy

Strategy sets direction.

Visibility determines whether progress is real.

Without visibility, leaders operate on assumptions.

With visibility, they operate on signals.

But the cause is usually concentrated in one place.

Where work enters the system.

Why intake determines everything

Every campaign, request, and initiative starts somewhere.

If that starting point is inconsistent, everything that follows becomes reactive.

Priorities shift.

Work gets reworked.

Teams operate in negotiation instead of execution.

Many organizations treat intake as an administrative step.

In reality, it is the foundation of the system.

What broken intake looks like

Work enters through multiple channels.

Email.

Meetings.

Messages.

Side conversations.

There is no single view of demand.

Teams make decisions based on what is most visible, not what is most important.

This creates constant reprioritization.

What changes when intake is clear

When intake is structured, the system behaves differently.

Demand becomes visible.

Prioritization becomes intentional.

Execution becomes more stable.

Teams spend less time reacting and more time delivering.

Why this is the first system to fix

Leaders often try to improve execution downstream.

But if the starting point is unstable, downstream improvements cannot hold.

Fixing intake creates leverage across the entire system.

Execution slows down.

Priorities shift constantly.

Teams feel overwhelmed.

Leaders lose confidence in what they are seeing.

Everything starts to feel connected. Because it is.

At that point, the instinct is to fix everything at once.

New processes get introduced.

New tools get explored.

New expectations get layered in.

And the system gets heavier instead of better.

Most organizations do not need to fix everything.

They need to fix where to start.

Why everything feels broken at the same time

Marketing is not a set of isolated functions.

It is a connected system of decisions, requests, workflows, and outputs.

When one part breaks, the impact spreads.

If intake is unclear, priorities shift.

If priorities shift, execution slows.

If execution slows, reporting becomes unreliable.

Leaders experience this as widespread dysfunction.

But underneath it, there is usually a starting point.

The mistake leaders make

When everything feels connected, leaders try to address everything simultaneously.

They redesign workflows.

They introduce new structure.

They increase oversight.

This creates more coordination.

More meetings.

More alignment conversations.

More effort just to move work forward.

The system becomes harder to navigate.

Where to actually start

There are three places that reveal more about a system than anything else.

How work enters.

How decisions are made.

How progress is seen.

If you fix those, the rest of the system begins to stabilize.

1. Intake

If work enters the system inconsistently, everything downstream becomes reactive.

Requests arrive through email, meetings, messages, and side conversations.

Teams negotiate priorities instead of executing them.

A clear intake path does not eliminate demand.

It makes demand visible.

2. Decision clarity

When decision ownership is unclear, work slows down.

Approvals expand.

Escalations increase.

Leaders get pulled into details they should not need to manage.

Clarity here does not require more process.

It requires explicit ownership.

3. Visibility

Most leaders are asked to manage outcomes without being able to see how work is actually progressing.

Status updates become conversations instead of signals.

Visibility changes that.

When leaders can see clearly, they stop needing to ask constantly.

A simpler way forward

Fixing a system does not require solving everything at once.

It requires identifying where leverage exists.

When intake is clear, work stabilizes.

When decisions are defined, speed increases.

When visibility exists, leadership becomes more effective.

From there, the rest of the system becomes easier to improve.

“We just need to finalize the process.”

What follows is usually a diagram.

Swim lanes appear.

Boxes represent teams.

Arrows connect handoffs and approvals.

Everyone nods.

The process looks clear.

And then the system still does not work the way people expected.

Campaigns stall.

Automation fails.

Teams bypass the tool and return to email or spreadsheets.

At that point the technology often gets blamed.

But the problem usually started earlier.

Because process is not the same thing as system design.

The three conversations organizations collapse into one

When teams say they are “designing the process,” they are often blending three different conversations together.

Each one matters.

But they solve different problems.

When they get mixed together, confusion follows.

Process mapping

What happens and who does it

Process maps describe how work moves between people.

They clarify requests.

They outline handoffs.

They show who reviews or approves work.

Process maps answer operational questions.

What triggers the work?

Who owns the next step?

Where does accountability live?

This layer is about clarity between humans.

It helps teams understand how work should move through the organization.

But a process map does not explain how technology will support that movement.

Solution design

How the system enables the work

Solution design sits between operations and technology.

It translates the intent of the process into system behavior.

This is where teams decide:

How work moves automatically.

Where governance lives.

What events trigger the next step.

How data supports decisions along the way.

This layer determines whether a process will feel seamless inside a platform or require constant manual intervention.

It is also the layer most organizations skip.

Teams move directly from process diagrams to technical configuration.

And that is where systems start to struggle.

Technical design

How the platform is configured

Technical design is the implementation layer.

Fields are created.

Automation rules are configured.

Permissions are defined.

Integrations are connected.

This work is critical, but it should not invent the process.

It should enable decisions already made at the operational and solution layers.

When technical teams are asked to fill in missing decisions, they are forced to guess how the system should behave.

Those guesses often become permanent system constraints.

Where implementations go wrong

Many organizations build a process map and treat it like a technical specification.

The diagram gets handed to engineers or platform administrators with the expectation that the system will simply follow the arrows.

But a process diagram describes human movement.

Systems behave differently.

Platforms need explicit logic.

They need to know:

What triggers an action.

Where data is stored.

How exceptions are handled.

Who has authority to override a decision.

Without that translation layer, the platform ends up compensating for unclear operational design.

That is when teams begin to work around the system instead of through it.

Technology cannot invent clarity

Technology can enforce decisions.

It can automate handoffs.

It can provide visibility.

But it cannot invent operational clarity where it does not exist.

When organizations skip the solution design layer, they often ask technology to solve organizational problems.

No platform can reliably do that.

What follows is familiar.

New fields appear.

Additional tools get introduced.

Manual workarounds multiply.

The system grows more complex, but the underlying problem remains the same.

The leadership responsibility

Strong transformation leaders learn to separate these three conversations.

They ask different questions at each layer.

At the process level:

How should work move between teams?

At the solution level:

How should the system support that movement?

At the technical level:

How do we configure the platform to enable those decisions?

When those layers stay distinct, systems become easier to design and easier for teams to trust.

Execution becomes more predictable.

Technology begins to reinforce clarity instead of exposing confusion.

The simplest way to think about it

Process defines how people work.

Solution design defines how the system supports that work.

Technical design configures the technology to make it happen.

Confuse those layers, and transformation stalls long before technology ever has a chance to succeed.

Separate them, and the system begins to behave the way everyone expected in the first place.

Leadership starts talking about transformation.

A new operating model.
A redesigned organizational structure.
A fresh vision for how the system should work in the future.

Whiteboards fill up quickly.

Future-state diagrams appear.
Roadmaps emerge.
Consulting language starts circulating.

Architecture is exciting because it feels strategic.

But many marketing organizations are not struggling because they lack a vision for the future.

They are struggling because the current system cannot reliably move work from idea to execution.

And that is not an architectural problem.

That is a plumbing problem.

The difference between architecture and plumbing

Architects design how a system should look.

They define the structure.
They plan how pieces connect.
They imagine how the system will scale.

That work is important.

But plumbing determines whether anything actually flows.

Requests.
Approvals.
Information.
Decisions.

Those are the pipes of a marketing organization.

When those pipes are blocked, leaking, or routed through too many checkpoints, the system slows down regardless of how elegant the architecture looks on paper.

Many organizations attempt to scale before they have repaired the flow of work inside the system.

The result is predictable.

More process layers.
More coordination meetings.
More tools meant to compensate for operational friction.

Execution becomes heavier instead of faster.

Where the leaks usually appear

In most marketing environments, the issues are surprisingly consistent.

Intake processes are unclear, so teams negotiate priorities informally.

Approvals pass through multiple leaders because decision rights were never explicitly defined.

Campaign work moves across teams without shared visibility into status or dependencies.

Data exists but does not reliably influence decisions.

None of these problems require a new operating model to identify.

They require someone willing to trace how work actually moves through the organization.

That is the work of plumbing.

Why organizations skip this step

Repair work is rarely as exciting as redesign.

Future-state models feel strategic.

Fixing operational flow feels tactical.

But the order matters more than leaders often realize.

When organizations introduce new frameworks or operating models without stabilizing execution flow, the framework simply amplifies existing friction.

Teams end up navigating the same problems with new terminology.

Velocity does not improve.

The organization just becomes more complicated.

Flow creates the conditions for scale

Architecture works best when the system underneath it already functions.

When intake is clear, work moves predictably.

When decision rights are visible, approvals happen faster.

When operational visibility exists, leaders can guide the system instead of micromanaging it.

Once those conditions exist, frameworks and structural changes become powerful tools.

Without them, even the most thoughtful architecture struggles to produce results.

The leadership shift

One of the most important transitions leaders make is recognizing when the organization needs vision and when it needs repair.

Both matter.

But many marketing organizations are trying to design their way out of problems that are fundamentally operational.

They do not need another diagram of the future.

They need clarity about how work moves today.

Because once flow is restored, the system often begins to improve faster than leaders expect.

Architecture can then do what it was meant to do.

Support scale instead of compensating for friction.

The question worth asking

Before launching the next transformation initiative, it may be worth asking a simpler question.

Is the system struggling because it lacks a better design?

Or because the pipes inside it are clogged?

The answer determines whether the organization needs an architect.

Or a plumber.

Execution slows down.
Teams feel misaligned.
Results plateau even though people are working harder than ever.

At that point leadership starts searching for a solution.

A new framework.
A new operating model.
A new methodology that promises to unlock speed and alignment.

And because marketing touches almost every part of the business, that new solution often lands there first.

Marketing teams become the place where organizational transformation gets tested.

When frameworks travel farther than they were designed to

Frameworks themselves are not the problem.

Most were created to solve very specific challenges.

Agile, for example, was originally designed for software development teams. Its purpose was to create space for engineers to finish meaningful work before new requirements interrupted them again.

Over time Agile spread far beyond engineering.

It became a management philosophy.
A planning model.
An enterprise operating structure.

Marketing organizations adopted it too.

But the environment inside marketing is different from the one Agile was originally built for.

Marketing operates across functions.
Across channels.
Across customer experiences.
Across data systems and executive priorities.

The framework remained the same.
The environment changed.

That is where friction begins.

Why frameworks rarely fix the real problem

Frameworks amplify the systems they inherit.

If decision paths are unclear, the framework multiplies confusion.
If workflows are fragmented, the framework accelerates the fragmentation.
If ownership is vague, the framework distributes accountability without resolving it.

When this happens, the model gets blamed.

Leaders say the framework failed.

In reality, the framework exposed the system that was already there.

Structure describes how teams are organized.

Systems describe how work actually moves.

Decisions.
Approvals.
Information flow.
Escalation paths.
Ownership.

Those mechanics shape outcomes long before an organizational chart ever does.

When those systems remain unchanged, introducing a new framework rarely produces the transformation leaders expect.

Why marketing requires operational clarity before structural change

Marketing is not a linear production environment.

It is a connected system of strategy, execution, technology, analytics, and cross-functional coordination.

Operating models can support that complexity.
But they cannot compensate for unclear decision systems or broken execution flow.

When organizations change structure without changing how work actually moves, they create new labels for old friction.

Velocity does not improve.

Meetings increase.

Ownership diffuses.

The organization feels busier but not more effective.

The question leaders should ask

The next time an organization introduces a new framework, the most important question is not whether the framework is innovative.

The more useful question is this:

What system will this framework inherit?

If decision rights are unclear, the framework will magnify that ambiguity.

If intake and prioritization are inconsistent, the framework will accelerate the inconsistency.

If operational visibility is weak, the framework will not create it.

Frameworks are powerful tools when applied to systems that are ready to support them.

But they are not substitutes for operational clarity.

Marketing does not need the next fashionable solution.

It needs leaders who understand how work actually moves and are willing to strengthen the system before redesigning the structure.

They love the creativity. The strategy. The moment when a campaign finally works and everyone feels it.

What they don’t love is feeling stuck managing noise instead of leading progress.

Somewhere between dashboards, approvals, and competing priorities, leadership started to feel less like designing outcomes and more like hosting a talk show where every guest is talking at once.

If John Stewart, Drew Barrymore, and a Jazzercise instructor all walked on stage simultaneously, you would not fix the situation by talking louder. You would redesign the format.

Marketing leadership works the same way.

The future of marketing is not about adding more tools or pushing teams harder. It’s about designing systems that allow people to do their best work consistently.

This is the shift happening now.

Leaders are moving from campaign managers to system architects. From reacting to designing. From constant oversight to intentional visibility.

For the love of marketing, this is the work now.

And honestly, it’s better work.

Because when systems work, teams breathe again. Creativity returns. Strategy becomes real instead of theoretical.

Leadership stops feeling like survival and starts feeling like progress.

Ender enters Battle School thinking success means following instructions better than everyone else. Over time, he realizes the real challenge is understanding how the system actually works.

Marketing leaders experience this constantly.

You inherit tools.

You inherit processes.

You inherit reporting structures that feel like they were assembled by Microsoft Clippy after three coffees.

And yet, you are expected to deliver results.

The leaders who struggle try to push harder inside the existing structure. The leaders who grow start asking different questions.

What assumptions are we operating under?

What rules are invisible?

Where is the real constraint?

This is where the line from the book matters so much.

“The enemy’s gate is down.”

It represents a shift from reacting inside the system to seeing the system clearly.

In marketing operations, this moment happens when leaders stop optimizing channels individually and start understanding how decisions connect across the organization.

Suddenly, problems that felt unsolvable become navigable.

Not because the work changed.

Because the perspective did.

Leadership inside complexity is not about control.

It’s about understanding the field well enough to move differently within it.

Join Book Club

We love solving problems. We love connecting ideas. We love building things that matter.

Somewhere along the way, chaos became part of the identity. Late nights. Last-minute pivots. Fire drills framed as proof of commitment.

For the love of marketing, we need to stop pretending this is healthy!

Chaos is not a requirement of good marketing.

It is a symptom of systems that have not kept pace with complexity.

When teams are constantly reacting, creativity suffers. When leaders are buried in noise, strategy gets thinner. When everything is urgent, nothing is intentional.

Loving the craft does not mean accepting dysfunction.

Strong leaders protect the work by designing systems that support it. They create clarity around decisions. They reduce unnecessary friction. They build visibility so teams can focus on what actually matters.

This is not about making marketing boring.

It is about making it sustainable.

If we truly care about the future of this profession, we have to stop celebrating chaos and start designing better environments for good work to happen.

That is leadership.

It’s a book club about leadership inside complexity, and why so many marketing leaders feel like they are fighting battles they did not design.

I chose Ender’s Game as the first book we’ll spend real time with because it mirrors the reality of modern marketing leadership. High accountability. Constant change. Incomplete information. Pressure to perform without full control.

Most marketing leaders are not struggling because they lack talent, creativity, or drive. They are struggling because they are operating inside systems that no longer match the complexity of the work.

That tension shows up everywhere. In disconnected tools. In unclear decision paths. In teams that are constantly busy but rarely ahead.

Ender’s Game captures this dynamic with unsettling clarity.

Ender is placed inside a system he did not design. The rules change constantly. The stakes are high. He is judged on outcomes, not context. He is expected to win without ever seeing the full picture.

Sound familiar.

But there is one moment in the book that changed how I think about leadership and systems entirely.

It comes down to a single line.

“The enemy’s gate is down.”

That sentence reframes everything.

For most of the story, Ender is taught to fight within the frame the system gives him. Up versus down. Attack versus defense. Win the way it has always been won.

“The enemy’s gate is down” breaks that mental model.

It is not a tactical insight.
It is a systems insight.

Ender realizes the problem was never the battle itself. It was the frame he was operating inside.

Once the frame changes, the entire system behaves differently.

This is where modern marketing leadership gets stuck.

We are taught to fight marketing problems the way they have always been fought. Channel by channel. Campaign by campaign. Tool by tool.

We optimize execution while ignoring the system shaping that execution.

When personalization fails, we blame data.
When campaigns stall, we blame process.
When teams burn out, we blame capacity.

But often, the real issue is perspective.

Leaders are fighting the right battles inside the wrong frame.

Marketing today is not a collection of tasks. It is a connected system of decisions, data, workflows, and people. When that system is misaligned, no amount of effort produces consistent results.

“The enemy’s gate is down” is what happens when a leader finally sees the system clearly and realizes the problem was never where they were told to look.

This is why we are reading Ender’s Game for the love of marketing.

Not because it offers answers.
But because it sharpens how we see.

This Book Club exists to help leaders step outside inherited frames. To recognize patterns. To question assumptions. To understand the systems they are actually operating inside.

Because the leaders who scale are not the ones who work harder or react faster.

They are the ones who see differently.

If you still love marketing but feel like you are fighting battles that never quite end, this work is for you.

We will spend time with this book. We will return to it often. And we will use it as a lens to explore leadership, systems, and marketing operations in a way most conversations never do.

For the love of marketing, it’s time to change the frame.

Join the Book Club

They started when leaders changed how they showed up.

When leaders stopped:

• Reacting to every fire

• Reworking every deliverable

• Carrying decisions that should have been distributed

And started:

• Clarifying decision frameworks

• Designing operational visibility

• Trusting systems instead of intuition alone

Something interesting happened.

Teams moved faster.

Confidence improved.

Leaders had space to think again.

This is the quiet side of leadership transformation that rarely gets talked about. Not the big reorgs or platform changes, but the internal shift from managing chaos to designing clarity.

This is the work I care most about.

If you’re a marketing leader who feels stuck between strategy and execution, this year is a good time to rethink how your system supports you.

Later this year, I’ll be working closely with a small number of leaders on exactly this shift.

If you’re interested in working together, send a message

When leaders tell me their marketing organization feels chaotic, I rarely hear randomness. I hear patterns that haven’t been surfaced.

Repeated rework.

Conflicting priorities.

Endless status updates with no decisions.

The work looks messy, but it’s usually consistent in all the wrong ways.

Strong leaders develop the ability to recognize these patterns early. They don’t wait for breakdowns. They notice where things drift, where signals conflict, and where energy gets wasted.

This is where pattern recognition becomes a leadership skill.

In my work, I think about marketing systems the way astronomers think about stars.

Individual efforts matter, but meaning comes from how they connect.

Constellations are not about individual brilliance. They are about structure, alignment, and shared direction.

When leaders can see the constellation instead of isolated points, they stop reacting and start designing.

They don’t chase noise.

They build coherence.

This is one of the most important shifts leaders can make as marketing grows more complex.

Subscribe now

Share

The most consistent pattern I see is this:

The moment a team starts to scale, the cracks in the system appear faster than anyone expects.

What breaks first is rarely creativity.

It’s clarity.

Teams lose clarity around:

• Who owns decisions

• How priorities shift

• What success actually means

• Where work gets blocked

As complexity increases, leaders often respond by adding more oversight. More meetings. More approvals. More tools.

That rarely fixes the problem.

What actually helps is stepping back and asking better questions about the system:

• Where are decisions slowing down?

• What work is being duplicated?

• Where does context get lost?

• Which teams are carrying hidden operational debt?

The strongest leaders I’ve seen don’t jump straight to solutions. They diagnose the system first.

They understand that scale doesn’t require more control. It requires better design.

When leaders learn to see the system clearly, teams regain trust. Work speeds up naturally. Accountability improves without micromanagement.

This is the difference between managing chaos and architecting clarity.

The leaders who scale are not the ones who approve faster or push harder. They are the ones who understand how decisions move, how work flows, and where friction hides.

This is what systems thinking really means in modern marketing.

It’s the ability to step back and see how strategy, operations, data, and people interact as one environment.

Most leadership breakdowns I see today don’t come from bad ideas.

They come from leaders being too close to the work and too far from the system.

When leaders focus only on outputs, campaigns, launches, dashboards, they end up managing symptoms. When they focus on systems, they change outcomes.

That’s why the most effective marketing leaders today:

• Design workflows before demanding speed

• Clarify decision rights before asking for alignment

• Build visibility before asking for accountability

In my work, I use a framework I call Constellations to help leaders see how everything connects. Not as a set of tactics, but as a way of thinking about the system behind the work.

We’ll talk more about that this year.

For now, this is the shift to pay attention to:

Leadership is no longer about controlling work.

It’s about designing systems where good work becomes inevitable.

If this resonates, you’ll want to stay close.

We’ve built teams full of smart, capable people surrounded by disconnected tools, competing dashboards, and workflows that look like spaghetti charts.

Every week, I talk to a marketing leader who says:
“We know what to do… we just can’t seem to do it consistently.”

That is the heart of the modern marketing mess.
It’s not about talent. It’s about translation.
It’s about how the system connects the dots between people, process, and purpose.

Where We’re Stuck

We were taught that “strategy” is the big picture and “operations” is the plumbing underneath it.
In 2026, those lines don’t exist anymore.

The system is the strategy.

How your campaigns are built, measured, and optimized determines whether your best ideas ever reach the customer or get buried in review loops, tech debt, and disconnected data.

Most marketing organizations are not underperforming creatively.
They’re underperforming operationally.

We have more data than ever, but less clarity.
More tools than ever, but less flow.
More potential than ever, but less progress.

What the Best Teams Are Doing Differently

The strongest leaders I work with are shifting from:

• Tool-first thinking → System-first design

• Campaign reporting → Business storytelling

• Firefighting → Flow-building

• Micromanaging → Monitoring intelligently

They are learning to lead both functionally and strategically.

They can speak “data” and “dollars” in the same sentence.
They can run an ops meeting and still hold a seat at the executive table.
They are the bridge between marketing chaos and marketing clarity.

What’s Next

I’m launching something new in January, a space for leaders who are ready to stop patching problems and start architecting smarter systems.

Think of it as a blend of:

• Functional mastery
  (data, MarTech, governance, orchestration)

• Leadership mastery
  (business fluency, cross-functional trust, executive presence)

It is for marketing leaders who understand that the future will not reward those who speak the loudest.
It will reward those who build the clearest systems.

If you’re tired of marketing feeling harder than it should be, stay close.
This is where we rebuild how marketing works and how you lead it.

year.→ Subscribe if you want to be part of the first conversation.

Subscribe now

→ Drop me a note if your team’s ready to pilot smarter systems before the new year.

This Substack is for the leaders who are ready to do the same.

Starting in January 2026, I’ll be sharing:

• Frameworks for building a smarter, simpler Marketing OS

• Field notes from transformation leaders who have fixed the system behind their marketing

• Leadership lessons that bridge the gap between strategy and execution

• Insights from my Constellations Framework™, my approach to designing marketing systems that connect every message, metric, and move into something that works

And because great leadership is pattern recognition, we will also kick off a monthly Book Club beginning with Ender’s Game, a story that is really about systems, empathy, and how to lead through complexity.

The future of marketing isn’t about more tools. It’s about better systems and leaders who can see the full constellation.

Subscribe now to get the first issue when it drops in January. Let’s make 2026 the year marketing finally starts working right.

Subscribe now