How to say you changed your mind as a leader

Say the new decision first, then say what new information caused it. A reversal with a reason attached reads as judgement. A reversal with no reason attached reads as weather.

People at the top of a team change their minds constantly and announce it badly, which is why changing your mind has a worse reputation than it deserves.

Open with what is true now

Open with what is true now, in one sentence, before any account of how you got there.

"We are keeping the current review process." Then the reason. Then, if it is needed at all, the acknowledgement that this is a change.

The instinct runs the other way. You want to walk people through the thinking so the change looks earned, and by the time the actual decision arrives in paragraph three, half the readers have built a theory about what is coming and are reading to confirm it.

A team reading a reversal wants to know what to do on Monday. Give them that in line one and they will read your reasoning in a much better mood.

Name what changed, and make it external if it truly is

The reason has to be a fact that arrived after the first decision, and it has to be specific enough to check.

"Two of the three teams told us the migration window does not work for them" is a reason. "On reflection, we felt this was the better path" is a mood, and a team can tell the difference instantly.

What makes a reversal look unsteady is never the reversal. It is a reason that could equally have been true a month ago, because that tells everyone the first decision was made without thinking, and by extension so was this one.

So look hard for the new input before you write. If there genuinely is not one, say that instead: "Nothing new came in. I got this wrong the first time." That is a stronger message than a manufactured reason, and it will survive contact with people who were in the original meeting.

Do not apologize twice, or at all if nothing broke

Apologize only for the cost the change imposed, and only once.

If people did three weeks of work that is now discarded, name that and name it plainly: "This wastes the last three weeks on the importer, which is on me." One sentence, specific, no repeat later in the message.

If nothing was lost, skip it. A reversal that arrives wrapped in apology teaches a team that changing course is shameful, and the next person who should change course will hold on longer to avoid the same performance.

There is a version of this that is worse than either: apologizing while making it clear you were pushed. "Sorry for the churn, but the feedback was very clear" hands the decision to a crowd and keeps the guilt for yourself, which is the least useful possible split.

Say what stays put

Tell people explicitly which parts of the plan are unchanged, because a reversal makes everything look negotiable.

This is the step almost everyone skips, and it is where the real damage happens. You changed one decision. Your team now quietly wonders whether the date moved, whether the priority moved, whether the thing they are building this week is still wanted.

Two lines fix it:

• What is changing, stated once, with the date it takes effect.
• What is not changing, listed plainly even where it feels obvious.

The second list is the one that stops the corridor conversations. Obvious to you is not obvious to somebody who just learned that decisions here can move.

Handle the people who argued for this all along

Give credit by name, in the same message, and do not make it a whole paragraph.

Somebody said this in the original discussion and was overruled. They know it. Everyone who was in the room knows it. A message that arrives at their position without mentioning them reads as quietly taking their idea, and that memory lasts a long time.

One clause is enough. "This is what the design team argued for in the first review, and they were right." Then move on to the logistics. Making more of it turns their win into a scene, which most people find worse than being overlooked.

Reversals are cheap, patterns are not

One reversal with a clear reason costs a leader almost nothing. What costs is a series of them with no visible logic between them.

People are extremely good at reading the shape of a sequence. Three changes in a quarter, each with a real external cause, reads as responsiveness. Three changes in a quarter that all happened to follow the last loud conversation reads as a leader who agrees with whoever spoke most recently.

So the honest question before writing is not whether this reversal is defensible. It is what the last three look like in a row.

I rebuilt Unvent's landing page once, looked at it for a day, and put the old one back. That reversal cost nothing. What I nearly did was reach for the same fix again a few weeks later, for the same vague reason, which would have turned one decision into a habit of redoing the front page whenever I got bored of looking at it. Responsiveness and drift feel identical from the inside. The sequence is the only place they look different.

The message people remember

What a team takes from a reversal is not the decision. It is whether their leader can say a true thing about their own reasoning without flinching.

That is why the manufactured reason costs so much and the plain admission costs so little. Everyone has worked for somebody who could never be wrong, and nobody enjoyed the guessing that came with it.

Write the short version, put the new decision at the top, and let the reason be exactly as impressive as it actually is. Getting an honest sentence out in a steady tone is most of leadership writing, and it is a skill rather than a temperament, which is the whole premise behind Unvent.