git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Let's have a user experience workshop

From
AMAlice Merrick <amerrick@google.com>
Date
May 20, 2022, 16:17 UTC
Message-ID
<CA+Yb-VQx2CMixGh6GExce9n=QxR-esuhPuuHwzfDKYNow4Zyzw@mail.gmail.com>
In-Reply-To
<CAJoAoZnP47PT9EQYkNib9+_a-Qg=HxhjowgUx7qJ1V7=KY5iiA@mail.gmail.com>
Show 6 quoted lines
>"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.

-- 
Alice Merrick | UX Researcher | amerrick@google.com | 206-785-7532
Previous: Emily ShafferNext: rsbecker@nexbridge.com
Message 13 of 14 in “Let's have a user experience workshop”
  1. Alice MerrickMar 15, 2022
  2. Philip OakleyMar 16, 2022
  3. Emily ShafferMar 16, 2022
  4. Philip OakleyMar 16, 2022
  5. Michal SuchánekMar 16, 2022
  6. Emily ShafferMar 16, 2022
  7. Michal SuchánekMar 16, 2022
  8. Junio C HamanoMar 16, 2022
  9. Jonathan NiederMay 10, 2022
  10. Emily ShafferMay 12, 2022
  11. Jonathan NiederMay 15, 2022
  12. Emily ShafferMay 16, 2022
  13. Alice MerrickMay 20, 2022
  14. rsbecker@nexbridge.comMay 20, 2022

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.