Consider recalibrating badge milestones

[misaugstad]

Brief description of problem/feature

I'm wondering if we want to consider messing with the badges @jonfroehlich? In particular, the 5k labels badge is a huuuge investment. There are only 22 users who have 5k labels, and of those, only 4 are marked as "low quality" and 6 are turkers.

I'm not totally against having a big stretch goal. I kinda like it! But thought it was worth bringing up and discussing now that it's been live for awhile and we have more data. On my own account in Seattle, for example, I have 550 missions (highest badge is for 100), 10k validations (highest badge is 5k), 17 miles (highest badge is 5), but only 2.5k labels (halfway to the highest badge).

The strongest reason to make the change might be the fact that for small cities, 5k labels essentially means labeling the whole city! In Oradell, we have fewer than 15k labels, and that's including tutorial labels, etc.

Maybe this is something that we could change when we add some stats that are summed across cities? We could make the goal in a given city more reasonable, like 1k or 2k, but then have a separate set of achievements for your cross-city stats with a higher label count for the highest badge!

[jonfroehlich]

Sure. Totally open to this.

The badges were created in Adobe Illustrator and exported to png. You can find them here: https://github.com/ProjectSidewalk/Design/tree/master/Badges

[misaugstad]

Did some recalibrating, and feeling good about this scaling:

• Missions: 5 -> 25 ->

Badge type	1st	2nd	3rd	4th	5th
Labels (new)	50	200	500	1k	2k
Labels (old)	50	250	500	1k	5k
Distance (new)	0.5 mi	2 mi	5 mi	10 mi	20 mi
Distance (old)	500 ft	0.25 mi	0.5 mi	1 mi	5 mi
Missions (new)	5	25	75	150	250
Missions (old)	5	10	20	50	100
Distance (new, km)	1 km	3 km	8 km	15 km	30 km

Summary of the changes with rationale:

• Decreased the number of labels needed for highest bad drastically. Mostly just evened out the increases in labels needed between badges from 50 -> 200 -> 250 -> 500 -> 4k to 50 -> 150 -> 300 -> 500 -> 1k. Now the increase in labels needed between badges basically doubles each time.
• Increased distance required for all badges. I increased the requirement for the first badge because it also lined up with the distance for your first mission. Between all the popups during your first mission and the mission complete screen, I think it makes sense to space out the badge a bit further into a user's experience. As for the tail end: if users added labels at the rate that we require for being marked as "high quality", they would have audited at least 33 miles by the time they have the 2k labels badge. So I really just decreased labels required and increased miles required for the highest badges so that they got closer together.
• Increased missions required for later badges. Getting the 5k validations badges would actually mean 500 completed missions, so it seemed like bumping up the missions badges made sense. I'm happy with missions badges still come in more quickly than validation ones, just brought them a biiit closer together.

The overall goal was to make the progression feel more natural, and to reduce the amount that users are flying through one or two sets of badges while another set feels out of reach!

And folks on our design team have agreed to make the changes to the badge icons for us, so thank you in advance! 🙏

[jonfroehlich]

Nice. Looks great.

Let's make sure that the new badges get back into the design repo: https://github.com/ProjectSidewalk/Design/tree/master/Badges