Once P4 is launched, it is fundamental to perform a project retrospective. This practice is useful to:
- assess pain points during the implementation
- improve the overall process
- establish next steps and community on-boarding
Part #1: the survey
As soon as celebratory drinks are over, everyone involved in the project (from NRO Sponsor to GPI Developer, from project manager to Content Editor) must fill the survey, it takes 3 minutes but it is super important for all NROs which will have to implement P4 in the future!
Part #2: the interview
Around a week after your P4 launch, someone from the GPI team (usually the implementation coordinator) must coordinate a meeting with the NRO core team (Project manager, Content coordinator and Digital lead). Main points for this meeting are:
- Impressions and feedback in the NRO (“How’s the office responding so far?“)
- Engagement activities update (mail to supporters, stories, tweets?)
- Outstanding activities recap (Archival, Datastudio dashboard..)
- Bug report and new feature submissions
- LIVE retrospective:
- What went well /wrong with NRO < > GPI relationship (communication, regular check-ins, ongoing support, etc)?
- What went well /wrong with the project plan (RASCI, project control, MOU, coordination, etc)?
- What went well /wrong with the project documentation (DRIVE, handbook)?
- Welcome to the P4 Community!
- Reminder to fill (and share with the whole team) the post-implementation survey
Part #3: the data analysis
Once both survey and interview are done, the GPI Planet 4 team must collect all information and perform a series of corrective actions, either to the process, the documentation or the stakeholders.
A useful way to visualise results of the post-implementation survey is to regularly check the DataStudio Dashboard, right below