Defining Maturity for UX Research

This epic is seeking to define maturity across each of our disciplines inside the company. To this end, I opened this issue to define what it specifically means in the context of UX Research. From Research's perspective, what does Maturity mean? What plans or actions are developed or taken at each step of the way? What is research doing when a feature is Viable? What about Lovable?

Current Maturity Goals:

• Planned: Not yet implemented in GitLab, but on our roadmap.
• Minimal: A minimal foundation so people can see where we're going and to validate customer need.
• Viable: Used by users/customers to solve real problems.
• Complete: Contains a competitive feature set sufficient to displace other single-purpose DevOps tools.
• Lovable: Provides an elevated user experience that customers love as measured by PNPS.

Proposed UX Research Maturity Goals

From the perspective of UX Research...

• When a feature is Planned, that means Research has validated that this feature solves a real problem or need.
• When a feature is Minimal, that means Research has validated with users that the MVC solves a real customer need through customer interviews.
• When a feature is Viable, that means Research is seeing moderate customer satisfaction of the feature through customer interviews and surveys.
• When a feature is Complete, that means Research is seeing high levels of customer satisfaction of the feature through customer interviews and surveys.
• When a feature is Lovable, that means Research sees that customers love the feature through customer interviews, surveys, and PNPS scores.

/cc @clenneville @sarahod