How architects actually work. Process, methodology, and the thinking that ships projects.
The anatomy of a solution design document that actually gets read. What goes in each section, what to leave out, and how to structure it so stakeholders and developers both get what they need.
Why architects always present three options — even when they already know the answer. How to frame alternatives, grade them against criteria, and use the process to build stakeholder trust.