The Instinct That’s Hurting Your Team
Here’s the trap every creative leader falls into.
You care about your team. You want them to succeed. So when you see someone heading toward a risky creative direction, you step in. You soften the edges. You steer them somewhere safer. You tell yourself you’re protecting them from a client rejection, from embarrassment, from wasted effort.
You’re not protecting them. You’re training them.
Every time you redirect a bold idea toward something more palatable, you’re sending a signal. And your creatives are paying attention. They’re learning what gets rewarded and what gets redirected. They’re mapping the borders of what’s acceptable. And over time, they stop even trying to go near the edges.
The most dangerous thing you can do as a creative leader isn’t approving risky work. It’s running a team that never produces it in the first place.
If your team is batting a thousand, the work is too safe. And safe work gets ignored.
How You Accidentally Train Your Team to Play It Safe
You don’t teach fear through a speech. You teach it through a hundred small moments that add up to a lesson.
Here’s a scene I’ve lived through more times than I can count. A brave creative brings me something weird. It’s unexpected. It’s a little risky. I feel that knot in my stomach because I’m already thinking about the client, the budget, the presentation, the way the room might go quiet when we put it up.
So I say something like: “I’m just not sure they’ll buy it.”
That’s it. That’s the whole moment. And just like that, I steered them back to safety. I didn’t reject the idea. I didn’t tell them it was bad. I just expressed doubt at the exact moment they needed conviction.
That creative just learned something. They learned: “Don’t bring weird ideas. Only bring ones you already know will land.”
I taught them that. Not the client. Me.
This happens in meetings constantly. Someone pitches a direction that feels genuinely different and a leader says, “Interesting. But let’s also explore a safer version.” The team hears: the safe version is the real version. The other one is just for show.
It happens in reviews. A junior designer takes a real swing and the feedback focuses entirely on what’s broken about it. No acknowledgment of what they were reaching for. No credit for the risk. Just red lines through the execution. They fix the red lines and next time they don’t swing.
It happens in approvals. Work has to pass through three rounds of sign-off before it goes to the client, and by the fourth revision it looks like every other campaign in the category. The edges have been sanded off by people who each wanted to reduce their exposure.
None of these people thought they were building a culture of fear. They were just doing their jobs. Being thorough. Being responsible. Protecting the work from failure.
But the result is a team that’s been trained to self-censor before they even open a brief.
What Psychological Safety Actually Means for Creatives
“Psychological safety” gets thrown around a lot. And it usually gets reduced to something like: making sure people feel comfortable. Making sure nobody gets talked over in meetings. Making sure there are no hostile personalities on the team.
That stuff matters. But it’s not what psychological safety means for a creative team.
For a creative team, psychological safety means one specific thing: permission to swing and miss.
It’s not about being comfortable. It’s not about being yourself in Slack or feeling okay saying a dumb idea out loud in a brainstorm. Those are entry-level conditions. Necessary, but not sufficient.
Real psychological safety in a creative context is knowing that if you bring something genuinely risky, the leader will protect you. Not protect you from the attempt. Protect you while you attempt it. And if it crashes, protect you from the fallout.
It’s the difference between “we won’t judge you for bad ideas” and “we will actually back you if you try something hard.”
That’s the thing your best creatives need before they’ll take real creative risks. They need to know the failure won’t be held against them. That a swing and a miss doesn’t mean they get labeled as someone whose judgment can’t be trusted. That the attempt is valued, even when the outcome isn’t.
Without that, your most talented people will give you competent, professional, forgettable work. Not because they can’t do better. Because they’ve accurately assessed the risk of doing better and decided it isn’t worth it.
Your creatives are smart. They will only be as brave as you let them be.
Three Things That Actually Change the Culture
These aren’t theoretical. They’re things I’ve run in my own team.
1. Ban the Safe Option
At the start of a project, ask the room: “What is the most boring idea we could make?”
Write it down, put it on the wall, and ban it.
Then tell your team they have to do better than that. The boring idea is now the floor, not the default. This does two things. First, it makes the safe option visible, which defuses its power. Most safe ideas get chosen by default because they never get named. Once you name it, it feels embarrassing. Second, it gives people explicit permission to go further. You’ve told them the safe road is closed. Now they have to find another one.
It’s a simple exercise and it consistently works.
2. Protect the Weird Idea
When a creative brings you something that makes you uncomfortable, there’s a reflex to immediately start critiquing it. To poke holes. To identify the problems. To manage the client expectation in your head before you’ve even given the idea room to breathe.
Try to resist that reflex.
Instead, say this: “I will protect this. You make it great.”
Those seven words do something important. They tell the creative that the idea has a shield. That if they do the work to develop it, you’ll go to bat for it. They remove the uncertainty about whether the effort is worth it.
You’re not committing to taking it to the client unchanged. You’re committing to not killing it before it gets a real shot. That’s all it takes. Give the weird idea a protected space to develop before anyone starts shooting at it.
3. Celebrate the Crash
When something risky fails, what you do next matters more than anything else.
If you go quiet, move on quickly, and never mention it again, the team draws one conclusion: failure is shameful. Don’t risk it.
If you debrief it like a crime scene, forensically examining every decision that led to the bad outcome, you’re teaching a different lesson: failure is a problem to be analyzed and prevented. Which means: avoid the situations that could lead to it.
Neither of those is what you want.
What you want is to talk about it openly, acknowledge what went wrong technically, and then clearly separate the quality of the attempt from the quality of the result. These are two different things and your team needs to see you treat them that way.
“That didn’t land with the client and here’s why. But I want to be clear: the fact that someone brought that idea into the room is exactly what I want from this team. The guts it took to pitch that? That’s the job. We’ll get better at the execution.”
That’s the message. Say it out loud. Repeat it. Your team is listening.
What a Good Crash Debrief Actually Looks Like
Most post-mortems on failed creative work are just autopsies. Everyone gathers around the body and tries to figure out what killed it. The intent is learning, but the effect is usually discouragement. The focus on what went wrong can feel like blame, even when it isn’t meant that way.
A good crash debrief does something different. It separates the three threads that get tangled together when creative work fails: the execution, the idea, and the attempt.
The execution is the part that can be critiqued honestly. What was the work missing technically? What would have made it land better? This is productive. This is craft.
The idea is more complicated. Sometimes bold ideas fail because they were genuinely wrong for the brief. Sometimes they fail because the execution didn’t serve them. Sometimes they fail because the client wasn’t ready for them. These are different problems and they need to be named clearly, because your creatives need to understand the difference between “this concept didn’t fit” and “bold concepts don’t fit here.”
The attempt is the thing you need to protect at all costs. The decision to bring something risky into the room. The willingness to be wrong in front of people. The fact that someone cared enough to try something hard instead of defaulting to something easy.
That last part never gets critiqued. It gets praised. Every time.
When you run a debrief this way, a few things happen. The team processes the failure without shame attaching to the person who took the risk. They walk away with clear technical learning. And they leave knowing that the next time they want to take a swing, there’s still a place for that in this team.
One more thing on this: involve the person who pitched the failed idea in the debrief. Don’t do it without them. If you process the failure in their absence, they’re left to fill in the blanks themselves, and what they’ll imagine is always worse than what was actually said. Bring them in. Show them the debrief is a conversation, not a verdict.
Stop Asking for Perfection. Start Asking for Trouble.
The creative teams that produce the most interesting work aren’t the ones with the highest batting averages. They’re the ones with the most at-bats.
They pitch more. They fail more. They try more weird things and bring more ideas into the room that have no business being there. And out of that volume and variety, occasionally something extraordinary appears that would never have existed in a culture where people only bring their safest, most polished, most defensible concepts.
Your job as a creative leader is not to protect the team from failure. It’s to make failure survivable. To build the conditions where someone can try something hard, crash, and come back to try again.
Ban the safe option, protect the weird idea, and celebrate the crash.
This Is What Thriveful Is Built For
The reason I’m so focused on this principle is because it’s the same problem that kills creative growth outside of work too.
Most feedback communities are validation loops. You post work, people say nice things, you feel good about yourself, and you’re no more skilled than you were before. The environment is comfortable. The feedback is safe. Nothing is at risk.
That’s not growth. That’s maintenance.
Thriveful is built on the opposite principle. You grow through honest critique and real risk, not validation. The community is structured to give you the kind of feedback that actually changes your work, delivered in a way that isn’t demoralizing. The same balance I’m describing for your team at work applies here: the environment needs to make failure survivable, not invisible.
If you’re a designer who wants to actually get better, the skill you need to build is the same one I’m asking creative leaders to build in their teams: the ability to swing and miss without shutting down. To hear hard feedback and stay open long enough to use it. To value the attempt as much as the result.
That’s what we’re building at Thriveful. Come take a swing.
-K
Thriveful is a gamified design feedback community for designers who want to grow through real critique. Join us at thriveful.xyz.
