<aside> 🏁

🏁 🔐 🏁 FRONT MATTER 🏁 🔐 🏁

Goals of this document: Provide a consistent structure for teams to reflect on both external and internal projects every ~3 months throughout their duration, and again after they fully wrap.

People who have worked on this: Alex Pandel, Sasha Magee, Laura Gerhardt, Colin Murphy, Kate Fisher, Dave Luetger

Purpose and intended audience: Project reflections are how 18F metabolizes what we learn from each project — lessons for 18F as a whole, future project teams, and what the team itself might do differently in the future. A reflection summary is intended to be shared with the broader 18F team in #project-reflections on Slack.

How to use it:

• This doc is a template for the summary of the major insights from the reflection session, but is not intended to be used as the basis for the reflection session itself. Teams can choose to include the raw notes below the summary for additional context to the wider organization.
• For a step-by-step guide on best practices for structuring, facilitating, and synthesizing a project reflection in order to arrive at this summary, please see the facilitation guide and session template

Last updated: 9/26/2024 by Ryan Ganser to update alignment between the guides and simplify the language

</aside>

[Partner agency or team] [project name or type (PA, E&I, internal)] [in-flight/final] reflection

Tock Line: [Tock code for project]

Time Frame: [Reflection period start & end date]

Team: [@teammember1 @teammember2 @teammember3 @teammember4]

What are the project’s intended outcomes?

[2-3 sentences, max; link to project impact tracker as well, if applicable]

Intended outcomes in order of priority

1. [rank based on voting]

Team’s reported delivery of outcomes

Select one and delete the others for easier skimming:

Not Successful

Limited Success

Somewhat Successful

Mostly Successful

Successful