Guidance QA and Rollback Gate (QA)

Guidance QA and Rollback Gate (QA)

1. 01

   Freeze the guidance build 48 hours before the client demo and tag the version

   Record the tour, checklist, and tooltip IDs in a single sheet so any post-demo edit can be traced back to the exact build the client approved.

2. 02

   Walk every flow as a brand-new account, not as an admin

   Admin sessions inherit permissions and skip empty states, which hides the broken first-run experience your client's end users will actually hit.

3. 03

   Test on the two smallest viewports the client supports

   Tooltips anchored to fixed pixel offsets clip or overlap on mobile web; confirm each step still points at the intended element before sign-off.

4. 04

   Verify trigger conditions fire once and only once per user

   Duplicate triggers are the most common cause of support tickets after launch, and they are invisible in a single-session test.

5. 05

   Confirm every survey and checklist writes to the analytics destination the client already owns

   If events land only in the vendor's dashboard, the client cannot tie adoption to their own product metrics, and the retainer conversation gets harder at renewal.

6. 06

   Run a rollback drill: disable the live guidance set and confirm the app renders clean

   A five-minute rollback test before launch is cheaper than an emergency call during a client's peak traffic window.

7. 07

   Log known limitations and open questions in the handoff doc, with an owner and a date

   Unresolved items stated plainly read as diligence; the same items discovered later by the client read as defects.