Dashboarding. Effective team interaction with data

What the talk is about

Kostiantyn Miroshnychenko explains how an analyst can work effectively with a team through dashboards. Analytics builds a knowledge base about the project and turns subjective opinions into numbers that can be checked. The aim of a dashboard is for a person to work with data autonomously: give them a decision algorithm and complete information, and strip out anything extra. An analyst should join once a stable product concept exists and the dates of the first tests are known. The speaker covers working with game designers (a tutorial funnel with cohort retention, metrics and segmentation in the design doc), producers (app "pulse" indicators, comparison baselines, filters), QA and balance. He advises keeping the analyst and balance roles separate and speaking in terms colleagues understand. Useful for analysts, producers, game designers and marketers.