And Why Big Change Quietly Stalls

Stylized cartoon portrait of a posed couple in coordinated teal outfits, the man in a black top hat holding a small Cavalier King Charles Spaniel puppy, the woman with elaborate pink upswept hair, both looking forward.

Posed, polished, and quietly not looking at each other. The honeymoon phase of any major change

Most transformations launch with momentum. So do most integrations. So do most change initiatives.

Then somewhere around 90 days in, the energy goes quiet. The dashboard still flags green on most lines. The strategy has not changed. The leadership team has not lost the room. But the thing that was moving is suddenly not. And nobody can quite tell you when it stopped or why.

It has a name. Call it the honeymoon tax. The cost you pay when an entire team is being polite while they figure out who they can be honest with.

What the Honeymoon Looks Like

The first weeks of any major change are loud on the surface and quiet underneath.

People show up. They go to the meetings. They nod at the new strategy or the new operating model or the new combined company. They take notes. They smile in the kickoffs.

What they are not doing is flagging the things they notice. The handoff that feels off. The decision authority that does not quite track. The way a colleague from the other side of the org chart answers a question. The phrase the new leader keeps using that means something different than they think it does.

None of this is anyone's fault. It is the same dynamic in every transformation, every integration, every change initiative that started with a Day 1. People keep their heads down while they read the new system. They wait to see who is safe to talk to. They wait to see what is actually allowed to be said out loud.

Integration leaders feel this most acutely because the stakes are explicit and the timeline is short. But the same pattern runs through any major change. You launched a new strategy and the directors got quieter. You restructured into a new operating model and the senior managers stopped pushing back. You merged two functions and the joint town halls feel oddly smooth. That is the honeymoon. It is also the tax.

Why People Go Quiet

Three forces are running in parallel. Each one is well-documented. None of them is about your team being timid.

The MUM effect. People withhold bad news from people with more power, especially in new relationships. Decades of research support this. It is not a personality trait. It is what humans do when the cost of being the messenger is unclear.

Social comparison. Festinger showed in the 1950s that people figure out what is normal by looking sideways. If nobody else is flagging the weirdness, the safest read is that you must be the one who is wrong. That is the mechanism that turns a room of people who all noticed the same thing into a room of people who all stayed quiet.

Sensemaking. Weick's work shows that groups construct a shared reality after a disruption. While that construction is happening, people do not yet know what counts as a signal versus what counts as noise. They hold their observations until they have a frame to put them in. That can take a quarter.

This is not dishonesty. People are not choosing to withhold. The system is making silence the smart bet.

The Math Underneath All of It

The mechanisms above explain what people are doing. The math explains why they keep doing it.

For an individual person, the cost of being the first to flag something is concrete. You can be labeled difficult, miscalibrated, or politically naive. You can damage a relationship you are still building. You can slow down a meeting that the senior person wants to keep moving.

The reward is diffuse. The org might benefit eventually. The project might land better. But the person who raised it usually does not get credit, and sometimes gets blamed when the issue surfaces in public.

So the rational calculation, for any individual in a new system, is to wait. Let someone else go first. See what happens to them. Recalibrate.

Multiplied across a team, that calculation becomes silence. Not because anyone is hiding anything. Because the math is doing exactly what math does.

The honeymoon is not a culture problem. It is the predictable output of a system where the cost of speaking up lands on the individual and the benefit lands on the organization.

Why 90 Days

The exact timing is not the point. The pattern is.

In most major changes, the first 90 days are about momentum. New systems get stood up. Org charts get redrawn. Quick wins get harvested. Status updates get circulated. The dashboard flags green because the visible work is moving and because nobody has yet decided to be the one to tell you it should not be.

By the time you get past the first quarter, two things are true at once. The buried signal has had time to accumulate. And the cost of bringing it up has gone up, not down. Because now the leader has visibly committed. Now there is a public narrative. Now the polite version of "this isn't working" sounds disloyal.

So the quiet keeps going. The drift starts. The milestones that depended on smooth collaboration start slipping. And the explanation, when it finally comes, is execution. The strategy was sound. The plan was right. People just did not deliver.

The truth is usually quieter. The information that would have let you adjust was sitting in people's heads at week six. It never made it to a room where it could matter.

The Cost

The honeymoon tax shows up as stalled progress. Transformations that do not transform. Integrations that do not integrate. Change initiatives that report green and produce nothing.

Most leaders read this as a culture problem or a trust problem. It is neither. It is a systems problem. Your people are doing the rational thing in a system that rewards silence. If you want different behavior, you change the conditions, not the people.

Build trust. Encourage candor. Lead by example. All of it is true and none of it is sufficient. The honeymoon tax does not get paid down by exhortation. It gets paid down by structure.

What Actually Pays the Tax Down

Two moves matter early.

Stop treating quiet as alignment. A smooth status update from teams that just got reorganized, merged, or asked to operate under new rules is not data. It is etiquette. The questions you would ask a friend over coffee are not the questions on the status template. Start asking them anyway. What is one thing you have noticed in the last six weeks that you have not figured out how to bring up yet? That question, asked in the right format, will tell you more than the dashboard.

Change the math. People speak up when the cost of doing so drops below the cost of staying quiet. That happens when the system makes surfacing observations the default, not the brave move. Not a survey. Surveys are too anonymous and too late. Something interactive. Something that gives the room a way to put what is in their heads on the table without any one person being the messenger.

The goal is not to make people braver. The goal is to make speaking up the obvious move, and to do it while the cost of adjusting is still low.

The Quiet Part

The honeymoon tax is not avoidable. It is a feature of how humans handle new systems, not a failure of any one team. The choice you have is whether to pay it up front, on purpose, with a process built to surface what is buried, or pay it later, in stalled progress and missed milestones and the slow loss of the momentum you started with.

Most leaders pay it later. The reason is that at 30 days, nothing visibly demands their attention. At 60 days, the dashboard still looks fine. At 90 days, you are already past the point where you could have caught it cheaply.

That is the moment. Not when things look broken. When things look fine.

If you lead a transformation, an integration, or any major change, the work to surface the buried signal happens early. That is what I do at IN8 Create. We help leaders get the honest read on what their teams already know, in a session, before the honeymoon tax compounds. Get in touch.

Related Posts

 
 
Next
Next

How to Write Team Working Agreements That Don't Become Posters