Paid feature module design
The goal of this issue is to build the designs for the paid feature module.
The module will focus on specifically selected upgrade points (points are to be determined, issues in epic) in .com to make the implementation process of this experiment easier. The module itself will be selected via a text link in the app that will then open/expand the module contents. The module will have two core states, one for admins who have the ability to upgrade and one for non-admins users that do not have the ability to upgrade. The content of the module in regards to describing the paid feature and tier will remain the same in both states, the only things that will change are the options that appear for the users.
Historical conversions on this topic can be found in the following:
To-do
-
Learn more about users, who they are, their flow and behaviour around paid features, using existing data/research materials. -
Document the findings. -
Define flows for the module. See epic. -
Ideate on potential solutions -
Share and discuss solution -
Iterate depending on feedback -
Finalise mock-up -
Design is validated and mock-up ready for handover to engineers. -
Gather user feedback once the solution is accessible to them -
Iterate?
Input data
Some personas to keep in mind while working on this issue:
- DevOps Director
- Chief architect
- DevOps Engineer, current frustrations using GitLab.
- System administrator/SRE, a bit more about the overflow of notification they receive here.
- Software Developer/Engineer.
Current flows
- Admin "Start a trial" current flow -> Recording. Experience map
- The different paywalls.
Linked issue to follow