Goal

• Transferring cluster ownership allows another individual to manage the cluster. Ownership can be transferred to other users in the same or different organization. Link to documentation.

• The current workflow is not conducive to users making a connection between their evaluation expiring and the action of subscribing. Our goal is to encourage users to transfer their clusters to an existing account and link that directly to the evaluation expiration.

Background

• There are 1981 unclassified clusters. Having clusters in an unclassified state means that Red Hat does not understand what Custom Global Customer Name (GCN) the cluster is associated with. This limits Red Hat’s ability to engage with the owner of the cluster in a meaningful way which decreases chances of revenue generation, retention, and customer success.
• There are several scenarios by which these unclassified clusters can occur. (see User's image attached below or slide 5 in the deck) 
• Low res wireframes have been approved from a strategic direction. We need to leverage those wireframes and create final designs. (see slide 16 in the deck)
  • There was a workflow Gina had designed for when we know your organization. Perhaps we should consider that use case as well and try to include that scenario. Jake Lucky will have more background on why that may be difficult to do from an implementation standpoint.
• Colleen/Megan can help with any additional background.

Requirements

• Leverage the eval status both on the clusters list and the cluster details to send users directly into a subscribe, transfer or buy flow:
  • If the cluster is connected to an account and has an active subscription we will default to the Subscribe option
  • If the clusters is not connected to an organization we will default to the transfer ownership and disable the subscription option
• For the transfer ownership workflow:
  • Improve the existing out of product "Pull secret" experience and bring as much of that into this modal/wizard as possible, while reducing the steps and making the UX as easy as possible for users.
  • Add necessary cluster information to provide context for the user and to decrease the likely hood they transfer the wrong cluster
  • Refine and understand the implementation necessary for an "Email" approach as an additional alternative to the "Pull secret"
  • Consider adding a nudge to users about contacting their Org admin to be added to their existing Organizations's existing account if applicable.
  • Consider what links to documentation would be necessary and useful.
  • Identify any other gaps that may not have been accounted for.
    • Do disconnected clusters need anything different?

Resources

• Slide deck: https://docs.google.com/presentation/d/1GJMATzWvLO7UA91dg49lGRXN6K2hxyu5bCHDPCbm97I/edit#slide=id.ge8ef82f34f_0_0
• Sketch files: https://sketch.com/s/3da04dc4-b859-42ca-96f5-85629d0b84b1
• Marvel: https://marvelapp.com/prototype/a77a24d/screen/82545002