1. Create a repository for architecture documentation and treat it like software that must be maintained and can be defective. 2. The documentation should be w

1. Create a repository for architecture documentation and treat it like software that must be maintained and can be defective. 2. The documentation should be written as a technical narrative for people to read like other documentation. This means written first in paragraph form but also contains diagrams of flow control. Be precise and treat this as a product. 3. This must be owned by the stakeholder that owns the corresponding business unit. Surely someone at your company wants to stop failing and stop burning money. If there is not a willpower to succeed then none of this matters. The people to do the work here are senior architects appointed by that owning stakeholder.