The 10 Questions Every CEO Should Ask Before Developing a Strategic Plan

questions before developing a strategic plan: turning ambition into strategic choices

questions before developing a strategic plan matters because organizations do not grow sustainably through activity alone. Leaders need a clear diagnosis, a defensible direction, explicit choices and an execution system. This guide helps CEOs, founders, executive teams and boards decide which questions must be resolved before a strategic-planning process begins in Kenya and relevant African markets.

Key takeaways

• Strategy is a connected set of choices about purpose, customers or beneficiaries, value, capabilities, priorities and resource allocation.
• A strategic plan must be grounded in evidence about the operating environment, stakeholders, performance, competitors and organizational capacity.
• Good planning makes trade-offs visible. A list containing every desirable activity is not a strategy.
• Execution requires owners, budgets, milestones, indicators, review routines and authority to resolve obstacles.
• Businesses, NGOs and public institutions need different success measures, but each requires a clear route from ambition to results.
• Plans should be reviewed when evidence or conditions change without allowing short-term pressure to erase long-term direction.

Why strategic planning matters

Organizations face more opportunities and demands than they can pursue. Without a disciplined process, priorities are set by the loudest stakeholder, the newest crisis or the easiest activity to fund. Teams become busy, but resources are fragmented and leaders cannot explain why one initiative should receive attention before another.

Strategic planning creates a structured conversation about current position, desired future, choices and the capabilities required to close the gap. It gives executives, staff, boards, partners and funders a shared frame for decisions. The most useful plans do not pretend the future is certain. They identify assumptions, scenarios, risks and the signals that should trigger a response.

In Kenya and across African markets, strategy should reflect specific customers, counties, countries, sectors and institutions. Africa is not one market. Demand, regulation, infrastructure, distribution, public policy, workforce conditions and stakeholder expectations vary. Evidence collected in Nairobi should not automatically be treated as representative of another county or country.

What strategy is—and what it is not

Strategy explains where an organization will focus, what value it will create, how it will succeed and what it will deliberately not pursue. A vision describes a desired future. A mission describes purpose. Goals express intended results. Projects are vehicles for delivery. Budgets allocate resources. These elements support strategy, but none is a substitute for strategic choice.

Ten questions for the CEO

1. Which decisions must this strategy resolve?
2. What evidence describes our current performance?
3. Whose needs define value?
4. Where will we compete or focus?
5. Which alternatives threaten relevance?
6. What advantage or capability can we sustain?
7. What will we stop doing?
8. Which assumptions create the greatest risk?
9. How will resources follow priorities?
10. How will leaders review and adapt execution?

These questions should guide research and workshops without predetermining answers.

A practical strategic-planning process

1. Confirm the mandate and decision

Agree who sponsors the process, who approves the final choices and how staff, customers, beneficiaries, partners or other stakeholders will participate. Define the planning horizon and the decisions the process must resolve. For an SME, the central issue may be which segment and offer can produce profitable growth. For an NGO, it may be which outcomes and delivery model best fit community needs, evidence and funding realities.

2. Diagnose the current position

Review performance, customers or beneficiaries, finances, people, operations, technology, partnerships and governance. Separate symptoms from causes. Falling revenue may reflect demand, positioning, price, distribution, retention or execution. Programme underperformance may relate to design, access, assumptions, delivery quality or context.

Use internal data alongside market research, stakeholder interviews, customer or beneficiary evidence and competitive intelligence. State data gaps rather than filling them with confident opinions.

3. Analyse the external environment

Identify market, economic, technological, social, policy, regulatory and environmental changes that could affect the organization. Map customers, competitors, substitutes, partners, funders, regulators and communities. Prioritize developments that change demand, cost, legitimacy, access or execution.

4. Develop strategic options

Create genuinely different routes, not small variations of one preferred answer. Options might change target segment, geography, value proposition, channel, partnership model, programme approach, capability investment or pace. Describe expected benefits, costs, dependencies, risks, evidence and reversibility.

5. Make and document choices

Assess options against mission fit, stakeholder value, evidence, feasibility, financial sustainability, risk and implementation capacity. Weighting should be agreed before final scores are known. Record why the selected route is stronger and why alternatives were not chosen. This decision record becomes valuable when conditions change.

6. Translate strategy into an execution roadmap

Convert priorities into outcomes, initiatives, milestones, owners, resources, indicators and dependencies. Sequence work so early initiatives build capability or test assumptions needed by later investments. Link the roadmap to budgets and individual or team accountability.

7. Establish review and adaptation

Create monthly operational reviews, quarterly strategic reviews and an annual refresh where appropriate. Operational meetings track delivery; strategic reviews test assumptions and outcomes. Do not change direction after every weak month, but do not protect a failing assumption merely because it appears in an approved document.

Evidence needed for strategic choices

Using SWOT without turning it into a list

SWOT can support synthesis when each item is evidence-based, material and relative to the decision. Strengths and weaknesses describe internal conditions. Opportunities and threats describe external conditions. Avoid vague statements such as “strong team” unless the relevant capability and evidence are defined.

