Shipping when the roadmap is foggy

Most of the teams we work with don't lack ambition — they lack a stable picture of what the next two quarters look like. Priorities shift, a new exec joins, a customer escalates, and suddenly the plan you sweated over in January is wallpaper.

The instinct is to plan harder. We've found the opposite is more useful: plan less, but make the planning you do unambiguous. Three habits do most of the work.

Pick the next outcome, not the next feature. A feature list is a wishlist with deadlines attached. An outcome — "checkout abandonment under 18%" — survives a re-org because everyone still knows what good looks like.

Decouple sequencing from estimation. A team that has agreed on the order of work can ship even when the dates are wrong. A team that has agreed on dates but not order will argue about both.

Run a weekly written check-in, not a weekly status meeting. Five sentences from each lead, posted by Friday, reveals drift faster than any standup.

None of this is new. What's hard is doing it when the org around you is doing the opposite.