Most multi-step process UI patterns include something for a "which step am
I on" wayfinding, the big question is usually how few steps can you get
away with not showing this UI element, 2? 3? 4? its murky. Since we don't
have that many complex multi-step processes, this was an idea to sidestep
the whole issues. button is blue, "I'm not done," button is green, "I'm
done"  I think it will be a subtle distinction for most users, some may not
even notice, and thats fine. If in the end we declare it a total failure we
can just clone mw.ui.button.constructive over mw.ui.button.progressive and
call it a day.  The rules for when you use one over the other are pretty
clear in most cases. In general we always look to existing patterns we can
borrow or steal, but sometime we invent something new. This is that case,
we could use one of the many breadcrumbs, pagination hacks, progress bars,
etc. but these feel over-designed for our simple 2-3 step processes, and
are more cognitive weight for users that we really want. We could try to
use an off the shelf pattern and adjust it for our needs, or we could try
something new. let's try something new.

p.s. Preview would be a progressive action, not a neutral one, since the
user would need to Save to finish the process flow of making an edit.



*Jared Zimmerman * \\  Director of User Experience \\ Wikimedia Foundation

M : +1 415 609 4043 |   :  @JaredZimmerman<https://twitter.com/JaredZimmerman>



On Wed, Nov 6, 2013 at 10:29 PM, Steven Walling <[email protected]>wrote:

>
> On Wed, Nov 6, 2013 at 10:15 PM, Jared Zimmerman <
> [email protected]> wrote:
>
>> I'd like to propose we go with "*N*eutral, *P*rogressive, *D*estructive,
>> and *C*onstructive" for the actual names in code.
>>
>
> I've heard a bit about this before, but I'm still confused about why there
> need to be different Progressive and Constructive button types.
>
> I think as far as users are concerned, there are only essentially two
> kinds of buttons they look for: Yes or No. (e.g. Confirm or Cancel, Save or
> Discard, and so on). We definitely need a neutral button type for "third
> options" like Preview or Review changes. But two types representing
> positive response and moving forward? Seems like we're maybe
> overcomplicating things.
>
>
> --
> Steven Walling,
> Product Manager
> https://wikimediafoundation.org/
>
> _______________________________________________
> Design mailing list
> [email protected]
> https://lists.wikimedia.org/mailman/listinfo/design
>
>
_______________________________________________
Design mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/design

Reply via email to