Velocity Architecture: Threat Modeling & Velocity Modeling
Threat modeling finds the trust boundaries. Velocity modeling finds the trust limits.
A hands-on workshop in the Velocity Architecture method: threat modeling and velocity modeling, run together on your own processes, so your team leaves knowing how fast each step can safely go.
Why It Matters
Most organizations are adopting AI the way factories first adopted electricity: swapping in the new tool and keeping everything else the same. The gains, and the risks, come from redesigning how the work is done.
Gathering requirements first no longer works on its own, because nobody can list everything an AI system might do. Find the limits first, and the requirements follow.
Threat modeling already gives teams a way to find where trust changes in a system. Velocity modeling adds the question AI forces: how fast can each step go before trust breaks? It’s built to feel familiar to anyone who has walked a data-flow diagram, and it works on a new process or one you already run. Read the summary of Velocity Architecture.
What We Cover
Velocity, trust, limits and decay: the four ideas behind the method
Threat modeling: drawing a process and its trust boundaries
PACER: how fast partners, attackers, customers, exposure and rivals make you go
LAW: the hard stops set by law, contracts and accountability
PROBE: finding each step's trust limit across people, reversibility, output, boundary and expense
The six decisions, and turning each limit into a requirement
What You Leave With
- A team that can run threat modeling and velocity modeling together
- A first register of threats and limits for one of your own processes
- A shared language for AI decisions across leadership and engineering
- A clear view of where AI is worth the most, and what has to be true before it goes there