10.2 Enterprise Goals and Alignment Goals

Quick Answer: COBIT 2019 organizes enterprise goals and alignment goals on a balanced scorecard (BSC) with four perspectives: Financial, Customer, Internal, and Learning and Growth. Enterprise goals are board-level outcomes for the whole enterprise. Alignment goals translate those outcomes into I&T-related goals — security of information, delivery of I&T services, competent people who understand both technology and the business. They are not “IT department goals.” The full official catalogs live in COBIT 2019 Framework: Introduction and Methodology and COBIT 2019 Framework: Governance and Management Objectives.

Section 10.1 gave you the cascade machinery. This section is the two middle layers: what enterprise goals look like, what alignment goals look like, and why both sit on a BSC instead of a single finance list. Governance and Management Objectives still owns this material. If you skip the BSC, you will miss items even when you remember the cascade order.

Why a balanced scorecard

Kaplan and Norton’s balanced scorecard exists because a purely financial dashboard is too late and too narrow. An enterprise can hit this quarter’s margin while customers leave, processes rot, and the skills needed to change walk out the door. COBIT borrows that idea so EGIT is not scored only on I&T spend or only on uptime.

The four commonly taught perspectives, with representative official-style enterprise goals — not a homemade numbered roster:

Staff skills, motivation and productivity is another official-style enterprise goal you must be able to recognize. Foundation items care that people-and-skills outcomes live on the scorecard. If a stem quotes a specific BSC pairing, trust the official table in Introduction and Methodology rather than a classic-BSC guess about which cell holds “skilled people.”

Skipping the BSC is an exam trap. A stem that says “enterprise goals are the financial targets in the annual budget” is incomplete. A stem that says “alignment goals are the IT department’s operational KPIs” is worse. Both layers use all four perspectives.

Enterprise goals

Enterprise goals are outcomes the enterprise must achieve. They are not IT projects and not department slogans. COBIT 2019 publishes a generic catalog of 13 enterprise goals, each with example metrics, grouped on the BSC. You should recognize the kind of goal. You should not recite a reconstructed EG01–EG13 list as if you photocopied the book unless a stem quotes official wording.

Representative official-style enterprise goals you should know on sight:

• Portfolio of competitive products and services — the enterprise can offer what the market will actually buy.
• Managed business risk — enterprise risk, including I&T-related risk, stays inside appetite.
• Compliance with external laws and regulations — the enterprise meets outside duties.
• Quality of financial information — numbers used to steer the enterprise are fit for that use.
• Customer-oriented service culture — service is designed around the customer, not around internal convenience.
• Quality of management information — leaders see timely, reliable information, not a swamp of conflicting reports.
• Optimization of business process costs — processes are economical without becoming unsafe or non-compliant.
• Staff skills, motivation and productivity — the enterprise has skilled, motivated people who can do the work.

The full wording, identifiers, example metrics, and mapping tables live in COBIT 2019 Framework: Introduction and Methodology and are used again in Governance and Management Objectives. Design factor 2 later reuses the same enterprise-goal catalog when you tailor a system. This section is recognition and BSC placement, not a license to fabricate IDs.

Enterprise goals still cascade from stakeholder drivers and needs. Cedar Ridge’s patient-safety need did not become “install multifactor authentication.” It became enterprise goals about managed business risk, compliance with external laws, quality of management information, and continuity of care. Authentication may show up two layers down.

Alignment goals

Alignment goals translate enterprise goals into I&T-related outcomes. They answer: what must information and technology achieve so the enterprise goals are possible?

COBIT 2019 publishes 13 alignment goals, also on the same four BSC perspectives. COBIT 5 called this layer IT-related goals. The 2019 rename is deliberate. ISACA dropped the “IT goals” shorthand because candidates and practitioners treated the layer as the IT department’s private objectives. Alignment goals belong to enterprise I&T — every use of information and technology that serves enterprise goals, including operational technology, digital products, data, shadow IT, and vendor platforms.

Representative official-style alignment goals:

• Security of information, processing infrastructure and applications, and privacy
• Delivery of I&T services in line with business requirements
• Managed I&T-related risk
• Quality of technology-related financial information and quality of I&T management information
• Competent and motivated staff with mutual understanding of technology and business
• I&T compliance with external requirements and with internal policies
• Realized benefits from I&T-enabled investments and services

Cedar Ridge’s alignment layer is therefore not “the CIO’s OKRs.” Security of information and delivery of I&T services for clinical systems are enterprise I&T outcomes. A radiology-owned imaging archive, a nurse-built scheduling spreadsheet, and a vendor medication-alert service all sit inside those alignment goals. “We do not own it, so it is not an IT goal” is the trap the rename exists to kill.

Same BSC, two layers

Put the two layers on one card so you can see the translation.

The table is a teaching map, not a substitute for the official mapping matrices. Official tables mark primary and secondary links. One financial enterprise goal can pull several alignment goals. One alignment goal can support several enterprise goals. That is the same many-to-many rule you already learned.

Do not collapse the two layers into one sentence. Quality of financial information (enterprise) is not the same claim as quality of technology-related financial information (alignment). The second exists to serve the first. Staff skills, motivation and productivity (enterprise) is not the same claim as competent and motivated staff with mutual understanding of technology and business (alignment). The alignment version is the I&T contribution to the enterprise people-goal.

Metrics stay on their layer

Each goal in the official catalogs ships with example metrics. Use them as a recognition test.

• An enterprise-goal metric talks about the business outcome: competitive win rate, material risk events, regulatory findings, cost per process, customer satisfaction.
• An alignment-goal metric talks about the I&T contribution: service delivery against business requirements, security incidents, I&T financial-information quality, staff who understand both the technology and the business.

If the board is shown only “mean time to repair,” someone skipped the enterprise layer. If the CIO is shown only “operating margin,” someone skipped the alignment layer. Both layers need measures, and the measures are not interchangeable.

Exam traps

1. Calling alignment goals “IT goals” as if they belong only to the IT department. They are I&T-related alignment outcomes for the enterprise.
2. Skipping the BSC. Enterprise and alignment goals are not a finance-only list and not an operations-only list.
3. Inventing a complete numbered catalog and treating your reconstruction as official. Recognize representative wording; send the full list back to the two framework books.
4. Collapsing the two layers. An enterprise goal and its related alignment goal are paired, not identical.
5. Starting from a department scorecard. Marketing KPIs or CIO OKRs are inputs. They are not automatically enterprise goals or alignment goals until they sit on the cascade and the BSC.

How this shows up on the exam

Expect four shapes. First, “which four BSC perspectives organize enterprise and alignment goals?” Answer Financial, Customer, Internal, and Learning and Growth. Second, a stem that calls alignment goals the IT department’s goals — refuse it. Third, a recognition item that quotes an official-style goal (customer-oriented service culture, optimization of business process costs, security of information) and asks whether it is an enterprise goal, an alignment goal, or neither. Fourth, “where is the full catalog?” Introduction and Methodology and Governance and Management Objectives — not a GRC tool and not ISO Annex A.

If you can place a goal on the BSC, say whether it is enterprise or alignment, and refuse the “IT-department goals” shortcut, you have this section.