It is often easy to read up on things but harder to imagine how to act based on what you read. The idea: have videos with small worked examples how we do use design and research methods, each 3-10min long showing a realistic, even if shortened work process and collect them.
Expert Review of and existing UI
Needs: A UI with no terrible, but findable issues
Using heuristics
Going though the UI
Writing down possible problems
Doing a remote think-aloud test
Needs: Simple website and a simple task
Focus on the think-aloud part, something like an open source version of the Nielsen example video
Since there are lots of explainers and articles on the internet, can we collect a few ways that we want this to differ? Put another way: why should we do a How To UX when so many others already have?
Iād propose, to start:
We donāt use terms like āmarketā or ācustomerā or ācompetition,ā we assume that the end goal is usability rather than growth
We donāt recommend or model expensive tools
We emphasize informed consent, minimal data collection, and data protection when explaining methods that involve users (how do you all feel about the term āusersā?)
Moreā¦?
We showcase free and open source tools and applications that can support execution, capture and analysis of research
We emphasise qualitative methods, as both more useful and productive for design purposes, and potentially more sensitive to privacy issues when combined with anonymisation techniques and good data handling practices.
We encourage a progression from user-centred to more participatory methods.
We position participating in research as a form of contribution to free and open source software.
PS: āusersā still much better than consumers or customers, as far I am concerned. But in general I prefer āpeopleā.
Since there are lots of explainers and articles on the internet
My main idea of differentiation is providing a worked example instead of a āgeneralā instruction. This would already be a lot.
But I certainly like what you suggested, as well.
We emphasize informed consent, minimal data collectionā¦
Yes. I guess the example format is not good for a general discussion of these but Iād love to show some in-situ, e.g. how to ask for and react to a participant wanting to skip a question or not wanting a recording.
The questions in the suggested format would rather be: Which situations and actions do we want to show as topics are probably far easier to cover in a written, general article (Of which there are many already)
I agree. Can I suggest we āprototypeā 1 or 2 of these videos and just see what happens? As we get feedback, we can tweak/learn/adjust what weād like from them. As a first example: I had a twitter thread this weekend on designing a control panel for a stove top. Not typical FOSS task but a fairly focused and known context that displays process, Visual and UX concerns, tied to how UX needs to prioritize. If that doesnāt seem right, no worries, please reply with another subject we could try.
I like that idea and I think that would fit well. I guess I could not do it (as I do not do a lot of physical design) but you seem to have experience with it, so I think it would be an awesome topic you could demonstrate some basic ideas and processes with.
I could get it started with an expert analysis based on the nielsen heuristics and record that. (Would need to find a good interface for reviewing, though)
This would be a nice little start to gether feedback on.
Would it be a good idea to set aside a 10 min slot in the community monthly calls for someone to do a prototype of a show & tell video with an audience and then have it recorded via jitsi? that way we can test it out as an activity
Here come a couple more: