A strategy can be thoughtful and still leave a team with too many priorities. The planning problem is often the gap between an ambition and work that someone can own. A 90-day plan is one way to make that gap visible. It is a working tool, not a guarantee that complex change will be completed in three months.
Start with a decision, not a template.
Ask leadership which organisational outcomes matter most in the next period. Separate an outcome from an activity. “Run a workshop” describes something you do; “agree who can approve each type of operational decision” describes a change the organisation can use.
Choose priorities that fit the available people and resources. Make the trade-off explicit: what will not be pursued during this period? If everything remains a priority, the plan has not yet helped the team choose.
Write a one-page working plan.
For each priority, define the change you want to see, one accountable owner, the next milestone and evidence of progress. Record dependencies and decisions only leadership can resolve.
| Field | Question |
|---|---|
| Outcome | What should be different? |
| Owner | Who is accountable for moving it forward? |
| Evidence | What will show progress or completion? |
| Next milestone | What is the next concrete step? |
| Dependency | What needs another person, decision or resource? |
| Review point | When will the team reconsider the plan? |
Treat dependencies as part of the work.
An action may depend on budget approval, system access, another team’s time or a scope decision. Name the dependency early and identify who can resolve it. Avoid recording a blocked task as though the owner simply needs to work harder.
For an NGO, include internal decision-making and applicable donor or programme constraints in the discussion. For an SME, be equally explicit about cash, management time and operational commitments. Check the organisation’s actual rules rather than assuming a standard requirement.
Use reviews to make decisions.
Choose a review rhythm that fits the work. Focus on changes since the last review: what moved, what is blocked, what has been learned and what decision is needed. A discussion that only reports activity may miss the reason the plan exists.
- Keep the agreed outcome in view.
- Distinguish completed activity from evidence of change.
- Update assumptions when the situation changes.
- Stop or reshape work that no longer supports the priority.
Close the period deliberately.
At the end of the planning period, review results and unfinished work. Decide what should continue, change or stop. Capture what the team learned about its capacity and the dependencies it needs to manage better.
Do not simply copy every unfinished action into the next plan. Reassess whether it is still the best use of attention. The benefit is a clearer pattern of decisions, not a growing archive of tasks.
Explore Business Strategy consulting or our approach if your team needs a shared diagnosis before choosing priorities.