In SAFe, Features and User Stories roll up into Epics.
This hierarchy is useful for organizing work, but it doesn’t prove the work is worth doing.
Epics are often based on internal priorities or assumptions.
Without customer input, they risk solving the wrong problems or missing the real ones.
Teams need to treat Epics as Ideas, not facts.
The fastest way to test those Ideas is by validating them directly with customers before committing to build.

SAFe yourself the trouble.

Validate the work that comes to the team.