Two Ways Teams Decide What's Next

Every org I’ve worked in sits somewhere on one planning spectrum, and most people know which end they’re on before they can explain why.

One end runs on conversation. At a startup I was at - everyone in one office - a regulator changed the rules midweek. We parked the in-flight work, someone walked the room through the new constraint at standup, and by the time we broke we were pointed elsewhere. No doc to amend, no meeting to re-open a plan, because there wasn’t a formal plan to re-open. Priority lived in the room, and the room heard the news together.

What that end does well is respond. New information in, new direction out, same morning - and in payments, where a rule change or an outage can eat your week, that’s worth a lot. The shadow is visibility. Ask a new hire what the roadmap is six months out and you get a shrug, because it isn’t written down; it’s in a few senior heads. The important-but-not-urgent work - the migration, the reconciliation cleanup - never becomes this week’s fire, so it just doesn’t get done.

The other end runs on the quarter. At the mid-size company, planning is a scheduled event: objectives, key results, confidence scores, cascading company to org to team. Distributed across time zones, that document is how people who never share a room stay aligned.

We committed to launching country A, then country B - both needing local payment methods built from scratch, both written up as key results. Then A launched soft, traction well under plan. The honest move was to pause and rethink B. We kept building B - not from conviction, but because pausing mid-quarter and re-scoping across a remote org was more friction than continuing.

That’s the double edge. The same commitment that keeps a team from thrashing every Tuesday - the one that also protects the unglamorous work, the migrations and on-call cleanup that never win on their own - is the commitment that kept us building toward B after the numbers went quiet. The plan did what a plan does: it held, past the point its assumptions did.

Then there’s AI. The heaviest cost of the quarterly end was always the paperwork - the planning week, the status rollup from ten teams. Most of that is near-free now: draft the structure, summarize every KR, generate the mid-quarter writeup in minutes. Which is clarifying, because once the ceremony is cheap you can see what it bought - alignment, or a document. And faster cycles are stretching the quarter thin: when a six-week feature ships in one, a twelve-week plan is betting on a stale world. The country-B problem, made structural.

So the spectrum is getting squeezed from the middle. Cheap rollups give rolling teams OKR-level visibility with no planning week; short cycles push quarterly teams to re-plan far more than four times a year.

Which end you gravitate to usually isn’t about which is right. It’s about which mess you’d rather own: the plan that was never written down, or the plan that outlived its assumptions.