Skip to content

Stakeholders workshop

Jump to bottom
Jim Kosem edited this page Dec 4, 2019 · 10 revisions

14 Nov 2019

Workshop format and intent

We conducted a remote workshop based on the Lightning Decision Jam format to first look at the stakeholder concerns with browsers, the address bar in browsers in particular and P2P. Secondly, we used the workshop to prioritise these issues and concerns to look at possible directions to focus on with future research and design.

There were three stakeholders (Dietrich, Marcin and Henrique participating with Jim facilitating the 50 minutes of collaboration and co-creation.

The Lightning Decision Jam (LDJ) is an excellent format for laying out the issues, starting with everything that anyone can think of as an issue, concern or possible thing to do and then going through rounds of voting and deciding on what is important. Each round produces a more granular set of results. Finally, we come to a graph like we see below where everything is mapped out on the matrix according to how much impact the thing would have and how hard it is to do.

Findings

The Impact-Effort Matrix resulted in ideas around what could amount to semi-transparent actions to the user which could be quite intersting. This goes along with user and expert research around the end-user actually needs to know and see and trusting that all is well otherwise with the actions and transactions involved. Complementing this is the idea of having notifications and alerting the user that they would be in a p2p mode in the browser.

In terms of impact vs effort the results would be the following

  1. Include a hint in copied URL with IDs/addresses of (n) nodes that are known to have content
  2. Default to HTTP url to a gateway. people with ipfs shall get redirected
  3. Use p2p notification system in addition to content load
  4. Explanatory language in link convention (s/ipfs/share/)
  5. Have gateway pwa with embedded node
  6. Really good icons

However, in terms of time taken to develop they would be ranked as follows

  1. Really good icons
  2. Explanatory language in link convention (s/ipfs/share/)
  3. Use p2p notification system in addition to content load
  4. Default to HTTP url to a gateway. people with ipfs shall get redirected
  5. Have gateway pwa with embedded node
  6. Include a hint in copied URL with IDs/addresses of (n) nodes that are known to have content

Clone this wiki locally