Business Analyst

# Business Analyst Reference Guide

This document provides detailed frameworks, techniques, and best practices for conducting effective product discovery and requirements analysis.

## Table of Contents

1. [Interview Frameworks](#interview-frameworks)
2. [Question Types and Techniques](#question-types-and-techniques)
3. [Discovery Process](#discovery-process)
4. [Documentation Best Practices](#documentation-best-practices)
5. [Common Pitfalls](#common-pitfalls)

## Interview Frameworks

### 5 Whys Framework

**Purpose:** Identify root causes by asking "why" repeatedly

**Process:**
1. State the problem clearly
2. Ask "Why does this happen?"
3. Take the answer and ask "Why?" again
4. Repeat 5 times (or until root cause found)
5. Address the root cause, not symptoms

**Example:**
```
Problem: Users abandon checkout process

Why? → The checkout takes too long
Why? → Users have to enter shipping info manually
Why? → We don't save shipping addresses
Why? → Privacy concerns prevented implementation
Why? → We haven't implemented secure storage

Root Cause: Lack of secure storage for user data
```

**When to Use:**
- Problem identification phase
- Understanding pain points
- Debugging user complaints
- Finding systemic issues

### Jobs-to-be-Done (JTBD) Framework

**Purpose:** Understand what users are trying to accomplish

**Core Concept:** People don't want products; they want to get jobs done

**Question Structure:**
- "When [situation], I want to [motivation], so I can [expected outcome]"

**Key Questions:**
- What job are you trying to get done?
- What are you using now to accomplish this?
- What's the hardest part about getting this job done?
- How do you measure success for this job?
- What would make this job easier?

**Example:**
```
Job: "When I'm planning my weekly meals, I want to quickly find recipes
that use ingredients I already have, so I can reduce food waste and save time."

Current Solution: Googling ingredients + recipe sites
Pain Points: Takes 30+ minutes, recipes often need items I don't have
Success Metric: Find suitable recipe in under 5 minutes
```

**When to Use:**
- Understanding user motivation
- Feature prioritization
- Identifying alternatives and competition
- Designing user-centric solutions

### SMART Goals Framework

**Purpose:** Ensure goals are well-defined and achievable

**Criteria:**
- **S**pecific - Clear and unambiguous
- **M**easurable - Quantifiable metrics
- **A**chievable - Realistic given constraints
- **R**elevant - Aligned with business objectives
- **T**ime-bound - Has a deadline

**Example:**

**Vague Goal:**
"Improve user satisfaction"

**SMART Goal:**
"Increase user satisfaction score from 3.2 to 4.0 (out of 5)
by Q2 2025 through implementing the top 3 feature requests"

**Application:**
- S: User satisfaction score, specific features
- M: 3.2 to 4.0 on 5-point scale
- A: Top 3 features (not 20)
- R: Tied to user satisfaction metric
- T: By Q2 2025

**When to Use:**
- Setting project objectives
- Defining success criteria
- Planning milestones
- Stakeholder alignment

### Problem-Solution Fit Framework

**Purpose:** Validate that solutions address real problems

**Four-Step Process:**

1. **Problem Definition**
   - What is the problem?
   - Who has the problem?
   - How painful is it?
   - How frequent is it?

2. **Current Solution Analysis**
   - How do users solve it now?
   - What workarounds exist?
   - What are the limitations?
   - What do they pay (time/money)?

3. **Proposed Solution**
   - How will this solve the problem?
   - What's the core value proposition?
   - What makes it better than current solutions?
   - What's the minimum viable solution?

4. **Validation Criteria**
   - How will we know it solves the problem?
   - What metrics will improve?
   - What user behavior will change?
   - What's the success threshold?

**When to Use:**
- Product discovery phase
- Feature validation
- Solution design
- Resource allocation decisions

## Question Types and Techniques

#