How to prepare a retrospective from project notes
A retrospective draft helps a team discuss what happened and what to improve. It works best when observations are tied to concrete events instead of broad judgments about people.
Start with the right material.
- What you provide
- a completed-project page or selected task notes.
- The intended result
- Save observations, what worked, what failed and proposed experiments grounded in notes.
How the workflow works.
Group supplied notes into what helped, what made work harder and possible improvements. Keep the evidence and proposed action together so participants can challenge or refine the interpretation.
What to check in the result.
Review the draft as a starting point for discussion. Confirm which actions the team accepts, choose owners and avoid presenting a generated explanation as an agreed root cause.
Preview the Markdown to check headings, lists and links as well as the words. Keep source references with the document so a reviewer can trace important statements back to the material you supplied.
Learn from the worked example.
The downloadable Markdown example shows one possible organization of the result. Read it alongside the source example and notice which statements are recorded facts, proposed wording or questions still needing an answer.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.