I have a pragmatic approach to testing, meaning more doing, less discussing theory.
I specialize in short runs of qualitative testing, where I use my extensive network to find test participants for interviews, workshops, and focus groups.
Testing in a short amount of time calls for flexibility and adaptability. It also calls for thorough planning, and tailoring the different test methods to every single project. There is no recipe, no best practices and no re-using old reports.
I’ve selected a handful of test-related activities from projects that I think were particularly interesting.
How I made a short demo video showing a newly developed system with tools most people have access to.
What do you do when you only have 2 days to test everything there is to test around UX on an app?
How well does your app perform when it leaves the comfort of the development lab? I rode the trains and took a bath to see how everyday situations effected app performance
It’s often crucial to know users’ elaborate ideas and opinions. But how do you manage to process that much data in a form where it’s usable for the project team?
Creating wireframes for an app from users’ feedback that a developer can use right away is an extensive task. I took it on in cooperation with a designer.
During the first meeting we talk about your needs and the system that is to be tested. You might want a specific sort of test run, and I might have suggestions for you.
Every test run is different. The methods and people I use for testing, depends on what questions you have, and how much time I have for the test run.
This is the phase where I tell you what I’ve discovered in both written form and face-to-face. The written report is a short, easily read document with results, list of issues and suggestions to changes.