User Experience I
A day about the terms and the process that design uses when it starts from use. Afterwards you know what UX people do, what they decide by, and what a digital product can be measured against.
Key facts
- 2-8 people
- 7,5 hours
- Decision makers & practitioners
- Understanding User Experience
How the day unfolds
The basis is human-centred design. What comes first is not the product but the people meant to work with it. The day walks through the whole process once: understand the context of use, derive requirements from it, draft design proposals, examine those drafts. Each stage brings the vocabulary that belongs to it.
Added to that are usability principles and guidelines you can use to assess an existing product, application or service. The day closes with two insights: into usability testing, and into process management, meaning the question of who examines what, when, and where in a project that belongs.
What you take away
An understanding that holds up in your next meeting: you can place requirements, examine proposals and ask the questions that move things forward. Plus materials and instructions to take with you.
The day makes nobody a UX professional. It makes you someone who can judge a design decision without having to make it.
One or two?
Both days are the same length and cover the same ground. The difference lies in the depth, not in an order.
User Experience I is the day for understanding. It is for everyone involved in planning and design, or working alongside usability and UX professionals: management, product owners, project leads, marketing, software development.
User Experience II is the extended version, for the people who design and build themselves: product owners, web and product design, project leads, software development. The same steps, carried further and spent longer on your own material.
Workshop I is not a prerequisite. If you know it needs to go deeper, book the second day straight away; if you first want to sort out the terms, the first one is the right one.
Who the workshop is not for
Teams that work with requirements, tests and acceptance criteria every day. For them the day is a repetition, and the second one is the fitting one.
And for anyone expecting an assessment of their own product. The workshop shows how to assess, it does not assess. If you want to know how usable your own service is, you need a usability test, not a day of training.
Related
1 person-day
Time on site. Preparation and follow-up come on top and depend on the format; I will name the effort in our first conversation.