topic : managed

3.3.1 - What “Ready” Actually Means - Define the readiness rule: say what has to be true, how it will be checked and who owns any remaining risk.

3.3.2 - Name the Risks Before Users Find Them - Name the launch risk: say what might break, what would trigger it and what response reduces the damage.

3.3.3 - Are You Comfortable Putting Your Name on This? - Set the ownership threshold: say what is still imperfect, what would happen if it failed and why shipping is still acceptable under those conditions.

When effort and systems stop being the same thing - At small scale, effort and systems look identical. The moment they stop looking identical is the moment you should have built the system one project ago.