COBIT 2019 Design and Implementation — Lesson 1: Enterprise Context, Strategy, Goals, Pain Points, and Design Factors

Learning Objectives

• Explain the roles, information, criteria, dependencies, and decision points governing enterprise strategy and enterprise goals.
• Implement or assess risk profile, pain points, and design factors using controlled evidence and acceptance criteria.
• Evaluate the condition where the planned enterprise strategy result cannot be trusted because enterprise goals scope, ownership, or prerequisite evidence is incomplete and select a proportionate corrective response.

Detailed Topics

• enterprise strategy applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• enterprise goals applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• risk profile applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• pain points applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.
• design factors applied to the course scenario, expected behavior, stakeholders, controls, risks, and evidence.

Instructor Demonstration

The instructor traces an enterprise tailoring COBIT 2019 to its strategy, risk profile, sourcing model, technology landscape, and improvement priorities. The walkthrough connects frameworks, processes, tools, decisions, and evidence captured in the COBIT design-factor assessment, target system blueprint, implementation plan, and benefits dashboard. It also tests the exception where the planned enterprise strategy result cannot be trusted because enterprise goals scope, ownership, or prerequisite evidence is incomplete.

Hands-On Exercise

Complete a controlled ISACA-aligned exercise covering Enterprise Context, Strategy, Goals, Pain Points, and Design Factors and preserve the verified result in the COBIT design-factor assessment, target system blueprint, implementation plan, and benefits dashboard.

1. Confirm scope, roles, criteria, prerequisites, information sources, dependencies, and acceptance conditions.
2. Execute the governance, risk, audit, security, data, cloud, or technology workflow while recording decisions and evidence.
3. Test normal behavior, one boundary condition, and the stated exception using a controlled scenario.
4. Document findings, corrections, ownership, retest criteria, communication, and operational handover.

Scenario Analysis

• Identify which role, process, objective, control, data source, or decision most strongly influences enterprise strategy.
• Compare two defensible responses and explain governance, risk, audit, security, privacy, operational, and business trade-offs.
• Determine how the COBIT design-factor assessment, target system blueprint, implementation plan, and benefits dashboard should be approved, retained, reviewed, retested, and updated.

Troubleshooting Guidance

Start where expected behavior first differs from the observed result. Check scope, criteria, ownership, data quality, process sequence, policy alignment, version compatibility, dependencies, status, and evidence separately. Treat “the planned enterprise strategy result cannot be trusted because enterprise goals scope, ownership, or prerequisite evidence is incomplete” as a hypothesis until records, interviews, configurations, calculations, and retest outcomes confirm the cause.

Validation Checklist

• Required roles, processes, criteria, controls, information, approvals, and dependencies are present.
• The COBIT design-factor assessment, target system blueprint, implementation plan, and benefits dashboard connects each conclusion to objective, reviewable evidence.
• Normal processing, a boundary condition, dependency behavior, and the stated exception were tested.
• Corrections, ownership, retest criteria, documentation, communication, and operational handover are complete.

Lesson Outcome

Learners can apply Enterprise Context, Strategy, Goals, Pain Points, and Design Factors, explain the resulting governance, risk, audit, security, data, or operational behavior, and defend the outcome through the COBIT design-factor assessment, target system blueprint, implementation plan, and benefits dashboard.