What it shows:
A strategic alignment map that traces top-level corporate or project Goals down to specific, measurable Objectives, and finally links them to the actionable Business Services that will execute them.
Why it’s needed:
Budget justification and KPI alignment. This proves to executive sponsors that the delivery is not just a technical exercise. It directly maps the deployed services to strategic KPIs. If the project’s budget or scope is ever questioned, this diagram shows exactly which executive goal will fail if the project is cut.
When to use it:
Highly recommended for SADs when kicking off major transformation projects, massive COTS platform deployments, or any engagement funded by a strategic or executive budget. It serves as the ultimate “executive summary” visual for the C-Suite.
When NOT to use it:
Generally best to omit for operational maintenance, pure infrastructure hardware refreshes (e.g., swapping out network switches, upgrading hypervisor versions), or “keep the lights on” IT projects. If the project is just maintaining the status quo and not actively driving a new strategic business objective, this diagram will look like unnecessary consulting fluff.
Example:
