Hypthesis Based Problem Solving

OUTLINE.md

Hypthesis Based Problem Solving

Business Problem -> Facts ~~ -> Gaps ~~ -> Solution
                               (Hypthesis)

Process: To work solution-oriented from an early stage, hypothesis are needed to "fill the gaps"

1. Develop a Day 1 Answer

inputs:

• What do I already know
• What are the likely hypothesis I can make outputs: a solution that can be improved and iterated on

Practical example: A mobile payment service provider wants to enter the Brazilian market

Drafted hypothesis: Market entry is recommended due to 4 reasons

• Growth
• Affinity to mobile payment
• Attractiveness of offering
• Little competition

Facts: Market growth in Brazil vs. other South American countries

• Population
• Affinity

2. Data analysis stage

Conduct research:

• population
• affinity
• attractiveness of offering could not confirm competition landscape

3. Structure project using MECE principle

Two tiers

Problem Structuring (top down):

input

• Management Objectives
• Project Objectives
  • [Key Drivers]
    • [Key Driver Hypothesis]
      • [Key Questions]

output

• [Required Analysis]

Problem Solving: Analytical Work (bottom up):

output

• Recommendation
  • [Conclusions]
    • [Findings]
      • [Facts]

input:

• [Conduct Analysis]

---

Key questions:

• What does management want to acheive
• What should the outcome of the project / work initiative be?
• What are the key problem drivers
• What can already be hypothesized about the key drivers
• What analysis needs to be conducted to verify or falsify the hypothesis