Skip to content

Optimize Listaflow for response rates

One of the main current issues of the sprint reporting of core contributors via Listaflow is the low response rate that we get. It's not really Listaflow's fault, but since it is starting to look like it's the main issue that the core contributor program managers have to deal with in terms of reporting, it would be invaluable if Listaflow could help improve those numbers.

So the goal of this ticket would be to identify ways for Listaflow to help the program managers to improve response rates. There are a few examples below taken from discussions with core contributors and from the experience running the program, but this list is meant to be completed and amended. Also, more generally, the proposal is to make the optimization for response rate the main goal of the project for the months to come.

  • Changes to the form for Open edX working groups:
    • Emphasize that the time reporting doesn't need to be precise - I agree with what you said on this Sarina "Take your best guess, don't spend too much time agonizing, we are looking that commitments are directionally correct". I agree that we need to make this more clear on the form, this could be a good helper text for it.
      • Suggested wording by Sarina: "Enter the approximate number of hours spent over the past 14 days. Take your best guess; we're looking to see if commitments are directionally correct, so don't spend too much time agonizing. Overall, you should aim to contribute an average of 20 hours a month over any six-month period."
    • We should probably also mention that the time logging can be flexible over time -- it can be allocated in chunks, as long as it remains > 20h*6 = 120h for the last 6 months (at all times, ie don't go in debt!)
  • Make the email reminders more personable -- instead of looking like an automated email, it could be customized by the managers of the form, and sent in their name (ie more like we were doing it manually before Listaflow)
    • A/B test different email formats to check which ones work better
  • Etc.
Edited by Xavier Antoviaque