What it shows:
A hierarchical “org chart” of the enterprise, breaking down the business from the highest executive level down through specific divisions, departments, and finally to the individual roles interacting with the deployed system.
Why it’s needed:
Governance, escalation, and stakeholder mapping. This diagram serves as the political map. It proves accountability for the budget and security sign-off. If a project is blocked by red tape, this diagram shows exactly where to escalate.
When to use it:
Highly recommended for SADs when deploying enterprise-wide solutions that cross multiple departmental boundaries. It is also highly recommended when establishing complex Role-Based Access Control (RBAC) to prove which departments get which permissions.
When NOT to use it:
Generally best to omit for deployments contained entirely within a single, existing team. If the deployment is just a localized software upgrade or backend infrastructure (like a firewall or load balancer) where the organizational structure is completely irrelevant to the technology, do not include an org chart.
Example:
