# Mission: Strategic Problem Solving

## Why
I'm a senior frontend engineer who's been reactive — problems land on my desk and I solve them. I want to shift from being a problem-*taker* to a problem-*shaper*. I need to spot the *real* problem hiding behind the symptoms, frame it clearly, and discuss solution paths at the same depth as a Head of Engineering or VP.

## Success looks like
- I walk into a sync with a VP and can name the real problem in 30 seconds — not the symptoms everyone's been chasing
- I naturally pause before solving and ask "Is this the right problem?" — even under pressure
- HoE/VP-level people seek my input on ambiguous, high-stakes problems
- I can lay out 2–3 solution paths with trade-offs they genuinely hadn't considered
- My PRDs, design docs, and proposals are structured around *problem framing* first, solutions second

## Constraints
- Full-time job — lessons need to be short, actionable, and fit in ~20–30 min sessions
- I learn best by doing: real-world scenarios, frameworks I can apply immediately
- Want the HTML lessons deployed to Cloudflare so I can review on mobile anytime

## Out of scope
- Generic "critical thinking" theory disconnected from engineering reality
- Soft-skills-only approaches (framing must be grounded in technical/org substance)
- "Positive thinking" or mindset content — keep it practical and framework-based