Meeting in St. Petersburg "The role of the analyst in making important product decisions"

What can help a product manager to minimize risks when making decisions on the development of certain features? How weighty can and should be the word analyst in the development process? Do product analysts have any other tools besides quantitative data?

On September 20, at the Wrike office in St. Petersburg, we will meet with a team of product analysts and product managers to try to answer these questions.
')
The meeting will be devoted to the problems of qualitative (vs quantitative) analytics, the interaction of analysts and product managers, the process and tools for the validation of product changes. We will talk 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.

1. 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 can we ultimately assess its impact on our clients and understand what can be improved? At the meeting, I want to share the tools of high-quality analytics that we use in Wrike, and tell them how they help us understand the real needs of our customers, how to collect feedback, organize it, interpret and present to stakeholders.

2. 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, the participation of many roles is needed, besides 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. About what difficult situations we had to face in Odnoklassniki, how we struggled with difficulties and what came out of it we will talk.

3. 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.

→ Register for a meeting
→ Watch online broadcast