Page MenuHomePhabricator

Investigation: Allow organizers to set group goals for events
Open, Needs TriagePublic

Description

NOTE: This task is just for the storing and handling of goal data. Progress bar will be a separate investigation: T407786.
User stories:

As an organizer, I want to be able to set group goals for my events, so that I can motivate participants to actively participate in the event as editors and so that I can have a sense of when my event is "done" and how can I report on the impact of my event.

Background:

We want to allow organizers to set goals for events, so that:

  • Participants can be motivated to join and participate with a concrete sense of what they are aiming to accomplish.
  • Organizers can report on event goals and outcomes to grant officers, organizing partners, and affiliated institutions.
  • All editors can have a better sense of the goals and impact of events and organized activities on the wikis.

To do this, we are imagining that organizers will first be able to set very basic goals, which means:

  • One goal per event
  • One progress bar for the goal

However, over time, this can be expanded and be made more complex, such as:

  • Multiple goals per event
  • Goals that can be made for groups or individuals
Acceptance Criteria:
  • Investigate how we can allow organizers to set goals for an event, which means:
    • Step 1 (short-term): Organizers can set 1 goal per event in the following format: [number] of [data point that we already collect in the Contributions tab, like new articles created].
      • Goals will be collectively shared by the whole group. So, any edits made for the event count toward the goal.
      • If a group exceeds the goal, we should still track how much they exceeded the goal (i.e., we shouldn't stop tracking when the goal is reached).
    • Step 2 (longer-term): Editors can set individual goals, like a personal challenge.
      • Editors will use the basic infrastructure of event registration to set a goal with a start end/date.
      • Perhaps they can choose if goal is open (so people can register and join) or closed (and therefore just for them). Closed goals will still be public.
    • Step 3: Organizers/editors can set more than 1 goal per event.
      • There will be one goal per event at first, but maybe later multiple: At first, we will probably only allow them to set 1 goal per event, for the sake of releasing a simplified first version. However, over time, I can imagine us allowing organizers to set a few goals (for example, a maximum of 3 goals), which can be tracked. For example, they could have a goal of creating 10 articles with at least 30 references added (if we later collect data on references).
      • We don't know how multiple goals will be stored (i.e., one goal with sub-goals or entirely separate goals). We will need to be flexible in how we think about it at this stage.
Design examples:

Organizer can set up a goal:

Screenshot 2025-10-29 at 1.54.59 PM.png (618×1 px, 91 KB)

Users can see progress against goal on various pages, such as the event page:

Screenshot 2025-10-29 at 1.55.31 PM.png (724×888 px, 309 KB)

Event Timeline

ifried updated the task description. (Show Details)

What kind of reports data would we like to have now or in the future, like:

  • Number of events that reaches their goals
  • Most used goal types
  • What are the type of goals people set for each type of events
  • What are the characteristics of the events that reach their goals

Are the event goals only numbers, or can we have goals that will not be a number.

In this example: have a goal of creating 10 articles with at least 30 references added
Are these 2 goals or one goal with 2 metrics?

cc: @ifried

These are great questions, and I'm also pinging @AJayadi-WMF, @SEgt-WMF, @Udehb-WMF to see what opinions they have.

Reports that I could see in the future could be:

  • Goal outcomes report (which events: reached goals vs. not reached goals)
  • Most common goals for events, separated by event types & outcomes (i.e., are the goals reached?)
  • Top performing organizers (i.e., which organizers have events that most often reach the goals) - but this is a maybe because it could provide too much incentive to do 'easy wins' rather than harder things
  • Goals reached by topic(s) (is this possible? maybe mapping article topics, as defined in LiftWing?)
  • Goals reached by wiki

Are the event goals only numbers, or can we have goals that will not be a number?: I can only think of numeric goals right now, and I think it may be best to just have numeric goals if we want a progress bar. The only "maybe" for not a number is the quality score of an article, but if we use the LiftWing quality score, that is also numeric (between 0 and 1).

In this example: have a goal of creating 10 articles with at least 30 references added. Are these 2 goals or one goal with 2 metrics?:

I am leaning toward having it as one goal because:

  1. I think it is better to have 1 progress bar than, for example, 5 progress bars. It is more visually simple and compelling. More of a sense of what people are trying to accomplish together.
  2. This would allow us to let organizers set more sub-goals. If we had multiple goals with separate progress bars, this would be so visually overwhelming that we would probably want to encourage people to only set a maximum of 3 goals. However, if it is 1 main goal with 1 progress bar, there is more flexibility.
  3. I think the sub-goals complement each other, such as: "I want to create 10 articles with 30 references, since the articles will be of better quality if they have references."

As for how we could visually represent the different progress between the sub-goals, @JFernandez-WMF and I have briefly talked about how they can perhaps be different colors and/or have a tooltip to show progress for each sub-goal.

Maybe we could have an optional goal setting especially for non-numerical goals?

I learned recently some organizers conduct surveys post-events to examine participants' experience of an event. So, if we could have an optional goal setting, organizers could add qualitative goals like "During my event, participants feel they are taught sufficient knowledge about Wikipedia and feel empowered to edit in the near future", then organizers can insert the summary of their survey results (if they do survey).

@AJayadi-WMF, this is a great insight about organizer goals related to survey satisfaction! My question is: Would we represent such data/goals same way? Our idea of goal-setting is to have a collective sense of goals for a group, which we can track and measure with generalized and reliable metrics (like number of edits, number of bytes, quality score, etc). For surveys, the questions and answers can really vary, so it can hard to set repeatable and measurable goals, and these are more internal goals for organizers rather than for the event overall. So, I think this is a great general insight, but it may be better suited for a project around survey support (which I'm not sure we would do). The alternative is for the organizers to manually input in the survey results, like you shared, but I think that could be prone to user error/less useful to add onto another interface.

But maybe there is something else that I am not thinking of OR other non-numeric goals that could be of use. If something comes up in your mind, I would love to hear!

@ifried thank you for the further clarification (also, very helpful to see the design examples). Indeed, re: surveys and/or its results are varied.

Side note: I chatted with Euphemia about this. She likes the "choose the type of goal" and "set a number" because, in the case of grant application, there are questions about target goals if the applicant(s) say they aim to contribute to X articles, etc. Also, she says the bar is interesting as it can be helpful to organizers to see their progress immediately.

Random notes from old team discussions:

  • Showing goals on event page can be problematic for caching (might consider hiding progress for logged-out users / cached page views)
  • Maybe consider storing unstructured targets (eg JSON) to support different future formats