Prioritization Scale

These correspond to Github issue labels. Use the descriptions below to determine if a prioritization label should be added to your issue.

P1: Show stopper

Work on this immediately. Must-have for next release.

Examples:

• incorrect data on the site
• high profile bug that prevents users from accessing crucial site content
• proprietary or personally identifiable information needs to be removed

P2: High

This doesn’t prevent the site from being used, but needs to be addressed in the near term. This issue affects a majority of users and impacts user goals or causes significant pain for users. May also include researching features we know users value or we’re going to implement, or outreach work that has an approaching deadline.

Examples:

• bug or usability issue in a high volume browser that obstructs user navigation
• writing a conference proposal due within the next sprint

P3: Medium

This doesn’t prevent the site from being used and can wait a bit before fixing. Affects a moderate number of users, impacts medium priority user goals, causes moderate pain for users, or reflects poorly on our brand or users’ confidence in the site. May also include researching features that we don’t know the value of, or outreach work that has a deadline within the next couple months.

Examples:

• issue on the Downloads page that affects users of one data file
• putting a message in IE saying we don’t support it, making it easier to prioritize IE bugs as low
• aesthetic problems in a high profile area of the site

P4: Low

This doesn’t affect a large number of users, or we’re not sure exactly how much impact it has. Might affect <10% of users and impacts low priority user goals or causes minor annoyance for users. May also include continuing research on features that we’re starting to see are low value for users.

Examples:

• IE bugs
• research on production rankings