The principal architect's brief

Most architecture functions are asked for the wrong things: standards documents, technology rationales, review boards. These artifacts have their place, but they are not why an organization needs architecture. They are what architecture produces when nobody has given it a real brief.

The real brief is shorter and harder: make the organization's complexity legible to the people who must make decisions about it. An executive should be able to ask 'what breaks if we acquire this company?' or 'what does this platform actually depend on?' and get an answer in days, not quarters.

That requires architects who spend less time in diagram tools and more time in decision rooms — who treat influence, not documentation, as their primary output. The best architecture functions are measured by the quality of the decisions they enable, not the volume of the artifacts they produce.

If you lead an organization, give your architects that brief. If you are an architect, write it yourself and start acting on it.