Presenting UXBASIS User Experience Process
•Download as PPTX, PDF•
6 likes•1,242 views
UXBASIS is a selection of 24 methods to be used in different situations, to help you design with the user’s experience in mind.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Presenting UXBASIS User Experience Process
Similar to Presenting UXBASIS User Experience Process (20)
More from Hello Group
More from Hello Group (10)
Recently uploaded
Recently uploaded (20)
Presenting UXBASIS User Experience Process
- 1. brings you a presentation Hello presents
- 2. 2 | Presenting UXBASIS | 26.09.2010 Hello my name is…
- 3. 3 | Presenting UXBASIS | 26.09.2010 We are Hello
- 4. 4 | Presenting UXBASIS | 26.09.2010 So what is it all about? User Experience is… UXBASIS •User experience is in the design, the visual experience. •It’s in the functionality, how the product works •It’s in the wants & needs of the users, and how successfully those are met •User experience is everywhere
- 5. 5 | Presenting UXBASIS | 26.09.2010 UXBASIS •Drawing a tractor for my son •I wanted to ensure the quality was tip top so I added additional features •Adding a chimney to it my son believed it to be a train
- 6. 6 | Presenting UXBASIS | 26.09.2010 UXBASIS •By not knowing my audience well enough my added work was more harm than good •Had I known which elements identify a tractor for him and which doesn’t this would have been avoided •This scenario happens in the design world all the time and wastes time and money
- 7. 7 | Presenting UXBASIS | 26.09.2010 Introducing UXBASIS? User Experience is everything UXBASIS •Today everything is about user experience •Because of this we at Hello group created UXBASIS •UXBASIS was created as a means for our clients to improve their users experience.
- 8. 8 | Presenting UXBASIS | 26.09.2010 How did we get here?
- 9. 9 | Presenting UXBASIS | 26.09.2010 Introducing UXBASIS UXBASIS
- 10. 10 | Presenting UXBASIS | 26.09.2010
- 11. 11 | Presenting UXBASIS | 26.09.2010 UXBASIS
- 12. 12 | Presenting UXBASIS | 26.09.2010 Business Intelligence UXBASIS
- 13. 13 | Presenting UXBASIS | 26.09.2010 Stakeholder Interviews UXBASIS • Interview key decision makers one-on-one • Focus is on overall deliverables • Aim is to form a thorough final brief • Conclude with a Concept model to add value
- 14. 14 | Presenting UXBASIS | 26.09.2010 Competitor Analysis UXBASIS • Identifies best practice in competing products • Focus is on what works and what doesn’t • Aim is to identify popular solutions • Can be used to solve issues during design phase
- 15. 15 | Presenting UXBASIS | 26.09.2010 Analysis UXBASIS
- 16. 16 | Presenting UXBASIS | 26.09.2010 User Interviews UXBASIS • One-on-one interviews with members of user group • Focus is on the users feelings towards the product • Aim is to get to know the users wants and needs • More qualitative information can be gained through non-verbal clues
- 17. 17 | Presenting UXBASIS | 26.09.2010 Personas UXBASIS • In-depth descriptions of fictional characters • Focus is on identifying common traits with users • Aim is to cover user behavior, attitude, skills and goals • Can later be used during testing to ensure appropriate recruitment
- 18. 18 | Presenting UXBASIS | 26.09.2010 Persona example
- 19. 19 | Presenting UXBASIS | 26.09.2010 Collaborative Workshops UXBASIS • Meeting with stakeholders to explore ideas • Focus is on concept, direction and content of product • Aim is to come up with more innovative solutions • Can identify business goals not previously mentioned
- 20. 20 | Presenting UXBASIS | 26.09.2010 Card Sorting UXBASIS • Held with users or stakeholders to create the structure • Focus is on content and the information structure • Aim is to create groupings that make sense to all • Can be held as open or closed card sorting
- 21. 21 | Presenting UXBASIS | 26.09.2010
- 22. 22 | Presenting UXBASIS | 26.09.2010 Concept Model UXBASIS • Provides an overview of possible product elements • Focus is the user wants/needs and the business goals • Aim is to create an overview map everyone can understand • Ideally created early and then edited throughout the process
- 23. 23 | Presenting UXBASIS | 26.09.2010 Concept model example
- 24. 24 | Presenting UXBASIS | 26.09.2010 Concept model example
- 25. 25 | Presenting UXBASIS | 26.09.2010 Structure UXBASIS
- 26. 26 | Presenting UXBASIS | 26.09.2010 User Journeys UXBASIS • User path to their goal in the product is defined • Focus is on user’s tasks, behavior and challenges • Aim is a tool from which the information structure can be generated • Useful with complex structures and multiple users
- 27. 27 | Presenting UXBASIS | 26.09.2010 User Journeys UXBASIS
- 28. 28 | Presenting UXBASIS | 26.09.2010
- 29. 29 | Presenting UXBASIS | 26.09.2010 Site Structure Diagram UXBASIS • Overview of the architecture, conveys the structure • Focus is on the information structure of the product • Aim is a tool that clarifies the scope and structure • Can be created early in the process and then reworked as new information appears
- 30. 30 | Presenting UXBASIS | 26.09.2010 User Journeys UXBASIS
- 31. 31 | Presenting UXBASIS | 26.09.2010 Interaction UXBASIS
- 32. 32 | Presenting UXBASIS | 26.09.2010 Wireframe • Key pages are wireframed possibly based on earlier sketches • Focus is on how the users navigates and completes tasks • Aim is a tool that can be used to start the interface design • Can be used in conjunction with a Think Aloud test UXBASIS
- 33. 33 | Presenting UXBASIS | 26.09.2010 Prototype • A fully functional HTML prototype with complete structure • Focus is on the interaction design of the product • Aim is working prototype the development team can use • Final testing can be done to ensure that the interaction matches the user requirements UXBASIS
- 34. 34 | Presenting UXBASIS | 26.09.2010
- 35. 35 | Presenting UXBASIS | 26.09.2010 Wireframe example
- 36. 36 | Presenting UXBASIS | 26.09.2010 Sample UXBASIS
- 37. 37 | Presenting UXBASIS | 26.09.2010 Think Aloud • Test participants comment on the experience and interaction • Focus is on the users needs and expectations • Aim is qualitative information that can inform the final solution • Testing can be done at any stage in the process, on wireframes, prototypes or end product UXBASIS
- 38. 38 | Presenting UXBASIS | 26.09.2010 Eye Tracking • Users are tested using hardware that tracks where they look • Focus is on the users apparent interest in product elements • Aim is useful information that helps optimizing the layout • Hello group does eye tracking on visual designs as the results from testing on wireframes are not as convincing UXBASIS
- 39. 39 | Presenting UXBASIS | 26.09.2010 User Journeys UXBASIS
- 40. 40 | Presenting UXBASIS | 26.09.2010 User Journeys UXBASIS
- 41. 41 | Presenting UXBASIS | 26.09.2010 Final points “Just because nobody complains doesn’t mean all parachutes are perfect”
- 42. 42 | Presenting UXBASIS | 26.09.2010 Thank you for listening Find out more on uxbasis.com Or follow us on Twitter: @uxbasis @hellogroup
Editor's Notes
- I’m Rune Leth Andersen This is Jeppe Henckel We are information architects From media agency Hello group Before Hello I worked in London For 2 NMA top 100 agencies. Through the years I have worked on countless projects Some projects ended up winning awards Came to Hello for the same reasons as why I am here today Because Hello is the elite when it comes to user experience in Denmark. We have come here today to talk to you about: User experience More specifically UXBASIS Our toolbox for dealing with user experience UXBASIS holds 24 methods of dealing with user experience We will explain a few of these today
- Hello Group is a media agency with focus on the users experience with the products we develop. We specialize in strategy. We specialise in Hello process is Think, Create, Evaluate Process ensures we achieve excellent successful executions Think tier is information gathering Create tier is where interface design and development is housed Evaluate tier is where strategy and testing is
- User experience is a hot topic Many definitions but rarely offer much value User experience is in the design, the visual experience. It’s in the functionality, how the product works It’s in the wants & needs of the users, and how successfully those are met User experience is everywhere
- Complex projects can easily become unwieldy and lack focus due to production factors and resource issues. This inevitably harms the quality of the product and does not promote a user focused solution. UXBASIS is a way of practically applying techniques from a business perspective, while keeping true to the goals of the users. UXBASIS is a process based on our experience of building digital solutions.
- We compiled a kit of 24 methods based on our experience To help our clients engage their users successfully It was evident that not all projects required same approach. We needed to be flexible in our offering. Each method has different time and cost implications. Evidence based design creates greater value for client business It encourages collaboration between in-house teams Results in knowledge sharing between individuals
- UXBASIS is not meant to be used in its totality for each project Each project requires their own approach The need for UXBASIS methods depends on the problem they will solve and the solution required
- UXBASIS has 5 sections Each section holds several methods Each section covers a particular user experience need The different sections are: Business Intelligence Analysis Structure Interaction Sample
- The Business Intelligence section involves: Identifying the clients needs Clarifying and finalizing the brief Noting the overall business goals
- Interviews with key decision makers Interviews are one-on-one Focus is on the overall deliverable Idea is to: Gain insight of the clients business culture Forming a thorough brief Ultimately dictates the end build Combine with a Concept Model to give added value to information gathered.
- Identifies what works, what doesn’t and ultimately best practice Gain understanding of users based on competitor interaction See what’s popular in the market Works as problem solver as it can be used to identify a competitors solution
- The Analysis section involves: Identifying the user needs Clarifying the end users Focusing on content and structure
- With a user interview we obtain qualitative information about: The users feelings toward the product Their feelings about competitor products Their wants and needs Their abilities Conducted one-on-one A script is used for consistency Preferably set in an environment the user is familiar with When we do these interviews we do ask the client not to be around as it can The client remains invisible throughout Non-verbal clues often offer information not conveyed verbally so using a camera is ideal
- In-depth descriptions of fictional characters based on user groups identified in user interviews Covers the users behavior, attitude, skill and goal with the product Can later be used when testing to ensure the right users are recruited for testing We’ve also found that the developers we use like having them around as they help them keep the end users at mind
- Meeting with stakeholders Formulate ideas, the concept, direction and content Can identify business goals not previously mentioned Allows design team to explore new suggestions More innovative solutions are created when stakeholders are allowed to contribute During the workshop some elements of the product can be sketched Sketches made will be the foundation for the wireframes and interface design work A concept Model should be developed as a result of this Does a Concept Model already exist, it should be amended. The workshop ensures that before any interaction design work is started that all are in agreement as to what will be delivered. Working with Novo Nordisk on their intranet we had a successful Collaborative Workshop
- Can be held with users or stakeholders Cards represent content for the product Cards are grouped by the participants according to what makes sense to them An open card sorting can help create an information structure based on the user perspective A closed card sorting tends to be used to validate an existing structure A quick and cost-effective method
- Designed to give an overview over the different possible elements of a product Can be used as a roadmap to identify which elements should get primary focus and which are secondary Outlines the needs/wants of the users in conjunction with the business goals Can be understood by everyone Is key at the end of the Analysis stage, but can feature multiple times The concept model is a necessary deliverable to all our projects as it outlines the needs and wants of the user base, alongside the business goals of what the application should satisfy. Aim: to give the developer group an easy point of reference as the project progresses to maintain focus on key strategic areas.
- Information gathered is used to develop the framework
- Having first defined the user roles we can now plot a path through the product for each user goal. Particularly useful with complex structures and multiple user types e.g. social networking or ecommerce. Aim: Shows user’s tasks, their modes of behavior and any potential challenges that a user may discover when using the product.
- Creating Develop the layout and overall structure Build product content templates
- Key screens are wireframed If sketching was done during the Collaborative Workshop these will be used here Focus is on: How the user navigates How they conduct themselves How they complete tasks Interface designers and information architects together create the wireframes Can be used for testing to ensure they meet users needs
- The right tools (UXBASIS) Cases Business and domain knowledge Avoid turning tractors into trains These days where the world is connected as well as it is and where social networking is an fundamental part of peoples lives, a persons negative experience with a product quickly becomes public knowledge.
- Will wrap up with questions…..and pass the box around for people to see