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
As part of this design doc, we want to see the effectiveness of messaging and start the process of measuring student engagement.
We currently have posthog analytics, perhaps we could fire off events to posthog and see if their tools could help us answer a few of these questions?
On average, how long does it take from a student's submission to receiving a review? - The shorter this time is, the faster the feedback hence higher engagement
Dropoff - at which point does the student submit, get feedback, and then left the platform? This could indicate the need for establishing proper mentoring / code review guidelines to make sure students are not discouraged
Plus any other efforts to answer engagement. Moving forward, I'd like metric considerations to be part of all future designs, perhaps this discord bot metrics could be a start.
The text was updated successfully, but these errors were encountered:
I haven't yet looked at posthog, I'll explore it. But these feel like things that could probably be achieved with some sql queries since we should already have this data in the database now that we store all attempts at a challenge. I'll see if I can add some queries in our metabase dashboard to show these statistics as a start.
As part of this design doc, we want to see the effectiveness of messaging and start the process of measuring student engagement.
We currently have posthog analytics, perhaps we could fire off events to posthog and see if their tools could help us answer a few of these questions?
Plus any other efforts to answer engagement. Moving forward, I'd like metric considerations to be part of all future designs, perhaps this discord bot metrics could be a start.
The text was updated successfully, but these errors were encountered: