A tailored course, built for your situation
Sources and specific examples on hand when peers push back
Build unshakable reasoning for Agile and ITSM decisions using real-world patterns and documented trade-offs
$199 one-time
24-hour access provisioning
30-day money-back guarantee
Hand-built implementation playbook
12 modules. 12 chapters per module. 144 chapters total.
12 modules, each with 12 chapters (144 chapters total), text-based, plus downloadable templates and a hand-built implementation playbook delivered alongside course access.
Having to second-guess or rejustify decisions that should already be settled
The situation this course is for
Even solid decisions get reopened when stakeholders lack context. Without accessible reasoning, teams default to debate instead of progress.
Who this is for
Senior Agile and ITSM practitioner operating in high-velocity product environments where governance must be both lightweight and defensible
Who this is not for
Junior implementers, consultants selling frameworks, or leaders looking for board-level presentations
What you walk away with
- Map justifications for every key control in your current ITSM workflow using ISO/IEC 20000 and ITIL 4 sources
- Reconstruct decision logic for past sprint adjustments using traceable team retrospectives and delivery data
- Build a referenceable library of precedent-based responses for common pushbacks on backlog prioritization
- Deploy a lightweight decision log that satisfies auditors and preserves team agility
- Walk through three real cases where documented reasoning prevented escalation or rework
The 12 modules (with all 144 chapters)
Module 1. When governance becomes a team sport
How modern Agile teams are shifting from compliance-as-a-checklist to governance-as-collaboration, with real examples from SaaS engineering cultures.
12 chapters in this module
- Shared ownership vs tribal knowledge
- The cost of silent disagreement
- Documented dissent patterns
- Precedent in sprint reviews
- Consent over consensus
- Traceability without bureaucracy
- The role of facilitators
- Log format comparisons
- Escalation triggers defined
- Rhythm of review cycles
- Feedback loop design
- Governance in stand-ups
Module 2. Decision logging for humans, not auditors
Design lightweight, team-owned logs that preserve intent without becoming overhead, using examples from Jira Service Management implementations.
12 chapters in this module
- Minimum viable log fields
- Auto-capture from tools
- Linking tickets to decisions
- Tagging by risk class
- Version control integration
- Searchable rationale
- Time-based purging rules
- Privacy-aware indexing
- Export templates
- Audit-ready views
- Team-editable entries
- Signature without ceremony
Module 3. ITIL 4 in the real world
Map service management decisions to actual ITIL 4 practices, not textbook versions, but adapted forms used in high-velocity teams.
12 chapters in this module
- Guiding vs mandatory principles
- Service request trade-offs
- Incident vs problem ownership
- Meaningful SLAs defined
- MTTR targets by service tier
- Change enablement rhythm
- Automated approvals logic
- Risk-based CAB scope
- Post-incident review depth
- Knowledge capture triggers
- Service desk empowerment
- Feedback into design
Module 4. ISO/IEC 20000 in agile contexts
Align core service management standards to iterative delivery, using examples from teams that passed audits without slowing down.
12 chapters in this module
- Clause mapping exercises
- Evidence without documentation
- Sampling methodology explained
- Control design vs implementation
- Compliance as code pattern
- Automated evidence gathering
- Audit interview prep
- Finding root causes early
- Corrective action tracking
- Internal vs external audits
- Scope boundary decisions
- Certification prep timeline
Module 5. Reasoning paths for common pushbacks
Pre-build explanations for recurring challenges, like skipping change advisory board or relaxing SLAs, with sources and examples.
12 chapters in this module
- We don’t have time for CAB
- Why we classify this as low risk
- Why SLA was adjusted post-launch
- Why we automated approvals
- Why we skipped peer review
- Why we changed the owner
- Why we kept the service live
- Why we rolled back fast
- Why we didn’t document it
- Why we overrode the system
- Why we used a workaround
- Why we accepted technical debt
Module 6. Building a precedent library
Create a living collection of past decisions that teams can reference, reducing re-litigation and increasing autonomy.
12 chapters in this module
- Naming decision types
- Template for logging
- Ownership assignment
- Searchable metadata fields
- Versioned reasoning
- Linking to incidents
- Tagging by domain
- Retirement rules
- Cross-team access model
- Monthly review cycle
- Integration with wikis
- Feedback into future
Module 7. The anatomy of a defensible decision
Deconstruct real decisions from Atlassian, GitHub, and GitLab to see what made them hold up under scrutiny.
12 chapters in this module
- Identifying core trade-offs
- Stakeholder impact mapping
- Documenting assumptions
- Evidence thresholds set
- Risk appetite alignment
- Escalation path clarity
- Timing rationale
- Alternative considered
- Success criteria defined
- Checkpoints built-in
- Ownership clarity
- Exit conditions included
Module 8. Facilitation techniques for tough calls
Guide teams through high-stakes decisions using structured reasoning, not groupthink, using templates from real retrospectives.
12 chapters in this module
- Pre-read packet design
- Silent input phase
- Dot voting with caveats
- Risk framing statements
- Decision safety check
- Dissent capture format
- Rationale synthesis
- Commitment level check
- Follow-up triggers
- Blind spots review
- Facilitator neutrality
- Time-boxing norms
Module 9. From policy intent to working practice
Trace how real teams interpreted policies into changes in behavior, without creating overhead.
12 chapters in this module
- Policy as hypothesis
- Pilot group selection
- Behavioral metrics
- Feedback collection
- Iteration cycle
- Scaling thresholds
- Documentation updates
- Training integration
- Audit alignment
- Tooling automation
- Leadership visibility
- Sunset clauses
Module 10. Handling escalation without rework
Use documented reasoning to resolve escalations quickly, turning challenges into alignment opportunities.
12 chapters in this module
- Early warning signs
- Escalation intake form
- Root cause depth
- Prepared response bank
- Stakeholder mapping
- Communication templates
- Resolution tracking
- Precedent linking
- Lessons into process
- Timeline expectations
- Ownership transfer
- Closure criteria
Module 11. Maintaining autonomy under scrutiny
Preserve team agility while meeting governance expectations, using real examples from product teams under audit.
12 chapters in this module
- Boundary setting phrases
- Evidence transparency
- Proactive disclosure
- Trust-building cadence
- Risk-based reporting
- Lightweight documentation
- Audit prep rhythm
- Internal mock audits
- Stakeholder education
- Feedback into policy
- Compliance storytelling
- Autonomy metrics
Module 12. Making governance compound
Turn every decision into reusable insight, so future choices are faster, not heavier.
12 chapters in this module
- Compound learning model
- Knowledge reuse rate
- Decision debt tracking
- Pattern recognition
- Template evolution
- Team-level customization
- Cross-silo sharing
- Leadership onboarding
- New hire integration
- External benchmarking
- Feedback loops
- Quarterly refinement
How this maps to your situation
- During sprint planning when controls are challenged
- After an incident where process gaps were exposed
- Before audit cycles where reasoning must be demonstrated
- When onboarding new team members into governance expectations
Before vs. after
Before
Rejustifying decisions repeatedly, relying on memory or tribal knowledge when challenged
After
Confidently walking through the why behind key choices with sources, examples, and clear logic
What's included with your purchase
- 12 modules with 12 chapters each (144 chapters)
- Downloadable templates and worked examples for every module
- Hand-built implementation playbook delivered alongside course access
- 30-day money-back guarantee
Delivery and format
- Course and learning environment access provisioned within 24 hours of purchase
- Hand-built implementation playbook delivered alongside course access
Format: Text-based modules and chapters in the Art of Service learning environment, plus downloadable templates and worked examples for every chapter, plus the hand-built implementation playbook delivered alongside course access.
Time investment: Approximately 3 hours per module, designed to be completed alongside regular work. Most practitioners finish in 6 weeks.
If nothing changes
Continuing to rely on informal consensus means decisions remain vulnerable to re-litigation, slowing progress and eroding trust in team judgment.
How this compares to the alternatives
Unlike generic compliance courses, this focuses on real-world Agile and ITSM decision patterns, with templates tied to tools like Jira and Confluence, and sources from actual audits and team retrospectives.
Frequently asked
Is this focused on ITIL or ISO standards?
It uses ITIL 4 and ISO/IEC 20000 as reference points, but focuses on how teams adapt them in practice, with real examples of what actually works in high-velocity environments.
How is the course structured?
12 modules, each containing 12 chapters (144 chapters total).
Will this help me during audits?
Yes, by helping you build and maintain defensible reasoning that auditors can follow without requiring additional explanation or evidence gathering.
$199 one-time. Approximately 3 hours per module, designed to be completed alongside regular work. Most practitioners finish in 6 weeks..
Within 24 hours your account in the learning environment is provisioned and the tailored implementation playbook is delivered alongside it.
30-day money-back guarantee·
144 chapters·
Hand-built playbook included·
Account access within 24 hours