public

You've seen them. You've probably made one: The architecture vision diagrams. The block diagrams, the message bus topologies... How many of these diagrams ever actually get built?

We never really finish constructing one of these grand visions before something interferes. Maybe it's a merger or acquisition. Maybe your company has a "regime change". (After all, the average tenure of a CIO is down to 18 months!)

The "end state" vision never gets built. Instead, we need to focus on how to flex and change, incorporating new technology, new principles, new business models, and even the last generation's legacy. Call it agile architecture, or meta-architecture, or "how I learned to love laminated stucco." It's architecture without an end state.

Also, "All models are wrong, but some are useful"