Feature Overview (aka. Goal Summary)

Customers are not sure about the benefits of using Helm Chart vs Operator to install RHDH. 

Goals (aka. expected user outcomes)

The documentation should contain a table with a list of pros/cons of each approach.

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

<enter general Feature acceptance here>

Who is your target persona?

<Role>

What stage of the user journey are you targeting?

<User journey>

Why is this content important?

<Justification>

What is the main user goal aka job to be done?

As a <role>, I want to <goal>

What high level steps does the user need to take to accomplish the goal?

1. <User steps to accomplish goal>
   

What pain points are the user likely to encounter when accomplishing this goal?

<Pain points>

Links to existing content

• <Add link to content>
  

People:

• SME: <SME>
  
• QE: <QE>
  

Release Note: Yes/No

Documentation Outline

• <Documentation outline>