Guidance Content QA Gate (QA)

Guidance Content QA Gate (QA)

1. 01

   Confirm the client's product build is frozen before any tour is authored

   A guidance layer built against a moving UI breaks silently. Get written confirmation of the release tag the tours will target, and re-baseline if the client ships mid-build.

2. 02

   Walk every tour end to end in a clean account with no prior session history

   Author accounts carry cached state that hides broken triggers. Use a fresh login so the first-run experience matches what a real new user sees.

3. 03

   Verify each tooltip and checklist step anchors to a stable selector, not a CSS class that ships with styling changes

   Ask the client's front-end lead which attributes are contractually stable. Selectors tied to layout classes are the most common cause of tours that vanish after a routine deploy.

4. 04

   Test the experience on the two slowest devices and browsers in the client's analytics

   Guidance that renders in 200ms on a laptop can stall on a mid-range Android. Pull the client's device mix and reproduce on the bottom two entries.

5. 05

   Check that every survey and checklist has a defined exit, including the abandon path

   Users who dismiss a tour halfway should not be trapped in a loop or re-prompted on the next page load. Confirm the suppression window is set explicitly.

6. 06

   Run the segmentation rules against real account data, not the author's test segment

   A tour aimed at trial accounts will fire for paying customers if the segment logic reads a field the client populates inconsistently. Spot-check 20 live accounts.

7. 07

   Log the QA pass with screenshots, the tested release tag, and the date in the client's shared workspace

   This record is what protects the retainer when a client later asks why a tour broke. It also gives the next agency or contractor a starting point.