Ask whether strategic planning should run top-down or bottom-up and you will get a confident answer either way, usually shaped by whichever one burned the person last. Both answers are half right, which is the problem. The two approaches fail in opposite directions, and knowing how each fails is more useful than picking the winner.
What top-down gets right and wrong
Top-down planning starts with leadership setting the direction and cascading it to the teams. Its strength is coherence and speed. A small group that can see the whole board sets a clear strategy in a focused block of time, and there is no question about what the company is trying to do.
Its failure is distance from the ground. A plan set at altitude tends to assume capacity that does not exist, timelines that ignore dependencies, and a readiness that looks real from the top and evaporates two levels down. Teams receive the cascade, recognize that parts of it are undeliverable as written, and quietly do what they always did while nodding along. The plan is coherent and the execution is theater, because nobody at the top knew what the plan would cost on the ground.
What bottom-up gets right and wrong
Bottom-up planning inverts it. Each team proposes what it can realistically take on, and the company plan is assembled from those proposals. Its strength is grounding. The plan reflects actual capacity, real constraints, and the knowledge that only exists close to the work, so what gets committed is deliverable.
Its failure is the absence of strategy. A plan summed from team-level proposals is a portfolio of locally sensible bets that, taken together, point in no particular direction. Every team is busy and defensible, and the company is not actually going anywhere, because no one made the subtractive choices that direction requires. Bottom-up planning is very good at producing a plan nobody can argue with and nobody can rally behind.
Reconciliation is the real method
The companies that plan well do not choose. They run a top-down pass and a bottom-up pass and treat the gap between them as the actual work of planning. Leadership sets the direction and the few objectives. Teams respond with what delivering those objectives would genuinely take, and where it collides with capacity. Then the two are reconciled, which usually means leadership cuts the ambition or reallocates capacity, and teams adjust what they had planned to do anyway.
This is sometimes called counter-planning, and the name is apt, because the value is in the collision. The top-down pass alone assumes too much. The bottom-up pass alone commits to too little. The reconciliation is where a plan becomes both directional and deliverable, which neither pass produces on its own.
The mechanics of that middle step are the hard part, and they are mostly about making team goals legible against company objectives. When a team's proposed work can be read directly against the objective it is meant to serve, the gap is visible and the reconciliation is a conversation about evidence. When it cannot, reconciliation collapses into negotiation by assertion. Connecting team goals to company strategy is the groundwork that makes the two passes meet.
Keeping the two aligned after the plan is set
Reconciliation at planning time is not a one-off. The top-down direction and the bottom-up reality drift apart again the moment execution starts, because teams adapt to events leadership cannot see and leadership adjusts the strategy to events teams cannot see. A plan reconciled in January is unreconciled by March unless something keeps watching the seam.
This is where the plan needs to stay live rather than static. Vindaris maps the top-down objectives down through the bottom-up goals and tasks, reads the work activity underneath, and flags where a team's execution has drifted from the direction above it. The reconciliation becomes continuous instead of annual, so misalignment surfaces as a signal rather than as a surprise at the next offsite. That is the role of strategic planning software that tracks execution: holding the two passes together after the planning meeting ends. The full cadence sits inside the strategic planning process.
FAQ
Is top-down or bottom-up planning better for a startup? Early on, planning leans top-down by necessity, because a founder holds the whole strategy and the team is small enough to stay close to it. The bottom-up pass matters more as the company grows and leadership loses direct sight of what delivery actually costs, which is usually around the point a second management layer appears.
How do you stop bottom-up planning from becoming a wish list? Hold the top-down direction firm while the bottom-up pass runs. Teams propose against the objectives, not in a vacuum, and anything that serves no objective has to justify itself or stop. The direction is the constraint that keeps the sum from drifting into a portfolio of unrelated bets.
Who owns the reconciliation? Leadership owns the final call, because cutting ambition or moving capacity is their decision, but the reconciliation itself works best as a shared, evidence-based conversation rather than a top-down override. When it becomes a pure override, you are back to top-down planning with extra steps.