Software development is sometimes chaotic, but I'm excited that the things we build are ambitious, even if they operate in a world of uncertainty.
User research is undeniably valuable but also resource-intensive. So, how could you conduct user research without a team?
Makers and designers are often taken aback when clients push back on allocating funds for user research and testing. Here's a software team's point of view.
If you need to quell your nerves, start by making your best assessment of the types of issues that could come up after the product launch.
It's important during user interviews to instill confidence. People want to know they've been heard and that you're going to give them what they want.
Getting your app into the hands of customers as soon as possible is highly recommended. Here are a few stories that illustrate the utility of user testing.
There are many ways to approach a beta trial. By thinking first about what outcomes you want, you can work backward to think about how.
Which gives you the optimal feedback from users — a clickable prototype with visual design or a simplified implementation of the app?
After doing usability tests for a year, this is the advice I would give my past self — prepare, practice, work with a pair, and above all, stay flexible.
This setup comes together easily, captures the most important data, and leaves me free to focus all my energy on the test participant.
In usability testing, you put together some great ingredients, follow the necessary steps carefully, and – voila! – a greater design emerges.
Design starts when there's a problem to solve. That's the designer's "broken test." After designing a solution, she does user testing to make sure it passes.