Research request for Audit Reports (CMS)
What’s this issue all about?
Creating awareness for UX research around the need for support in Category Maturity Scorecard efforts.
What hypotheses and/or assumptions do you have?
~"Category:Audit Reports" is expected to progress in maturity from Minimal → Viable in FY23-Q1
What questions are you trying to answer?
Has the category matured enough to score rating of at least 3.14 to be considered Viable.
Core questions
maturityminimal checklist
-
Available in the product, and works in the recommended setup. -
Has utility to the user, but does not completely address the job-to-be-done, yet. -
❌ Not to be used as a primary selling point, as capabilities are minimal. -
❓ Suitable to replace the need for existing tools for new companies, departments, and teams.
maturityviable checklist
-
❓ Significant use at GitLab the company. -
❓ CM Scorecard at least 3.14 for the job to be done (JTBD) when tested with internal users. No assessment of related jobs to be done. -
❓ Suitable to replace the need for existing tools for new namespaces, projects, and environments.
Additional questions
What persona, persona segment, or customer type experiences the problem most acutely?
Complete: Category Maturity Scorecard is conducted with external users on the JTBDs
Personas: Cameron (Compliance Manager) & Sam (Security Analyst)
GitLab team members or Slack channels for consideration
-
@pranavpolisetty, Pranav is our internal SOX auditor - Owners of GitLab Org, unlikely it is worth their time
- Engineering managers (
#eng-managers) might be a viable option. Several of the participants I have met with in the past carry a "lead" engineer role
What business decisions will be made based on this information?
An update to the maturity rating and corresponding epic will be the outcome.