Good design does not begin at the screen but with the people who are meant to use something. I design digital services from use backwards: first understand how people work, then draft, then test against real behaviour. Everything else on this page is a tool for those three steps.
User experience and human experience
User experience (UX) describes the experience with a concrete product: is it usable, accessible, efficient, and does using it satisfy? Good UX means a service creates benefit, explains itself and invites people back.
Human experience (HX) reaches further. It asks not only about the interaction with an interface but about a person’s whole experience with a service: emotional, social, cultural, physical. UX optimises a product; HX asks what it does to, or makes possible in, people’s lives. I work with both views: the narrow one for usability, the wide one for the question of whether the right thing is being built.
User research: understand first, then draft
User research systematically establishes what the target group needs, expects and actually does. Depending on the question and the phase I combine qualitative and quantitative methods: interviews for depth, surveys for breadth, observation and field studies for real behaviour in real surroundings, focus groups for the conversation among each other, usage data for the patterns nobody reports about themselves. The result is evidenced assumptions instead of guessed ones.
User stories: requirements from the user’s side
I phrase requirements as user stories: “As a [role], I want [goal], so that [benefit].” A story records who needs something, what exactly and to what end; acceptance criteria make it testable when it is fulfilled. Prioritised in a product backlog, this becomes a development plan oriented on needs rather than technical preference. The format comes from agile development and works wherever teams must decide what gets built first.
User testing: checking the product against behaviour
In testing, people from the target group carry out real tasks with the prototype, observed and afterwards interviewed. Expert reviews complement the tests but do not replace them: how hard a task really is shows only in the person attempting it for the first time. Testing early finds mistakes while fixing them is still cheap, and yields solid data on need and acceptance along the way. For young projects especially, it is the fastest aid to decision.
Usability evaluation: formative and summative
Evaluation gathers the findings and turns them into recommendations. Formative, during development: heuristic evaluation along established usability principles, cognitive walkthroughs along the user paths, tests on intermediate states. Summative, after completion: tests, questionnaires and field studies measure how usable the whole has become. The two belong together: the formative loop prevents wrong turns, the summative one proves the result. And because requirements change, evaluation is not a closing ritual but part of operation.
