A VISUAL COMPANION TO THE BOOK
From an idea
to a working
product.
See what happens at every stage of development, what the work produces, and what needs checking before you move on.
Eight stages. A clear route. A guide you can print.
Evidence moves it forward.
THE WHOLE PICTURE
Follow the work from start to finish.
Start with a useful outcome. Then follow the decisions, working results, and checks.
Quality is part of every stage. Requirements get checked before code. Changes get reviewed and tested. Live use needs observation, support, and recovery.
BEFORE STAGE 01
Give the idea a useful outcome.
A person → a difficulty → work they need to finish.
OPEN ANY STAGE
What happens next?
Each stage has a visual flow, concrete actions, a result, and a condition for moving forward.
Understand the starting point
Look at the current work, prototype, dependencies, and failures before choosing the next move.
Agree on the result
Turn observed needs into a bounded release, explicit rules, and checkable outcomes.
Design the system
Connect the user journey, interface states, data, and external services before building them together.
Build working components
Build in small slices. Keep the requirement, changed files, and actual check results together.
Test quality and risk
Test the whole outcome, its boundaries, and its failure paths. Check the saved state as well as the message.
Pilot and accept
Observe a bounded live use, learn from the work, and separate software acceptance from permission to expand.
Release version 1.0
Rehearse the operating response, protect existing records, and open the checked version under explicit conditions.
Take over and improve the product
Transfer usable knowledge and responsibility. Feed operating evidence into the next release.
THE THREAD THROUGH IT ALL
Testing starts with
a clear promise.
A passing check needs a version, conditions, and an observed result. A correction needs another check.
See the testing loop