But seriously, it comes in waves, and it helps that I’m helping structure the problem area for the data collection. We’ve found like cycles of data collection once or twice a week can be very helpful in gathering signals that push projects forward.
There’s a lot that can be accomplished without data from continuous discovery, especially when there are core goals being targeted for improvement. But that continuous discovery data is crucial in the moment when the team is trying to innovate.
Many teams struggle to see how this fits into their processes due to the limitations they’ve developed over time.
→ WHY DATA (Frame the challenge): This data uncovers the motivations and needs behind user behaviors, providing insight into the root causes of why users do what they do.
→ HOW DATA (Assess the potential): It examines the user’s approach and interaction with a product or service, revealing their methods and experience.
→ WHAT DATA (Finalize the choices): This is the measurable outcome of user interactions with a product or service, offering concrete metrics on performance, usage, and satisfaction after launch.
