There's a rule I keep coming back to. You don't tell a team their work is being automated until you have a real plan for what happens to them next.
No plan, no announcement.
Every time I say it out loud, someone pushes back. Usually a version of the same thing. "That's lovely in theory, Tracey. But we move fast. 90-day cycles. We can't sit around waiting for a perfect plan before we do anything."
Fair. I get it. Speed is the whole point right now.
But that objection misreads the rule, and the misreading is where good intentions turn into a mess. Because the rule was never "have every answer before you speak." It's "don't announce an outcome you can't stand behind."
Those are two very different things. And the gap between them is exactly where you either keep your people's trust or you don’t.
Communication isn't one thing
Here's the trap. We treat communication like a single event. The Big Announcement. The town hall. The email that goes out to everyone at 9am on a Tuesday.
But there are two different messages hiding in there, and we keep confusing them.
One is the outcome.
"Your role is changing." "This work is being automated." That message needs a plan behind it. Period. You don't get to open that door and then shrug when someone asks what's on the other side.
The other is the process.
How decisions get made. When people will know. Who owns the conversation about where they go next. That one you can share early. In fact you should, long before any outcome is settled.
Move fast on the work. Stay disciplined on the outcome message. Those two don't fight each other. Most leaders just never separate them.
What you can commit to on day one
So what do you actually say when you're moving quickly and you honestly don't have the answers yet? You commit to the things you can hold.
You commit to a process, not to individual outcomes. You tell people when they'll have clarity, and then you hit that date. You name a person who owns the conversation about where people go next, so it doesn't quietly become nobody's job. And you're honest about what you don't know. "We don't have the full picture yet, and here's when we will" is a real thing to say. It lands. People can work with that.
What they can't work with is confident vagueness. The cheerful non-answer. The leader who clearly knows something's coming but keeps smiling and saying it's all going to be great.
People smell that from a mile off. And the moment they smell it, you've lost them.
Silence is not the safe option
Here's the mistake I see most. A leader can't announce an outcome yet, so they say nothing at all. They think they're being careful. Responsible, even. Waiting until they've got it all worked out.
But silence isn't neutral. Not to the people waiting on the other end of it.
To them, every quiet week is a week they fill in themselves. And they don't fill it with the optimistic version. They fill it with the worst one. The rumor. The thing they overheard. The layoff they've been quietly dreading since the AI conversation started.
You think you're protecting them by waiting. You're actually leaving them alone with their worst assumptions.
The answer to "we're not ready to announce" is never "so we'll go quiet." It's "so we'll tell them the process." When they'll know. How it works. What support exists either way. You give people something solid to stand on, even when the outcome isn't solid yet.
Certainty about the process beats silence every single time.
Speed is a trust account
Now here's the part that turns this from a nice ethical point into a hard operational one. Because I'm not really making a moral argument. I'm making a speed argument.
The thing that lets you move fast next quarter is the trust you kept this quarter.
Surprise a team once. Announce something ugly with no plan, no warning, no path forward. Then watch what happens to your next initiative. People hedge. They resist. They wait for the other shoe to drop before they commit to anything. Every cycle after that one gets slower, because you spent the trust that made speed possible in the first place.
Do it well, though, and something quietly compounds in your favor. Plan first. Communicate the process. Keep your word on the dates. People notice. And the next time you need them to move fast, they will, because you've shown them what you do when it gets hard.
Fast and honest were never a trade-off. Honesty is the thing that keeps you fast.
So does the rule survive?
Yes. It survives just fine in a 90-day world. It's the thing that makes a 90-day world survivable for the people living inside it.
Move fast on the work. Never announce an outcome you can't stand behind. And when you're not ready to announce, don't disappear. Tell people the process.
None of this is a brake on speed. It's the thing that keeps you moving.
And look, I'm still working a lot of this out in real time, same as everyone. Nobody has AI change fully figured out, and anyone telling you they do is selling something. But this one I'm sure about. You can move fast. You just don't get to do it by blindsiding the people you're going to need next quarter.
Change management isn't the thing you bolt on when it gets uncomfortable. It's built into the work from the start. That's the whole job.