The change: Cadence is moving to async-first working — default to written updates and recorded decisions over live meetings — and folding three regional teams into two cross-functional pods (a small reorg). The real why-now: not the tidy version ("to empower flexible work"). The honest one: meeting load is drowning the depots, two leads are leaving, and the company can't keep scheduling six time zones into the same standup. What we will not do: pretend this is purely a gift to employees. For some groups it removes something they rely on, and the narrative says so before it says anything else.
"We're trading the meeting for the written record — so the work survives the time zone, and so two people leaving doesn't take the knowledge with them."
Every audience hears this same line first. Then each hears the part written for what they stand to lose — not one upbeat message pretending the loss isn't real.
Read of resistance: MODERATE overall — high in two groups, low in one. This is a reasoned read of likely resistance for Cadence's context, not measured sentiment.
| Audience | Resistance | What they actually fear (the specific loss) | The honest message that answers it |
|---|---|---|---|
| Engineers | High | That "written-first" means more process and a paper trail that reads like surveillance — every move logged and reviewable. | "This isn't a tracker. The written record replaces the status meeting, not your autonomy — and no manager gets a dashboard of your keystrokes. You lose the interrupt-driven day; you keep heads-down time you've been asking for." |
| Team managers | Moderate | Losing visibility and the sense of control that came from the live standup — not knowing what their team is doing without a meeting to see it. | "You're losing the standup as your window in — that's real. What you get is a written trail you can scan in five minutes instead of sitting through six. We'll coach the shift; you won't be flying blind, you'll be reading instead of watching." |
| Frontline / depot leads | High | Tech and a way of working they didn't ask for, imposed from a head office that doesn't run a depot floor. | "You didn't ask for this, and the rollout is built around that. Depots keep their live huddle where the floor needs it — async-first is for cross-team coordination, not for replacing how you run your shift. You tell us where written doesn't fit, and that's where it won't go." |
| Execs | Low | That adoption stalls — the tools roll out and people quietly keep meeting anyway, so nothing actually changes. | "The risk isn't resistance to the idea; it's a soft rollout that lets the old habit win. That's why the highest-resistance groups hear it first and in person, and why managers are coached, not just emailed." |
Each fear is a role-based inference, not survey data. The objection sits in the same row as the answer — that's the point. A narrative that can't state the worry isn't answering it.
"Heads up on the async shift: this kills standup, not your autonomy. No surveillance dashboard, no keystroke logging — the written record is so decisions survive when someone's offline. You get your mornings back. Push back in-thread if any of this lands wrong."
"You're losing your live window into the team, and we're not going to pretend that's nothing. Here's the new five-minute read that replaces the six meetings — and a two-week coaching loop so the handoff doesn't feel like flying blind."
"You didn't ask for this and you run the floor, so here's the line: your live huddle stays. Async-first is for the cross-depot coordination that's currently drowning everyone in calls. You map where it doesn't fit; we hold that line with you."
"The failure mode here is a quiet non-adoption, not loud resistance. The sequence front-loads the two high-resistance groups and coaches managers through the visibility loss. Watch adoption in the pods, not applause in the all-hands."
An AI asked to "write the rollout announcement" writes a press release: one upbeat message for everyone. This runs the opposite discipline: it asks what each group fears losing, and names it first.
| Ask AI for "the announcement" | This narrative |
|---|---|
| One upbeat message for everyone | Names what each group fears and answers it |
| Reframes every loss as an "opportunity" | States the loss plainly, before the upside |
| Assumes the whole org fears the same thing | Maps resistance group by group |
| Broadcasts once and hopes it lands | Sequences it — high-resistance groups first, in person |
| Reads like a press release nobody believes | Holds up read aloud to the most skeptical room |
Anyone can write the upbeat version. The product is naming what each group is afraid to lose — and answering it honestly.
Get the narrative spine, the resistance map, and a segmented message kit for your change in three business days. Pairs directly with the AI Onboarding Sprint when the change is adoption. Start your change narrative →