The value comes from combining factors. A real strategic implication might use a verified distribution capability to enter an underserved segment, or address a digital-service weakness before a competitor changes customer expectations. Rank implications by value, feasibility, urgency and risk.

From priorities to measurable results

Each strategic priority should specify an outcome, not only an activity. “Conduct marketing” is activity; “increase qualified demand in the selected SME segment” is closer to an outcome. Define a small indicator set combining outcomes, drivers and delivery milestones. Too many indicators dilute attention.

Indicators need definitions, sources, frequency, baseline, target and an accountable owner. Targets should be ambitious but grounded in evidence and resources. For newer initiatives, use staged targets and learning milestones. Link this work to monitoring and evaluation where programmes need systematic evidence about implementation and outcomes.

Resource allocation and strategic discipline

A strategy becomes credible when resources move. Budgets, leadership time, recruitment, systems and partnerships should reflect the declared priorities. If every department keeps its previous activities and receives a new strategy label, the organization has not made a real choice.

Use portfolio review to stop, redesign, continue or scale initiatives. Consider strategic value, performance, future potential, risk and dependency. Stopping low-value work can be as important as approving new projects. Leaders should explain trade-offs so teams understand that focus is not neglect.

Common strategic-planning mistakes

• Copying a template: use frameworks to structure thinking, not to replace evidence and choice.
• Starting with projects: first define outcomes, customers or beneficiaries and strategic logic.
• Avoiding trade-offs: a plan with fifteen equal priorities provides little direction.
• Ignoring implementation capacity: assess skills, systems, governance, time and cash.
• Separating strategy from budget: resources must follow priorities.
• Measuring activity only: track whether activity changes the desired outcome.
• Publishing and forgetting: use a regular management review and adaptation cycle.

What this means for your organization

Begin with the decisions that leadership has postponed or repeatedly debated. Identify the evidence missing from those decisions. Agree a small number of strategic choices and translate each into ownership, resources and measurable outcomes. The plan should be clear enough that teams can use it when approving a project, partnership, hire or expenditure.

For businesses, this means connecting customer value, competitive position, growth economics and operational capability. For NGOs and development organizations, it means connecting needs, outcomes, delivery model, partnerships, evidence, funding and sustainability. For public institutions, it means connecting citizen value, mandate, policy, service delivery, transparency and accountable implementation.

How Walaco Africa can help

Walaco Africa can support organizational diagnosis, market and stakeholder research, strategy workshops, option assessment, strategic-plan development, implementation roadmaps and performance frameworks. The appropriate scope depends on the organization’s mandate, evidence gaps, leadership decisions and implementation capacity. Recommendations should remain practical, prioritized and transparent about assumptions.

Frequently asked questions

How long should a strategic plan cover?

The horizon depends on the sector and uncertainty. Three to five years is common, but the organization still needs annual planning and more frequent reviews. A longer horizon should not imply fixed assumptions.

Who should participate?

Leadership and the governing body need decision authority, while staff and relevant stakeholders contribute evidence and implementation knowledge. Participation should be designed, not treated as an unrestricted vote on every choice.

How many priorities should a plan include?

There is no universal number, but each priority must receive attention, resources and ownership. If the organization cannot explain trade-offs, the list is probably too broad.

What is the difference between strategy and an annual work plan?

Strategy sets direction and choices. The annual work plan specifies near-term activities, milestones, owners and budgets that advance those choices.

When should the strategy be reviewed?

Review implementation regularly and revisit assumptions when customer needs, funding, regulation, technology, competition or organizational capacity changes materially.

Strategy governance, communication and learning

Execution improves when decision rights are explicit. Define which choices belong to the board, executive team, programme or business-unit leaders and initiative owners. Escalation rules should help teams resolve cross-functional dependencies, budget conflicts and risks without waiting for an annual review. Governance should provide direction and accountability without creating unnecessary approval layers.

Communication must translate the strategy for different audiences. Staff need to understand priorities, their contribution and the trade-offs behind choices. Customers, beneficiaries, investors, partners or donors need a concise explanation relevant to their relationship with the organization. Avoid releasing a long document without a practical summary, roadmap and opportunity for questions.

Build learning into implementation. For each major assumption, specify what evidence will be collected, when it will be reviewed and which decision could change. Pilots should have success, redesign and stop criteria. Capture implementation lessons so teams do not repeat the same mistakes when scaling into a new county, customer segment, programme area or market.

Finally, maintain a strategy decision log. Record significant choices, supporting evidence, alternatives considered, responsible leaders and review dates. This provides institutional memory, helps new leaders understand the logic and makes adaptation more disciplined. Changing direction can be responsible when new evidence emerges; changing it without documenting why creates confusion and weakens accountability.

Next step

Prepare a concise strategy brief covering the decision, current performance, stakeholder expectations, market or programme context, constraints and evidence gaps. Use it to design a focused planning process rather than beginning with a generic template.

Sources and review note

• International Finance Corporation — private-sector development context
• United Nations Sustainable Development Goals

This article presents a decision framework and does not guarantee organizational growth, funding or investment. Recommendations should be tested against current evidence, sector obligations, available resources and the organization’s circumstances.