1: Before the Strategic Plan- Understanding the Groundwork

Introduction to Strategic Planning for Public and Nonprofit Organizations · LibreTexts

0%

Contents

    Text

    Size
    100%
    Theme
    Typeface
    Line length
    Spacing

    Read aloud

    How

    Speed: 1×
    Light up
    Highlight

    Symbols: Mulberry Symbols, © 2018–2026 Steve Lee, CC BY-SA 4.0 (licence, the set), the site's own copies.

    From LibreTexts, under CC BY-NC-SA 4.0, as the source states it; its equations are written in TeX, which the PDF shows typeset. This page at LibreTexts.

    1: Before the Strategic Plan- Understanding the Groundwork

    Introduction: Why This Part Matters

    When people first hear the phrase strategic planning, they often imagine a group of people sitting around a table deciding on goals. That is part of it, but it is not the beginning.

    The real beginning of strategic planning happens earlier. Before an organization can decide what it wants to accomplish, it has to understand how planning will work, who should be involved, what information matters, and what larger environment the organization is operating in. If those questions are ignored, even a well-written plan can fall apart once people try to use it.

    Think about it this way: writing the strategic plan is a little like writing the final draft of a paper. You cannot do it well if you have not first figured out the topic, gathered evidence, thought through your argument, and understood your audience. A strategic plan works the same way. The final document is only as good as the preparation behind it.

    This chapter focuses on that preparation.

    It is especially important for students and others new to planning because this stage of planning is often invisible from the outside. When you look at a finished strategic plan, you usually see polished goals, attractive formatting, and confident language. What you do not see as easily is the earlier work that shaped it: the meetings about process, decisions about who would participate, review of existing documents, conversations with stakeholders, analysis of data, and debates about what the organization could realistically accomplish. That work may seem less exciting than writing the goals, but it often determines whether the plan will actually be useful.

    In public and nonprofit organizations, this early stage is even more significant because these organizations rarely operate in simple environments. They often face budget constraints, political pressures, legal requirements, multiple stakeholder groups, and competing expectations. A private company might judge success mostly in terms of profit. A public or nonprofit organization is usually asked to do much more than that. It may be expected to serve the public, meet legal obligations, demonstrate fairness, respond to community needs, and maintain trust, all while operating with limited resources. That complexity means that planning has to begin carefully and with clear intentions.

    So before we talk about goals, objectives, and implementation, we need to start with a more basic question: what has to happen before a strategic plan can even begin to make sense?

    Key Terms and Concepts

    • Process
    • Strategy
    • Written charge
    • Key performance indicators
    • Alignment

    When Process Takes Over

    One of the easiest mistakes in strategic planning is to confuse doing planning activities with thinking strategically.

    Imagine that a city needs to repave a public parking lot. On the surface, this sounds like a simple operational problem. The city needs to decide what kind of pavement to use, how much money to spend, when to close the lot, and whether any design changes are necessary. Because public money is involved and people will be affected, a committee is formed to help think it through.

    So far, this sounds reasonable.

    But then the planning process starts to take over. People begin debating who should be on the committee. Should it include city staff? Nearby business owners? Elected officials? Residents? Should one group have more representation than another? Once the committee is finally formed, the early meetings focus on rules, procedures, norms, and whether more public input is needed before any actual options are considered. By the time the group gets around to the real issue, people have spent more time discussing the process than the actual problem.

    Then something else happens: the outside world intrudes. A decision that seemed practical becomes controversial. People interpret it politically. Complaints appear. Leaders are forced to respond to reactions they never anticipated because the committee was so focused on its own internal discussions that it neglected the broader context.

    This is a useful example because it illustrates a common planning failure. Organizations can become so absorbed in process that they lose sight of strategy. They can produce meetings, agendas, minutes, surveys, and draft language without ever asking the deeper questions that give the process meaning.

    This is a valuable lesson. Planning is not just a matter of completing steps. Strategic planning is not good simply because it looks organized. A planning process only becomes strategic when it helps an organization understand its situation, make better choices, and prepare for implementation.

    In other words, a planning process can be busy and still be shallow, and we don’t want that. The groundwork helps ensure that the process is doing more than performing seriousness.

    Organizing for Planning

    One of the first things an organization has to decide is how it will organize the planning effort itself.

    Some organizations treat strategic planning as a project. They gather a small group, hold a retreat or a few meetings, produce a final document, and move on. That approach is understandable. People are busy, and many organizations want to complete the process quickly. But there is a problem with this model in that it treats planning as a one-time event rather than an ongoing organizational responsibility.

    A better approach is to think of planning as an ongoing process that needs structure.

    This does not mean every organization must create the exact same kind of committee. Some may form a standing planning committee. Others may use a temporary steering group that continues to meet during implementation. Still others may assign planning oversight to an existing leadership group. The structure can vary. What matters is that someone is responsible not only for helping create the plan, but also for maintaining continuity after the document is finished.

    There are several reasons for this. First, strategic planning requires a kind of thinking that many people are not used to doing. A person may be excellent at running a program, managing a budget, supervising staff, or serving clients, but strategic thinking asks a different set of questions. It requires people to step back and think about the organization as a whole: its mission, its environment, its opportunities, its limits, and the relationship between present actions and future outcomes. That is not always easy. People often need time and practice to develop that way of thinking.

    Second, a strategic plan does not matter much if no one pays attention to it after it is written. Someone has to keep asking whether the plan is still relevant, whether goals are actually moving forward, and whether the organization needs to adjust because conditions have changed. If the planning group disappears the moment the draft is approved, a lot of the knowledge developed during the process disappears too.

    Third, planning can strengthen organizational learning. When people from different parts of an organization work together on planning, they can gain a better understanding of how the whole organization functions. They see how different units connect, why some tradeoffs are difficult, and why the final plan may not include everything everyone wanted. This kind of shared understanding can make the organization stronger in the long run.

    The takeaway here is that planning is not just about making a document. It is also about building the organizational capacity to think and act strategically over time.

    The Committee’s Charge

    Once an organization has decided to form a planning group, the next question is simple but critical: what, exactly, is this group supposed to do?

    This is where a written charge becomes useful.

    A committee charge is a document that explains the committee’s purpose, responsibilities, structure, and expectations. It is essentially the committee’s official assignment. Without it, people may come into the process with very different assumptions. One member may think the group is advisory only. Another may think it has decision-making authority. One may think the committee exists only to write a draft. Another may assume it will also oversee implementation. Those differences can create confusion and conflict very quickly.

    A written charge helps prevent that.

    It is useful to think of the charge as answering five basic questions.

    Why does this group exist?

    What is its role in the planning process? Is it supposed to gather input, review data, draft goals, monitor progress, or some combination of those things?

    Who is on it?

    Why were these people selected, and what perspectives are they expected to contribute?

    How long will they serve?

    Is this a temporary group, or will it continue after the plan is finished? If members rotate off, how will continuity be preserved?

    What authority does the group have?

    Can it make decisions, or only recommendations? What issues must be approved elsewhere?

    What does meaningful participation require?

    Are members simply expected to attend meetings, or are they also expected to read materials, gather feedback, and help communicate with stakeholders?

    This might sound overly formal at first, but in practice it is extremely helpful. A clear charge gives the committee direction and legitimacy. It tells members that this is not just another vague organizational meeting, but a structured effort with a defined purpose.

    This is also a good place to learn a relevant lesson about public and nonprofit organizations: clarity is often a form of leadership. Ambiguity can feel flexible in the short run, but it often creates frustration later. A written charge is one way organizations reduce avoidable confusion before the real work begins.

    Committee Development: Who Should Be at the Table?

    If a planning committee matters, then committee membership matters too.

    This part of the process deserves more attention than it often receives. Organizations sometimes fill committees in routine ways. They invite people based on title, hierarchy, convenience, or habit. But good strategic planning requires more intentional thinking than that.

    A better question is this: what kinds of knowledge and perspective does the organization need in order to plan well?

    Leadership is necessary. Executive directors, department heads, agency leaders, or other senior administrators often understand the organization’s broader responsibilities, political constraints, and resource limitations. Their participation also signals that the process is being taken seriously.

    But leadership alone is not enough.People who understand the organization’s daily operations are also essential. Front-line staff, program managers, and operations personnel can often identify practical barriers that senior leaders may miss. They know where procedures break down, where clients struggle, and where ambitious ideas may run into real-world constraints.

    Financial and administrative knowledge also matters. An organization cannot create a realistic plan if no one at the table understands budgets, staffing, compliance requirements, technology systems, or fundraising limits. A strategic plan that ignores capacity is likely to be unrealistic no matter how inspiring it sounds.

    In nonprofits, board members may also bring useful perspectives, especially when it comes to governance, sustainability, and external relationships. In public organizations, similar roles may be played by advisory boards or oversight bodies.Depending on the organization, it may also make sense to include community partners, volunteers, members, or external stakeholders. These people can provide perspectives that insiders may not see.

    Most importantly, organizations should think seriously about whether the people most affected by the organization’s work have any real voice in the planning process. If an organization serves residents, clients, students, patients, or community members, it should at least ask whether those groups are represented meaningfully. It is easy to write plans about people without actually involving them.

    At the same time, we should be careful not to treat representation as a magic solution. A committee can include many types of people and still fail to hear them equally. Who gets interrupted? Whose ideas are taken seriously? Who feels comfortable speaking? These questions matter too. Inclusion is not just about who is invited. It is also about how the process is designed.

    Consultants: Help or Hazard?

    People are often surprised to learn how often organizations hire outside consultants to help with strategic planning. This can be useful, but it can also create problems.

    A consultant may be helpful when an organization lacks internal expertise in facilitation, data gathering, stakeholder engagement, or planning. Some organizations do not have staff who know how to structure a planning process, lead difficult conversations, or synthesize a large amount of input into something usable. In those cases, a consultant can add real value.

    A good consultant usually contributes process expertise. They may know how to move a group from scattered concerns to focused priorities. They may be skilled at asking difficult questions, organizing stakeholder input, and designing meetings that produce real decisions rather than endless discussion. They can also make it easier for internal leaders to participate rather than spending the entire time trying to manage the room.

    But there are limits to how a consultant can be helpful. A consultant should not become the author of the organization’s identity or the substitute for its leadership. The consultant does not have to live with the consequences of the plan. The organization does. That means the consultant can help structure the process, but the substance of the plan should still belong to the organization and its stakeholders.

    This is an important distinction. Consultants can support strategic planning, but they should not replace internal judgment. If an organization hires a consultant because it wants someone else to solve internal disagreement or tell everyone what to do, the process may look smoother in the short term but become weaker in the long term.

    So the key question is not simply, “Should we hire a consultant?” The better question is, “What role should the consultant play?” Used wisely, a consultant supports organizational thinking. Used poorly, a consultant becomes a substitute for it.

    Information Gathering: You Cannot Plan from Guesswork

    Many people want to move quickly from forming a committee to writing goals. Goals feel concrete. They sound impressive. They make it seem like progress is happening. But in strategic planning, goals that come too early are often based more on assumption than understanding. Before an organization can decide where it wants to go, it needs to understand where it currently stands. That means gathering information.

    This is critical: strategic planning is not just a creative exercise. It is also an evidence-based one.

    Organizations need to gather several kinds of information.

    They need to examine formal documents such as laws, mandates, prior plans, contracts, board directives, mission statements, and performance requirements. These documents help define what the organization is already expected to do and what constraints it faces.

    They also need to look inward. What is the organization doing well? Where is it struggling? Are demands increasing? Is staff capacity weakening? Are certain programs underperforming? Are there patterns of dissatisfaction or inequity? A planning process that skips these questions will not be grounded in reality.

    At the same time, organizations must look outward. Strategic planning is not only about improving internal operations. It is also about understanding the environment. Public opinion, funding conditions, demographic change, political conflict, labor shortages, new technology, and actions by partner organizations can all influence what is possible.

    Understand that information gathering is not just about numbers. Quantitative data matter, but qualitative information matters too. Surveys, interviews, focus groups, listening sessions, and informal conversations can reveal things that spreadsheets do not. Numbers can show a pattern. People can often explain why the pattern exists.

    This stage may not feel exciting, but it is where planning begins to become serious. Without it, the plan risks becoming a list of opinions with nice formatting.

    In Real Life: Why External Factors Matter

    A county public health department began developing a strategic plan centered on expanding in-person wellness programming. Committee members liked the idea because it was visible, positive, and aligned with their general mission. They discussed adding more nutrition workshops, exercise classes, and community health events across the county.

    The problem was that the committee focused mostly on internal preferences and not enough on the outside environment.

    If the group had looked more carefully at external factors, it would have seen several warning signs. The county’s population was aging, making transportation a growing barrier. A nearby hospital system was already offering similar in-person programs. State funding priorities were shifting toward telehealth and partnership-based delivery models. Many rural residents were asking for mobile screenings and easier access to services, not more on-site classes.

    Because the committee did not examine these external conditions early enough, it spent time building goals around a strategy that was poorly matched to community needs and funding realities.

    The takeaway is straightforward: organizations should not plan based only on what sounds appealing internally. Strategic planning requires an understanding of the external environment, including demographics, policy changes, funding trends, community demand, and the actions of partner or competing organizations.

    Discussion Questions
    • What external factors did the department fail to consider before building its draft plan?
    • Which of those factors do you think would have been most important, and why?
    • How might community input have changed the planning process earlier?
    • What information should the committee have gathered before deciding on its strategic priorities?
    • How did the department confuse a good internal idea with a good strategy?If you were advising this organization, what would you tell the committee to do next?

    Key Performance Indicators: What Should an Organization Measure?

    At some point in this process, planners usually encounter the term KPI, or Key Performance Indicator. This phrase can sound technical or intimidating, but the basic idea is simple: A KPI is a piece of information that helps an organization judge whether it is doing what it is supposed to do and whether it is doing it effectively.

    The challenge is not just collecting data. Most organizations already collect more information than they actually use. The harder task is identifying which indicators are most useful for thinking strategically.

    For public and nonprofit organizations, KPIs often fall into several broad categories.

    • One category focuses on activity. What is the organization doing, how often, and for whom? This might include number of clients served, response times, participation rates, or number of programs delivered.
    • A second category focuses on quality and outcomes. Serving many people does not automatically mean the organization is succeeding. Useful indicators might include completion rates, client outcomes, satisfaction measures, compliance rates, or evidence of improvement over time.
    • A third category focuses on equity and access. Who is being served? Who is not? Are there disparities across groups or communities? Are some people facing barriers that others are not?
    • A fourth category focuses on capacity. What is the organization able to sustain? This may involve staff turnover, vacancy rates, training levels, budget reserves, volunteer retention, or technology limitations.
    • A fifth category focuses on trust and relationships. Public and nonprofit organizations depend heavily on legitimacy. Indicators such as donor retention, public participation, stakeholder satisfaction, or community partnerships can reveal how strong or weak those relationships are.

    The exact indicators should depend on the organization’s mission. A public health department, an arts nonprofit, and a parks agency will not use the same measures because they are trying to achieve different things.

    A good KPI is not just a number that looks nice in a report. It is a number that helps the organization think more honestly and more clearly.

    Aligning with the Larger Plan

    People new to the planning process sometimes assume that strategic planning begins with writing goals of their own. In practice, one of the first steps is usually much simpler: figuring out what larger plans, priorities, and expectations already exist. Many strategic plans are created at the unit, department, program, or division level, which means they are rarely written from scratch. Instead, they are developed within a broader organizational context and are expected to align with larger institutional goals.

    This can be a frustrating place to begin because broader organizational plans are often written in very general terms. They may emphasize ideas like innovation, service, equity, sustainability, or community impact without giving much guidance about what those ideas should look like in a specific office, program, or department. Even so, becoming familiar with those larger priorities is an essential part of preparing to plan.

    Why? Because smaller units do not plan in a vacuum. If they begin developing strategy without first understanding the larger goals they are supposed to support, they may create priorities that conflict with organizational expectations, duplicate efforts already underway elsewhere, or make it harder to justify resources and support. Before a planning group starts generating its own ideas, it needs to know the broader framework it is working within.

    At the same time, one should not misunderstand what alignment requires. Preparing for alignment does not mean copying phrases from the larger organizational plan and dropping them into a smaller one. That usually produces language that sounds polished but provides very little direction. The real preparation involves interpretation: learning what those broad priorities mean and thinking carefully about how they might apply in a specific context.

    If the larger organization emphasizes equity, for example, a planning team should ask what equity might mean in this particular program or unit. Does it suggest changes to outreach, service delivery, eligibility rules, hiring practices, or data collection? If innovation is a larger priority, what kind of innovation makes sense here? Better use of technology? More responsive service? New ways of partnering with the community? If community engagement is emphasized, what would meaningful engagement look like in this setting?

    This is one of the most significant early steps in strategic planning: getting familiar with the larger mission, goals, and expectations that will shape the plan before you start writing one of your own.

    In Real Life: Planning Begins with Knowing the Larger Framework

    A youth services nonprofit decided it was time for its mentoring program to create a strategic plan. The program team was eager to get started and quickly began brainstorming new goals. They wanted to expand into more schools, create a leadership program for older teens, and launch a new social media campaign to attract volunteers.

    All of these ideas sounded promising. The problem was that the team had not yet reviewed the nonprofit’s larger organizational strategic plan, recent grant commitments, or board priorities.

    Once they did, they realized several important things. The organization’s larger plan emphasized serving rural communities that had been historically under-reached, but the mentoring team’s first ideas focused mostly on schools already located in the city. The organization had also made a commitment to improve outcome tracking for all programs, yet the team’s draft goals said little about assessment. On top of that, a major funder had recently signaled that future grants would prioritize collaborative community partnerships rather than stand-alone expansion. What the program team initially saw as a strong draft now looked incomplete and somewhat misaligned.

    This did not mean their ideas were bad. It meant they were trying to plan before fully understanding the larger framework they needed to work within.

    After reviewing the broader strategic plan and related expectations, the team revised its approach. Instead of focusing only on expansion, it began asking different questions: How can this program support the organization’s rural outreach goals? What partnerships would strengthen the program and fit funder expectations? How should assessment be built into the plan from the start? The planning process became much more focused once the team understood what it needed to align with.

    The lesson is simple: before writing a strategic plan, a unit needs to know the larger mission, priorities, and commitments already shaping its work.

    Discussion Questions

    1. What mistake did the mentoring program team make at the beginning of the planning process?
    2. What larger documents, priorities, or expectations should the team have reviewed before drafting goals?
    3. Were the team’s original ideas bad ideas, or were they simply incomplete? Explain your answer.
    4. How did the larger organizational plan change the way the team thought about its own strategy?
    5. Why is alignment important before a unit begins setting priorities of its own?
    6. What kinds of problems can happen when a program plans in isolation from the larger organization?

    Why the Early Stage Matters So Much

    At first glance, this preparatory stage can seem less weighty than the later parts of strategic planning. There are no final goals yet. No fancy graphics. No implementation chart. No launch event. Instead, the work involves structuring committees, clarifying authority, gathering information, choosing participants, and reviewing documents. That can feel slow. But this stage matters because it shapes everything else.

    A weak strategic plan often fails long before the final document is written. It fails because the wrong people were involved, or because the right people were not actually heard, or because no one understood the scope of the committee’s authority, or because the organization skipped serious information gathering, or because the plan was built on hopes and vibes rather than evidence.

    By contrast, strong planning processes often look less dramatic at first precisely because they are doing the harder work of preparation. They are building legitimacy. They are clarifying expectations. They are grounding the conversation in evidence. They are helping the organization become ready to make real choices. This is a big lesson in both planning and leadership. The most valuable work is not always the most visible work. In strategic planning, preparation is not a detour from the “real” process. It is the real process.

    Conclusion

    Strategic planning does not begin with a list of lofty goals. It begins with groundwork.

    Before an organization can identify priorities, it has to decide how the planning effort will be organized, who will participate, what authority they have, what information matters, and how the organization’s larger environment will shape its choices. It has to think carefully about continuity, legitimacy, evidence, and fit.

    For people learning this material for the first time, that may be the biggest takeaway from this chapter: strategic planning is not simply about deciding what sounds good. It is about building the conditions under which an organization can make thoughtful, realistic, and publicly defensible choices about its future.

    That is especially true in public and nonprofit settings, where organizations often work under constraints that are political, financial, ethical, and social all at once. Planning in those contexts requires more than ambition. It requires preparation.

    In the chapters that follow, the organization can begin to define priorities, frame goals, and think about implementation. But none of that work will mean very much unless this earlier stage has been taken seriously.


    This page titled 1: Before the Strategic Plan- Understanding the Groundwork was last modified on Sun, 30 Aug 2026 22:30:44 GMT and is shared under a CC BY-NC-SA 4.0 license and was authored, remixed, and/or curated by Jayme Renfro via source content that was edited to the style and standards of the LibreTexts platform.