Action-Learning Methodology
Unlike traditional hackathons with predefined problems, the action-learning approach requires teams to discover, validate, and solve real community problems through systematic evidence gathering.
The Four Mandatory Quadrants
┌─────────────────────┬─────────────────────┐
│ 1. GROUND TRUTH │ 2. FORMULATE │
│ │ INSIGHT │
│ Community Research│ Pattern │
│ Voice Notes ✓ │ Recognition │
│ Observations │ Root Causes │
└─────────────────────┴─────────────────────┘
┌─────────────────────┬─────────────────────┐
│ 3. FORMULATE │ 4. DEFINE │
│ HYPOTHESIS │ OPPORTUNITY │
│ │ │
│ Problem Statement │ Solution Options │
│ "We believe..." │ Feasibility Study │
└─────────────────────┴─────────────────────┘The Quadrants Explained
Do: Interview community members, record voice notes, observe problems
Output: Raw evidence of community needs
Do: Analyze patterns, identify themes, find root causes
Output: Key insights and “superior interests”
Do: Write clear problem statement with testable hypothesis
Output: “We believe that… because… and if we… then…”
Do: Explore multiple solutions, evaluate feasibility, select best option
Output: Justified solution choice with scoring matrix
Core Principles
- Evidence-Based → Voice notes and documented research mandatory
- Community-Centered → Problems defined by community, not assumptions
- Iterative → Validate before building, adjust based on feedback
- Documented → Track journey on team pages for evaluation
Timeline Mapping
| Hackathon Phase | Quadrants Focus |
|---|---|
| Phase 1-2 (Nov 1-21) | Quadrant 1: Ground Truth collection |
| Phase 3 (Nov 22) | Validation with mentors |
| Phase 4 (Nov 23 - Dec 5) | Quadrants 2-3: Insights & Hypothesis |
| Phase 5 (Dec 6) | Quadrant 4: Define Opportunity |
| Phase 6-7 (Dec 7-13) | Build solution based on validated opportunity |
Common Pitfalls
❌ Rushing to solutions before completing all 4 quadrants
❌ Skipping voice notes (mandatory evidence)
❌ Superficial research (talking to only 2-3 people)
❌ Assuming problems instead of discovering them
❌ Poor documentation on team pages
Additional Resources
Learn more: Build What Matters philosophy →