ux scotland - ux patterns case study
out of 40
Post on 01-Nov-2014
Embed Size (px)
DESCRIPTIONWe (Patty, Lorraine and Mike) have presented at UX Scotland on UX patterns library we have established at Royal London. Presentation was held on 21.06.2013 at Dynamic Earth, Edinburgh; http://uxscotland.net/sessions/index.php?session=19
- 1. How we got to do UX in a large client-side organisationUX PATTERNS A CASE STUDYPattyBright GreyLorraineScottish LifeMikeScottish Life
- 2. Who are
- 3. We had some ups and downs!OUR STORY
- 4. SETTING THE SCENE
- 5. 1979 1995 2005Architecture Software UI1988 1992UsabilityDESIGN PATTERNSA brief history
- 6. WHAT IS A UX DESIGN PATTERN?
- 7. WHAT IS A UX DESIGN PATTERN?NOT
- 8. A UX design pattern is not aSTYLE GUIDEStyle guideA primary button should bemore prominent thansecondary button in order tocapture the users attention.Design patternPrimary buttonPrimary button Secondary buttonSecondary buttonThe Elements of User ExperienceJessie James Garrett
- 9. Design patterns are implemented using code but cannot be reduced to codeA UX design pattern is not aWIDGET
- 10. Rationale System should indicate that a process is in progress to avoid the userinferring that something has gone wrong System should indicate how long the process will take to manageuser expectations and enable planningSolutionsProgress can be determinedProgress cannot be determinedName System activity indicatorDESIGN PATTERN ELEMENTSContext
- 11. SO, WHY USE THEM?Design patterns benefit.. the bottom line: Efficiency. the user: Consistency. the organisation: Collaboration, alignment. the UX team: Visibility, authorityDesign patterns allow the UX team to do UX
- 12. IN THE BEGINNING
- 13. And sliding down into the darknessLETS DO THE PATTERNS!
- 14. Positive outcomes reinforced the value of thework.IDEALISED VIEW
- 15. REALITY OF THE WORK
- 16. Strategy for success3 MONTH MARKER
- 17. How we created and sold the business casePROVE YOUR POINT TO THE BIZ
- 18. GOOD HOUSEKEEPINGUsability evaluation and Reportof the current system (one of them!)The Holy s**t list of inconsistencies andthe basic patterns needed
- 19. GETTING SOMEMOMENTUM1 day/ week to work explicitly on the patterns But was this enough?
- 20. GETTING SOMEMOMENTUM1 day/ week to work explicitly on the patterns But was this enough?
- 21. THE BIZ CASE1. Show the rough estimate how you go faster2. Quantify the benefits3. Make sure its a 1-pager!
- 22. THE BIZ CASEMore information in case it was needed:- Convey the benefits (bacteria diagram)- Address pain points of the organisation- Dont speak UX!:- Success definition- Key benefits- Key objective- Resourcing (internal & external)
- 23. Managing external resource Making sure the business can see the benefitsDAVIDS ONBOARD!
- 24. DAVID IS PART OF THETEAM1. Full time, in our office2. Had access to everyone he needed3. We had access to him every day throughout the 3 monthsHe organises the pattern meetingsCreates the content for reviewDoes the researchGathers feedbackWrites up the patternReports on the progressShow & Tell to the biz at the end...
- 25. 1. 36 patterns published on the company internal Website2. Axure library for consistent UI design across all UX resources3. Brands across the business develop consistent style guidesROLLINGOUTCOMES IN 3 MONTHS
- 26. 1. Contracted external designer2. 1 monthStyle Guide for Bright GreyPATTERNS AS A SPRINGBOARDProve by doing!3. Highlighted the need for otherbusinesses to invest in thattype of content
- 27. NEXT CHALLENGES
- 28. PATTERNS ALONE WILL NOT SOLVEYOUR PROBLEMS
- 29. Promote the patterns but also explain their purpose.COMMUNICATE!
- 30. Avoid preoccupation with consistencyEDUCATE
- 31. What we have learned in the processTIPS
- 32. Evangelise & get buy-in sooner to get resourceBUSINESS BUY-INRe-cap with the biz to show progressGet a dedicated resource (internal or external)to get it done!Get senior stakeholders in your corner identify aUX champion
- 33. Quantify and communicate the benefitsBIZ CASEDont bore them one page is enoughMake it stick use your creative UX skills tocommunicate the problem differently
- 34. Try not to get hung up on points of disagreement strive to find common groundCOLLABORATIONEngage others across disciplines to gain buy-in and create more robust solutions
- 35. Make use of patterns that are out thereCREATING PATTERNSGet the right level of detail and dont be a slaveto the patternUX design patterns are for you (the UX team) aswell as others
- 36. Get them full time in houseWORKING WITH EXTERNALAgree the scope up-frontEnsure engagement with the whole patterngroup
- 37. WORKING WITH A LARGECLIENT AS AN EXTERNALHave a clear picture of what youre there to do&Make it clear what youre going to deliverRemain true to it despite politics andagendas. Its easy to be swayed to keep peoplehappy!
- 38. http://developer.yahoo.com/ypatterns/about/libraries.html http://ui-patterns.com/patterns http://osdpl.fluidproject.org/ http://www.bbc.co.uk/gel https://www.gov.uk/designprinciples http://wiki.fluidproject.org/display/fluid/How+to+Write+a+Good+Design+Pattern http://patternry.com/patterns/RESOURCES
- 39. THANK YOUPatty (Kazmierczak) FroncRoyal LondonPatty.firstname.lastname@example.org@PattykaLorraine PatersonScottish Lifelpaterson@scottishlife.co.uk@lorraine_pMike JeffersonScottish Lifemjefferson@scottishlife.co.uk@mikeyj_uk
View more >