I’ve had quarters where priorities did a full spin every Monday. What’s helped me manage up is getting out of the “surprise me” loop. I pre-wire the two execs most likely to dissent using a one‑pager that lays out the tradeoffs in plain terms: impact this quarter versus next, resourcing shifts, and what slips if we say yes. After every decision meeting, I send a short write‑back with the call, the owner, the date we’ll revisit, and the sunset condition if data doesn’t show movement. I also anchor everything to their OKRs and board dates, so the conversation is about sequencing, not taste. When they want to “explore,” I timebox it and schedule a re‑baseline so we don’t churn forever. That’s kept me sane, but it’s not bulletproof. For those of you who’ve managed execs who flip the brief mid‑sprint, what exact phrases, artifacts, or rituals have actually stopped the thrash? Do you come in with options, a single recommendation, or a “not now”—and why?
execs don’t “change their minds weekly.” they never decided in the first place. you want less whiplash? trap the decision in writing. send a recap that starts with “as you directed on 9/12…” and quote them. amazing how fast the U‑turns slow when their words are the breadcrumb trail. also, get one vp ally who hates surprise fire drills. cc them on the recap. suddenly, everyone remembers the tradeoffs. fancy frameworks are nice; receipts are better.
stop trying to win philosophy class. control the calendar. pre‑read goes out 24h earlier, decision meeting is 25 mins, you open with the call and cost of delay, and you force a trade. if they won’t pick, you pick the smallest viable and put a date on the next check‑in. executives respect momentum more than theory. oh, and quit promising “we’ll figure it out.” that’s a blank cheque for thrash. ship, measure, move.
i started using a 1‑page “decision memo” with 3 lines: what we’re doing, what we’re not, why now. execs actually read it. less back‑and‑forth, way fewer pivots. tiny thing, big diff.
quick tip: i open with, “we can do X by Q3 if we drop Y.” makes the tradeoff super clear. ppl stop adding more stuff once they see the slip.
i pre‑wire on slack with a short loom. 3 mins tops. fewer surprises in the meeting, and my vp comes in already leaning one way. helped a ton.
Two rituals have consistently reduced churn for me. First, a weekly “no‑surprises” note to executive stakeholders that summarizes what changed, what didn’t, and why, using one screen of text. Second, a standing “sequencing” conversation where we place new asks next to current commitments and explicitly decide what gets deferred. When a pivot request comes mid‑sprint, I reference the last signed decision and offer three outcomes: keep the commitment, timebox a spike and revisit, or swap in the new priority and move a dated item. Framing it as sequencing, not blocking, keeps the discussion constructive and anchored to outcomes.
You’ve got a solid playbook already! Keep leading with clarity, tradeoffs, and short recaps. Momentum plus transparency wins. You’ve got this—ask for one concrete decision per meeting and watch the thrash drop.
At a previous gig, the CFO kept parachuting in with “one more thing.” I started framing responses as budget swaps: “happy to add it; which line should we move?” He’d pause, pick, and I’d capture it in a tiny decision note. After two cycles, he began pre‑checking with me before requests, because he knew it would require a visible trade. Not perfect, but the fly‑bys turned into real choices, and our roadmap stopped getting shredded.
Treat this as a decision hygiene problem. Use a one-page memo that states the decision, options, effort ranges, expected ROI proxies, and the cost of delay in days. Start the review by confirming who the decision owner is and the revisit condition. In my last two orgs, most reversals traced back to unclear ownership and missing revisit triggers, not bad choices. Track reversals and their causes; when you show reduction in throughput variance after adopting pre-reads and decision logs, executives will stick with the process because it demonstrably saves time.