StrategyBlocks outlines 90‑day review

Strategy reviews are supposed to keep a company pointed in the right direction. But in a lot of teams, the quarterly review has turned into a status meeting with nicer slides. That is the gap these posts are trying to close. StrategyBlocks pushed the idea that a 90-day review should be a decision point, not a reporting ritual, while Balanced Scorecard Institute and Eric B. Lint filled in the operating logic around it. (strategyblocks.com) ### What changed here? The actual news is not a product launch or earnings print. It is a sharper operating argument. StrategyBlocks published a fresh piece on how to run a 90-day strategy review that “drives decisions,” basically saying the meeting should force choices about priorities, resources, and direction instead of just explaining what already happened. (strategybl([strategyblocks.com)es 90 days matter? Ninety days is short enough to react and long enough to see whether a strategic bet is working. Annual planning is too slow for that. Weekly check-ins are too tactical. The quarterly window is the middle layer where leaders can test assumptions, spot drift, and still change course before a bad plan hardens into the default. That is why the review format matters so much. (strategyblocks.com) ### What is the mistake these reviews usually make? Most strategy reviews collapse into reporting. Teams bring KPI updates. Everyone explains variance. Nobody wants to reopen the plan itself. The meeting becomes a backward-looking accountability exercise rather than a forward-looking choice. StrategyBlocks’ point is simple but useful — if the review does not end with a decision, it probably was not a strategy review at all. (strategyblocks.com) ### What capabilities make that work? Balanced Scorecard Institute lays out seven capabilities that make a review cycle real: process discipline, engaged leadership, cross-functional collaboration, strategic alignment, performance analysis, use of technology, and change management. That list matters because it shifts the problem away from “we need better meetings” toward “we need a system that can support better decisions.” A weak review is usually a symptom, not the disease. (balancedscorecard.org) ### Why bring leadership structure into this? Because decision quality is only half the problem. Decision flow is the other half. Eric B. Lint’s recent writing keeps coming back to the same idea: execution slows when decisions stop moving through structure and start depending on ad hoc leadership intervention. In plain English, if every hard call has to be escalated, the organization looks busy but moves late. (ericblint.substack.com) ### So what does “decision friction” look like? It looks like unresolved tradeoffs, duplicated approvals, and teams waiting for clarity that never quite arrives. A quarterly review can expose that friction fast. If the same issues keep appearing every 90 days, the problem is not just execution. The problem is that ownership, authority, or escalation paths are fuzzy. That is where Lint’s structural lens and the Balanced Scorecard checklist fit together. (balancedscorecard.org) ### Why does this land with engineering leaders? Because engineering organizations feel this failure mode early. They already run on sprint cadences, roadmap checkpoints, and delivery metrics. The trap is assuming that because execution is measured tightly, strategy is being reviewed tightly too. But measurement cadence is not decision cadence. A team can ship every (balancedscorecard.org)eview argument. (strategyblocks.com) ### What is the bottom line? The useful takeaway is not “have more reviews.” It is “design the quarterly review so a real choice has to happen.” StrategyBlocks supplied the meeting logic. Balanced Scorecard Institute supplied the capability checklist. Lint supplied the warning that without structure, leadership becomes a bottleneck. Put together, that is a practical playbook for teams that want strategy to be something they steer, not just something they report on. (strategyblocks.com)