Why should you plan your action? How do you plan your action? How do you implement your solution? Evaluating what's happened What can go wrong, and what to do about it A group can spend substantial time defining a problem, examining its causes, generating possible responses, and choosing an approach. None of that guarantees that the decision will actually be carried out. Implementation is the part of the problem-solving process in which a proposed solution becomes organized action. It requires more than enthusiasm or agreement. People need to know what will happen, who is responsible, what resources and authority are available, when important steps are due, how progress will be monitored, and what the group will do when conditions change. This section focuses on turning a selected approach into an action plan, implementing it, evaluating what happens, and adapting when the plan does not work as expected. Why should you plan your action? Planning creates a practical bridge between a decision and implementation. A useful action plan can: Clarify the scope of the work Assign responsibility Identify required resources and authority Establish milestones and deadlines Identify dependencies among tasks Anticipate major risks and barriers Establish how progress and outcomes will be monitored Make follow-up easier Planning cannot anticipate every problem. Conditions may change, assumptions may prove wrong, resources may become unavailable, or implementation may create unexpected effects. A good plan should therefore provide enough structure for coordinated action while allowing responsible adaptation. Match the planning effort to the work A small, low-risk action may need only a responsible person, deadline, and brief written record. A larger or higher-risk intervention may require: A detailed action plan A budget Formal approvals Contracts or procurement Staff or volunteer training A communication plan An accessibility plan A data and evaluation plan Risk and contingency planning A longer implementation timeline Do not create a complicated planning process for work that does not need one. At the same time, do not rely on informal verbal agreements for a project whose success depends on many people, organizations, resources, or deadlines. How do you plan your action? Confirm what was decided Before developing the implementation plan, make sure the selected approach is clearly described. Ask: What problem or condition is this intended to address? What outcome do we expect? Who made or authorized the decision? What assumptions does the approach depend on? What important risks or uncertainties remain? If the solution has changed so much during decision-making that it no longer clearly addresses the original problem, revisit the analysis before implementation begins. Describe how the solution is expected to work For a complex intervention, it can help to describe the connection between: Resources or inputs Activities Immediate outputs Short-term outcomes Longer-term outcomes Important contextual factors and assumptions This can be written as a logic model, program roadmap, theory of change, or another format that clearly shows how the group expects its activities to produce results. The purpose is not to create paperwork for its own sake. It is to make assumptions visible so they can be tested during implementation and evaluation. Break the solution into action steps Identify the work required to move from the decision to implementation. Depending on the project, action steps may involve: Approvals and governance Staffing or volunteer roles Partnerships Funding Procurement Facilities Technology Accessibility Training Communications Participant recruitment or outreach Data collection Evaluation Example Suppose a community health program has found that evening appointments have a high no-show rate. After examining several causes and possible responses, the organization decides to pilot later transit support, more flexible appointment times, and a simpler rescheduling process. Action steps might include: Confirm which transportation partner can support the pilot Identify the appointment times and participants included in the pilot Update scheduling and rescheduling procedures Make information available in accessible formats and appropriate languages Train staff on the revised process Establish baseline attendance data Define measures for attendance, access, participant experience, cost, and unintended effects Establish a review date and criteria for continuing, modifying, expanding, or stopping the pilot This type of planning connects implementation directly to the problem analysis and to the evidence that will later be used to judge results. For each action step, answer the key questions What will be done? Describe the task clearly enough that the responsible person knows what completion means. Who owns it? Identify one person or role with primary responsibility for making sure the task moves forward. Other people may provide support, advice, approval, or information. Make clear who: Is responsible for doing the work Is accountable for completion Must be consulted Needs to be informed Do not assign someone responsibility without considering whether they have the authority, time, skills, resources, and role needed to carry it out. What is the timeline? Identify: Start date Deadline Important milestones Dependencies Some activities cannot begin until another task is finished. Others can occur at the same time. Make timelines realistic enough to support planning rather than simply choosing the earliest possible date. What resources are needed? Resources may include: Funding Staff or volunteer time Expertise Equipment Technology Facilities Data Training Partnerships Identify where those resources will come from and what happens if they are not available. What approvals or authority are required? Determine whether the step requires: Leadership approval Board or committee action Government authorization Contract or procurement approval Legal or compliance review Partner agreement Do not assign responsibility to someone who cannot legally or organizationally authorize the work. What accessibility and inclusion requirements apply? Consider accessibility during planning rather than adding it after implementation begins. Depending on the activity, this may include: Physical access Language access Communication accommodations Accessible electronic materials Transportation Scheduling Technology access What could interfere with the work? Identify major risks and dependencies. For each important risk, consider: How likely is it? What would the effect be? What warning signs should be monitored? What can reduce the likelihood or impact? What is the contingency plan? Who decides whether the contingency plan is activated? How will progress be monitored? Decide before implementation begins: What information will show whether the step is on track Who will collect or review that information How often it will be reviewed What would trigger follow-up or escalation Establish a source of truth Put the action plan in an approved location where the people responsible for the work can find the current version. The plan may be maintained in: A shared action-plan document A spreadsheet A project-management system Another organizational system Avoid keeping the only current version in one person's notes or email. For complex work, document significant changes to scope, budget, responsibilities, timeline, or strategy. How do you implement your solution? Implementation is not simply carrying out a finished plan. It is a period in which assumptions, capacity, partnerships, and real-world conditions are tested. Confirm responsibilities Before work begins, each responsible person should understand: Their task Deadline Available resources Decision authority Dependencies How to raise a problem or request assistance Responsibility may be accepted voluntarily, assigned as part of a legitimate staff role, or established through another appropriate organizational process. Do not pressure volunteers into responsibilities they have not agreed to take on. Use appropriate communication channels Identify how project participants will communicate about: Routine updates Questions Delays Decisions Urgent risks Use appropriate organizational contact methods rather than requiring people to disclose personal telephone numbers or other private contact information. Monitor implementation as it happens Ask: Are activities occurring as planned? Are milestones being met? Are resources sufficient? Is the intervention reaching the intended participants? Is the quality of implementation acceptable? Are barriers or unintended effects appearing? Monitoring allows the group to respond before a missed milestone becomes a major implementation failure. Use meetings when they are useful A follow-up meeting may be useful when people need to: Make a decision Resolve an interdependent problem Examine evidence together Coordinate significant changes Routine status information may be shared asynchronously. Do not schedule recurring meetings merely because meetings were part of the original plan. Adapt responsibly Some implementation changes can be made by the person responsible for the work. Others may affect budget, scope, legal requirements, evaluation, community commitments, or strategy and require additional approval. Establish in advance: What can be adjusted routinely What requires approval Who has authority to approve it How significant changes will be documented Evaluating what's happened Evaluation should begin during planning, not after implementation is finished. Before the work begins, identify what the group needs to learn and what evidence will answer those questions. Evaluate the implementation process Process or implementation evaluation asks whether the intervention was carried out as intended and what helped or hindered it. Questions might include: Were planned activities completed? Were they completed on time? Who was reached? Who was not reached? What resources were used? What barriers affected delivery? What adaptations were made? Was implementation quality consistent with what was intended? Evaluate outcomes Outcome evaluation asks whether the intended results occurred. Depending on the project, questions might include: Did the targeted condition improve? By how much? For whom? Over what period? Were results different across relevant groups or locations? What unintended positive or negative effects occurred? An observed improvement does not automatically prove that the intervention caused it. Other events or conditions may also have influenced the result. Use credible evidence The appropriate evidence depends on the question and stakes. Sources may include: Administrative data Program records Surveys Interviews Observations Financial information Community and participant feedback Other appropriate measures Define baseline measures before implementation when change over time is important. Evaluate equity and access Overall improvement may hide important differences. Ask: Who participated? Who benefited? Who encountered barriers? Did the intervention reduce, maintain, or increase important disparities? Gather feedback about the process Feedback from staff, volunteers, partners, participants, and other relevant people can help identify: Confusing procedures Accessibility problems Workload issues Unanticipated barriers Useful adaptations Feedback can be collected through written, digital, verbal, anonymous, interview, or other accessible methods. Satisfaction may be useful information, but it should not be confused with evidence that the intervention achieved its intended outcome. Act on the findings Evaluation should inform decisions. The group may decide to: Continue the approach Modify it Expand it Reduce its scope Test another approach Stop it Document the evidence and reasoning behind significant changes. What can go wrong, and what to do about it Implementation rarely proceeds exactly as planned. When a problem appears, diagnose it before choosing the response. The person assigned to a task does not have the right capacity or support Ask: Were role requirements clear? Does the person have the time, authority, skills, and resources needed? Would training or a co-owner help? Would another role be a better fit? Discuss role fit respectfully rather than labeling someone as the "wrong person." No one accepts responsibility for a task Ask why. Is the task necessary? Is the workload realistic? Are the required skills available? Is the responsibility appropriately a volunteer role? Does it need to be assigned to staff or contracted expertise? Are adequate resources or compensation available where appropriate? Do not pressure someone privately to take on a responsibility merely because nobody volunteered publicly. Participation or energy declines Low participation may reflect: Excessive workload Competing responsibilities Unclear progress Insufficient resources Frustration with the process Lack of clarity about the purpose Identify the cause before assuming that people simply need more motivation. Recognizing progress can be useful, but celebration does not substitute for resolving an implementation barrier. The work is taking longer than expected Examine: Whether the original estimate was realistic Which tasks are delayed Whether a dependency is blocking progress Whether staffing or resources are sufficient Whether unnecessary scope has been added Whether lower-priority work should be deferred Adding more people does not automatically make work faster and may increase coordination needs. Community members or partners oppose the approach Do not assume opposition should be defeated or appeased. Determine what the concern is. It may involve: A legitimate harm or unintended consequence Accessibility Rights or legal concerns Cost or burden Different community priorities Insufficient engagement Missing information Misinformation about the project Respond according to the substance of the concern. The appropriate response may be explanation, additional engagement, modification, mitigation, further evidence, or reconsideration of the approach. A new opportunity or alternative appears Avoid switching direction solely because something new appears attractive. Compare: Evidence Expected benefits Risks Transition costs Existing commitments Strategic fit Effect on the implementation timeline Use the established decision authority to approve significant changes. The solution is not being implemented as planned This is an implementation problem. Ask: Which activities are not occurring? Why? Are resources, staffing, training, or systems inadequate? Is the original plan unrealistic? Should the implementation approach be adapted? The solution is being implemented but outcomes are not improving This may indicate a different problem. Ask: Was the causal analysis correct? Has enough time passed for the expected outcome? Is the intervention reaching enough of the intended population? Is the intervention strong enough to affect the outcome? Have outside conditions changed? Are the measures capturing the outcome accurately? Do not assume that waiting longer will eventually make an ineffective intervention work. The intervention creates unintended harm Some problems require immediate modification, pause, or termination. Establish criteria in advance where possible for: Pausing implementation Escalating a safety concern Modifying the intervention Ending the intervention Legal, ethical, safety, and safeguarding obligations should take priority over preserving the original plan. The intervention appears successful Success also requires analysis before expansion. Ask: Is the evidence strong enough to support the conclusion? Under what conditions did the approach work? For whom did it work? What resources made the result possible? Can those conditions be maintained at a larger scale? Were there unintended consequences? Scaling a successful pilot may require a different implementation plan rather than simply doing more of the same thing. In Summary Choosing a solution is not the end of problem solving. Implementation is where the group's assumptions are tested against real conditions. Begin with a clear action plan. Identify tasks, owners, authority, resources, timelines, milestones, dependencies, accessibility requirements, risks, and communication methods. Plan monitoring and evaluation before implementation begins. Track both whether the intervention is being delivered as intended and whether the expected outcomes occur. Use credible evidence, examine who is reached and who benefits, and watch for unintended consequences. When implementation problems occur, diagnose them rather than assuming that people simply lack motivation. Delays, opposition, weak results, or declining participation may reveal problems with resources, workload, accessibility, assumptions, strategy, or context. Finally, use what you learn. Continue approaches that are working, improve those that can be strengthened, and modify or stop those that are ineffective or harmful. Effective implementation is not rigid execution of a plan. It is coordinated action supported by clear responsibility, evidence, monitoring, communication, and the willingness to adapt when conditions or results show that a different approach is needed. Contributor Jenette Nagy Chris Hampton Resources Print Resources Avery, M., Auvine, B., Streibel, B., & Weiss, L. (1981). Building united judgement: A handbook for consensus decision making. Madison, WI: Center for Conflict Resolution. Dale, D., & Mitiguy, N. Planning, for a change: A citizen's guide to creative planning and program development. Dashiell, K.A. (1990). Managing meetings for collaboration and consensus. Honolulu, HI: Neighborhood Justice Center of Honolulu, Inc. Interaction Associates (1987). Facilitator institute handbook. San Francisco, CA: Author. Lawson, L., Donant, F., & Lawson, J. (1982). Lead on! The complete handbook for group leaders. San Luis Obispo, CA: Impact Publishers. Meacham, W. (1980). Human development training manual. Austin, TX: Human Development Training. Moore, C. (1987). Group techniques for idea building. Newbury Park, CA: Sage. Morrison, E. (1994). Leadership skills: Developing volunteers for organizational success. Tucson, AZ: Fisher Books.
