🎯 Phase 1: Business Needs Process 1.1

Issue Clarify

Define and clarify the core business problem or opportunity that the AI solution will address. This foundational process ensures all stakeholders have a shared understanding of the issue, its scope, and its importance to the organization.

⏱️ Duration: 2-5 days

👥 Roles: PO, PM, Business Stakeholders

Status:

📋 ITTO: Inputs, Tools & Techniques, Outputs

📥 Inputs

1

Business Context Documents Strategic plans, annual reports, market analysis
2

Stakeholder Requests Initial problem statements, improvement ideas
3

Current Process Documentation Existing workflows, pain points, inefficiencies
4

Historical Data Past attempts, lessons learned, benchmarks

🔧 Tools & Techniques

1

5 Whys Analysis Root cause identification technique
2

Stakeholder Interviews One-on-one and group discovery sessions
3

Problem Statement Canvas Structured template for defining issues
4

Fishbone Diagram Cause-and-effect visualization
5

Affinity Mapping Grouping related issues and themes

📤 Outputs

1

Problem Statement Document Clear, concise definition of the issue
2

Scope Definition Boundaries and constraints identified
3

Stakeholder Alignment Record Documented agreement on problem definition
4

Initial Hypothesis Preliminary ideas on AI applicability

✅ Best Practices

💬 Engage Multiple Stakeholders

Don't rely on a single perspective. Include business users, technical teams, and leadership to get a holistic view of the problem and ensure buy-in from all parties.

📝 Document Everything

Create a written record of all discussions, decisions, and assumptions. This becomes invaluable during later phases and helps maintain alignment throughout the project.

🎯 Be Specific, Not Vague

Avoid generic problem statements like "improve efficiency." Instead, specify measurable issues: "Reduce order processing time from 48 hours to 4 hours."

🔍 Question Assumptions

Challenge existing beliefs about the problem. What seems obvious may not be accurate. Use data to validate assumptions before proceeding.

⚠️ Common Pitfalls to Avoid

❌ Jumping to Solutions

Teams often skip proper problem definition and jump straight to "we need AI/ML for this." This leads to building the wrong solution.

Solution: Force yourself to define the problem without mentioning any technology. Focus on the "what" before the "how."

❌ Scope Creep

The problem definition keeps expanding as more stakeholders add requirements, making the project unmanageable.

Solution: Define clear boundaries early. Document what IS and IS NOT in scope. Get stakeholder sign-off before moving forward.

❌ Ignoring Root Causes

Addressing symptoms instead of underlying issues leads to solutions that don't provide lasting value.

Solution: Use the 5 Whys technique to dig deeper. Keep asking "why" until you reach the fundamental cause.

📄 Download Process Template

Get the Issue Clarify template with Problem Statement Canvas and interview guides

📥 Download PDF 📋 Download PPTX

←

Back to Phase 1 Overview

Next Process 1.2 Success Measure Definition

→