Your current filters are…
How can your skills be used for social good? Come work out the answer with others in this practical and challengisesame shop. The session will start with real life stories and examples of how tablets and smartphones are changing lives. After hearing how a tablet gave a teenage girl a voice and how a smartphone helped an elderly man 'keep his brain active', the challenge is then turned over to you and your skills and tools. In small groups you will be a given a profile of someone with specific skills and needs. (eg disability, older, etc). Using the skills and experience in yur group, you then work together to come up with ideaenable how to enable that person to have a better life.
Workshops are a great way to explore ideas for a user-centered design project, but when should you actually plan to have one? At what point would a workshop be useful? And when would it be harmful? Why have user workshops got a bad reputation with some UX practitioners?
In this talk, Jenny will answer these questions and provide examples from her own experience of planning and delivering successful UX workshops. The aim of the talk is to inspire you to run your own workshops and to provide practical tips that will help you get started right away. Jenny will include examples of workshops for internal design teams and stakeholders, as well as for groups of external users, potential users and clients. At EMBL-EBI, we specialise in delivering services to scientists and computational biologists all over the world, so Jenny can also offer special insights for those of you that work with ‘geeky’ audiences and/or in an international environment.
A little bit like speed dating, but with three people and a design problem to solve. More about collaboration and communication than it is about sketching!
The aim is to show that you can bring people together who might not usually work side-by-side, and by rapidly brainstorming with them about design problems, you can often elicit solutions and ideas you might never have spotted. Sometimes, a fresh perspective is what you need.
It would be great if participants for this workshop could bring their own problems to work on. Examples might include UI features that just don't quite sit right; information design challenges; working out how to prioritise content on a web page, etc.
Some fairly discreet thing that fits into the overall picture of UX design activity where you work.
Something that you have been scratching your head over, and for which you can explain the context and the problem faced.
Failing that, the facilitators will have some that they prepared earlier.
There will be lots of paper and pens.
A good product requires a good user experience. And a good user experience requires the close collaboration of product management and design.
User experience (UX) professionals are increasingly becoming interested in the business aspects of what they do. On the other hand, business professionals (such as Product Managers and Business Analysts) are becoming more aware of the role of UX in their activities. Often these two fields merge and it is difficult to differentiate where UX ends and Product Management starts and vice-versa, with many UX and business professionals incorporating aspects of these two ‘worlds’ in their job descriptions.
Terms and concepts such as Usability and User-Centered Design are used now more than ever before, and growing in importance and relevance to the IT industry.
This discussion aims to address the topic of the role of UX in product management and similar activities, by bringing together opinions, experiences and suggestions from people with a background on both sides, to guide future generations of professionals in these areas in understanding the nature of their roles.
One sentence summary: A former investigator uses lessons learned in the insurance business to inform and improve design research methods.
Design researchers can learn a lot from investigators in other fields. Insurance claims assessors follow specific interview protocols to reduce interviewee bias, build trust/rapport, navigate a variety of circumstances, and document responses properly—all in order to discover the reality and the facts of the loss. These investigations also have to be carried out in compliance with strict regulations.
In this session:
Structuring interviews and questions to reduce bias, build trust, and validate information
Note-taking styles to maximise efficiency
Keeping participants on topic during an interview
Dealing with communication barriers such as language, hearing impairments, and the emotional state of the participant
We will illustrate these techniques with real-world examples of investigations into automotive accident claims, property damage claims, and employee dishonesty claims.
This session is designed to expand the design researcher’s toolkit.
by Ryan Haney
Innovation games work and are a great addition to your UX tool-kit. They save time, help to build better products, can help difficult teams to collaborate and generally are more fun. But introducing these games to an unreceptive or even receptive organisation can be a challenge. Knowing which games to use and when to use them, getting stakeholder and team member buy-in, and bringing games out of product definition workshops and in to everyday/weekly meetings can feel like an uphill battle.
In this collaborative session we'll explore ways to overcome these hurdles. We'll look at strategies to get comfortable with playing games as well as ways to get your entire organisation to embrace them.
This workshop will explore to integration of UX techniques into Agile software development approaches.
Since we’re talking about Agile, we plan to run the session in a similar way to a typical Agile retrospective. Retrospectives are those meetings Agile teams have at the end of a sprint to review the past sprint and plan out ways – ‘experiments’- for improving the next one. The only difference for our workshop is that the retrospective will be looking at the last 10 years or so of Agile + UX development rather than a wee two-week sprint!
We hope that at the end of the workshop we’ll have a shared understanding of what has worked and what hasn’t across a spectrum of companies. More importantly, we expect to have a few ‘experiments’ for participants to be able to take back home and try out with their project teams.
by Kathryn Tanner and Miriam Walker
One sentence summary: Retailers could do much more with store locators to promote customer loyalty and attract new customers to increase sales.
We will show how a well-designed store locator will anticipate the needs of the user beyond simple search + location; it will use design and technology to put together a useful, meaningful experience for users, reducing confusion and frustration; it will make it easy for users to find what they need fast. These are powerful ways to build loyalty and, for customers who are ready to buy, to increase the chance of a sale.
Retailers, banks and the post office could do much more with their online store locators. By making some smart, creative improvements to this useful tool, they would increase sales to motivated, brand-loyal customers but also steal customers from those brands which do not make the effort. We see four key opportunities for improvement:
1. • Location detection
2. • Branch density sensitivity
3. • Time sensitivity
4. • Branch information
We will illustrate these through a user journey, showing how a customer would initiate a search, review results, filter information, and make a choice. We will articulate the functionality of an ideal store locator by critiquing good and bad examples.
Initiating a search (location detection) -
How do store locators work?
Automatic – Your location is detected - Tesco
Manual – You ascertain and enter your location (post code, street, town) Argos or you select your location from a closed list - John Lewis
We will walk through the pros and cons of each approach. For example many users will not know their destination or location details or they are looking for guidance about the destination and wish to leave it open. We can make it easier for users by identifying their location automatically. HTML5 can collect this information in three ways:
Local wireless networks (non-mobile computers)
Reviewing results (branch density sensitivity) –
How to be relevant and appropriate?
With location identified, the system must then define ""nearby"" in a meaningful way. Store locators should be sensitive to the density of stores so that there is a balance between surfacing too many or too few options “nearby”; and the map should scale to show results accordingly. If you are searching for a chemist in the centre of Leeds, then a map radius of 100 meters will be sufficient. If you are running the same search around Aberystwyth, the map radius will need to be much wider to return a useful set of results. Maps that do not scale intelligently force users to work harder to narrow the field and make a choice.
Filtering the results (Time sensitivity) –
Many tasks are time-sensitive, e.g. posting a parcel on Saturday or purchasing an item on sale. Store locators can filter results to help customers find branches that are currently open. Argos does this well by building a priority structure into its store location results. Location searches conducted at 6pm automatically default to stores that are open after 6pm.
Selecting a result (branch information) –
In addition to geography and opening hours, store locators should provide information as well. Store locators should offer a summary of store information, or a simple set of filters to narrow the results enabling the user to get specific information related to the task they want to accomplish. The Tesco iPhone Finder app is a successful example. It not only includes a store locator, but also a price checker, and can pinpoint a product’s location in the store. This leverages a key point in the user’s journey and can even persuade him to visit one store over a closer competitor.
It is crucial that this information is accurate and up to date. Otherwise, a retailer could lose credibility and their customers’ trust by sending them on fruitless journeys.
We will conclude by discussing the ROI of a well-designed store locator and the best KPIs to use to measure success.
by Aylin Uysal
Employees can stay well connected with their managers, co-workers, and direct reports with collaborative networking tools integrated throughout business processes. We will present the steps followed creating an Employee User Experience which transformed how employees connect, share information, find the right knowledge in the company, collaborate and build their business network.
We will also talk about social collaboration trends, potential employee use cases/scenarios and how these use cases can be identified.
by Sedef Gavaz
In order to understand and gain insight UX techniques need to be adapted to the audience, organisation and culture.
I'd like to share my experience in China including how I altered plans as I went along, what worked and the bits that didn't work quite as well as I would have liked.
I'll finish off with a 'what I'd do next time' - my lessons learnt.
10th–11th November 2011