IMHO one of the strongest aspects of the playbook analogy is that playbooks can vary widely between teams. Unlike software design patterns, which software architects have attempted to canonize into a central, authoritative tome, playbooks are fluid. They’re as messy as the real world, and they don’t pretend to be a covering set.
So, coaches will share methodologies and terminology. They will borrow. Their assistant coaches and teams will apprentice with them and go on to coach their own teams. But no two playbooks will be alike. And every coach will assemble a game card to meet each particular engagement.
I think that’s a great analogy for how product and design people (and, tech leads of all stripes) can approach the hairy problem of bringing products to life.