How to run a strategy review that leads to actual decisions

Most annual strategy sessions in Indian companies produce a presentation that gets filed and forgotten. The team spends two days in a hotel in Lonavala, the founder gets excited, ambitious targets are set, and by February everything is back to the same patterns. Here's why that happens and how to fix it.

The problem: strategy is treated as an event, not a system. A strategy review should produce 3–5 specific decisions, each with an owner, a deadline, and a budget. Not 15 priorities, not a vision statement, not a list of things to 'explore.' Actual decisions that change what you do on Monday.

Before the session: do the homework. Revenue by segment for the last 3 years. Win/loss analysis on deals. Client satisfaction data. Competitive landscape. Where growth actually came from vs. where you thought it came from. The strategy session should be spent discussing the analysis, not generating it.

The questions worth spending time on: Where have we actually grown and why? Where have we lost and why? What's changed in the market in the last 12 months that we're not yet responding to? What should we stop doing? What one thing, if we did it well, would have the biggest impact in the next 12 months?

Output format: a one-page strategy document. Where we're going (2–3 sentences), what's changed in how we're getting there, three to five specific decisions with owners and deadlines. Distribute it. Review it quarterly. Change it when the world changes.

TBC facilitates strategy sessions for growing companies — structured, evidence-based, and designed to produce decisions rather than slides. If your last strategy session didn't result in things changing, the process needs to change.