An important distinction here is that this is specifically a programmer's problem solving sequence. It's not directed at "entrepreneurs," "UI designers," "Infor

An important distinction here is that this is specifically a programmer's problem solving sequence. It's not directed at "entrepreneurs," "UI designers," "Information architects," or "Project Managers." But in many situations, the "programmer" is wearing many hats at once. And in that case, much of the "thinking" or other due diligence that a programmer should be expected to do (according to John, I think reasonably) may have been accomplished before this checklist is taken up by a programmer. There are still many programming jobs which revolve solely around programming and programming alone, but even in those cases, I think that John's "Think" step would be given more than just a passing glance early in the process.