SA-301h · Module 2

Governance Board Communication

3 min read

Architecture governance boards review cross-cutting decisions, approve technology standards, and evaluate architectural compliance. Presenting to a governance board is a different discipline than presenting to a project team. The board has limited time, broad scope, and decision authority that affects multiple teams. The presentation must be efficient, decision-oriented, and framed in organizational — not project — terms.

Do This

  • Lead with the decision you need the board to make — "We are requesting approval to adopt GraphQL as a secondary API paradigm alongside REST"
  • Frame the impact across the organization — which teams are affected, what standards change, what costs are involved
  • Provide the evaluation matrix and the recommendation — the board reviews your analysis, they do not conduct their own

Avoid This

  • Present the full technical background — the board does not need to understand GraphQL internals to approve its adoption
  • Request approval without a clear recommendation — "we could do A or B, what do you think?" wastes the board's time
  • Omit the organizational impact — the board's job is organizational governance, not technical evaluation