End to End Usability Testing MVP - Name Request and Name Examination

## Description (Hypothesis):
- Short Description of the needed Epic in the below format

* As a (who/ person)
* I want (what/ goal)
* so that (why/ benefit proposal)
or
* What are the most critical features being built as part of this Epic
* Expected Outcome – Justification why this Feature must be built, what is expected value and justification for priority.

----
## Acceptance Criteria
* Used to determine whether the implementation is correct and delivers the business benefits

----
## Additional Information
* Start date when team will start to work on: This is visible in ZenHub under "Roadmap"
* End date Epic will be delivered: This is visible in ZenHub under "Roadmap"
* T-shirt size: X (S, M, L, or XL) (S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints). Story points needs to be updated in Epic. This can be decided by team.
* Process Flow (if applicable)
* CM considerations?
* Possible dependencies or blockers foreseen right now? - Please create a story and block this epic by the dependency story.

----
Enabler Epics:
* action
* result
* object

The issue names no files, tests, or entry points and contains only a template for an epic. First clarify the usability-testing MVP, including the name-request and name-examination scope and acceptance criteria; implementation cannot be started or considered complete from the current description.

Written by the indexing model from the issue text.