Contextualizing a Problem
Before mapping anything, ask why this became a problem in the first place. A stated problem usually arrives pre-packaged with someone else's framing: who noticed it, what they blamed, and what they already tried. Learn to trace a problem's history before accepting its definition, to identify whose incentives shaped how it got described, and to separate the actual objective from the fix someone has already decided on. Students learn to ask the question most AI projects skip: is this the real problem, or the version of the problem that was easiest to hand off? Real cases include a churn problem that was actually a pricing problem, and a productivity problem that was actually a tooling problem in disguise. Getting this step wrong means every following module, no matter how well executed, solves the wrong thing precisely.














