I presented a talk back in Oct 2019 to colleagues describing what UX is, and why I believe it should be embedded within the delivery of any solution where an end-user exists. I thought I would share my slides here… I’m going to break it down into separate posts. Here’s part one!
“User Experience is the science and art of designing a product”
- Easy to use
- Fits users expectations
- Meets business goals
A quote by the Nielsen Norman Group, World Leaders in Research-Based User Experience.
In fact, Don Norman of the Neilsen Norman Group first coined the term ‘user-centred design’ back in the late eighties in his book ‘The Design of Everyday things’. But it wasn’t until the nineties that he was the first to call himself a ‘user experience architect’ at Apple Computers.
“I invented the term because I thought the human interface and usability were too narrow. I wanted to cover all aspects of the person’s experience with the system, including industrial design, graphics, the interface, the physical interaction, and the manual.” – Don Norman
Why do I want to talk about UX?
Because I feel passionately that to build a product or service for an end-user, that their needs must be at the heart of every decision that is made, to deliver that solution successfully…
The UX Process
Typically when a customer comes to a designer with a problem, a lot of designers jump straight to solutions… don’t do this!
Instead, start by identifying the problem…
- Who has the problem?
- What is the problem?
- How will we solve this problem?
- What will the solution achieve?
- What features are required to accomplish the objective?
- What will the product look like and how will it function?
Smart user experience design starts by identifying the problem and guiding all ideas to solve that problem.
If you take the time to properly define the persona, problem, strategy, objective and features, it will provide a more effective solution.
One of the more common processes in developing the user experience is called User-Centred Design. It is an iterative process made up of 4 steps.
Try to understand the context in which users may use a solution. To do this you must perform various user research activities. These can include a combination of some of the following research activities:
- User questionnaires;
- Stakeholder & user interviews;
- Diary studies;
- Focus groups and workshops.
Ethnography is a good one. By definition, it is the systematic study of people and cultures. In the UX world, researchers observe and/or interact with a study’s participants in their real-life environment. Activities can include observation, interviews and surveys. All of these ethnographic methods can be very valuable in helping identify and analyse unexpected issues.
A slight caveat about this context step though… A delivery team seldom establishes the context from scratch. But there’s nothing stopping them from conducting research to clarify any assumptions they might be making, or to gain a deeper understanding of a problem.
Requirements are the result of synthesising your user research and identifying business requirements or user goals that must be met for the solution to be successful. At this step, Stakeholder/User Needs are defined.
Some examples of requirements activities:
- Empathy mapping;
- Card sorting;
- Competitor analysis;
- User journey mapping;
- Business process mapping.
An empathy map is a collaborative method to visualise what you know about a particular type of user. It helps create a shared understanding of user needs, and aid in decision making.
A user journey map, however, is a way of mapping out steps in an action such as ordering a new passport. It helps identify pain points and helps map out an aspirational experience.
This is where the UX team designs solutions. You approach this in stages and to varying degrees of fidelity.
Some examples of design activities:
A very lightweight mockup of a site of app’s layout. Useful for sketching out where buttons, text blocks, logos, etc are placed. Usually presented mono-chromatically.
- High fidelity mocks
A more detailed representation of the final design, with styles and fonts etc applied. Gives a more realistic view. Not very interactive.
Usually a far more realistic view of what will be the end solution, with a more interactive capability. This is achieved by using software such as Axure, or written in native code.
You check how well a design is performing. This is typically done by performing usability testing, either in-person, remotely or even via a method called guerrilla testing, where you ask passing people to test a feature randomly. Employ the ‘Think aloud’ technique.
Some examples of evaluation activities:
- Usability testing;
- Solution usage reviews;
- Task analysis;
- Accessibility testing.
Rinse and repeat until the solution is refined successfully.
Obviously integrating that into a fixed-price Agile project will be quite challenging, but doable with the right planning upfront. Employ a technique called Staggered Sprints, where UCD is performed in advance of a development sprint, as shown by the diagram below:
I hope that has given you an overview of what UX is, and the processes involved.
Look out for part 2!Share my post!