Discover more from akoratana
Today, we launched Flows: the biggest update to PlayerZero since our Product Hunt launch in October 2022.
PlayerZero was designed from the beginning to streamline some of the most fundamental decisions that product & engineering teams have to make every day about their product quality. A central property of PlayerZero is unified product and technical storytelling; building causal relationships between issues and the real things that they may affect. In other words, our product tells the story of an issue, and it’s part of why hundreds of teams use us every day to identify and prioritize issues across their product.
Why we built flows
A lot of times, I explain PlayerZero as a platform that sits in between product analytics and engineering monitoring. The reason that analogy works is because, today, these disciplines already exist and often produce a disconnected output.
Analytics lacks actionability, and monitoring lacks relevance.
In product analytics teams can understand the intent of the business and the broad movements of users. With product analytics and a well executed query, I might learn about a 5% decrease in peoples ability to complete onboarding. But why is this happening? And what can I do to fix that?
While product analytics is able to tell the business story, it lacks actionability.
On the other hand, engineering monitoring holds a wealth of technical data that is intrinsically actionable. But its connection to the broader business context is often missing. Where is this happening? And while I could do something about it, is it important right now?
Flows are powerful in their simplicity
Flows represent a space for these two worlds to blend together.
PlayerZero's Flows use a declarative language to represent the critical paths in an application. This language is designed to be easy to understand and allows for a granular representation of the user journey. PlayerZero's Flows are monitored by the platform, which can detect and alert on any issues along these critical paths. This allows for quick identification of any issues that could prevent users from completing their journey.
Flows represents a change to the the core design mechanism we use to tell that story.
Declaratively represent what you care about. We wanted to create a way for engineering and product teams to declaratively represent the paths they really care about. By creating a Flow, you can
Get everyone on the same page, quickly. When an issue arises, PlayerZero can now communicate the context of the issue in a language that everyone on your team can quickly understand. Rather than saying, “this issue leads to a loss in conversion to the /cart page”, instead we can say that “this issue leads to fewer users successfully checking out”.
Get to what matters, fast. With Flows, theres now a simpler way to understand which issues are getting in the way as a checklist, instead of as a list of issues. At a glance, you can now understand the quality posture of your product and all the things getting in the way.
Flows is now available for all of our users to set up across all platforms. Hop in and get started! If you’re interested in using PlayerZero, feel free to reach out or get started for free at go.playerzero.app.
Thanks for reading akoratana! Subscribe for free to receive new posts and support my work.