From: <email@example.com> To: "'Alice Merrick'" <firstname.lastname@example.org>, "'Emily Shaffer'" <email@example.com> Cc: "'Jonathan Nieder'" <firstname.lastname@example.org>, "'Git List'" <email@example.com>, "'David Aguilar'" <firstname.lastname@example.org> Subject: RE: Let's have a user experience workshop Date: Fri, 20 May 2022 12:22:33 -0400 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <CA+Yb-VQx2CMixGh6GExce9n=QxR-esuhPuuHwzfDKYNow4Zyzw@mail.gmail.com> On May 20, 2022 12:18 PM, Alice Merrick wrote: >>"3. Testing ideas >> with users" I would find it worrisome if getting user input would >>require reviews on a given patch stalling out until the next monthly >>meeting. (Reviews are already slower than they should be as it is!) I >>don't know that that's what you meant to suggest; I'm just aiming to >>understand what you mean about the "all 4" above. > >I agree, you wouldn't want to wait until something is in review to get user >feedback or testing. I think a Lean UX >(https://www.scaledagileframework.com/lean-ux/) approach would be more >appropriate especially when there is no designated UX person. You might need to >lean more heavily on design standards and instrumentation for feedback, but >sessions with users would still be important for developing standards and could be >used as needed if it's not possible to do them on a regular basis. > >> > > I'd envision it as something between a working group and a book >> > > club - we could learn different aspects of UX design and research, >> > > and apply them in various ways. > >I like this idea. A working group could work on developing design standards and >work out what to measure and how to measure it. I would imagine that some patch series do not directly impact UX while others do. Figuring out which are what might be a starting point. In some places, an API change would be UX - if the users are developers. Just a thought. --Randall
prev parent reply other threads:[~2022-05-20 16:22 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-15 21:04 Alice Merrick 2022-03-16 17:36 ` Philip Oakley 2022-03-16 17:48 ` Emily Shaffer 2022-03-16 21:50 ` Philip Oakley 2022-03-16 20:10 ` Michal Suchánek 2022-03-16 20:41 ` Emily Shaffer 2022-03-16 21:34 ` Michal Suchánek 2022-03-16 22:05 ` Junio C Hamano 2022-05-10 3:35 ` Jonathan Nieder 2022-05-12 22:23 ` Emily Shaffer 2022-05-15 16:17 ` Jonathan Nieder 2022-05-16 7:43 ` Emily Shaffer 2022-05-20 16:17 ` Alice Merrick 2022-05-20 16:22 ` rsbecker [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --firstname.lastname@example.org' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='RE: Let'\''s have a user experience workshop' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).