This repository was archived by the owner on Jun 2, 2020. It is now read-only.
User testing: IPFS Colorado in-person test day #355
Labels
dif/medium
Prior experience is likely helpful
effort/days
Estimated to take multiple days, but less than a week
topic/design-ux
UX strategy, research, not solely visual design
User Testing Summary
Event
IPFS Colorado User Testing Day
Boulder, Colorado, 16 Oct 2019
In conjunction with Ethereum Boulder, we co-hosted a free full-day event for anyone interested in or already experienced with IPFS and the decentralized web. Participants during the daytime event were offered a day of free coworking at The Peregrine, plus some delightful IPFS swag, in exchange for a half-hour, in-person interview.
Evening participants were treated to an "IPFS Basics" interactive presentation from ProtoSchool chapter organizer and community dude extraordinaire @nukemandan. Plus more fun IPFS swag! You can view the presentation here.
Researchers
@ericronne and @jessicaschilling
Methods
Participants RSVP'd ahead of time, but it wasn't possible to discern clearly what their existing level of interest in or involvement with IPFS was; keeping this in mind, we opted to keep testing extremely open-ended and conversational, leading with some initial interest/skill inventory questions and from there discussing one or more artifacts depending on their response: an outline version of our proposed beta site navigation structure (worked in issue #273), the "no content here yet" page proposed for our beta site (worked in issue #342), and/or our goal-based IPFS user personae (see Mural doc).
We had eight participants with a widely varying degree of existing expertise, a broad variety of reasons for caring about IPFS and the dweb, and a very wide-ranging spectrum of goals and end-game interests. Identifying characteristics have been removed in our interview notes to protect privacy.
Take-aways
Please view the full test summary here for all the take-aways!
TLDR: This exercise was primarily a level-setting endeavor; we were hoping to confirm/deny overall validity of our foundational efforts in Q3 and the beginning of Q4 2019 before going full-tilt into building out the new docs beta site. While we definitely received insights that changed some details of the build, it was encouraging to see that there weren't any significant holes in our approach so far. This test also provides us with a useful baseline for comparison for future user tests on the docs beta in Q4 -- as well as some wonderful Colorado connections for future rounds of testing!
Test day artifacts
The text was updated successfully, but these errors were encountered: