Let's have a user experience workshop

Let's have a user experience workshop

[Alice Merrick]

Hello Git,

I’m doing a 20% project with the Git Core team at Google. I've been
encouraged by Emily Shaffer and Jonathan Nieder to reach out to the
Git community to help incorporate UX practices into the Git
development cycle. My goal is to 1) gauge interest in improving Git's
user experience and 2) recruit interested folks in organizing or
attending a workshop where you can learn more about what UX is and
discuss ways to bake UX into the process of making changes to Git to
improve the experience for all users.

Some additional context about me: I am a UX (user experience)
professional at Google. I have experience applying UX and
accessibility practices[1] to developer tools for searching,
reviewing, debugging code, etc. For the past couple years I’ve worked
with the Golang project on their websites and helped set project
priorities by collecting community feedback through their annual
developer survey[2].

Interested?
* Join the git UX Google group (https://groups.google.com/g/git-ux) if you
are interested in participating in an event.
* Reply directly to this email if you are interested in organizing the
event to discuss git UX (scheduling the event, sending invites,
communicating with invitees)


[1] https://doi.org/10.1145/3411764.3445544
[2] https://go.dev/blog/survey2020-results

-- 

Alice Merrick | UX Researcher | amerrick@google.com | 206-785-7532

Re: Let's have a user experience workshop

[Philip Oakley]

Hi Alice,

On 15/03/2022 21:04, Alice Merrick wrote:
> Hello Git,
>
> I’m doing a 20% project with the Git Core team at Google. I've been
> encouraged by Emily Shaffer and Jonathan Nieder to reach out to the
> Git community to help incorporate UX practices into the Git
> development cycle. My goal is to 1) gauge interest in improving Git's
> user experience and 2) recruit interested folks in organizing or
> attending a workshop where you can learn more about what UX is and
> discuss ways to bake UX into the process of making changes to Git to
> improve the experience for all users.
>
> Some additional context about me: I am a UX (user experience)
> professional at Google. I have experience applying UX and
> accessibility practices[1] to developer tools for searching,
> reviewing, debugging code, etc. For the past couple years I’ve worked
> with the Golang project on their websites and helped set project
> priorities by collecting community feedback through their annual
> developer survey[2].
>
> Interested?
> * Join the git UX Google group (https://groups.google.com/g/git-ux) if you
> are interested in participating in an event.
I joined the group, but there are no current entries, and, at present I
can't post anything.

I am interested in the UX from the perspective of Human Error and how we
form our mental models of the task at hand (e.g. see historic
discussions about the 'staging area').

Git does have rather a lot of non physical concepts to grasp, and now
that it's way beyond being just an SCM for the Linux kernel, the user
base has become rather diverse.

I'm a retired systems engineer who worked in defence electro-optics in
the UK. I am mainly on Windows.

> * Reply directly to this email if you are interested in organizing the
> event to discuss git UX (scheduling the event, sending invites,
> communicating with invitees)
>
>
> [1] https://doi.org/10.1145/3411764.3445544
> [2] https://go.dev/blog/survey2020-results
>
--
Philip

Re: Let's have a user experience workshop

[Emily Shaffer]

On Wed, Mar 16, 2022 at 10:38 AM Philip Oakley <philipoakley@iee.email> wrote:

> > Interested?
> > * Join the git UX Google group (https://groups.google.com/g/git-ux) if you
> > are interested in participating in an event.
> I joined the group, but there are no current entries, and, at present I
> can't post anything.

I can shed a little light here. I set up the list; for now, it's
primarily intended for use as a roster for a future live event
(similar to, but smaller scale than, the diversity/equity/inclusion
workshop we had a couple of years ago). Maybe after the event it will
be useful to open that list up for posting, but if I'm being honest,
I'd personally prefer to keep discussions about Git's UX on git@vger,
where everybody can participate. Hopefully that rationale clears up
why you're unable to post or see anything there. :)

 - Emily

Re: Let's have a user experience workshop

[Philip Oakley]

Hi Emily,

On 16/03/2022 17:48, Emily Shaffer wrote:
> On Wed, Mar 16, 2022 at 10:38 AM Philip Oakley <philipoakley@iee.email> wrote:
>
>>> Interested?
>>> * Join the git UX Google group (https://groups.google.com/g/git-ux) if you
>>> are interested in participating in an event.
>> I joined the group, but there are no current entries, and, at present I
>> can't post anything.
> I can shed a little light here. I set up the list; for now, it's
> primarily intended for use as a roster for a future live event
> (similar to, but smaller scale than, the diversity/equity/inclusion
> workshop we had a couple of years ago). 

Could you at least add a post to the group (doesn't need to be sent out)
to that effect, so that the UX of those that register is informative?
> Maybe after the event it will
> be useful to open that list up for posting, but if I'm being honest,
> I'd personally prefer to keep discussions about Git's UX on git@vger,
> where everybody can participate. 
I'd be reasonably happy with that. An initial event would help clarify
expectations.

> Hopefully that rationale clears up
> why you're unable to post or see anything there. :)
>
>  - Emily

Re: Let's have a user experience workshop

[Michal Suchánek]

Hello,

On Tue, Mar 15, 2022 at 02:04:09PM -0700, Alice Merrick wrote:
> Hello Git,
> 
> I’m doing a 20% project with the Git Core team at Google. I've been
> encouraged by Emily Shaffer and Jonathan Nieder to reach out to the
> Git community to help incorporate UX practices into the Git
> development cycle. My goal is to 1) gauge interest in improving Git's
> user experience and 2) recruit interested folks in organizing or
> attending a workshop where you can learn more about what UX is and
> discuss ways to bake UX into the process of making changes to Git to
> improve the experience for all users.
> 
> Some additional context about me: I am a UX (user experience)
> professional at Google. I have experience applying UX and
> accessibility practices[1] to developer tools for searching,
> reviewing, debugging code, etc. For the past couple years I’ve worked
> with the Golang project on their websites and helped set project
> priorities by collecting community feedback through their annual
> developer survey[2].
> 
> Interested?
> * Join the git UX Google group (https://groups.google.com/g/git-ux) if you
> are interested in participating in an event.
> * Reply directly to this email if you are interested in organizing the
> event to discuss git UX (scheduling the event, sending invites,
> communicating with invitees)

Can you, please, use a sane mailing list for the discussion?

The user experience of Google Groups really bad.

Also it seems it is accessible only to people with a google account.

Could you use a more inclusive technology?

Thanks

Michal

Re: Let's have a user experience workshop

[Emily Shaffer]

On Wed, Mar 16, 2022 at 1:11 PM Michal Suchánek <msuchanek@suse.de> wrote:

> > * Reply directly to this email if you are interested in organizing the
> > event to discuss git UX (scheduling the event, sending invites,
> > communicating with invitees)
>
> Can you, please, use a sane mailing list for the discussion?
>
> The user experience of Google Groups really bad.
>
> Also it seems it is accessible only to people with a google account.
>
> Could you use a more inclusive technology?

Git already uses Google Groups for the security list (e.g. for fixing
pre-disclosure security issues) and for the mentoring list, and it's
fine to subscribe to one with a non-Google account; it acts just as a
normal mailing list in your inbox. Anyway, as I mentioned in
https://lore.kernel.org/git/CAJoAoZn91dyFEdMKUj_XU8CjUbh5EtdqjTR3CaAe%3DBhii7dt3Q%40mail.gmail.com,
the list mostly serves as a roster, not as a place for discussion.

 - Emily

Re: Let's have a user experience workshop

[Michal Suchánek]

On Wed, Mar 16, 2022 at 01:41:59PM -0700, Emily Shaffer wrote:
> On Wed, Mar 16, 2022 at 1:11 PM Michal Suchánek <msuchanek@suse.de> wrote:
> 
> > > * Reply directly to this email if you are interested in organizing the
> > > event to discuss git UX (scheduling the event, sending invites,
> > > communicating with invitees)
> >
> > Can you, please, use a sane mailing list for the discussion?
> >
> > The user experience of Google Groups really bad.
> >
> > Also it seems it is accessible only to people with a google account.
> >
> > Could you use a more inclusive technology?
> 
> Git already uses Google Groups for the security list (e.g. for fixing
> pre-disclosure security issues) and for the mentoring list, and it's
> fine to subscribe to one with a non-Google account; it acts just as a

The link you provided only allows access with a Google account. If there
is one that allows access in other ways it was not provided.

Please try to use open technologies that are accessible to everyone, not
only people affliated with one specific company.

Thanks

Michal

Re: Let's have a user experience workshop

[Junio C Hamano]

Emily Shaffer <emilyshaffer@google.com> writes:

> Git already uses Google Groups for the security list (e.g. for fixing
> pre-disclosure security issues) and for the mentoring list, and it's
> fine to subscribe to one with a non-Google account; it acts just as a
> normal mailing list in your inbox.

I think the groups.google URL is not the one that acts just as a
normal mailing list.  <git-ux@googlegroups.com> address may be what
needs to be advertised.

I would prefer to see such a discussion on this list, too, not on a
separate place people need to subscribe to, though.

Thanks.

Re: Let's have a user experience workshop

[Jonathan Nieder]

(bcc-ing git UX workshop attendees as a heads up)
Hi,

Alice Merrick wrote[1]:

>                    My goal is to 1) gauge interest in improving Git's
> user experience and 2) recruit interested folks in organizing or
> attending a workshop where you can learn more about what UX is and
> discuss ways to bake UX into the process of making changes to Git to
> improve the experience for all users.

Thanks, Alice!  I enjoyed the workshop.  There are some notes at [2],
which perhaps someone may want to summarize for the mailing list.

A few bits I took away:

0. Examples

The examples Alice gave, especially from the Go project (generics as a
UX project!) were interesting and helpful.

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. :)

2. Sharing research

Some of us are already doing some research, in the form of surveys,
metrics collection, testing with prototypes, analyzing user issues in
internal bug trackers, and so on.  It would be nice to share that
more, so different participant's studies can build on each other.

I'm curious about what a good form for that is in an open source
project.  Should we send findings as papers to the mailing list?  Do
we want some kind of repository (using git, Figma, or some other tool)
of findings that we build together collaboratively?  Whatever we do is
likely to involve some extra work to deal with confidentiality; how do
we notice when something is worth the work of jumping through that
hurdle?

3. Testing ideas with users

It's not unusual for there to be a question on-list about some facet
of the UI such as an option name, that ends up being decided as a
matter of taste.  Alice mentioned that we have a chance to make more
user-focused decisions by just talking to a few users, which can be as
simple as recruiting five users from #git on IRC and sending them a
private message asking questions like "Suppose you have just run this
command; what would you run next? What would you expect that command
to do?"  This seems like a straightforward addition to our workflow
that we could get better at over time.

Do you agree?  If this is a good idea, how would we like to go about
it?  (E.g., how do we notice when there's a question that could
benefit from that kind of experiment, how do we come up with the
questions for users, and how do we present the results?)

4. Stating assumptions about users

Another theme was that when we choose what to work on and form designs
for our work, we regularly make numerous assumptions about users'
desires and goals, habits, what will be intuitive for them, and so on.
Stating these assumptions would have a few benefits:

- they would make the rationale behind a design clearer, which makes
  it easier to continue to honor that design in the future;

- when those assumptions turn out to be false, it would be easier to
  revisit early design decisions;

- they could give interested people ideas for how to follow up and
  check those assumptions;

- over time a clearer model of the user would emerge that could be
  useful to make use of in later designs

The downside, of course, is that it can be embarrassing to make
assumptions that turn out to be wrong, but that seems like a small
downside relative to those benefits.  So I am thinking it could make
sense for us to make a concerted effort to describe these kinds of
assumptions in commit messages more often.  If this seems like a good
idea, I'd be happy to send or review a patch to SubmittingPatches
saying as much.  What do you think?

5. Bug tracker

For many open source projects, a bug tracker is what allows someone to
follow a particular effort without having to "drink from the firehose"
of the full mailing list.  That's particularly likely to be helpful
when bringing in contributors such as designers who do not necessarily
live the same mailing list based lifestyle.

In [3] we (somewhat tongue-in-cheek) suggested using Bugzilla as a bug
tracker that would be equally undesirable to everyone, but it doesn't
seem to have gone anywhere.

I suspect GitLab's issue tracker might be fine in that respect as
well.  Would it be worth setting up a bug tracker there?  (Just like
with the Linux kernel's and with the existing crbug.com/git, I'm
imagining a bug tracker would mostly consist of pointers to the
mailing list, but it would still be useful for someone wanting to
following along and help with an issue.)

