January 14, 2016 UXC Meeting Page

USER EXPERIENCE COMMITTEE MEETING NOTES

Attendees:

• Mary Hodder
• Ellen Nadeau
• Jim Zok
• Paul Knight
• Noreen Whysel
• Tom Jones
• Bev Corwin
• Linda Braun, Global Inventures

Meeting Notes

• Mary Hodder led the call. Notes taken by Linda Braun
• Meeting was called to order at 12:05 p.m. EDT
• Meeting Notes: No minutes approved.
• IPR policy reminder:

http://www.idesg.org/portals/0/documents/governance/IDESG%20IPR-Policy.pdf

• Recording policy:

https://workspace.idesg.org/kws/groups/idesg_members/download.php/475/Recording_Policy_Conduct_at_IDESG_Meetings[1].pdf

• Roll call.

Minutes

• Mary made some changes to the About the User Experience Committee overview on the wiki. She included the WebEx logistics for the regular weekly UXC meetings.
• Mary and Noreen also fixed some links. The page is now a little bit longer.

The recording policy is missing from idesg.org and Linda will post it and send the new link to Mary.

• Design Pattern. Tom added a Trustmark Anti-Patterns page; Mary made a few edits. Tom added a description and a disclaimer. Tom’s comment – important for UXC to make sure that context is clear. We should write rules in such a way that they are not confusing. He suggested that we be careful about generic pattern – and warned about including too much UXC information. Mary made some edits to the Trustmark Evolving Pattern section during the meeting. Use scope of work within the committee was suggested instead of using examples. Need to be careful that we stay within what the IDESG is and not do a global discussion. Identity and personal management would be OK to use.
• The word “consumers” is used as well as “individual” and “user.” Need carbon-based user. In UXC charter we define user as carbon-based. In UXC, supplemental guidance, and requirements refers to people.
• UXC decided to use “user” in the Design Pattern page; one definition is better. Mary will make this change.
• Design Pattern Content: Problem Description was discussed. There are a lot more desktop apps and people are becoming more comfortable with downloading files. Some of these are not addressed in our requirements. The “apps universe” was suggested to add in our problem statement. Digital environment could be used. However, project scope creep should be considered so UXC doesn’t. Digital displays to users is what we should focus on. UX is things users can see and respond to. If not, it is something we desire to do in this committee. UXC discussions around requirements discussed that for V1.0 that we would scope to web interfaces because we won’t prepared yet to get to a scope of products or displays for users. It is not that we only deal with frontend issues, but display is what users see.
• UXC is trying to make clear for this first round and then add more in v2.0.
• Ellen will add some wording to link to Lory Cranor study from CM on length of time to read under references and citations.
• FTC had a privacy conference recently. Google in now on 97 percent of the top 1,000 sites and are able to collect personal data from all those sites. A recommendation was made to add some of the appropriate presentations from this conference to the UXC anti-pattern section.
• Recommendation made that we might want to consider adding metrics as well to this section.
• Not included on the Design Pattern page, but some other place.
• Some work has been done in this area on the UXC page already, but we may want to take a look again.
• Ask TFTM if they would like to read this section on anti-patterns.
• Jim Zok also offered to take this to the Privacy Committee for their review.
• Mary to follow up with Sal about an informal Management Council review.
• Common to any Internet Identity Ecosystem – section – was reviewed. No anti-pattern information included here. UXC can put common problems with identity here. Tom to update page.
• Trustmarks of IDESG images discussed. Images will go into the common patterns section.
• References and citations will need to be added in this section as well.
• Noreen will work on citations.

• Next regular meeting, January 19, 2016.
• Action: See above.

Adjourn

• Adjourn: Meeting was adjourned at 2::56 p.m. ET