Reviewing and recording results takes headphones and about as many hours as was spent testing.
A less obvious reason to start researching sooner rather than later is that it’s a really good way to address the questions teams have and inform the decisions they make: should this or that screen come next to keep the flow, will a user “get it” or know what to do next. The alternative can be hit and miss.
Existing services are challenged when AI becomes involved. Testing a system’s design, functionality and content before and during development reduces risk and improves usability.
“We will be gamed” – How we don’t always win when games are used to develop real world systems.
In 1997 “Deep blue” became the first machine to beat a reigning world chess champion. Though Kasparov went on to win the series 5:1, it was a significant milestone.
Previous posts in this category describe how Neilsen’s popular methodology of Discount Usability Testing can identity around 80% of a site’s usability issues. It’s quite “doable”, typically taking a day, with 5 […]
A recent assignment with local government brought home the challenges of introducing digital, agile and service design into a traditional service provider; into an environment that’s neither digital first nor […]
Researching for a county council involved looking at other local government websites to see if there was a structure to the visual design, if they used a visual language. Unlike […]
The post “Different types of research“, categorised user research as either formative or summative (aka generative/evaluative): – Formative investigates environmental and human factors, constraints, opportunities, behaviours, requirements, and objectives. Summative evaluates the performance of […]
Plan for each phase and update the plan A research plan can be one of the outputs of a design sprint, when there is one. If not, it’s still helpful to write it as […]