Boundary craft
Interface dependency workshop
Practice naming what a system depends on at its edges so reviews stay grounded in contracts, not screenshots.
We list observable interfaces first: APIs, file drops, human handoffs, and third-party touchpoints. Then we mark which dependencies are confirmed versus assumed.
You leave with a dependency grid template and a sample write-up you can adapt for vendor or build-vs-buy conversations.
Useful before integrations, migrations, or when two teams argue with different mental maps of the same product.
