“The role of the analyst in making important product decisions”: video recordings of reports from the meeting

In late September, a meeting for product analysts and product managers was held at the St. Petersburg office of Wrike . The meeting was devoted to the issues of qualitative (vs quantitative) analytics, the interaction of analysts and product managers, the process and tools for the validation of product changes.



We talked about how to evaluate the quality of products, test product hypotheses, collect relevant user feedback and build a roadmap for product development, based on it.

We hurry to share video recordings of reports.



Alexey Smirnov, Wrike “Qualitative analysis in product analytics. How to prioritize product initiatives and effectively assess their impact on customers. ”

')





In Wrike, the work of product analytics is closely tied to the interaction with the product-owner of each specific functionality (yes, we are working on Scrum).



He is in fact the right hand of the product manager: he helps with the validation of new ideas and the prioritization of existing ones, provides operational support and distributes knowledge in the team. But often we are faced with a situation where, on the basis of quantitative data, it is not clear how to choose a worthy idea from a thousand? How to evaluate its impact on our customers and how to understand what can be improved and is it worth it? At the meeting, I want to share the tools of high-quality analytics that we use at Wrike, and tell them how they help us understand the real needs of our customers, how to collect their feedback, organize it, interpret and present to stakeholders.







Dmitry Bugaychenko, Odnoklassniki "The Way of Kamikaze 2.0: how to survive the" hopeless "Data Science project"







When Data Science is confronted with the real world, “unexpectedly” it turns out that for the full implementation of the project many roles are needed, in addition to the actual date of the scientists. This is a product development team, project / product managers, classical analysts, and often top management. Each of them may have their own expectations and their attitude to data science, ranging from blind deification and admiration to fierce hatred, but without their informed participation the project is doomed to failure. A report on what difficult situations we had to face at Odnoklassniki, how we struggled with difficulties and what came of it.







Bella Gromakovskaya, Pavel Volkov, Wargaming, WOWS project “How are innovations in the game evaluated”







The process of interaction of product analysts with the development team: all stages - from the intention of the game "features" to assess its success after reaching a wide audience. Comprehensive assessment during testing and after release - data, surveys, community opinion and game experts. Specific examples of the evaluation of innovations.