Reflection

The role reflection plays in our work cannot be over-stated. In navigating so much complexity, it’s important to normalise that not everything will register the first time. Especially when trying to actively speak to complex systems in an ongoing learning process, sometimes calls with partners are designed to be about surfacing thinking, to make sense of later by using the recording. This is a process of making visible your thinking, to reflect and synthesise later.

Reflection is also important on the level of your own contributions to the team you’re part of. Working in a process-oriented way necessarily means there is an inner dimension to the work. Working to complete a project, without reflecting on where your contributions are coming from, is likely to result in just the completion of a project. One thing that makes certain projects more regenerative is when team members and the project (and its environment) co-evolve together, throughout its development. This can only happen when there is a level of awareness of the possibility of such relationship, and that happens through reflection. This is also part of the depth our publishing tooling has been designed for.

Lastly, such reflection can come in different forms and timeframes. Sometimes reviewing notes from the prior week can feel like the perfect refresh ahead of what’s to come. Other times, you might find yourself watching back call recordings from 18 months ago, remembering the original purpose of a much larger project trajectory.