|
Hi there,
Imagine this: You’re in a late afternoon meeting with your product team, and it isn’t going well. In fact, it’s turned into a total disagreement about what your team should be building during the next sprint.
Just a few weeks ago, everyone seemed aligned on the problems you were trying to solve with a new product feature. You put a week into designing user flows and screens, but after reviewing them with the team, it’s clear that everyone else had a different picture in their minds of what’s best for the customer and the business.
In your notebook, you find yourself writing down a list of things you wish you’d done differently:
-
Your team wasn’t aligned on what success looked like for this new feature. What metrics would you be moving with this feature, and how would you measure them over time to show improvement?
-
You didn’t review any product data with your team about how the product is currently doing. Your team has a ton of different ideas about how to move this metric. Maybe this feature wasn’t the right thing to start with?
-
Your team is skipping to solutions, rather than testing where to invest in product improvements. Maybe we should have created some quick experiments to prove where to focus our limited product resources? And validate that our design recommendations are going to truly have an impact?
If you’ve struggled with these kinds of situations before, then our Data-Driven Design course can help. Over 6 weeks, you’ll learn how to set success metrics for product work, analyze product data to inspire
different design hypotheses, and craft experiments to test your ideas and validate their impact.
Our course starts in June, and there are limited spots available. If you’re interested, you can go ahead and enroll via the link below, or simply hit reply with any questions!
|
