A good solution starts with properly identifying the problem and naming all requirements. This could be done by so called User Stories: A collection of individual points of view of the ones using, interacting with or being affected by the changes we are considering. However, we take this approach a bit further and ask ourselves which non-individuals may be affected. This could be the ecosystem, social structures of the nearby community, as well as future generations. These stories may change or be extended with time and additional insight. Actually that’s the beauty of working and thinking in a circular way: there’s no beginning and no end, just iterations, allowing continuous improvement.

Based on all the stories we’ve collected we start thinking about the wildest concepts that could fulfill their needs. The success of these first two phases highly relies on talking to others, frequently changing the point of view and not bending the requirements to fit predefined solutions in our heads. The concept phase will be concluded with an objective comparison of all concepts and the question which one will be taken to design. Sometimes the answer may also be: None.

The Design phase entails most of the work. We define all specifications of the solution, build the team needed for implementation and maintenance, explore potential collaborations, create a timeline, set up a budget plan and predict the ecological, social and financial benefits of the project. At the end of this phase there’s THE review: users, participants, and those who will be affected by the project decide if the design is ready for implementation and wether it has the impact we’ve hoped for. When passing this review, we start funding: Everyone involved in, affected by, or just wanting to support the project can fund a part of it. In return supporters get a voucher representing the value of their funding, to be used for the products of the COC or their next stay at the HAFH.

As soon as the project’s execution is financially covered by a predefined funding-threshold, its implementation starts. Our goal is to closely integrate the supporters and the Collective into that phase in all conceivable ways, since everyone has different strengths and passions to learn from. Thereby turning the realization of the project into a collective effort and gain.

And finally we use it, test it, review our work, probably break and repair it and gather feedback. All insights will be shared. Because you never know who can benefit from them and put them to good use in another context. In the end: we don’t aim for permanence! So the next cycle will come for sure …