Becoming the Agent of Change Your Content Team Needs

On May 20, 2026, I joined Dawn Stevens on The Content Wrangler webinar channel — sponsored by Heretto — to talk about what it actually means to be the agent of change on a documentation team, whether you chose the role or not.

Most documentation teams are navigating real pressure right now: AI adoption, new delivery requirements, leadership mandates with unclear success criteria. Someone has to be the person who helps the team move. This conversation gets into what that actually looks like — not the theory of change management, but the mechanics of it. How do you build trust when you do not have authority? How do you surface resistance before it derails the project? How do you understand your own motivation well enough to know what you can genuinely contribute? We also get into why the organizations most at risk are the ones measuring the wrong things — tracking token usage instead of asking whether their content is functioning as a strategic asset.

If your team is being asked to absorb change faster than it can process — and someone needs to be the person who makes that work — this conversation will give you something to actually do with that situation.

Watch the recording on The Content Wrangler.

If your organization is rolling out AI tools and no one has stopped to ask whether your content architecture can support what you are asking those tools to do, that is the gap I help close. It tends to show up late, when projects are already underway — and it is much cheaper to address early.

Book a free discovery call today.

This session was hosted by Dawn Stevens on The Content Wrangler webinar channel, sponsored by Heretto.

If you're navigating the other side of this dynamic — the resistant teammate rather than the change leader — our curmudgeon webinar covers that conversation in depth.

For the scenario-by-scenario version of this material, the ConVEx 2025 slides walk through four real situations where agents of change and their teams talk past each other.

Previous
Previous

What Can Localization Learn from the CMS Industry?

Next
Next

Structured, Modular, Open: The DITA Promise, 20 Years Later