As an end user, I want

1. to be able to uninstall OSSM smoothly and
2. be able to verify that OSSM is uninstalled completely

This is based on a feedback from support:

[A customer case] (sev 2) was quite a ride to read through.
 

• Opened as Sev 2 and immediately escalated
• 2 remote sessions setup for the customer
• 2 TSEs and 1 TSE Manager involved
• Case seemingly resolved simply by following the docs? https://docs.openshift.com/container-platform/4.11/service_mesh/v2x/removing-ossm.html
   
  From reading those comments, its not clear to me if the customer missed one of the steps or one possibly didn't complete, preventing the following from successfully working.  Is there an opportunity to add verification after each of those steps in the docs, so when a customer opens a case they can at least state which step was not successful for them?  I've seen a few cases in service mesh where uninstalling has been troublesome for customers, and causing an undue burden on support.  It shouldn't take multiple support people and an escalation for a customer to become unstuck, it should be self-solve.

From Jamie:
in the past, there was a lack of validation steps in our docs and that always causes challenges when you have a multi-step procedure (which we often do). I recall holding back the federation docs until they were added. We added them to many of the getting started pages (often using Kiali), but perhaps as Tim suggested we consider adding a few to the Uninstallation steps. Definitely something to be on the look out for if we see repeats of such cases.