Analytics provide the basis for stakeholders to make decisions in the best interest of the company, and the users, according to the data. In order for analytics to be produced on a product, a data pipeline must first be established within your product and you must have an audience to use or already using the product.

Analytics colleagues can do their best work when they're provided user story maps and when they have some designs to reference. User journeys provide an opportunity to capture and collect various data within your product.

Once you have journeys created, sync with the analytics team and ask them to create a WIP analytics framework based on those and the various user personas within the product.

Plan this framework as one of the exercises in the last days of your workshop. Involve Analytics colleagues once you have the user stories map ready and let them prepare for the workshop. They’ll do most of the talking, while you’ll be there to support them in facilitating the discussion.

Some frameworks they might use are FMF or AARRR. It’s up to them to decide depending on a specific project. They’ll prepare a test set of metrics based on those frameworks, walk the client through those, and start a discussion.

Since implementing analytics costs time and money, clients need to see value early on. Allowing them to have a say in building the metrics framework does just that.