[katello-devel] Nitty gritty UX feedback on System groups

Thu Jun 28 20:44:55 UTC 2012

Hi Malini,

Attached is the screen shot for the System Groups Event History page 
requested in the action items below.

Thanks,
Brad

On 06/22/2012 12:22 PM, Malini Rao wrote:
> Hello everyone,
>
> Thanks for the feedback on email and in the meeting this morning about the feedback I sent.
>
> Here's the summary of what we discussed in the meeting based on my original feedback and the responses received thereafter -
>
> 1. "Just use simple numbers instead of the oval round" - There are black tooltips and white info-tipsies in place in the tool today and the latter can stick upon click and even scroll if necessary. Both need some kind of affordance that a hover state exists and since they are distinguished visually, it will be good to carryover that distinction in the trigger affordance as well. While I wasn't proposing simple text in my original feedback, I feel like we should not use the visual treatment reserved for notifications, alerts and summary rollups for this purpose since it reduces the impact and effectiveness of that treatment for the original purpose. Group did not like the idea of using a link for the number.
>
> ACTION ITEM:
> - Harlan/ Kyle will explore how this can be presented in another way that will work across the board as a pattern for triggering info-tips.
>
>
> 2. "Should not use all caps for title." - I understand this is consistent across the board but it is pretty rare to have all caps for titles as a general UX best practice. This becomes more of an issue when the titles are more than a one word label which is probably how it was used when it was first proposed. Tom's point about potential translation issues is also very valid. I don't think Brad needs to make any change for this page right now but we should reconsider this when updating the styles as part of extending the new Shell styles down to pages and components. Similarly, there was an agreement that the pipe is best used to separate groupings and so we can use the colon consistently when we update the styles.
>
> ACTION ITEM:
> - Harlan/ Kyle will take this ( All caps and Pipe) into account as they are extending the new updated visual feel. We will share these at some point for comments and feedback.
>
>
> 3. "Title too long." - Yes, there can be merits in being more verbose but here, it does not seem to add more value. In general UX best practices for titles is that they should be short, crisp and articulate. The shorter they are, the more they will stand out as titles and allow better scanabilty. Brad explained that there was some feedback on how this was confusing and so he ended up making the title long and no one on the call had objections to shortening this esp since it will be hard to make this a consistent pattern and list all actions possible on any given page as part of the title. The title also seems to be attached only to the top parameters and not the list below which might be adding to the confusion on what is happening on the page. Some of this could potentially be alleviated by pulling the title out of the table.
>
> ACTION ITEMS:
> - Brad to shorten the title.
> - Kyle to send Brad an example of the title displaying outside the tables so Brad can model this fix after it.
>
>
> 4. Events - Brad explained the intended flow and interaction. All agreed that having a link between the status on the install/ update packages page and the event details is important to make the task flow seem more seamless. Seems also like the Events page will likely be more heavy weight with many other types of events that could be possible in the future. Until that point, we will not move the events page from where it is.
>
> ACTION ITEMS:
> - Brad to send UX the events list page so we can have all the screenshots of the interaction flow.
> - UX to propose&  share a way in which the event information can be presented alongside the status of the job on the Packages / errata pages without necessarily having to go find it on the events page ( some ideas talked about were info tips, overlay panels etc.)
>
> Thanks
> Malini
>
>
> ----- Original Message -----
> From: "Brad Buckingham"<bbuckingham at redhat.com>
> To: jrist at redhat.com
> Cc: "Tom McKay"<thomasmckay at redhat.com>, katello-devel at redhat.com, "Malini Rao"<mrao at redhat.com>
> Sent: Friday, June 22, 2012 9:47:28 AM
> Subject: Re: [katello-devel] Nitty gritty UX feedback on System groups
>
> On 06/22/2012 09:34 AM, Jason Rist wrote:
>> On Fri 22 Jun 2012 05:11:32 AM MDT, Tom McKay wrote:
>>>
>>> ----- Original Message -----
>>>> From: "Malini Rao"<mrao at redhat.com>
>>>> To: katello-devel at redhat.com
>>>> Cc: "Brad Buckingham"<bbucking at redhat.com>
>>>> Sent: Thursday, June 21, 2012 4:01:29 PM
>>>> Subject: [katello-devel] Nitty gritty UX feedback on System groups
>>>>
>>>> Hi Brad,
>>>>
>>>> I had made notes of some UX things that struck me as I watched your
>>>> last Sprint demo for system groups. The major functionality looks
>>>> great and these are at a pretty nitty gritty level but nevertheless
>>>> important to fix at some point for the finished product. The only
>>>> slightly bigger topic is where the events page should live and we
>>>> can discuss that. Other than that, if you have any questions, let me
>>>> know.
>>>>
>>>> Thanks
>>>> Malini
>>>> _______________________________________________
>>>> katello-devel mailing list
>>>> katello-devel at redhat.com
>>>> https://www.redhat.com/mailman/listinfo/katello-devel
>>>>
>>>
>>> Slide 1:
>>> + "Just use simple numbers instead of the oval round" - Disagree. The
>>> oval style is an explicit indicator that hovering over it will bring
>>> up a "tipsy" with more information.
>>>
>>> Slide 2:
>>> + "Should not use all caps for title." - This is consistent across
>>> the entire site for titles of tables. Why the change?
>>>
>>> + "Title too long." - If there's room, please retain verbose wording.
>>> A valid reason to reconsider might be if translations to primary
>>> supported languages cause wrapping of title.
>>>
>>> Slide 3:
>>> + "Sub nav should be reconsidered." - Disagree. There are some panels
>>> that are very crowded (eg. Systems).
>>>
>>> + "Events under Details" - Agree. I believe Kyle(?) instigated the
>>> rule that Details always be the first tab with "Events History" under
>>> that. (eg. see Systems)
>>>
>>> + "Event detail should be more closely related to where the action
>>> takes place" - Don't understand. This table is the list of packages
>>> and package groups that are being installed, updated, or removed.
>>>
>>> + "Link to events page" - Agree. That would be nice. However, I am
>>> against having to go to another page to get details about something
>>> that can just as easily be shown inline (eg. through a tipsy). Our UI
>>> is not friendly in switching back and forth between pages at the moment.
>>>
>>> _______________________________________________
>>> katello-devel mailing list
>>> katello-devel at redhat.com
>>> https://www.redhat.com/mailman/listinfo/katello-devel
>> I definitely have to agree with Tom on Slide 1.  I have this to add:
>> "Need to standardize how hover states look – Contact Kyle/ Harlan
>> about that. " - Why? One type of tipsy has help information (black)
>> and one contains expanded information about what you're hovering over
>> (white).  This is established (packages) and common.
>>
>> Agree with Tom on Slide 2 on both points. Why be terse when verbose is
>> so much more helpful and the difference is so minor?  Otherwise it's
>> more unclear and confusing, degrading the user experience.
>>
>> Agree again with Tom on Events under Details.  What should be the
>> default (first showing upon panel expansion) page for this pane? I am
>> not sure that System Group Info or Events would be good/useful.
>>
>> Slide 4: "Group 1 title is getting cut off because of the way the
>> package install panel overlays on top. Need to adjust the spacing so
>> there is no clipping."
>> This should be a bug across the system, as it will impact everything
>> with a subpanel.
>>
> I was going to wait for the meeting, but now I'm compelled to add a
> reply. :)
>
> Slide 1:
> - agree with the comments above
> - "Use colon instead of the | after the field label" - We can do that;
> however, this style as used as it was part of the System->Errata mockup
> used for past implementations.  If we change it here, we should
> propagate the styling there as well.
>
> Slide 2:
> - agree with the comments above
>
> Slide 3:
> - "Sub nav should be reconsidered" - agree with the comments above.
> This was done to be consistent with System->Details->Events (now both
> are called Event History).  If we change this here, we also need revisit
> systems for consistency.
> - "Event details should be more closely related to where the action
> takes place" -  Was actually planning to make this either a tipsy (upon
> completion) or link to open the actual event (e.g. subpanel).  Using the
> link may actually be better in this case as there could be a fair amount
> of information generated depending upon the size of the group.  Another
> alternative would be a tipsy w/ brief summary with link in the tipsy
> that opens the event for more details.
>
> Slide 4 -
> - agree with the comments above.  This one is actually a generic 2-pane
> issue.
>
>
>

-------------- next part --------------
A non-text attachment was scrubbed...
Name: SystemGroup-EventHistory.png
Type: image/png
Size: 117165 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/katello-devel/attachments/20120628/c76b6a74/attachment.png>