What would be concrete examples of when we took the output of mixpanel (ie the stats), had a discussion around it, and acted up on it.
Example 1. DApp usage is high considering how deeply hidden within the UI it is placed today (3 clicks deep). This means that we should be focus on improving our DApp development documentation and everything DApp related (see hackathons, DevRel hiring, etc. etc.)
@Chad can probably point to a lot more clear examples where we have used it for product improvement rather than just pat on the back stuff.
obvious stuff (“users use dapps!”)
It may be obvious to you, but it isn’t for everyone. Some people think that Status is just messenger, or just a wallet, or just a DApp browser. Saying ‘obvious stuff’, implies that every user of Status sees the application from your perspective.
what’s the interest in knowing DTU to begin with? What do we do with that particular number, except to check off key results?
It’s a guiding point that let’s us know if we are actually building something that people use or not. What if 0 people used Status, how would we know? Also, I’m not particular tied to DTU, happy to use something else as a proxy for “Do people use the Status app”.
Also, what can be replaced with reasoning, experience and other types of (smaller) studies.
That leaves decision making to the loudest voice in the room. I’m sure you can imagine a community member chiming in with: “Our wallet flow sucks, we need to improve it”. How does it suck? Why do you think it sucks? Qual research is applied during the design phase to validate the improvement, but in order to even engage with the conversation about whether the wallet flow sucks, quant metrics are incredibly useful.
This has happened repeatedly at Status over the past 4 months (I’m sure @Chad can point to specific Slack threads where metrics were used as the objective truth on a subjective topic).
is engagement/time spent in app something we’re optimizing for?
This relates to which metrics are most important for Status, which is great!.
I personally don’t see ‘time in app’ as something we want to optimize, as it encourages shady/dark ux tactics to keep bringing users in. If someone uses Status to send money, and it takes < 10 seconds, then thats a great success!
DTU’s has been thought of as the main metric purely because it is a safe measure of daily utility of the Status. Considering the breadth of tools people have access to in Status, we assume the time frame is daily (vs a weekly/monthly, for example Google Maps is used more on a weekly/monthly basis since most people don’t need a map in their daily routine). If our goal is to bring DApps/messaging/wallet to the masses, then DTU is a good proxy that we are providing utility for users in one or more of the three areas.
As mentioned above, I’m more than happy to collab/brainstorm on alternatives. DTU was the best we could think of 7 months ago and lot has changed since then.