Comparison Matrix
"HEAT vs Traditional Tools"
HEAT vs Time Tracking
| Feature | Time Tracking | HEAT Framework |
|---|---|---|
| What it measures | Hours logged | Cognitive load intensity |
| Granularity | "8 hours development" | "x7 blocker + x2 feature + x1 support" |
| Burnout detection | None | 🔥 Pain Streak alerts |
| Knowledge risk | None | Bus factor mapping |
| Overhead | 5-10 min/day | 30 sec/day |
| Privacy | Manager-owned | Developer-owned (opt-in sharing) |
| Purpose | Billing, compliance | Team health, capacity planning |
HEAT vs Enterprise Tools
| Capability | Jellyfish/Uplevel ($50K+/year) | HEAT |
|---|---|---|
| Effort visibility | ✓ | ✓ |
| Burnout detection | ✓ | ✓ (Pain Streaks) |
| Integration | API-based | Sidecar (works with anything) |
| Cost | $50K-$100K/year | Productized solution ($20-40K one-time) |
| Privacy model | Surveillance-adjacent | Developer-controlled |