A comprehensive training program equipping Agency leaders, project managers, and staff with practical tools and methodologies aligned with the PMBOK® Guide 7th & 8th Editions — delivered October 2026 through June 2027.
Training Modules
Months of Delivery
Audience Tracks
PMBOK Editions
Each module features three interactive tabs — learn the concepts, practice with drag-and-drop exercises, and assess your knowledge. Click any module to expand it.
Distinguish between symptoms and underlying problems using structured frameworks to create durable solutions aligned with the Agency's Strategic Plan logic model.
Root Cause Analysis (RCA) is a structured method for identifying the underlying causes of problems rather than treating their symptoms. When we fix symptoms, the problem returns. When we fix root causes, the problem stays solved. This module teaches you to use logic models ("so that" chains), the 5 Whys technique, and Fishbone (Ishikawa) diagrams to trace problems to their source and design durable solutions.
Apply the "so that" logic model to connect actions → objectives → goals
The "so that" logic model is a simple but powerful chain that connects your daily activities to your strategic vision. Start with an action, ask "so that?" to find the objective, then ask "so that?" again to find the broader goal. This ensures every task has a clear purpose and contributes to the bigger picture.
📋 Example
"We conduct weekly air quality monitoring SO THAT we identify pollution sources SO THAT we reduce health disparities." If you can't complete the chain, the action may not be worth doing — or it needs to be reframed to connect to a goal.
Differentiate symptoms from root causes using 5 Whys and Fishbone (Ishikawa) diagrams
A symptom is what you see on the surface; a root cause is the underlying reason. The 5 Whys technique drills down by asking "why?" repeatedly. The Fishbone diagram explores causes across categories (People, Process, Policy, Technology) so you don't miss anything. Use 5 Whys for simple problems and Fishbone for complex, multi-factor ones.
📋 Example
Symptom: 'Permit reviews are slow.' 5 Whys: Why? → Checklist is outdated. Why? → No one owns it. Why? → No MOCHA roles. Why? → The process was never mapped. Root cause: Missing role assignments. Fix the root cause, not the symptom.
Develop logic models that map clear pathways to Strategic Plan goals
A logic model maps the pathway from activities to outcomes. It shows how resources (inputs) become activities, which produce outputs, which lead to short-term outcomes, and ultimately to long-term goals. This visual helps stakeholders see how day-to-day work contributes to the big picture and builds buy-in for solutions.
📋 Example
Input: Monitoring equipment. Activity: Air sampling. Output: Data reports. Short-term outcome: Source identification. Long-term goal: Reduced exposure in overburdened communities. The logic model shows the full chain from investment to impact.
Align root cause findings with equity and environmental justice focus topics
Root causes often disproportionately affect overburdened communities. When analyzing root causes, explicitly consider equity implications: Who is most affected? Does the solution reduce or worsen disparities? This ensures improvements serve those who need them most and align with the Agency's environmental justice commitments.
📋 Example
If air pollution monitoring reveals higher exposure in low-income neighborhoods, the root cause analysis should consider whether historical zoning policies contributed to this disparity — and the solution should prioritize those communities, not just apply a blanket fix.
Symptom vs. Root Cause
A symptom is what you observe (e.g., permits are delayed). The root cause is why it happens (e.g., the review checklist is outdated). Always dig past symptoms.
"So That" Logic Model
A chain that links Actions → Objectives → Goals. "We conduct air monitoring SO THAT we identify pollution sources SO THAT we reduce health disparities." Each step must logically lead to the next.
5 Whys
Ask "why?" five times in sequence. Each answer becomes the next question. By the fifth why, you've typically moved from symptom to root cause.
Fishbone (Ishikawa) Diagram
A visual tool that maps potential causes across categories (People, Process, Policy, Technology, Environment). The 'head' of the fish is the problem; the 'bones' are cause categories.
Problem
Permit Reviews Take 45 Days
People
Process
Policy
Technology
Action
Conduct air quality monitoring
Objective
Identify pollution sources
Goal
Reduce health disparities
Problem: Permit reviews take 45 days instead of the target 20 days. Using 5 Whys: Why are staff overworked? → Reviews pile up. Why? → The checklist hasn't been updated in 3 years. Why? → No one owns the checklist. Why? → MOCHA roles were never assigned. Why? → The process was never mapped. Root cause: No process map or role assignment for permit reviews. Solution: Create a process map, assign MOCHA roles, and update the checklist.
💡 Practical Tips for Real-World Application
7th Edition · 8 Domains · 12 Principles
Performance Domains
Principles
8th Edition · 7 Domains · 6 Principles
Performance Domains
Principles
Capture and depict current ("as-is") and improved ("to-be") workflows with flowcharts, SIPOC diagrams, and swim lanes to uncover inefficiencies as part of a culture of continuous improvement.
Clarify responsibilities in a project using the MOCHA framework — Manager, Owner, Consultant, Helper, Approver — balancing efficiency and good communication across projects.
Leverage types of project and process data for decision-making, and break projects into manageable, actionable steps using WBS with prioritization techniques and resource blocking to assign deadlines.
Track performance after change implementation and ensure improvements are sustained over time through structured evaluation, KPI frameworks, and accountability mechanisms.
Every module is mapped to both the PMBOK® Guide 7th Edition (8 Performance Domains, 12 Principles) and the 8th Edition (7 Performance Domains, 6 Principles), ensuring training reflects the most current global standard while maintaining continuity with the prior framework.
8 Performance Domains · 12 Project Management Principles
Performance Domains
Principles
7 Performance Domains · 6 Project Management Principles
Performance Domains
Principles
Five structured tasks spanning October 2026 through June 2027, aligned with the Agency's adaptive management halfway revision and culminating at the All Staff Retreat.
October 2026
Detailed curriculum outlining topics, connections, delivery methods, training objectives, and a full training schedule with review deadlines.
Ongoing
All training materials prepared to align with the approved curriculum and submitted to the Agency one week prior to each training for review and approval.
November 2026 – June 2027
Leadership training (2 hr), Project Manager training (2 hr), monthly all-staff sessions (1 hr virtual, Nov–May), and culminating in-person training at the All Staff Retreat (June 2027).
October 2026 & June 2027
Pre-training assessment to determine current knowledge base; post-training assessment to capture content effectiveness and observed outcomes.
End of June 2027
Comprehensive summary report with recommendations for ongoing training and future skill development pathways for Agency staff.
Tailored delivery for each group within the Agency, ensuring shared understanding from leadership through to all staff — culminating at the annual retreat.
2-Hour Session (In-Person or Virtual)
November 2026
2-Hour Session (In-Person or Virtual)
November–December 2026
1-Hour Virtual Sessions (Monthly Cadence)
November 2026 – May 2027
Full-Day In-Person Culminating Training
June 2027
A structured evaluation framework measuring knowledge growth from baseline through sustained application, with actionable recommendations for the Agency's future.
October 2026
After Each Monthly Session
June 2027
End of June 2027