Documenting and Communicating IT Strategic Planning Outputs (CGEIT – Governance of Enterprise IT)
Overview
Within the ISACA CGEIT domain of Governance of Enterprise IT (and closely linked to Strategic Management), Documenting and Communicating IT Strategic Planning Outputs covers what happens after the IT strategy is developed. The strategy must be formally recorded, approved, translated into actionable artifacts and communicated to the right stakeholders in the right way, so that everyone understands it, accepts it and acts on it. A brilliant strategy that sits in a drawer delivers no value. CGEIT expects you to think like a governance professional who makes sure strategy turns into aligned decisions, investments and behaviour across the enterprise.
Why It Is Important
1. Alignment: Documented and communicated outputs make sure business and IT share one view of priorities, objectives and expected value. Business-IT alignment is the main goal of IT governance.
2. Accountability: Formal documentation sets out who owns which initiatives, outcomes and metrics. This supports RACI-based accountability and oversight by the board and executive committees.
3. Decision support: Portfolio, program and investment decisions (for example through a Val IT style approach or COBIT's APO05 Managed Portfolio) depend on a documented strategy as the reference point.
4. Stakeholder buy-in: Communication builds understanding and commitment. Without buy-in, change initiatives meet resistance.
5. Transparency and assurance: Boards, regulators and auditors need evidence that IT direction is deliberate, approved and monitored.
6. Continuity: Documentation keeps strategic intent intact through leadership changes and allows consistent review and updating.
7. Measurement: Documented goals, KPIs and targets make performance monitoring possible, for example through an IT balanced scorecard.
What It Is
IT strategic planning outputs are the formal products of the strategic planning process. Typical outputs include:
- IT strategic plan: vision, mission, strategic objectives, guiding principles and the link to enterprise goals (often shown with a COBIT goals cascade).
- Strategic roadmap: a sequenced, time-bound set of initiatives and programs that moves the organisation from its current state to its target state.
- Target enterprise architecture: the business, information, data, application and technology architectures that support the strategy.
- Investment portfolio and business cases: prioritised programs with expected benefits, costs, risks and funding.
- Tactical/operational plans: shorter-term plans that break the strategy down into actionable work.
- Performance measures: KPIs, KGIs, targets and scorecards linked to strategic objectives.
- Resource and sourcing strategy: people, skills, vendors and budget requirements.
- Risk considerations: strategic risks, risk appetite alignment and dependencies.
- Policies and principles: high-level direction that guides implementation.
- Communication plan: who needs what message, when, through which channel and from whom.
In COBIT 2019 terms, this relates mainly to APO02 Managed Strategy. Its practices include defining the strategic plan and roadmap and communicating the I&T strategy and direction. It also connects to EDM01 (governance framework), APO01 (management framework), APO03 (enterprise architecture) and APO05 (portfolio).
How It Works
Step 1 – Consolidate and document: Gather the analysis (current state, target state, gap analysis, business drivers) into a structured strategic plan. Keep documentation clear, concise and written in business language, not technical jargon. Version control and formal ownership are essential.
Step 2 – Validate and approve: Present the plan to the appropriate governance bodies, typically an IT strategy committee (board level) and an IT steering committee (executive/management level), for review and endorsement. Board or executive approval gives the plan authority and legitimacy.
Step 3 – Translate into actionable plans: Break the strategy down into tactical plans, programs, projects, budgets and service objectives. Link each initiative clearly to strategic objectives so that traceability is maintained.
Step 4 – Develop a communication plan: Identify stakeholder groups such as the board, executives, business unit leaders, IT staff, partners, regulators and end users. Tailor messages to each audience:
- The board wants value, risk, alignment and investment summaries.
- Business leaders want impact on their units, priorities and benefits.
- IT staff want direction, roles, skills and changes to ways of working.
- Vendors and partners need the relevant sourcing and architecture direction.
Step 5 – Deliver communication through suitable channels: Use executive briefings, town halls, intranet portals, dashboards, workshops and cascaded management meetings. Senior leadership sponsorship (tone at the top) greatly increases credibility.
Step 6 – Confirm understanding and gather feedback: Communication should be two-way. Use surveys, feedback sessions and checks that objectives are reflected in departmental plans and individual goals.
Step 7 – Monitor, review and update: Track performance against documented KPIs, report progress to governance bodies, and revise the strategy when business conditions change. Changes must be communicated again. The strategy is a living document.
Key Governance Roles
- Board / IT Strategy Committee: directs and approves strategic direction and oversees value and risk.
- Executive management / IT Steering Committee: prioritises investments, approves plans and monitors execution.
- CIO: leads development, documentation and communication of the IT strategy, in partnership with business leaders.
- Business owners: co-own the outcomes and benefits.
- Enterprise architects, PMO and portfolio managers: translate strategy into architecture and portfolios.
Common Pitfalls
- Strategy written in technical language that the business does not understand.
- No formal approval, so the strategy lacks authority.
- One-way, one-time communication with no follow-up.
- No link between initiatives and enterprise goals.
- No metrics, so success cannot be measured.
- The document is never updated as conditions change.
- Messages are not tailored, so stakeholders get irrelevant detail.
Exam Tips: Answering Questions on Documenting and Communicating IT Strategic Planning Outputs
1. Think governance, not technology. CGEIT answers favour business alignment, value delivery, stakeholder engagement and accountability over technical detail.
2. Business alignment is the anchor. Prefer options that link IT strategic outputs explicitly to enterprise goals and objectives.
3. Approval comes before communication. If a question asks what should happen first after drafting the strategy, the best answer usually involves validation and approval by the appropriate governance body, such as an IT strategy committee or the board.
4. Tailored communication beats generic distribution. Answers that say "send the full strategy to all staff" are usually wrong. Look for stakeholder-specific messaging.
5. Executive sponsorship matters. Choices showing senior leadership endorsing and communicating the strategy are typically stronger.
6. Look for measurable outcomes. Prefer options that include KPIs, targets and monitoring mechanisms. A strategy without measures cannot be governed.
7. Two-way and ongoing communication. The best answers involve feedback loops and regular updates, not a single announcement.
8. Recognise the "MOST important" trap. When several answers seem valid, choose the one with the broadest governance impact, such as stakeholder buy-in, alignment or board approval, over operational details like formatting or tool choice.
9. Know the escalation path. Strategic matters go to the strategy committee or board. Prioritisation and execution matters go to the steering committee.
10. Traceability is key. Initiatives, projects and budgets should trace back to documented strategic objectives. If an exam scenario describes projects with no clear link to strategy, the root cause is often poor documentation or communication of strategic outputs.
11. Living document mindset. If business conditions change, the correct response is usually to review and update the strategy and then communicate the changes, not to continue unchanged or abandon it.
12. Use COBIT references wisely. APO02 (Managed Strategy) is the core reference. Connect it to EDM processes for direction and oversight and to APO05 for portfolio translation.
13. Watch for root-cause questions. If a scenario shows resistance, misaligned spending or duplicated initiatives, a likely cause is inadequate communication or a lack of a documented and approved strategy.
14. Eliminate extremes. Discard answers that are purely technical, purely tactical or that bypass governance structures.
Sample Question Approach
Scenario: After a new IT strategy is approved, business units continue funding projects that do not support it. What should the governance professional do FIRST?
Reasoning: The issue points to weak communication and a weak link between strategy and investment decisions. The best answer is to make sure the strategy is effectively communicated to business leaders and embedded into the portfolio and investment prioritisation process. Cancelling projects outright or buying new tools would not address the root cause.
Summary
Documenting and communicating IT strategic planning outputs turns strategy into shared understanding and coordinated action. Effective practice includes:
- clear, business-focused documentation;
- formal approval by governance bodies;
- translation into roadmaps, portfolios and measurable objectives;
- tailored, sponsored, two-way communication;
- continuous monitoring and updating.
For the exam, always choose answers that strengthen alignment, accountability, stakeholder buy-in and measurable value delivery.
