The thinking behind the results.

Most organizations do not fail because of change. They struggle because they underestimate the cost of absorbing it.

• A new leader arrives.
• An acquisition is integrated.
• A reorganization takes place.
• A platform is migrated.
• Compensation plans are redesigned.
• Territories are adjusted.

None of these are inherently bad decisions. Many are necessary. The challenge is that every change creates both benefits and consequences.

Organizations tend to spend significant time evaluating the upside of a change. Far fewer spend enough time thinking about what else that change might touch.

You may achieve 80% of the outcome you were hoping for, but there is almost always some level of disruption.

• New handoffs emerge.
• Relationships change.
• Processes break.
• Knowledge gets lost.
• Teams spend time relearning instead of executing.

That is why when performance starts to slip, the question often becomes, “What broke?”

A more useful question is, “What changed?”

Because the issue is often not the change itself. It is an unintended consequence that showed up somewhere else in the business.

I learned most of this integrating two demand organizations after an acquisition.

The obvious work was the visible work. Two demand platforms. Two marketing automation systems. Two analytics stacks. Two definitions of a qualified lead. That work was difficult, but it was scopeable, and we did it.

The part that was not scopeable was everything that had been true informally. Who a regional seller called when a campaign underperformed. Which analyst a business unit leader trusted to check a number before taking it to a board review. The unwritten understanding about who could approve an exception without escalating it. None of that appeared on any integration plan, and all of it had to be rebuilt, mostly by people discovering in real time that the old path no longer worked.

We also made a coverage decision I would make again, and it still cost something. The combined team did not have enough marketers to dedicate coverage across every European market. So we moved to cross-business-unit country coverage, which meant some units would receive less dedicated attention while senior leaders engaged directly with their sales counterparts to close the gap. It took roughly six months to settle.

The decision was right. The absorption cost was real. Saying so openly mattered, because the teams living it already knew, and pretending otherwise would only have cost me the credibility I needed to ask them to stay with it.

One lesson I have learned is that organizations can survive almost any individual change. What they struggle with is absorbing several at the same time. The effects compound, which makes it difficult to isolate root causes and understand which change created the conditions for the problem.

The leaders who navigate transformation best do not avoid change. They anticipate the ripple effects. They understand that every change creates both value and friction, and they plan for both.

Every change solves a problem. The best leaders spend equal time thinking about the new problems it might create.

If you worked in IBM Analytics when I did, you probably either loved or hated Calibri.

But you definitely remember it.

The leader I reported to at the time had a standard, and the standard included the font. I thought it was mostly about packaging. The look and feel. The consistency.

What I did not appreciate then was why any of it mattered.

Back in those days, teams would squeeze presentations down to 8-point font, trying to fit every detail onto a slide.

Over time, that changed. Larger fonts. Cleaner slides. The narrative moved into the speaker notes. The discussion moved into the room.

Years later, I realized this was never really about Calibri.

It was about clarity. It was about helping people focus on what mattered. It was about understanding that communication is not measured by how much information you present. It is measured by how well your audience understands the message.

She approached data the same way. She loved understanding why. The metric was never the destination. It was the starting point for a deeper conversation.

That lesson is the reason a reporting environment I later sponsored ended up looking the way it did.

When we moved marketing reporting off large Excel workbooks with macros and multiple tabs, the easy win was the technology. The harder question was the same one behind the 8-point font. How much can a person actually hold in their head, and what are they supposed to do next?

So we branded the reporting environment, gave it consistent navigation, and worked to make many separate reports feel like one journey rather than twenty-three destinations. Adoption followed from that. It did not follow from the underlying data model, which had been broadly correct for a while before many people were using it.

A dashboard nobody opens is not a reporting problem. It is the 8-point font again.

Looking back, some of the most valuable lessons I learned had very little to do with fonts. They were about clarity, curiosity, standards, and understanding what actually drives outcomes.

I read an article about why 68% of companies do not trust their sales forecasts.

The core issue is not forecasting models. It is visibility and process discipline.

It reminded me of three questions I wanted our teams thinking about in forecast reviews.

1. What percent of late-stage opportunities are past historical cycle time?
2. What is weighted coverage by segment, not just total pipeline?
3. Where is stage progression slowing quarter over quarter?

Those questions usually lead to the same place, which is stalled pipeline. Opportunities that stop moving often tell you more than the ones progressing.

None of the three is hard to answer. That is the point.

