Continuing the discussion from When is the next community call?:
It is just around the corner! And we want to design (or plan) the call and our next steps together with everyone. The main goal of the call would be to develop our next steps as we look to:
Helping the co-op ecosystem is what we want to do next, we realise from our surveys, meetings and activities so far that we have is definitely useful, but how might we make it better for you, your co-ops, and the ecosystem as a whole?
To help you and all of our partners better tell how we might help, we want to do a co-design session. We haven’t fixed a date and a timeline of events as we want to plan this openly. Anyone who wants to partake can chip in and we’ll collate the responses into an action plan.
To make it clear what we want to do, let me give a short overview of the co-design session and share the materials we hope to use. This session is based on Stanford d.school’s design thinking workshops.
Our Next Community Call: A Design Thinking Exercise
For our next community call, we are looking to do a Design Thinking Exercise to help us better understand what our needs are as co-ops and co-op members, so we can better build for us. The goal would be to answer the question:
How can we improve the Cooperative Experience
This is similar to the statement Rich shared:
This just rephrases it to allow us to contemplate it from another perspective.
The exercise will be done asynchronously and in pairs of 2. We have a call to kick it off, explain briefly, and pair up. People can join afterwards and be paired up.
Once paired, we’d go through different short tasks of asking our partner questions and documenting their answers. This will be done in a dedicated category here in Discourse and each pair or group would have their own topic for this. There will be a quick demo showing how it all works on the call and a slide to guide us through the steps, all you’d have to do is follow the prompts and write out your results.
Afterwards, we’d get to it and work on this over a 1 - 2 week period. The 2 weeks is a soft cap as you can continue his process with your partner, but we’d start collating at 2 weeks.
We’d be collating the needs, insights, problem statements and solutions that each group comes up with. We would use them to help us understand how we can make our product more useful for us all.
We will also factor in past contributions on this like:
- @equalmatt’s post on Data trusts: Data trusts and co-operative credentials - #3 by equalmatt
- … please reply with links to others I may have missed
See the presentation/slide we would use for the exercise: Design Thinking Exercise on Improving the Cooperative Experience - Google Präsentationen
To restate the steps involved in this co-design session:
- Agree on the plan
- Fix a date for the intro and kick-off call for the asynchronous co-design session
- Explain the process and do a live demo here in the dedicated category of the Co-opCreds Discourse instance to show how it would work
- Everyone partakes in the asynchronous co-design session for 1 - 2 weeks
- After 2 weeks, collate findings and allow another 1 - 2 weeks for community deliberation and structuring of shared findings
- After 2nd set of 2-week deliberations, share finalised results from the co-design
Our next first step is for all of us to share our thoughts on this process and fix a date for the call and start of the session.
So what do we think of this process?
and …
When do we want the first call to be?
