Software feature launch · Production guide
Show a before-and-after software workflow with matched start states
Pick one task and define the same starting and finishing states in both builds. List each verified interaction, then capture a before/after pair from those builds.
Input and decision
This original practice interface has two paths to the same result. It is a simulated release comparison. A claim about a real Ciyo release requires evidence from the two actual builds.
Set up the comparison
Number each required action and remove time spent in a title animation from the comparison. When the older build is unavailable, say which side cannot be verified.
Make the comparison
Run each path from a reset state, log the clicks and compare its final output. The paired demo illustrates the method with an original mock interface.
Worked record
The downloadable worksheet includes the records below and a blank row for your own project.
| Build | Starting state | Action count | Ending state | Source |
|---|---|---|---|---|
| Before | Same sample input | Measure actual count | Defined outcome | Old build required |
| After | Same sample input | Measure actual count | Same outcome | New build required |
| Review | Matched account state | Exclude title cards | Confirm equality | Reviewer notes |
Check the result
A “three steps to one” claim requires real captures of both versions. Label an illustrative diagram as a proposal until both sides are verified.
Hand off the revision
Archive the simulated comparison as a practice artifact. For a release claim, attach recordings from the two actual product builds.
Review question
When may a release story claim a reduction from three actions to one?
Count the actions on real recordings of both product builds using the same task and permissions. The paired practice flows and demonstration recording document a fictional comparison only.
Use the task on your own brief
Use a copy of the worksheet to keep the project’s source files, reviewed options and decisions together.