Managing Project Issues

Issues are current problems that need attention, unlike risks which are uncertain future events. Effective issue management ensures problems are identified early, analyzed properly, and resolved before they derail the project.

Issues vs. Risks

Understanding the distinction between issues and risks is fundamental:

A risk that occurs becomes an issue. Effective risk management reduces issues; effective issue management resolves them.

---

The Issue Log

The Issue Log is a project document used to track and monitor issues throughout the project lifecycle.

Issue Log Components

Issue Priority Levels

---

Issue Management Process

Standard Issue Management Flow

1. Identify: Recognize and document the issue
2. Categorize: Classify by type and priority
3. Assign: Designate an issue owner
4. Analyze: Investigate root cause
5. Develop Options: Identify possible solutions
6. Decide: Select resolution approach
7. Implement: Execute resolution actions
8. Verify: Confirm issue is resolved
9. Close: Document and capture lessons learned

Issue Escalation

When issues cannot be resolved at the project level:

• Follow governance escalation paths
• Provide complete information to decision-makers
• Recommend solutions when possible
• Track escalated issues through resolution

---

Root Cause Analysis (RCA)

Root Cause Analysis is a systematic process for identifying the fundamental source of problems. RCA focuses on addressing underlying causes rather than treating symptoms.

Why RCA Matters

RCA Core Principles

1. Focus on remedying causes rather than symptoms
2. Realize there may be multiple root causes
3. Focus on how and why, not who
4. Be systematic and methodical
5. Find cause-and-effect evidence
6. Take a comprehensive approach

---

Root Cause Analysis Techniques

The Five Whys

The Five Whys technique involves asking "why?" repeatedly (typically five times) to drill down from symptoms to root causes.

Example:

Root Cause: Lack of review process for database schema changes

Corrective Action: Implement schema change review process

Fishbone Diagram (Ishikawa Diagram)

The Fishbone Diagram (also called cause-and-effect diagram) visualizes potential causes organized by category.

Standard Categories (6 M's for Manufacturing):

• Manpower: People, skills, training
• Methods: Processes, procedures
• Machines: Equipment, technology
• Materials: Inputs, data, resources
• Measurements: Metrics, criteria
• Mother Nature/Environment: External factors

Adapted Categories for Projects:

• People: Skills, availability, communication
• Process: Methods, workflows, procedures
• Technology: Tools, systems, infrastructure
• Resources: Budget, materials, equipment
• External: Vendors, regulations, environment

Other RCA Techniques

---

Collaborative Issue Resolution

Effective issue resolution leverages team collaboration:

Benefits of Collaborative Approach

• Diverse perspectives: Different viewpoints uncover causes
• Shared understanding: Team aligns on problem and solution
• Buy-in: Involvement creates ownership
• Better solutions: Collective wisdom outperforms individual
• Knowledge sharing: Team learns together

Collaborative Techniques

Creating a Blame-Free Environment

For effective issue resolution:

• Focus on what happened, not who
• Treat issues as learning opportunities
• Encourage reporting without fear
• Celebrate identification of issues
• Recognize problem-solvers

---

Issue Management Best Practices

---

Key Takeaways

• Issues are current problems requiring resolution; risks are future uncertainties
• The Issue Log tracks all issues through identification to resolution
• Root Cause Analysis prevents recurrence by addressing fundamental causes
• The Five Whys and Fishbone Diagram are key RCA techniques
• Collaborative approaches yield better solutions and team buy-in