Study guide

5.2 Tailored to Enterprise Needs

ISACA COBIT 2019 Foundation Certificate Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 Certificate Rules, Retakes, and How to Study

2 Chapter 2: Framework Introduction

2.1 Purpose of COBIT and EGIT 2.2 I&T Versus the IT Function 2.3 COBIT 2019 Product Family 2.4 Stakeholders, Audience, and Benefits

3 Chapter 3: Framework Positioning

3.1 Umbrella Framework and Related Standards 3.2 Evolution from COBIT 5 to COBIT 2019

4 Chapter 4: Governance System Principles I

4.1 Provide Stakeholder Value 4.2 Holistic Approach 4.3 Dynamic Governance System

5 Chapter 5: Governance System Principles II and Framework Principles

5.1 Governance Distinct from Management 5.2 Tailored to Enterprise Needs 5.3 End-to-End Coverage 5.4 Three Governance Framework Principles

6 Chapter 6: Governance System Components Overview

6.1 Seven Governance System Components 6.2 Generic Versus Variant Components 6.3 Focus Areas

7 Chapter 7: Process and Structure Components

7.1 Processes Component 7.2 Practices, Activities, and Metrics 7.3 Organizational Structures 7.4 Principles, Policies, and Frameworks

8 Chapter 8: Information and People Components

8.1 Information Component 8.2 Culture, Ethics, and Behavior 8.3 People, Skills, and Competencies 8.4 Services, Infrastructure, and Applications

9 Chapter 9: Integrating Governance System Components

9.1 How Components Work Together 9.2 RACI Charts and Key Roles 9.3 Components Supporting Objectives

10 Chapter 10: The Goals Cascade

10.1 The Goals Cascade 10.2 Enterprise Goals and Alignment Goals

11 Chapter 11: Core Model and EDM Governance Objectives

11.1 The 40-Objective Core Model 11.2 EDM Governance Objectives 11.3 Governance Versus Management Objectives

12 Chapter 12: APO Align, Plan, and Organize

12.1 APO Strategy, Architecture, and Innovation 12.2 APO Portfolio, Resources, and Relationships 12.3 APO Risk, Security, Data, and Quality

13 Chapter 13: BAI, DSS, and MEA Management Objectives

13.1 BAI Build, Acquire, and Implement 13.2 DSS Deliver, Service, and Support 13.3 MEA Monitor, Evaluate, and Assess

14 Chapter 14: Performance Management

14.1 Performance Management Principles 14.2 Capability Levels 0–5 and Maturity

15 Chapter 15: Designing a Tailored Governance System

15.1 Why Tailor: Design Factors 15.2 The Eleven Design Factors 15.3 Design Workflow and Toolkit

16 Chapter 16: Business Case

16.1 Business Case for EGIT 16.2 Benefits, Costs, Risk, and Tracking

17 Chapter 17: Implementation Lifecycle

17.1 Implementation Lifecycle Overview 17.2 Seven Implementation Phases 17.3 Roles, Pain Points, and Challenges 17.4 Design Guide and Implementation Guide Together

5.2 Tailored to Enterprise Needs

Key Takeaways Explain This Topic AI

There is no single correct COBIT implementation; the governance system must be tailored to the enterprise.

Eleven design factors customize and prioritize components and objectives rather than treating all 40 objectives as equal.

Variants and focus areas further adapt generic guidance without replacing the 40-objective core model.

The classic trap is “implement all 40 objectives equally” or drive every objective to the same capability level.

Design-factor depth belongs to the Designing domain; this principle only requires why tailoring exists and what COBIT uses to do it.

Last updated: August 2026

Quick Answer: There is no single correct COBIT implementation . The governance-system principle tailored to enterprise needs says the system must be customized using design factors that prioritize components and objectives. COBIT 2019 names 11 design factors . Variants and focus areas also tailor. The exam trap is “implement all 40 objectives equally,” or drive every objective to the same capability.

A 40-person professional-services firm, a global bank, and a municipal water utility can all use COBIT 2019. They must not end up with the same governance system. Different strategy, different risk, different regulation, different size, and a different role of IT produce different priorities. If they did look identical, at least two of them would be wasting scarce people on work that does not move stakeholder value.

COBIT 5 already said the framework should be applied to the enterprise. COBIT 2019 made tailoring a first-class governance-system principle and then published a design-factor toolkit so the principle is not a slogan. The later Designing a Tailored Governance System domain (7%) teaches the workflow and the toolkit math. This Principles item only needs you to know why tailoring exists, what COBIT uses to do it, and which “complete implementation” story to reject.

Why “one true COBIT” fails

Think of a building code versus a finished building. The code is shared. The hospital, the warehouse, and the apartment tower still look different because the site, the occupancy, and the risk are different. The 40 governance and management objectives are the code. Design factors are the site conditions. Tailoring is how you get a building you can actually occupy.

A Foundation stem that praises a consultant for “standing up all 40 objectives at capability level 5 so nothing is missed” is describing a failed tailoring job, not a gold-standard program. Completeness in COBIT 2019 means the right objectives at the right target capability for this enterprise , not every objective at the maximum score .

Tailoring is also how COBIT stays honest about resources. The purpose of EGIT is value from I&T through a balance of benefits, risk, and resources. Treating every objective as equally urgent burns the resource dial and delays the benefit dial. The principle is therefore not a luxury for large enterprises. Small enterprises have more reason to tailor, because they cannot staff a copy of a global bank’s committee stack.

What actually gets tailored

Tailoring is not “skip COBIT.” It is a deliberate choice about three things.

Which objectives matter most. Not all 40 get the same attention or the same target capability. A digital first-mover will raise innovation and architecture. A cost leader will raise budget, assets, and operations. A heavily regulated insurer will raise risk, security, compliance, and assurance.

