The First 15 Seconds
I want you to think about a specific situation…
Someone on your team shows up to a meeting with something you didn’t ask for. It’s good. Maybe better than an idea you’re currently building. And you have about 15 seconds to decide what happens next. Not just for this idea. For this person’s willingness to bring you the next one.
Most managers blow it. Not because they’re bad at their jobs. Because they’re trying to do two things at once.
The moment someone presents an unsolicited idea, two separate calculations happen in a manager’s head simultaneously: is this idea good, and can we actually use it? Those are different questions. But they almost always get answered at the same time, out loud, in the same breath.
This happened to me.
A team member shows up with a redesigned UX that is genuinely better than what’s already been built. I can clearly see it, know it, but I immediately start explaining why it wouldn’t work due to all the red tape. The idea gets constrained before it gets acknowledged. The person walks away not quite sure whether their work was good or just inconvenient.
The problem is not the redirect. The redirect was probably right. The problem is sequencing.
When ideas get constrained before they get acknowledged, people learn something. They learn that bringing unsolicited thinking is risky. Not because they’ll be punished, but because they’ll be ignored in the specific way that hurts most: their work will be evaluated for its utility before it’s recognized for its quality.
That’s how you get a team that stops pressure-testing things. Stops reaching. Stops showing up to meetings with something you didn’t ask for. The creativity doesn’t disappear. It gets redirected somewhere safer, which usually means somewhere less useful to you.
This keeps happening because the redirect feels like the urgent task. The timeline is real, the investment in the current version is real, and a manager’s job is to keep things moving. Acknowledging the idea first feels like slowing down, or worse, like raising someone’s hopes before letting them down. So managers skip straight to the decision. It feels efficient. It usually isn’t.
The fix is not complicated, but it requires discipline in the moment. Name the win before you state the reality. Not as a softener. As a true statement that happens to come first.
“This is really strong work. The UX you’re showing is genuinely better in some important ways. And given where we are, with the investment already made and the timeline we’re on, we’re going forward with the current version.”
Both things are true. Say them in that order.
Then do one more thing: create a visible parking spot for the idea. “Let’s capture what we’d steal from this if we were starting from scratch.” That sentence turns disappointment into contribution. The idea doesn’t disappear into the void. It becomes input. Close by naming the behavior you want more of. “Keep building and pressure-testing like this. Even when we can’t act on it immediately, it makes the work better.” That tells them: this wasn’t a mistake. This was leadership behavior.
Think about the last time someone on your team brought you something you couldn’t use. Did they know their idea was good before you told them why it wouldn’t work? If you’re not sure, you probably went in the wrong order.