The diagnostic phase produces a large amount of evidence about performance, stakeholders, finances, capabilities, funders, peers, and the external environment. The next challenge is to convert that evidence into a focused set of strategic issues. Without disciplined synthesis, organizations often move directly from findings to preferred initiatives, missing the choices and tradeoffs that should guide the strategy.
12.1 Synthesizing Findings From the Diagnostic Phase
Synthesis is more than summarizing every analysis completed during the diagnostic phase. It requires identifying patterns, relationships, contradictions, and implications across multiple sources. A useful synthesis explains what the evidence means for future choices rather than repeating what each report found.
Start with the strategic questions: Return to the questions defined before kickoff. Organize findings according to the decisions the organization must make, such as where to focus, which programs to prioritize, how to strengthen revenue, or what capabilities to build. This prevents the synthesis from becoming a general description of the organization.
Separate facts from interpretations: A fact may be that participation in one program declined by 18 percent over three years. Possible interpretations include reduced need, stronger alternatives, access barriers, weak outreach, or declining service quality. The team should distinguish what is known from what remains uncertain.
Look across evidence sources: Program data, staff interviews, beneficiary feedback, financial trends, funder conversations, and peer analysis may point to the same issue from different directions. Convergence increases confidence. Contradictions should be examined rather than hidden.
Identify root causes: Repeated symptoms may arise from a shared underlying problem. Slow service, staff frustration, inconsistent data, and missed reporting deadlines may all reflect an operating model that has become too complex. Addressing each symptom separately may fail to solve the deeper issue.
Examine relationships among findings: Weak unrestricted funding may limit investment in systems, which increases administrative burden, which contributes to turnover, which reduces program consistency. Strategy should account for these linked effects instead of treating each problem as independent.
Assess materiality: Not every finding deserves strategic attention. Prioritize issues that materially affect mission impact, financial sustainability, organizational viability, stakeholder trust, or the feasibility of future priorities.
State the implication: Every major finding should answer the question, “What might this mean for strategy?” A trend is useful only when the organization understands which choice, assumption, or capability it affects.
A practical synthesis process can begin with individual workstream summaries. Each workstream should identify its five to seven most important findings, supporting evidence, confidence level, and possible implications. The core team can then compare these summaries, combine related findings, and eliminate duplication.
The team should avoid averaging away meaningful differences. Beneficiaries, staff, board members, and funders may hold different views because they experience the organization differently. The synthesis should identify where perspectives align, where they diverge, and why the difference matters.
Visual tools can support synthesis. A program portfolio, trend chart, stakeholder map, financial scenario, or system map may reveal relationships that are difficult to explain in prose. However, visuals should support judgment rather than replace it.
The final diagnostic synthesis should be concise. It may contain ten to fifteen major findings, grouped into a smaller number of implications. Leaders and the board should be able to understand what is working, what is changing, where the organization is exposed, and which decisions can no longer be postponed.
12.2 Distinguishing Operational Problems From Strategic Questions
Strategic planning processes often collect a long list of concerns. Some are strategic, while others are operational problems that should be resolved through management. Distinguishing between them protects the planning process from becoming an organizational improvement project covering every issue.
Operational problem: An operational problem concerns how current work is executed within an agreed direction. Examples include delayed reports, inconsistent meeting routines, poor scheduling, unclear forms, a specific vacancy, or a broken approval process. These issues may be important but usually do not require reconsidering the organization’s fundamental choices.
Strategic question: A strategic question concerns what the organization should do, whom it should serve, where it should focus, how it will create distinctive value, what capabilities it must build, or how it will sustain the work. The answer changes priorities, resource allocation, or the organization’s role.
A useful test is to ask whether solving the issue requires a choice among meaningfully different futures. “How do we shorten intake time?” is usually operational. “Should we continue operating a centralized intake model, shift intake to partners, or redesign eligibility?” is strategic because it changes the delivery model and distribution of responsibility.
Another test is the time horizon. Operational issues often concern immediate execution, while strategic questions usually shape several years. However, time alone is not decisive. A short-term funding loss can create a strategic question if it forces the organization to reconsider its portfolio or revenue model.
Use the following criteria:
- Mission impact: Would the answer change the outcomes pursued, the populations served, or the organization’s contribution?
- Resource significance: Would it materially alter budgets, staffing, facilities, technology, leadership attention, or funding requirements?
- Organizational breadth: Does the issue affect several programs or functions rather than one team?
- Irreversibility: Would the decision be difficult, costly, or disruptive to reverse?
- External positioning: Would it change relationships with beneficiaries, funders, partners, regulators, or peer organizations?
- Tradeoff: Does choosing one path require saying no to another credible path?
Some operational issues reveal a strategic pattern. High staff turnover in one unit may require a management response. High turnover across the organization, combined with compensation pressure, growth, and leadership overload, may raise a strategic question about scale, operating model, and workforce investment.
The project team should create an operational issues log for important concerns that fall outside strategy. Each item should have an owner, next action, and review date. This reassures participants that their concerns have not been ignored while keeping strategic discussions focused.
Leaders should also avoid misclassifying difficult strategic decisions as operational fixes. A weak program cannot always be repaired through better marketing, process improvement, or staff training. If need has changed, funding is unsustainable, or other providers create greater value, the organization may need to reconsider the program itself.
12.3 Framing the Choices the Organization Must Make
Once the strategic issues are identified, they should be framed as explicit choices. Strong framing makes the alternatives, criteria, and consequences visible. Weak framing produces broad aspirations that everyone can support but that provide little guidance for action.
Use neutral language: Do not frame the question so that one answer appears obviously correct. “How should we expand?” assumes expansion. A stronger question is, “Should we deepen our current footprint, expand to new communities, or pursue growth through partners?”
Define the decision boundary: State what is included and excluded. A portfolio question may cover three major programs but exclude a legally required service. Clear boundaries prevent the discussion from expanding indefinitely.
Describe credible alternatives: Strategic choice requires more than comparing a preferred option with an unrealistic alternative. Options should be genuinely plausible and sufficiently different to reveal meaningful tradeoffs.
Identify evaluation criteria: Agree in advance on how alternatives will be assessed. Criteria may include mission impact, equity, beneficiary need, evidence, feasibility, financial sustainability, distinctiveness, risk, capacity, and stakeholder support.
State the consequences: Explain what each choice would require and what the organization would stop, defer, or risk. Choices without consequences are usually aspirations rather than strategy.
Surface assumptions: Identify what must be true for each option to succeed. Expansion may depend on funding, leadership capacity, community trust, or a delivery partner. These assumptions should be tested rather than treated as facts.
Clarify timing: Some choices must be made now, while others can follow pilots or additional research. Framing should distinguish immediate commitments from options that remain open.
A well-framed strategic issue can be expressed in one or two sentences. For example: “Demand for the organization’s core service is growing outside its current region, but existing sites are operating inconsistently and unrestricted funding is limited. Should the organization prioritize strengthening current delivery, open new locations directly, or expand through licensed or partner-led models?”
The framing should include enough context to make the question understandable without embedding the answer. A short issue paper may present the evidence, urgency, options, criteria, uncertainties, and decision authority. This creates a common basis for leadership and board discussion.
Where disagreement is significant, the team should determine whether participants disagree about facts, values, assumptions, or risk tolerance. Different causes require different responses. Factual disagreement may require analysis. Value differences require governance judgment. Uncertain assumptions may justify scenarios or pilots.
12.4 Developing a Short List of Strategic Themes
Individual strategic issues should be grouped into a small number of themes that describe the major areas in which the organization must make choices. Themes help leadership see connections and prevent the final strategy from becoming a list of unrelated decisions.
Mission and impact: Questions about target populations, desired outcomes, theory of change, equity, advocacy, and the organization’s distinctive contribution.
Program portfolio and growth: Choices about strengthening, scaling, redesigning, partnering, transferring, or exiting programs, services, or geographies.
Revenue and financial resilience: Questions about funding mix, unrestricted revenue, cost structure, reserves, concentration risk, investment, and earned income.
Operating model and capabilities: Choices about structure, leadership, talent, technology, data, facilities, governance, partnerships, and processes.
Stakeholder and ecosystem role: Questions about community relationships, collaboration, influence, policy, referrals, and coordination with other organizations.
These categories are examples, not a required structure. Themes should reflect the organization’s actual issues. A nonprofit undergoing founder transition may have a theme focused on leadership and institutionalization. An organization facing policy change may need a theme focused on advocacy and public-system relationships.
Most organizations should aim for three to five strategic themes. Fewer themes improve focus, but themes should not be so broad that they become meaningless. “Organizational excellence” can hide many unrelated issues. A more useful theme might be “Building the management, data, and technology capacity required for reliable multi-site delivery.”
The core team should test each proposed theme:
- Strategic significance: Does it affect the organization’s future direction or ability to deliver a mission?
- Distinctiveness: Is it meaningfully different from the other themes?
- Decision content: Does it contain choices rather than only desirable outcomes?
- Evidence base: Is it supported by diagnostic findings?
- Manageability: Can leadership and the board address it within the planning process?
- Implementation relevance: Will resolving it lead to priorities, initiatives, resource decisions, or changes in accountability?
The team should examine dependencies among themes. A growth choice may depend on revenue diversification and management capacity. A partnership strategy may reduce the need for direct expansion. These relationships should be visible so that decisions are made in a logical sequence.
Strategic themes are not yet the final priorities. They define the fields of choice that must be resolved. After options are developed and evaluated, some themes may become priorities, others may be combined, and some may be addressed through enabling initiatives.
12.5 Strategic Issue Framing Template
The following template can be used to document each proposed strategic issue and prepare it for discussion:
- Issue title: Give the issue a short, neutral name.
- Decision question: State the choice the organization must make in one sentence.
- Why it matters now: Explain the trigger, urgency, and consequences of delay.
- Evidence: Summarize the most relevant diagnostic findings.
- Current position: Describe how the organization currently addresses the issue and where the model is under pressure.
- Root causes: Identify the underlying drivers rather than listing only symptoms.
- Stakeholders affected: Note who benefits, bears risk, provides resources, or must implement the decision.
- Credible options: List the distinct paths the organization could pursue, including maintaining the current approach where appropriate.
- Evaluation criteria: Define how the options will be compared.
- Key assumptions: State what must be true for each option to work.
- Evidence gaps: Identify information still required and whether a pilot, scenario, or consultation is needed.
- Tradeoffs: Explain what each option enables, limits, delays, or stops.
- Risks: Describe major mission, financial, operational, legal, people, or reputational risks.
- Dependencies: Note links to other strategic issues and the order in which decisions should occur.
- Decision authority: Identify who recommends, who contributes, and who decides.
- Decision date: Set the point by which the issue must be resolved.
- Next step: Assign the immediate analysis, discussion, or preparation required.
After completing the templates, the core team should compare the issues as a portfolio. Several issues may be different expressions of the same underlying choice and should be combined. Others may be operational matters that belong in the issues log. The remaining issues should represent the few decisions most likely to shape the plan.
The team should then present the proposed issue set to executive leadership and the board. The discussion should test whether any material choice is missing, whether the framing is neutral, whether the evidence is sufficient, and whether the organization has the authority and capacity to act on the answer.
Agreement on the strategic issues is an important decision point. It prevents leaders from developing attractive initiatives before confirming the problems those initiatives are meant to solve. It also creates discipline for the next phase, in which the organization will generate options and evaluate tradeoffs.
A strong set of strategic issues makes the planning process more demanding but also more useful. It brings unresolved choices into the open, connects evidence to decisions, and forces leadership to consider what the organization will prioritize and what it will not. Once these questions are framed clearly, the organization can move from diagnosis toward a strategy grounded in mission, reality, and deliberate choice.