On September 29, 2022, Matt Wallaert joined us for an exciting walkthrough on behavioural science and product.
Key takeaways
- The value that comes from using behavioural statements is in how they can help us frame up conversations, align efforts so we look to solve the right problems, avoid alignment drift and misinterpretation, and help assign accountabilities.
- A behavioural statement is written as When [Target Audience] who [Limitations] want to [Motivation], they will [Behaviour] (as measured by [Data]
- It’s critical for teams to build evidence, ask questions, and a build a strong backstory
- Pressures are either inhibiting pressured or promoting pressures and we want to design against those pressures, experiment to learn (low or no code), create evidence, and get to decisions.
- Qualitative and quantitative contexts — there are five: 1) always, 2) never, 3) sometimes, 4) started, and 5) stopped.
- Great teams have a mix of strategist, quant (e.g. data science), qual (e.g. UXR), design, and product and should work together throughout.
Resources