Thanks,
Jonathan

[1] https://lore.kernel.org/git/CA+Yb-VSaeKy-g_ywkZzQuEX=k3EXM+Ky-rHOb2az0SHGVbdaVw@mail.gmail.com/
[2] https://docs.google.com/document/d/1KDThcte2NHnzZBVXG7lHlqCQNzict6EIpOe9Z1iXEMg/edit
[3] https://lore.kernel.org/git/20211021134105.ziqmcknnpdsg6cvc@meerkat.local/

Re: Let's have a user experience workshop

[Emily Shaffer]

On Mon, May 9, 2022 at 8:35 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
> A few bits I took away:
>
> 0. Examples
>
> The examples Alice gave, especially from the Go project (generics as a
> UX project!) were interesting and helpful.
>
> 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. :)
>
> 2. Sharing research
>
> Some of us are already doing some research, in the form of surveys,
> metrics collection, testing with prototypes, analyzing user issues in
> internal bug trackers, and so on.  It would be nice to share that
> more, so different participant's studies can build on each other.
>
> I'm curious about what a good form for that is in an open source
> project.  Should we send findings as papers to the mailing list?  Do
> we want some kind of repository (using git, Figma, or some other tool)
> of findings that we build together collaboratively?  Whatever we do is
> likely to involve some extra work to deal with confidentiality; how do
> we notice when something is worth the work of jumping through that
> hurdle?
>
> 3. Testing ideas with users
>
> It's not unusual for there to be a question on-list about some facet
> of the UI such as an option name, that ends up being decided as a
> matter of taste.  Alice mentioned that we have a chance to make more
> user-focused decisions by just talking to a few users, which can be as
> simple as recruiting five users from #git on IRC and sending them a
> private message asking questions like "Suppose you have just run this
> command; what would you run next? What would you expect that command
> to do?"  This seems like a straightforward addition to our workflow
> that we could get better at over time.
>
> Do you agree?  If this is a good idea, how would we like to go about
> it?  (E.g., how do we notice when there's a question that could
> benefit from that kind of experiment, how do we come up with the
> questions for users, and how do we present the results?)
>
> 4. Stating assumptions about users
>
> Another theme was that when we choose what to work on and form designs
> for our work, we regularly make numerous assumptions about users'
> desires and goals, habits, what will be intuitive for them, and so on.
> Stating these assumptions would have a few benefits:
>
> - they would make the rationale behind a design clearer, which makes
>   it easier to continue to honor that design in the future;
>
> - when those assumptions turn out to be false, it would be easier to
>   revisit early design decisions;
>
> - they could give interested people ideas for how to follow up and
>   check those assumptions;
>
> - over time a clearer model of the user would emerge that could be
>   useful to make use of in later designs
>
> The downside, of course, is that it can be embarrassing to make
> assumptions that turn out to be wrong, but that seems like a small
> downside relative to those benefits.  So I am thinking it could make
> sense for us to make a concerted effort to describe these kinds of
> assumptions in commit messages more often.  If this seems like a good
> idea, I'd be happy to send or review a patch to SubmittingPatches
> saying as much.  What do you think?

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?

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.

 - Emily

Re: Let's have a user experience workshop

[Jonathan Nieder]

(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.

> 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?

Thanks,
Jonathan

Re: Let's have a user experience workshop

[Emily Shaffer]

On Sun, May 15, 2022 at 6:17 PM Jonathan Nieder <jrnieder@gmail.com> wrote:
>
> (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.

>
> > 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 ;)

>
> 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.

Re: Let's have a user experience workshop

[Alice Merrick]

>"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

RE: Let's have a user experience workshop

[rsbecker]

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