You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think there's a myth sometimes that "we don't have that data" for some KPI or interesting question because it's not necessarily easy to get that piece of data. For example, there's a concern that we have no way of knowing anything about seasonality in the TF platform, but that's not entirely true. We have lessons from season 1, those lessons have progresses that tie them to users, and those users may have made comments or taken quizzes that demonstrate they participated in season 1.
We also have Google Analytics data and a User ID-enable view that should give us some power to connect user activity back to a season, although again it depends on how much work we're willing to do.
I think the idea here is to do a little open-ended data exploration to give us a starting point for assessing what data is compelling to the team, which can in turn guide discussions on how we might more effectively collect that data in the future.
@hellafitz Am I describing the intent here correctly?
The text was updated successfully, but these errors were encountered:
From Iridescent-CM/technovation-app#2170
I think there's a myth sometimes that "we don't have that data" for some KPI or interesting question because it's not necessarily easy to get that piece of data. For example, there's a concern that we have no way of knowing anything about seasonality in the TF platform, but that's not entirely true. We have lessons from season 1, those lessons have progresses that tie them to users, and those users may have made comments or taken quizzes that demonstrate they participated in season 1.
We also have Google Analytics data and a User ID-enable view that should give us some power to connect user activity back to a season, although again it depends on how much work we're willing to do.
I think the idea here is to do a little open-ended data exploration to give us a starting point for assessing what data is compelling to the team, which can in turn guide discussions on how we might more effectively collect that data in the future.
@hellafitz Am I describing the intent here correctly?
The text was updated successfully, but these errors were encountered: