There's some useful templates in there. From many many years' experience as an architect it lacks a fair bit of context though. How do you choose which tool or

There's some useful templates in there. From many many years' experience as an architect it lacks a fair bit of context though. How do you choose which tool or document template to use at a given time? Why in an architecture context do fine-grained things like creating an MVP even feature? Especially under business architecture? Architecture (business, technology, process or any other typre of architecture) has these basic steps: - Assess current state Understand the transformation (one or more processes) the client seeks to address, and find out what the technology landscape looks like. Start identifying stakeholders, and familiarise yourself with the client's worldview, environment, and the power and political landscape. It helps to spend time understanding a situation before assuming you know how to improve it. - Set an objective Identify who the client is, and define the client's objective. It's guided by the previous step. - Define scope Bound the solution by outlining it's features and functions, by defining what's out of scope, and by discussing the criteria by which success is measured. The scope delineates what stakeholders expect the project to deliver. - Design and build This is what most of us do. The Architecture Playbook seems to focus here most. That leaves managing risk and stakeholders, and the post-project review. A better guide might be had from the management consulting world - like Betty Vandenbosch's book Designing Solutions for Your Business Problems. My own architecture cheat sheet is https://www.wittenburg.co.uk/Work/Consulting.aspx https://www.wittenburg.co.uk/Work/Consulting.aspx For sure there are some templates in the architecture playbook that I'm going to read through to find gaps in my own knowledge.