@iamjessklein and I just talked about this during our meeting. The task description reflects our latest thinking.

The videos and feedback from the testing sessions @Esanders ran at the Hackathon are here: VE mobile testing, Prague 2019.

Next steps

• Tomorrow (21-May), @Esanders, @iamjessklein and I will document feedback and steps for our next iteration. See: T220385#5198097

In T223178#5198112, @ppelberg wrote:

Next steps

• Tomorrow (21-May), @Esanders, @iamjessklein and I will document feedback and steps for our next iteration. See: T220385#5198097

☝️ see: T220385#5205295

Testing learnings

In addition to what we learned about the prototypes (see VE mobile testing, Prague 2019), we also learned some things we can improve for our next live user testing session.

Those learnings live here for now: Guerrilla testing learnings: Prague Hackathon 2019

Bring 2 devices: one for testing; one for recording

• This would resolve a couple issues we encountered at the Hackathon:
  • 1) Tester would not need to turn off their notifications. Contributors don't want the contents of their notifications/messages recorded and shared
  • 2) Tester and test administrator would not need to share a link to the prototype(s) via email/SMS/etc.

Create note taking template ahead of time

• "Test administrator" shouldn't have to think about a) Where do I take notes? and b) What format should I take notes in?

Prototype: don't "middle"

• It's better to have a lower fidelity prototype (that does not look finished and will not create an expectation that it is) or an interactive prototype (read: high fidelity) that looks and functions as if it's real.
• Middling in between, as we did for this test, is potentially distracting to the tester in so far as the prototype looked real enough that people expect it to behave like the real thing (i.e. being able to place the cursor anywhere).

31-May | Update

• Post learnings to Edit cards project page