Curating Content To Support Learning About Humanity's Transition

This content was posted on  11 Jun 21  by   The Hum  on  Facebook Page
In a retrospective, we stop to reflect and learn. We’re looking for small adjustments or …

In a retrospective, we stop to reflect and learn. We’re looking for small adjustments or improvements we can do.

we lift our awareness from what we are working on, to how we are working as a team.

In our working teams we run a retrospective at the end of each work cycle (for example: every two weeks). There are many ways to run a retro but the basic pattern is: 👍 Good, 👎 Bad, 🔁 Change.

1- Start by asking: What worked well in the past cycle? Take some time to notice, acknowledge and celebrate your strengths.

2- What could have been better? Where are the tensions, frustrations or inefficiencies?

3- Choose just 1 or 2 things to improve by asking: what will we do differently to make the next cycle better?

The idea is to make consistent, gradual improvements. You’ll hear about frustrations when they’re still small and manageable, instead of waiting for them to build up into explosive conflict. And you can turn these tensions into innovations, improvements, and positive changes.

Let us know how it worked!

Scroll to Top