Leading Creative Teams Through Change: New Tools, New Trends, Same Humans
The Edit #1
How your team operates will change this year.
Maybe it already has. A new platform… a new process… a directive from above that everyone needs to get comfortable with about something nobody fully understands yet.
And if you watch closely when that happens, you’ll notice something that doesn’t get talked about much.
Your strongest people grow quiet.
Not because they’re disengaged or don’t want to learn, but because they’ve spent years building something that matters to them — a standard, a reputation, an instinct that other people rely on — and suddenly they’re a beginner again.
Despite what it looks like on the surface, it’s not resistance. It’s actually something more human than that.
What Change Actually Threatens
Here’s the thing a lot of folks get wrong about creative professionals, and it’s something that separates them from most other knowledge workers.
Their competence is their identity.
A senior copywriter doesn’t just do good work.
She is someone who does good work.
That distinction lives in how she carries herself in a brief, how she gives feedback, how the junior writers watch her work and try to reverse-engineer what she does naturally.
Introduce a new tool… and that identity gets temporarily destabilized.
The junior who had nothing to prove picks it up over a weekend and suddenly looks more capable than the person who’s been here for 8 years. And the hierarchy that everyone understood (even if no one ever named it) gets flipped.
The senior writer knows it.
She can feel it.
And what looks like resistance is usually this: a rational response to a status threat. The person isn’t saying “I don’t want to learn.” She’s saying, “I don’t want to look incompetent in front of the people I’ve been leading.”
Leaders who miss this spend all their energy on the tool. They run demos. They share tutorials. They talk about efficiency gains and workflow improvements.
None of that touches the actual problem.
(Can you tell that I’m kinda talking about AI yet?)
Your Job as a Leader Isn’t Change Management
Honestly, “change management” is a corporate concept. It treats people like variables that need to be aligned to a new configuration.
That’s not what’s being asked of you here (it lacks empathy anyway and I’m not an unempathetic guy).
What’s being asked is harder and more specific: create enough safety for your team to try something they might fail at, without that failure meaning something about their worth.
And you know what? That starts with you.
If you’re rolling out a new tool or process you haven’t fully figured out yet, say that! Don’t “perform” confidence you don’t have. Your team will see through it immediately, and the gap between what you’re projecting and what’s actually true will cost you more trust than the uncertainty itself.
Model the learning out loud. Let them watch you struggle with something. Ask questions in the room instead of only behind closed doors. When you make the beginner visible — when you show that even you haven’t figured this out yet — you give everyone else permission to be figuring it out too.
Make the try-and-fail window explicit. Don’t assume people know they’re allowed to be bad at something before they’re good at it. Say it!
“For the next month, we’re learning. Nothing we produce in this context is going into a performance review. We’re just figuring out what this does and doesn’t do for us.”
Assumed safety isn’t safety.
Named safety is.
Does your team actually believe they’re allowed to struggle with this in front of you? Or do they feel like they’re supposed to have it figured out already?
If the answer is the latter, you haven’t created a safe space yet. Get to work.
Pilots = Signals
The reason low-stakes pilots work isn’t really about the stakes.
It’s about the signal.
When you set up a pilot — a real project, real work, but not a client deliverable riding on the outcome — you’re telling the team: this is learning time, not performance time. That distinction matters more than any tutorial you could run.
The structure doesn’t need to be complicated. Give the team a genuine brief. Run it with the new tool or process. Then sit together and look at the results.
Not to evaluate who got it right but rather to figure out what the experience actually was.
What worked?
What slowed people down?
Where did the new approach help the thinking, and where did it get in the way of it?
That debrief is the point. The output is secondary.
And at the end of it, ask each person something simple: one thing that felt useful, one thing that felt off. That’s not data collection. That’s a leadership act. It tells your team that their experience of the change matters to you, not just the outcome.
That’s different from most rollouts. Most rollouts ask people to adapt and then measure whether they did. This one asks people to think and create alongside you.
And honestly? That sense of shared ownership creates buy-in like no other.
What To Say (And What Not To)
Most leaders undersell the difficulty and oversell the benefit. But what actually builds trust during change is specific and honest, not positive and vague.
Name what’s changing.
Name what isn’t.
And name what you don’t know yet.
Before you make any announcement, ask yourself one question: am I framing this for them, or for me?
If the answer is for you — to look decisive, to project control, to manage up — the framing will land hollow. People can feel the difference between a leader who is leveling with them and a leader who is managing them.
Level with them.
The Part No One Talks About
Some people on your team won’t adapt the same way. And a few of them won’t actually be resisting. They’ll have a legitimate case.
A writer who has spent 15 years in direct response, who has built a process that produces reliably strong work, may find that certain new tools actively interrupt how she thinks. The friction isn’t stubbornness. It’s craft.
Your job is to know the difference, and I argue, respect the difference.
The question isn’t “is this person resisting?” It’s “does this new approach actually serve the work they’re doing?” Those are different questions with different answers.
Good leaders leave room for that distinction. They don’t mistake uniformity for alignment. A team that has genuinely evaluated a new tool and reached different conclusions about how to use it is a healthier team than one where everyone adopted it on the same timeline because that’s what was expected.
The goal isn’t consensus on method. It’s shared commitment to the standard.
The Tools Will Keep Changing
They always do.
Something will come out next year that makes the current conversation feel dated. Your team will be asked to learn it, adapt to it, and eventually become fluent in it.
What won’t change is this: your team is made up of people who built their careers on being good at something. Every time the ground shifts, that competence feels briefly at risk.
Your job isn’t to manage that away.
It’s to hold the space while they find their footing again.
New tools.
New trends.
Same humans.
Same job.
Further Reading
For leaders who want to go deeper on the human side of change. Curated for creative leaders — not enterprise change managers.
Managing Transitions: Making the Most of Change — William Bridges & Susan Bridges The clearest book on why change is hard even when people want it. Bridges separates the external event from the internal psychological reorientation — and argues it’s the transition that leaders almost always undermanage. Start here.
Switch: How to Change Things When Change Is Hard — Chip Heath & Dan Heath Change fails not because people are stubborn, but because leaders appeal to the rational mind and ignore the emotional one. Practical and human.
Dare to Lead — Brené Brown Specifically useful here for its research on psychological safety and vulnerability in leadership. The chapters on trust and learning cultures map directly to what this essay is about.
Leadershift — John Maxwell Focused on the internal shifts leaders need to make before they can lead others through change. Useful if you’ve ever wondered why your team isn’t following you when you feel like you’re doing everything right.
The Fifth Discipline — Peter Senge A slower read, but foundational. Senge’s concept of the learning organization asks: how do you build a team that can adapt without breaking? Worth the time if you’re thinking long.
HBR’s 10 Must Reads on Change Management — Harvard Business Review A survey of the field’s core frameworks without committing to one author’s worldview. Good desk reference if you want range before you go deep.