To problem solve effectively together, you must create a shared understanding of what success looks like for your project or product. You might already have a set way of measuring this. For an app it might be the number of installs or the time it takes to complete a critical task. Perhaps it’s a revenue target. Taking the time to review what current metrics you have and explore what new measurement tools you might need will help align the team around a tangible end goal.

Google often uses the HEART method, which breaks down the process of creating metrics. It encourages you to consider 5 categories when developing goals and choosing metrics for each of those goals. HEART stands for Happiness, Engagement, Acquisition, Retention and Task Completion.

Directions:

Time: 20 min
Activity: Small teams

1. GOAL: Start by thinking about the big picture: What are you trying to help users do? What problem are you trying to solve?
2. SIGNAL: Next, consider what change in user behavior or opinion would indicate you’ve been successful in your goals. There may be multiple signals for each of your goals.
3. METRIC: Finally, determine how to measure the size of any change in user behavior or opinion. This could be through surveys or logs analysis.

Example: ADOPTION : Goal -> Users start using “smart pay” to pay their bills Signal -> User clicks on the action to pay Metric -> Proportion of clicks on action to pay that result in a paid bill