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>