We met with @cynthia, @enrico and @simone at the OuiShare Fest in July and asked ourselves some questions about what works well / what are our bottlenecks / and we shared some ideas on how to get over those bottlenecks. In order to prepare the get together in Australia, we propose here to focus on one of the main aspects that came up in that discussion : the product vision and technical strategy.
A - Why ? The outcome expected from Aus gathering.
Our intention for the Aus gathering is to get a better vision of the product we collectively develop and a clear action (common roadmap) plan that we can then enforce.
That means understanding :
- Who are our respective targets in every instance ? How do they organize ? What do they need in terms of features ? What does OFN already covers and what’s missing ? > Our targets priorities will be our priorities as an instance.
- From that what is the product vision : what are the technical implications, evolutions needed ? In terms of architecture, features, review and merging processes ?
We would like to come up at the end of the Aus gathering with the following deliverables :
- A written product vision so that we can come back to it if needed when prioritizing
- A roadmap, with action items organized by priorities
- A team & process for product curation (facilitate the discussions if request to change something in the roadmap, curate re-prioritization in a non-bureaucratic way)
- A clear and agreed upon development process (so that we can become more agile and answer quicker our users needs)
B - The discussion we had at OuiShare Fest on product vision
We realized that we didn’t share exactly the same vision of where we would like the product to go, what we wanted it to do, and for whom. The need to write down our product vision arose, and the need also for a curation team and light process to identify the common priorities, depending not only about who has the money to pay a feature, but on a common product strategy.
We thought of a 4 step plan:
a = our vision of our dreamy product in each instance. Are our local realities different, and if yes, what are the differences? Do we manage to attract the users we want (customer acquisition) ? Who are our respective targets, what are their needs, and does OFN meets their needs ?
b = share and identify a common product vision that we all agree on. Based on the analysis and understand of each instance product vision, we can build a common product vision that would answer those various instance needs. But we can’t do all at the same time, and if each instance has its own roadmap, our product will end up not being consistent, if we all pull the product in different directions. So we need to build a common roadmap.
c = list the priorities for each instance and ask each instance to rate them to identify the shared priorities. That will help us build a common roadmap that would take into account the various instances priorities.
d = designate a curation team (2/3 people?) in charge of facilitating the roadmap implementation, and curating discussions if an instance wants to change something in this roadmap (new emerging priority, etc.) Bugs and tech debt can also be prioritized by the curation team.
C - We need your inputs and views to get prepared for the Australian gathering !
We have prepared some share documents to facilitate that collective journey on product vision, and make your life easier. So you don’t have to start from a blank page ! We have written down with @enrico three “base documents” on which we propose you to add your views :
(to open the mindmup document, you need to click on “open with / connected app / mindmup”. If you have difficulties to open them, go in the OFN global drive, this folder, and open the files with mindmup)
1 > What is the general offer of a local OFN instance (beyond the marketplace):
OFN share offer
I started that based on a French reflexion, but can serve as a base maybe for a more general reflexion of the OFN offer. Add anything that’s missing, suggest rephrasing by adding new bubbles / modify existing ones.
2 > Who we want our marketplace to serve and how are they working ? (step before identifying their needs) :
The OFN target board
Add any target we have forgotten and fill in the info about this target if we missed something. And feel free to add any comment in your instance column if you want to specify how you tried to work with some targets but it didn’t work, etc.
User stories mapping
We have put only some main user stories here, some might be super large and we will need to split them. User stories are usually not serving one specific target, various targets share the same needs. We express the needs from the role of a user. If some user stories are really specific to one target, then we can add a “target tag” on this user story.
Add any important user story or corresponding solution that’s important and missing.
4 > From those unmet needs identified, what are the priorities ?
User stories mapping
Again in the same file, add a “country tag” to the priority solutions you think we should work on. We allow each instance 5 instance tags !!! (I put the 5 French tags already, use the same color and change the tag name !)
This will help us through the reflexion on the technical choices to come, and will help us structure and propose a common roadmap to the community.
Due date : ideally 14th november, the latest 1st december.
D- Your job for the next global Zoom 14th November
So that we can move forward on the product vision, and the technical evolutions to serve that vision (modularization ? backend and connexion with multiple front ends through powerful API ? micro-service architecture ?) we would like to dedicate the next ZOOM session to hear every local instance vision / feedbacks from the exercise above. Please get prepared for a 5-7 min pitch each .
Estimate preparation time : 2 hours
FEEL FREE TO ADD ANY SUGGESTION TO IMPROVE THAT PROCESS