Users forgive what you warn them about, not what surprises them - A 30 minute interactive Q&A on naming the rough edges before users hit them. Examples not tutorials. Places are limited to twenty.
reducing risk :: Spotting what could go wrong and shrinking the size of the bet.
Reviewing AI-Assisted Code Changes - When AI changes a lot of code quickly, review is no longer about reading lines. It’s about making sure you still understand what will happen in production.
3.3.2 - Name the Risks Yourself Before Users Find Them in Production - Name the launch risk: say what might break, what would trigger it and what response reduces the damage.
2.2.3 - Understanding the Shape of the System Before You Change It - Map the system shape: say which part owns what, what each part depends on and where the important handoff happens.
1.2.3 - The Risks You're Avoiding Naming Are the Ones That Bite You - Name the named risk: say what might fail, who or what it would affect and what action will reduce the damage.
The risk you won't say out loud is the one that ships - A 30 minute interactive Q&A on naming the risk the team can feel but no one wants to say. Examples not tutorials. Places are limited to twenty.