They are hard to answer consistently, because each one rests on a definition somebody has to own and defend. Historical cycle time for which segment, measured from which stage. Weighted coverage against which target. Stage progression by whose stage definition, and whether that definition survived the last reorganization.

Most forecast reviews I sat in were arguments about the number when they should have been arguments about the definitions underneath it. Once the definitions were settled and visible, the reviews got shorter and the disagreements got more useful, because everyone was finally looking at the same thing.

That is also the moment marketing's contribution stops being contested. Not when marketing produces a bigger number, but when the number means the same thing to marketing, sales, and finance.

Open pipeline feels good. Predictable pipeline builds trust.

Forecast discipline is not just math. It is culture. It requires honesty, clear definitions, and shared accountability across the organization.

I noticed something this past spring about how differently teams operate depending on size.

On a Saturday, we had a smaller invitational group of around 30 athletes. The environment felt more intimate. As coaches, we had time for conversations, teaching, encouragement, and simply paying attention to how each athlete was doing mentally and physically.

The athletes responded differently because of it. They communicated more openly. Asked more questions. Competed with more confidence.

Then Monday came and we were back to managing a team of nearly 100.

The dynamic changed immediately. More moving parts. More decisions. More conversations happening at the same time. Less visibility into every interaction.

And it reinforced a lesson I have run into repeatedly in business.

One athlete was pushing hard because he wanted the team to win a relay at a meet that was not our priority. I was doing my best to temper that, because the league championship was days away.

But conversations happened when I was not around.

Another athlete had just returned from injury and had already run a season best earlier in the meet. He chose to run a second race and re-injured himself.

When I asked him why, his answer stayed with me.

“I didn't want to disappoint the team.”

He could not compete in the championship meet, which was where we actually needed him.

What also stayed with me is that the athlete pushing to build the strongest possible relay lineup almost certainly believed he was helping. He was not being reckless. He was optimizing for the thing directly in front of him, without the context that would have told him it was the wrong thing to optimize.

The same thing happens inside organizations.

As companies scale, leaders naturally become more stretched. Complexity increases. Visibility decreases. More decisions happen in rooms you are not in.

But one thing should never scale down: attention.

The farther leaders get from people, the less truth they tend to hear.

People perform differently when they feel seen. People communicate differently when trust exists. People make better decisions when communication stays open and grounded.

This is the part I think gets misdiagnosed most often. When something goes wrong at scale, the instinct is to add process. But the failure was rarely a missing process. It was usually someone making a defensible decision without the context that would have changed it.

One of the biggest risks in a growing organization is not process failure. It is people quietly making decisions under pressure without enough guidance, context, or communication.

The best leaders find ways to scale clarity, trust, and connection alongside the business.

Otherwise growth creates distance instead of alignment.

Something that has become clearer to me over the years: people often grow into opportunities long before they feel fully prepared for them.

I have experienced both sides of that.

Earlier in my career, expectations changed faster than preparation. A leadership transition shifted responsibilities around me quickly, and I struggled in some important moments. I did not fully understand the long-term effect that had on my confidence until years later. That experience is part of why I pay attention to how organizations hand people expanded scope, and whether anyone is actually helping them carry it.

Later in my career, I experienced the opposite.

In my last operating role, I started by leading a relatively small organization focused on campaigns, digital, and sales enablement. Within months, additional teams moved over. Then partner and field marketing. Then operations and reporting. Then integration leadership during a major acquisition. And eventually more.

Some of those areas I had never led before.

Field marketing runs on a different rhythm than campaigns, and it answers to people whose incentives are regional rather than functional. Operations and reporting required me to be fluent in definitions and data lineage rather than channel strategy. Integration leadership required something else again, which was making decisions with incomplete information while two organizations watched closely to see whether the new structure was going to be fair.

What changed everything was having leaders who trusted my ability to learn, adapt, build relationships, and move the business forward, along with people around me willing to share what they knew in the areas where I still needed to grow.

Over time, my role grew from leading roughly 20 people to more than 200.

That experience reinforced something important for me.

The best leaders do not evaluate people only on what they have already done. They look for hunger, adaptability, self-awareness, resilience, and the willingness to grow into something bigger.

Many of the opportunities that define careers come from someone being willing to bet on potential rather than on prior titles, direct experience, or checking every box on paper.

Sometimes the commitment to improve, work hard, and take feedback matters more than having every qualification already mastered.