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

Re: Let's have a user experience workshop

From
Emily Shaffer <emilyshaffer@google.com>
Date
May 16, 2022, 07:43 UTC
Message-ID
<CAJoAoZnP47PT9EQYkNib9+_a-Qg=HxhjowgUx7qJ1V7=KY5iiA@mail.gmail.com>
In-Reply-To
<YoEnsb2UpDwdjDpd@google.com>
On Sun, May 15, 2022 at 6:17 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 31 quoted lines
>
> (bcc-ing workshop attendees again)
> Hi,
>
> Emily Shaffer wrote:
> > On Mon, May 9, 2022 at 8:35 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
>
> >> 1. Continuing the conversation
> >>
> >> I and some others (e.g. David, cc-ed) ended the workshop wanting to
> >> discuss a little more --- when deciding (1) what to work on and (2)
> >> settling on a design for that work, what has worked well for us in the
> >> past?  What didn't work?  What research methods have we tried?  What
> >> would we like to try?  We mentioned wanting to continue that
> >> discussion on-list, so trying that now. :)
> [...]
> > For all 4 of the above - I wonder whether it really makes sense to try
> > and organize those things asynchronously. If I'm being honest, what
> > I'd much prefer would be a monthly-or-so working group meeting with
> > other folks interested in performing research, making recommendations,
> > learning how to improve Git's UX, etc. I'd absolutely make time to
> > attend such a thing, and I believe it would be the easiest way to
> > organize research and concert our efforts. Would other folks be
> > interested in showing up, too?
>
> Interesting!  I'd also enjoy a meet-up, but e.g. for "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.

Oh, thanks for clarifying. I agree waiting for some monthly user feedback session wouldn't be ideal; rather, I'd like to see that kind of meeting establish a process for getting user feedback sooner. Right now I think it's a little intimidating to say "let's just start getting user feedback" with no other instruction.

Show 9 quoted lines
>
> > 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. It might be nice to have Alice along for at
> > least the first couple of sessions to answer questions and help us
> > learn in a bit more targeted direction than we got at the workshop.
>
> Sounds nice to me.  If others turn out to be also interested, then
> what would be the next step for making that happen?

Seems like we can go the typical route - vote for timezones and put it on tinyurl.com/gitcal - but I'll wait to see more people than just you and I talking about it before we do that ;)

Show 8 quoted lines
>
> Thanks,
> Jonathan
>
> --
> You received this message because you are subscribed to the Google Groups "Git UX" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to git-ux+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/git-ux/YoEnsb2UpDwdjDpd%40google.com.
Previous: Jonathan NiederNext: Alice Merrick
Message 12 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.