- Build not for longevity but obsolescence
- If it doesn't have an API, it's not worth having
And one more that he does not explicitly mention, but that I think is a very important one for organizations newly undertaking architecture and technology practices: become comfortable with the not knowing.
All too often I've seen all sorts of projects and initiatives fail due to the very human desire (some would say need) to know it all up-front. This is impossible. Deal with it.
Yes, the architect will work with you to provide a broad scheme... blueprints if you will for the planned vision. This is not a detailed plan, just an overview. There are still risks, and unknowns. As you work though the plan (via projects), you identify and manage the risk. You cannot -- must not -- stall progress until all the unknowns are known. You'll wait forever.