Everyone should talk to customers. Most companies buy the idea. They also believe it's a waste of time with developers. Here's why they're wrong.
Outcomes are measures of behavior. Here's the difference between a business outcome and a user outcome and why it matters.
Despite decades of advice and proof that building learning into our work improves results, organisations are still resistant. Why is that?
The key to reducing analysis paralysis and amplifying evidence-based decisions is knowing when to let an idea go.
Whether you’re a leader, engineer or someone else who isn’t usually associated with “getting to know the customer”, there's no excuse for not talking to your audience.
Doing customer interviews is great! Doing it with a clear sense of what you’re trying to learn is even better. Here’s why.
Measuring the performance of our products and services can easily get confused with measuring our users' behavior. Here's how to avoid that.
Running experiments in a corporate environment can be daunting. Here's one trick to help bring good ideas into perspective.
If you're going to work with hypotheses you need clear success criteria. Outcomes provide the objective lens needed to determine our next steps.
Defining your work is crucial to creativity, innovation and agility. Here are two templates to help your team do that.