Turning the Crank: Design as a Mechanical Process
October 18, 2024 16 minute read
I asked the team to share their architecture and design documentation with me. In response, they sent me a 25-page document that walked through the evolution of their data model and application layout, culminating with their system architecture diagram.
That diagram is supposed to be the answer to the most important question anybody can ask about the project: what will this thing actually be once we’ve built it?
Here in this public venue, I have presented every bit of specific, proprietary information contained in my client’s core architectural design artifact. Which is to say: none at all!
If you can post your core design artifacts in public without redacting anything from them, they’re too generic to be useful!
