17.4 Design Guide and Implementation Guide Together
Key Takeaways
- The Design Guide answers what the tailored system should look like: design factors, prioritized objectives, and target capability.
- The Implementation Guide answers how to move from current state to that target through the seven-phase lifecycle.
- Foundation tests recognition of both guides; do not over-study toolkit math or programme simulation for this sitting.
- COBIT Design & Implementation is a separate exam: 60 questions, 180 minutes, 60% pass, US$275, with Foundation as the published prerequisite.
- After this last domain, drill /practice/cobit-2019 against the eight official weights — especially the 30% components and 23% objectives domains.
Quick Answer: The Design Guide answers what the tailored system should look like — factors → prioritized objectives → target capability. The Implementation Guide answers how to move from current state to that target through the seven phases. Foundation tests recognition of both. COBIT Design & Implementation is a different sitting: 60 questions, 180 minutes, 60% pass, US$275, with Foundation as the published prerequisite. Do not over-study toolkit math for Foundation. When this domain is done, use /practice/cobit-2019 against the eight exam domains.
This is the last teaching section in the guide. It locks two books together, separates two certificates, and sends you back to retrieval practice. If you still cannot say which guide owns what versus how, fix that before you drill anything else in this 8% domain.
What versus how
Keep the two companion books in one sentence you can recite.
| Question the enterprise is asking | Owner | What you get |
|---|---|---|
| What should our governance system look like, and at what capability? | Design Guide | A tailored profile: which of the 40 objectives matter more, target capability, component realization |
| How do we get from here to that profile, and then keep improving? | Implementation Guide | The seven-phase continual-improvement lifecycle |
| What are the principles and the product architecture? | Introduction and Methodology | Concepts, including that design and implementation exist |
| What does a named objective contain? | Governance and Management Objectives | The core model you just tailored and are now implementing |
The handoff is real work, not a diagram decoration. Design concludes: resolve priority conflicts, complete the system, set target capability. That concluded profile is the phase-3 answer to where do we want to be? Implementation then assesses where we are now, plans what needs to be done, executes, reviews benefits, and keeps momentum. If design never happened, phase 3 has nothing honest to aim at, and the programme slides into boiling the ocean.
Aether’s CISO urgency belongs inside design as threat and compliance factors, then inside implementation as a sponsored lifecycle toward those raised security and data targets. Northline’s plant urgency belongs inside design as operations, assets, and cost, then inside implementation as a smaller, prioritized set of changes. In both enterprises, opening the Implementation Guide first so someone can “show progress” is the start-without-a-design trap you already learned.
Design without implementation is a workshop binder. Implementation without design is seven phases of the wrong work. Foundation likes the second failure. Do not create the first one either.
What Foundation actually tests
Foundation is a 75-question, 120-minute, 65% pass, US$175, no-prerequisite, closed-book recognition exam. In this domain it asks you to:
- Recognize the seven questions in order
- Know that implementation is a cycle, not software and not a one-time project
- Separate pain points from trigger events
- Place audit as advisor, not owner
- Keep Design on what/capability and Implementation on how
- Refuse boiling the ocean and binder-only “success”
It does not ask you to operate the design-toolkit spreadsheet, score eleven factors into a 40-row model, build a real RACI for a live enterprise, or manage a 180-minute applied case. Candidates who sink nights into toolkit arithmetic for Foundation are studying the wrong sitting.
If a stem claims Foundation requires you to key the toolkit, it is describing Design & Implementation lore, not this exam. If a stem claims the two guides are the same workshop at two reading levels, reject it.
Foundation versus Design & Implementation
ISACA’s published next certificate is COBIT Design & Implementation. It is not a harder form of the same 75 items. It is a different exam on applied design and implementation.
| COBIT 2019 Foundation | COBIT Design & Implementation | |
|---|---|---|
| Items | 75 | 60 |
| Time | 120 minutes | 180 minutes |
| Pass mark | 65% | 60% |
| Fee | US$175 | US$275 |
| Prerequisite | None | Foundation (published prerequisite) |
| Depth | Recognition of concepts, named lists, and traps | Applied design and implementation in more depth |
| Toolkit math | Know purpose, not operation | In scope at a much deeper level |
Do not swap the logistics. Foundation is shorter, cheaper, 65%, and open to anyone. Design & Implementation is longer, costs more, uses a 60% pass mark, and assumes you already hold Foundation. You cannot treat them as interchangeable sittings. You also should not try to “get ahead” by drilling D&I toolkit steps on the night before Foundation — those hours belong to components (30%) and objectives (23%).
Close the guide: eight domains and /practice/cobit-2019
You now have the full official blueprint as teaching. Study time should follow weight, not chapter order and not what felt new this week.
| Domain | Weight | ~items of 75 | What “done” looks like |
|---|---|---|---|
| Governance System and Components | 30% | ~23 | Seven components, variants, focus areas, how they work together |
| Governance and Management Objectives | 23% | ~17 | Goals cascade, 40-objective core model, EDM vs management domains |
| Principles | 13% | ~10 | Six system principles and three framework principles by name |
| Framework Introduction | 12% | ~9 | EGIT purpose, I&T vs IT function, product family, audience |
| Implementation | 8% | ~6 | This chapter: cycle, seven questions, roles, design+implementation |
| Designing a Tailored Governance System | 7% | ~5 | Eleven factors, four-step workflow, toolkit purpose |
| Performance Management | 4% | ~3 | Capability 0–5 versus maturity of a focus area |
| Business Case | 3% | ~2 | Why EGIT is funded; benefits, cost, risk, tracking |
Those rounded counts sum to 75. They are a planning model, not a promise about your form.
Use /practice/cobit-2019 for retrieval. Use this guide when a miss shows a hole in a named list. A closed-book exam punishes knowledge that only exists while the page is open.
A practical last-week pattern:
- Write the named lists from memory: 6+3 principles, 7 components, 5 domains, 40 IDs at recognition level, 11 design factors, 7 implementation questions, capability 0–5.
- Drill mixed sets on /practice/cobit-2019, with extra volume on the 30% and 23% domains.
- Re-read only the sections attached to misses — especially any swap of Design versus Implementation, or phase 2 versus phase 3.
- Sit inside the eligibility window. Foundation is a certificate. Passing it is the published door to Design & Implementation if you want the applied sitting later.
If a stem on exam day offers a programme that designs first, then walks the seven questions with a sponsor, process owners, and a benefits review, take it. If it offers software, binders, audit-owned EGIT, or execution as the finish line, you already know the trap. That is the whole 8% domain, and it is enough. Now go practice.
How do the COBIT 2019 Design Guide and Implementation Guide work together?
How should a Foundation candidate treat the Design & Implementation certificate versus Foundation?
You've completed this section
Continue exploring other exams