-
Notifications
You must be signed in to change notification settings - Fork 3
Goals and metrics
lpgoldstein edited this page Dec 6, 2022
·
15 revisions
Product Goal | Metric |
---|---|
Industry can accurately report their production and pay their royalties due. |
|
Industry is aware of laws, regulations, and policies that impact them. |
|
Industry can get help troubleshooting problems they have when reporting or responding to compliance actions. |
|
New industry reps can get help understanding how to report and pay. |
|
Resource owners can ensure the trust responsibilities are being met. |
|
Users can understand what ONRR does. |
|
- Users come to the site when looking for information related to reporting and what ONRR does.
- Action: Track number of ONRR.gov users
- Users can find the information on the site that they are looking for. (User experience)
- Usability testing/User interviews
- Action: Track number of user interviews in each study
- Number of inquiries or emails to ONRR web email account
- Action: Track emails or reports
- Decisions based on analytics
- Action: Track monthly analytics
- Action: Track search.gov
- Automated accessibility checks
- Action: Test webpages with Lighthouse and document any identified issues.
- Action: Run accessibility test on all documents requested to be updated and document any identified issues.
- Manual accessibility checks
- Action: Test webpages with a screen reader.
- Test with screen reader users
- Action: Fix at least 2 accessibility issues identified in the previous fiscal year.
- Efficient, documented, replicable processes to update and maintain content on the website. (Business/technical)
- Amount of ODDD time used to update content and perform routine maintenance on site
- Number of issues closed related to bugs vs. maintenance/data updates vs. enhancements?
- Action: Track velocity categorization on spreadsheet
- Improve quality of GitHub requests
- Action: automated a checklist in GitHub when opening a new issue
- Action: communicate and educate ONRR with the GitHub process
- Ability for more than all members of the ODDD team and content owners to make data updates (with ONRR furnished equipment)
- Action: Implement VPN sign in for Directus
- Consistent workflow process for content update and requestor reviews.
- Action: Document and implement a process
- Vulnerability Disclosure Policy
- Action: Add ONRR VDP page to onrr.gov.
- Action: Monitor Bugcrowd and respond to vulnerability submissions within 3 business days.
- Promote the website and encourage collaboration.
- Action: Create spreadsheet with SME contacts for each webpage.
- Action: Contact SME’s to notify them of any issues identified in the annual content audit.
- Action: Hold 1 session annually internally to demonstrate GitHub request submission.
- Action: Publish at least 1 blog post related to onrr.gov to share knowledge.
- Action: Submit at least 2 proposals to present at conferences or forums.
- Problem statement
- Product vision
- User types
- What we're not trying to do
- Product risks
- Prioritization scale
- Adding content internal checklist
- CMS user guide
- Content review process
- CMS admin guide
- Releasing changes
- Goals and metrics
- Analytics
- DAP-GA4 templates & instructions
- DAP-UA templates & instructions
- Dev site analytics
- User research plans & findings
For details about our processes see our Natural Resources Revenue Data wiki.