The job wasn't to take orders.

How I rebuilt a global content team around editorial expertise, independent judgment, and the confidence to challenge the brief.

We had writers. What we needed were thought partners.

When I became Global Head of Content, I inherited a seven-person team organized largely around the types of content they produced.

Much of our source material came from engineers and technical specialists who knew their subjects inside and out. But communicating that expertise clearly to a business audience required a different set of skills.

When a stakeholder insisted that their draft shouldn't be substantively changed, our writers were accustomed to checking for glaring typos and moving on.

The result was content that often needed considerably more than proofreading.

The engineers brought deep technical expertise. Our responsibility was to make that expertise clear, compelling, and useful to the people we were trying to reach.

That takes curiosity, critical thinking, and the confidence to ask questions—and push back when someone else thinks they can do your job for you.

I wanted writers who would dare to own their own expertise.

Respecting someone's technical knowledge doesn't mean surrendering your editorial judgment.

If an argument is weak, an explanation is confusing, or a message misses its audience, I expect my writers to recognize it, say so, and recommend something better—even when the stakeholder is senior.

And I make sure they know I'll back them when they do.

You can't just tell people to "be more strategic."

So I changed how we hired, organized, and developed the team.

We moved from assigning work by content type to giving writers ownership of specific business units. I challenged each to operate as the Head of Content for their business unit—someone who understood the offerings, knew the audience, and took responsibility for the quality of the work.

I introduced hiring exercises that tested reasoning alongside writing ability, required team members to regularly demonstrate their business knowledge, and made editorial judgment central to our coaching conversations.

The transformation was gradual. Changing an org chart is considerably easier than changing capabilities, expectations, and habits—especially on an enterprise scale.

What changed?

As the team and its operating model evolved, our reporting showed meaningful improvements in audience engagement:

91% increase in average blog engagement time
133% growth in blog users

These results reflect the efforts of the team and its cross-functional partners, not the organizational changes alone.

But the shift I value most isn't captured by those numbers.

It's a team that is capable of contributing professional judgment, not just polished words.

What matters most to me

I don't want to be the kind of leader who insists everyone blindly follow my directions.

I want people who can recognize a problem, question an assumption, and confidently recommend a better way forward.

And when someone on my team tells me there's a better way to do something?

Good. That's exactly what I hired them to do.