Don Normans "Never solve the problem as stated" rule has a corollary for software development: Don't write functional specification documents. Clearly, the functional spefication document is just the kind of problem statement Norman wants you to discard. So if you shouldn't solve the problem like that, you probably shouldn't write the specification in the first place.
This argument obviously is also expressed in various XP practices.