Everyone Knew It Didn't Fit. We Shipped It Anyway.

The launch went out on time. It demoed beautifully. Six weeks later, almost nobody was using it. The strangest part wasn't the silence in the metrics, it was the silence that came before it: half the room had a quiet feeling the thing wasn't what users actually wanted, and not one of us said so out loud. We didn't ship something broken. We shipped something nobody asked for, exactly on schedule.

That failure has a name, and the name isn't bad luck. Go Fever is the collective excitement to hit a goal that quietly overrides every signal telling you to stop — a phrase engineers first reached for in the wreckage of an aerospace program, then watched repeat itself for decades. Its partner is groupthink, the term Irving Janis gave in 1972 to a group trading accuracy for harmony, swallowing the doubt that would break the consensus. Go Fever is the momentum to ship. Groupthink is the silence that lets a team mistake its own enthusiasm for the user's.

Inside a product organization, the two together rarely produce an outage. They produce something quieter and far more expensive: the feature the team fell in love with, the redesign everyone knew users wanted, the roadmap bet defended long past the evidence. All of it shipped on time, to a shrug.

The crater you can't see

Software's Go Fever leaves no mark you can point to. No fireball, no inquiry, no front page. There's just adoption that never crosses the line you drew, retention that dips and gets blamed on seasonality, a support queue filling with confusion that you decide is an onboarding problem rather than a fit problem. None of it lands on launch day, so none of it gets traced back to the afternoon the team stopped asking whether the thing fit and started asking only when it would ship.

Aerospace was forced to reckon with Go Fever because its failures were undeniable. Product teams get to keep it, because their failures are deniable — diffuse, delayed, and easy to re-attribute. So the team reorganizes, picks a fresh bet, and runs the same play with new faces. The disease that forces a reckoning in every industry where the stakes are visible gets to quietly become a culture in ours.

The tell isn't the data. It's the silence.

You won't catch this in a dashboard. You catch it in the room. Janis's symptoms map almost perfectly onto a launch review. There's the illusion of unanimity, where nobody objects so everybody assumes everybody agrees. There are the self-appointed mindguards, the lead who quietly handles the skeptical designer before the meeting so the room stays smooth. There's direct pressure, usually delivered as a joke: you're not seriously going to be the one to push the date? And there's self-censorship — the product manager who has seen the research, suspects it doesn't fit, and decides the doubt isn't worth the political cost of saying so. None of it looks like dysfunction in the moment. It looks like a team getting along. Strip away the politeness and the signs are specific:

• The date was set before anyone validated that users want the thing.
• "Users will get it once they're in" is doing an enormous amount of work.
• The only research that survives the meeting is the research that agrees with the plan.
• The loudest case for shipping is excitement, not evidence.
• Someone says "we're too far in to change course now," and it ends the conversation.
• The real doubts are frequent and specific — and only ever spoken in DMs.

Normalization of deviance, product edition

Underneath Go Fever sits a deeper mechanic with the least catchy and most useful name of the three: normalization of deviance, coined by the sociologist Diane Vaughan. A warning sign appears. Nothing visibly breaks. So the warning sign gets quietly reclassified from problem to normal, and the next one has a lower bar to clear. Each acceptance moves the line a little further.

Product teams run this exact loop on fit signals. The usability test where three of five users got lost becomes "small sample." The beta cohort that didn't come back becomes "wrong audience." The activation metric that looked ugly becomes the metric you quietly stop putting on the dashboard. No single dismissal is irrational, and none of them kills the launch on its own. Together, they are the runway Go Fever needs. By the time you reach ship day, you've spent weeks rehearsing how to ignore the exact signals that were trying to tell you the thing doesn't fit.

Make "this doesn't fit" cheap to say

This is a culture problem, which means you can't fix it with a poster that says speak up. Smart, committed, courageous people stayed silent in every case study you've ever read, because in the moment, silence was cheaper than speaking. The only durable fix is to change the price. You make dissent structural, so that saying this doesn't fit the user becomes an ordinary move anyone can make without spending a reserve of personal courage they may not have on a given day. A few things that actually work:

• Give dissent a seat. Name a person whose explicit job in the review is to argue that users don't want this. Doubt that is assigned isn't disloyalty; it's a role, and a role can't be punished for doing its job.
• Run a pre-mortem. Before you commit, have the team write the story of the launch that flopped and explain why users shrugged. It launders private unease into shared evidence, on the record, before the momentum starts.
• Separate the decider from the champion. The person who can say stop should not be the same person who is in love with the idea and whose name is on the date.
• Tie the launch to a fit signal, not a date. Decide in advance, while everyone is calm, what evidence would prove users want this and what result would mean you pull it. A date defended past the evidence is just Go Fever with a calendar.
• Protect the user who didn't get it. The outlier in the test is the cheapest warning you will ever receive. Make it expensive to wave away and cheap to take seriously, not the other way around.

Notice what every one of these does. It turns "no, this isn't right for the user" from an act of individual bravery into a normal step in how the team decides. That is the whole game, and it's the opposite of becoming the Department of No. The goal isn't a team that says no more often. It's a team where the truth about the user is cheap to say out loud, in the room, while there's still time to act on it.

A delay is better than a launch nobody wanted

Safety cultures have a line they repeat until it's reflex: a delay is better than a catastrophe. The product translation is less dramatic and just as true — a delay is better than a quarter spent shipping the wrong thing beautifully. The reason it's so hard to act on is a trick of perspective. The wasted quarter is abstract and lives in the future, while the delay is concrete and sits right in front of you, in a room that is already excited and has already promised the board a date.

Your culture isn't the values on the wall. It's what happens in the thirty seconds after someone says I don't think users want this. If that sentence is cheap to say and gets taken seriously, Go Fever never builds up enough speed to matter. If it's expensive, no amount of process will save you, because the process will be run by people who have already learned to stay quiet. Leadership's real job here was never to have the best instinct in the room. It's to make sure the room can hear its own doubts before the user has to deliver them for free.

The strongest product cultures I've worked inside weren't the ones with the best ideas. They were the ones where it was safe, and cheap, and slightly boring to say the idea didn't fit, before it shipped. If you're trying to build a culture like that and you can feel how much harder it is than buying a tool, let's talk →