Reflect on Impact

Reflecting on impact means looking back at what your project actually did — not what you hoped it would do. Honest reflection makes the next project stronger. You gather evidence, separate what worked from what did not, notice what surprised you, and turn the whole experience into clear lessons for next time.

Evidence: Numbers AND Stories

Real impact has two sides. Numbers tell HOW MUCH happened. Stories tell WHY it mattered. A campaign that delivered 50 thank-you notes (number) is more powerful when one helper says, "I felt seen for the first time" (story). Strong reflection collects both.

• Quantitative evidence (numbers): how many, how often, how much, how far it reached.
• Qualitative evidence (stories): quotes, moments, photos, observations, feelings shared.
• Use BOTH — numbers without stories feel cold; stories without numbers feel anecdotal.
• Write evidence down soon after the project, while memories are still sharp.

What Worked / What Did Not

Sort your project into honest piles. What worked is anything that helped you reach the goal — a smart plan, a kind action, a good partner, a clear message. What did not work is anything that slowed you down — a confusing step, a missed deadline, a rule you forgot. Both lists are useful.

1. List three things that clearly worked — be specific, not vague.
2. List three things that did not work — describe the moment, not the person.
3. Mark which problems you can fix yourself and which need help to fix.
4. Be kind in your wording — reflection is about learning, not blaming.

What Surprised You

Surprises hide the biggest lessons. A surprise is anything you did not predict — a class that loved an idea you thought was small, a step that took twice as long, an audience you forgot to include, a partner who became a leader. Write the surprises down before you forget them.

• Positive surprise: something better than expected — what made it work?
• Negative surprise: something harder than expected — what was missing in the plan?
• People surprise: someone helped or struggled in a way you did not predict.
• Time surprise: a step that took much more or much less time than planned.

Lessons Learned and Next Time

A lesson learned is a short sentence you can carry into your next project. Turn each lesson into a clear "next time" action. "We did not check the audience" becomes "Next time, ask three people in the audience first." Small, specific changes beat vague promises like "do better."

1. Pick the three biggest lessons — do not list everything.
2. Write each lesson as one short sentence anyone can understand.
3. Pair each lesson with a "next time" action you can actually do.
4. Keep the list — the next project starts where this one ended.

Sharing Impact With Your Audience

Sharing impact is not bragging — it is closing the loop. Tell the people who helped, the people you served, and the people who care what happened. Share the wins AND what you would do differently. Use real numbers, real stories, and ask consent before sharing names or photos.

• Choose the right audience: helpers, friends, families, the people you served.
• Pick a clear format: a poster, a short talk, a class email, a slide.
• Lead with one number and one story — the rest is detail.
• Always ask consent before using a name, a quote, or a photo of someone.