Share research findings
Every open source project is unique
Open source is often a fairly dynamic environment where every team and every project is unique. Below we have some suggestions which you are free to try out and see what works best for the team.
Most open source projects in the bitcoin and lightning ecosystem have a culture of openness, transparency, and decentralisation. The guidelines below are aimed at creating a culture where
Everyone's voice is heard
Decisions are made collaboratively
People are encouraged to work together and ideate on solutions
User insights are easy and accessible for the rest of the team to understand
The steps
Present a high level overview of the project itself
Providing context for what you are communicating is important. Since many open source bitcoin and lightning projects have contributors jumping onto the project at various stages of the project lifecycle, taking the audience into account is key.
Provide a high level overview of the project for any new people joining the call.
Provide some insights into what the project is looking to achieve.
If there is a project management folder in Github, feel free to share that as well.
Resource: Roadmap figma file
Show the roadmap
Share the ideas you have with the team about the research that you have already done. This will allow the team an opportunity to ask questions, make suggestions and also offer to help out. You can do this in many ways:
Quick and easy, step by step overview using a diagram on Figma.
A more roadmap style showing what you’ve done and what you’ll be doing in the future.
Share a brief outline of the user persona you are building for at this stage. This is contextual and depends on who you are sharing the research with.
Present data
There are various options with presenting the users voices to the team:
User comments and ask “How can we?” (see below)
User comments and insights
Tips on presenting:
Grab a screenshot of the screen by taking a screenshot or from the Figma file
Showcase a maximum of 5 user comments per screen state
Use an arrow or circle with numbers to indicate that you are specifically referring to a button of a part of the design
You are simply sharing the voice of the users, their pain points, their struggles with the interface. Oftentimes this can be a very educational and enjoyable process for the whole team. The user comments can be shared using; Figma, Penpot, images, slides.
It also helps to be specific on which part of the user flow that is being presented. For example; let’s say we did research on the entire user flow of a lightning wallet. Presenting a snippet of just the user comments from the onboarding section could help with bucketing the solution process to being specific to that part of the interface.
Ask “How can we?”
The data from the research could be presented visually (see example above), and then the whole team is asked to come up with a solution together by asking the question “how can we?”
Trusting the intelligence and the knowledge of the entire team brings a richness and a unique dynamic with the solution building process. It allows for the feeling of “we are building together” and this allows for a dynamic within the team where everyone's voice feels heard. It is also a decentralised approach to problem solving.
The dynamics of how the projects is worked on varies from project to project and so after presenting you as a team can then decide how to move forward.
Some teams prefer to work mostly asynchronously.
Teams could be spread across the globe.
People join open source projects and may occasionally contribute
Links to examples: