Curious to know a summary of the motivation to bring this topic into the meeting. What is the need you are trying to satisfy? @nathalie @Vasilis_Ntouros
Writng a few thoughts on that:
Developing a strategy for Karrot has been an ongoing task and we have tried out a number of things through the years to explore that topic.
Recently we reached out an agreement that involves 6 ovearching strategic aims.
Following that we started developing a process where members of the Karrot-team take on different tasks which align with our strategic aims (can be with more than one aims).
As we commit on tasks, the topic of ‘measuring’ the impact/outcomes of each task came up and one of the big questions has been if we need sth like that and if that would be applicable to all tasks.
We havent agreed yet on that and how/if we proceed.
Nathalie and myself though took some co-working time to start thinking about that and we have developed a proposal (available on the main wall of the Karrot-team and feedback) wherein we propose that contributors after having commited to a task (among other questions) also answer the following: “Is there a measure you could keep track of? How do you evaluate that this task contributed to the Strategic Aims?”
As the question is open, obv one could suggest that this task is not measurable.
However if a task’s outcomes can be somehow measurable this can be good feedback to have for future iterations/adaptations.
Also this idea of measuring, keeping track can probs improve responsibility and accountability.
We have tried this out sth similar already in the context of our general meetings where we keep track of actions members undertake. The more one action is not ‘done’ the more numbers it gets.
Finally, in the context of community-tech and the culture of Karrot one could say that measuring should be a no go zone as it could graft the project with values and processes that we do not appreciate (coming from the traditional market environments). Therefore it remains sth to explore, try out if we reach consent and re-evaluate as we move forward.