Which components need extra weight. A culture problem is not solved by adding another process narrative. A missing decision right is not solved by buying a new tool. Holistic approach (Chapter 4) said the seven component types work together. This principle says you still emphasize the components the design factors point at.

How generic guidance is specialized. The core model describes generic components. A variant is an alternate way a component can be realized so it fits context — for example, a small-enterprise organizational structure that cannot copy a global bank’s committee stack. A focus area applies a lens to the core model for a topic such as small and medium enterprises, information security, DevOps, or risk. Focus areas do not replace the 40. They apply them.

Together, design factors, variants, and focus areas are why two faithful COBIT implementations can look different and both be correct.

The 11 design factors — preview, not the full toolkit

ISACA publishes eleven design factors. You do not need the full design-workflow arithmetic on a Principles item. You do need the names and the idea that each factor can raise or lower the importance of particular objectives and components.

# Design factor What it asks Why it changes the system

1 Enterprise strategy Growth, innovation, cost leadership, client service, or a mix? A digital-growth strategy elevates innovation, architecture, and data; a cost-leadership strategy elevates budget, assets, and operations

2 Enterprise goals Which balanced-scorecard outcomes matter most? Goals cascade into alignment goals and then into governance and management objectives

3 Risk profile Where is I&T-related risk concentrated? High cyber or third-party risk raises security, risk, vendor, and continuity objectives

4 I&T-related issues What is already going wrong or frustrating stakeholders? Current pain — failed projects, shadow IT, audit findings — points at specific objectives

5 Threat landscape Normal or high? A high threat landscape pushes security services, continuity, and risk optimization

6 Compliance requirements Low, normal, or high? Heavily regulated enterprises raise compliance, assurance, and control objectives

7 Role of IT Support, factory, turnaround, or strategic? Strategic IT needs stronger strategy, architecture, innovation, and relationship objectives

8 Sourcing model for IT Insourced, cloud, outsourced, hybrid? Heavy outsourcing or cloud raises vendor, service-agreement, and continuity work

9 IT implementation methods Traditional, Agile, DevOps, hybrid? Agile and DevOps change how change, projects, and configuration should be governed

10 Technology adoption strategy First mover, follower, or slow adopter? First movers need more innovation and architecture; slow adopters need more operational stability

11 Enterprise size Large, or small and medium? Size changes structures, formality, and which variants are realistic

Memorize the names . A stem that lists “enterprise strategy, risk profile, and sourcing model” is pointing at design factors, not at a secret twelfth system principle. The Designing domain will teach archetypes — including the four classic roles of IT — in more depth. Do not try to run the whole design toolkit from this section.

A useful grouping for recall, not an official regrouping: factors 1–4 describe who we are and what hurts (strategy, goals, risk, current I&T issues). Factors 5–11 refine that picture (threats, compliance, role of IT, sourcing, methods, adoption, size). You will meet that initial-scope versus refine-scope split again in the design workflow. For Principles, the scoring fact is simpler: all eleven are design factors, and design factors are how this principle is made real.

Scenario: two hospitals, one framework

Riverbend Community Hospital is a 90-bed independent facility. Its electronic health record is a single-vendor software-as-a-service (SaaS) platform. IT is a twelve-person shop. The board’s strategy is safe, reliable care — not being a digital first mover. Compliance is real but local. The threat landscape is closer to normal than to a research-hospital target.

MetroHealth System is a multi-hospital academic center building a patient-facing digital product, running a hybrid cloud, and operating research data lakes. IT is a strategic function. The threat landscape is high. Compliance requirements are high. Implementation methods are mixed Agile and DevOps. Enterprise size is large.

Both can adopt COBIT 2019. Neither should implement all 40 objectives at the same capability.

Riverbend will likely raise APO10 Managed Vendors , APO09 Managed Service Agreements , DSS04 Managed Continuity , and the EDM risk and resource objectives, because a single SaaS clinical platform is an existential vendor concentration. It will not staff a large APO04 Managed Innovation engine, and it will use small-enterprise variants for organizational structures rather than inventing a MetroHealth-style architecture review board it cannot sustain.

MetroHealth will raise APO02 Managed Strategy , APO03 Managed Enterprise Architecture , APO04 Managed Innovation , APO13 Managed Security , APO14 Managed Data , and MEA03 Managed Compliance With External Requirements . It may apply an information-security focus area on top of the core model. It still uses the same 40-objective spine. The priorities differ because the design factors differ.

If a consultant tells either hospital “COBIT means standing up all 40 objectives equally,” that consultant is violating this principle. Equal treatment is not rigor. It is a refusal to design.

Exam trap: implement all 40 equally

This is the highest-yield trap attached to the principle.

Wrong instincts:

  • “A complete COBIT implementation means capability level 5 on every objective.”
  • “Skipping or deprioritizing an objective is always non-compliant.”
  • “Design factors are optional decoration for large enterprises.”
  • “Focus areas replace the core model, so you can ignore the 40.”
  • “The same RACI and the same committees work for every enterprise.”
  • “Tailoring is something you do after you have implemented everything.”

Right instincts:

Tailoring is required, not optional.

Design factors customize and prioritize components and objectives.

Some objectives will have higher target capability than others.

Variants and focus areas further adapt generic guidance.

A small enterprise and a regulated academic medical center should not look the same.

The Business Case and Designing domains will add the cost argument: treating every objective as equally urgent wastes resources and delays value. That argument starts here, as a principle. When a stem offers a one-size-fits-all COBIT program, reject it. When it offers design factors, variants, or focus areas as the way two enterprises can both be faithful and still differ, take it.

Loading diagram... Tailoring a governance system with design factors, variants, and focus areas