Yes, I do have a tool to help teams identify relevant project metrics
The approach to identifying relevant metrics is called “Questions first”.
Here´s a link to an article explaining this approach. At the end of the article you will find two versions of the canvas: one in PDF format to fill out as a document, one as a high resolution image to paste in your favorite digital canvas (Figjam or similar).
This is really excellent! I walked through this and noticed a few things:
Ship then Measure - This is coming from the perspective of having already shipped the feature, so the framing is more concrete, which makes sense.
Design Role Play - In my work, we’re gathering findings during the design phase, pre-launch. It was helpful to me to imagine that we had ‘launched an opportunity’, then walk through the “Questions First” approach provided.
Metric Bridge - Now, we still need to bridge these product and UX metrics. If we imagine the feature has launched, we have specific product or feature usage metrics we would be targeting. Outlining these can be helpful to find our UX Metric targets.
@sol_mesz curious if you’ve had an success applying a similar approach during the design/development stages?
Circling back around to this article @sol_mesz, it’s a great one! We have a similar concept in Glare around Hunches and Questions, which aligns with your thinking. Great stuff.
As we dive deeper into our Glare AI Skills, we realize that the connection between “what we did and our goal” is becoming even more valuable as we shape the outputs.
Having clarity on the business side creates a stronger tension with the user side- this is actually a good thing. We need to know how to balance the user needs and business goals.