One of the most common things I hear in ideation meetings is “Oh, well, I’ve seen something like this before, and it didn’t work.”

There’s real value in that reflex and there’s a version that’s just a verdict in disguise. So how do you tell which one is which in the moment?

Two Versions of the Same Sentence

Real pattern recognition and cynicism say the same four words aloud: I’ve seen this before. What’s different is what happens inside your head after you say it.

Pattern recognition treats the sentence as a hypothesis. “This reminds me of a migration that stalled for a specific reason, so let me check whether that same reason applies here before I decide anything.” It’s falsifiable. You’re still looking at the case in front of you, and you’re prepared to be wrong about it.

Cynicism treats the sentence as a verdict. It’s still “I’ve seen this before,” but the thought that follows isn’t a question. There’s nothing left to check, because the outcome was settled the moment the sentence started.

A vendor pitch for “real-time” fraud scoring can trigger either version. Pattern recognition asks whether this vendor’s specific pipeline still has the batching delay that sank the last one. Cynicism says real-time vendors always overpromise and moves on to the next slide. Across a conference room table, both versions sound identical to your team and your peers: confident, a little world-weary, and unbothered by the enthusiasm in the room.

What I Check Now

The test I use on myself, most days and imperfectly, is simple: can I name the specific mechanism I expect to repeat, not just the memory that it didn’t work?

If I can name the specific dependency or the stakeholder who blocked it last time, that’s still pattern recognition doing its job. I can check whether that mechanism is present this time, and I might be wrong, which is the whole point. If all I have is the flat memory that something like this failed once, with no mechanism attached, then I’ve got battle wounds and experience, but I’ve likely started being cynical (and probably need another cup of coffee).

What It Does to the Room

Say the wrong version of “I’ve seen this before” often enough and pitches start getting shorter. You haven’t told anyone, explicitly, “no”, but they’ve learned the outcome gets decided in the first ten seconds, so they save their energy.

The research backs this up from both sides of the table. In the leader’s seat: people reject creative ideas most readily when they’re trying to reduce uncertainty, and the bias interferes with their ability to recognize a creative idea (Mueller, Melwani, and Goncalo, 2012). In the team’s seat: when people expect their ideas to be judged, they generate fewer of them, and self-censoring is where the loss happens (Diehl and Stroebe, 1987).

I’ve written about psychological safety before. Nobody’s afraid, in the traditional sense, to speak up. They’re accurately predicting that speaking up won’t change anything, based on watching the pattern enough times. The room doesn’t go silent. It starts bringing you things that already look like things you’ve approved.

I noticed this on my own team before I connected it to my own habit. New ideas were getting narrower and safer over time, and for a while, I assumed that was caution about the market. It took longer than it should have to consider that I might be the market condition.

It’s a different mechanism than the vague-criteria problem I wrote about in The Leader Who Knows What They Don’t Want, where a team narrows its pitches because it can’t tell what the leader is actually judging against. This one narrows for a simpler reason: the team has decided the verdict is already in before anyone opens their mouth.

The narrowing is a drift, which is what makes it easy to miss, and it responds to the same thing that causes it: what I do with the idea in the room.

Fixing It

I don’t think the fix is forcing myself to treat every new idea as if I have no history with it. That’s its own kind of dishonesty and throws away real information a newer person in the room doesn’t have yet.

If you’re the one in the leader’s seat, here’s what I’d try. Say the reasoning out loud instead of the verdict. “We tried that, and it failed because of this specific thing. Here’s why I think that’s still true, tell me if I’m wrong” invites correction. “We tried that, it won’t work” just ends the conversation.

I don’t always remember to do this. Some days the reflex wins and I catch it after the meeting, not during it, and have to go correct it.

Your job as a leader is to keep the conversation going long enough for people to learn from it. Left unattended, your experience will end it for you.