For QA and design
Proof that the documented flow still works.
Sabí tries every documented step in your product and shows you what it saw, or tells you where it broke.
Your week, before and after
Before
Documentation contradicts the product.
Screenshots from three versions ago.
Nobody owns keeping flows written down.
After
Every documented step tried in the product.
Failures flagged, not published.
A record of every check.
Every step, tried in the product.
The page on the left, what Sabí saw on the right.
Enter the amount you received and click Save.
Failures are caught, not published.
A step that doesn't work is held back with the reason.
Click Send reminder for the remaining amount.
Sabí couldn't find this button. It's built, but not switched on for customers yet. This step won't be published until someone looks at it.
A record of every check.
See when each page was checked, approved or edited, and by whom.
You stay in control.
Choose which checks publish straight from a pass and which route to a human first.
Every page carries its own badge: checked in the product, backed by a ticket, or needs a human look.
A step that doesn't work is held back and flagged, never published.
Who approves what
Choose, per area of your product, what publishes on its own and what waits for a person.
A scenario, not a customer story
The new payment flow ships. Sabí tries all five documented steps. Four work. One button isn't switched on yet, so that step waits. QA sees it before any customer does.
Make the case to your manager
Documented flows drift from the real product, and nobody notices until a customer does.
A test version of your product and a test login.
Share of documented steps that are checked in the product.
Questions
What does it test against?
A test version of your product that you choose. Never your live product.
Does it change data?
It uses a test account on your test version. [Confirm what happens to data it creates, and how the test version is reset.]
What if a check is unreliable?
A step that can't be proven is held back and flagged, never published. [Confirm retry behaviour.]
See it on your own product.
Product documentation that writes itself, then checks itself.