And the idea behind paper prototyping is to be able to discard without regret. Once you code, you can get attached to your first ideas and not iterate, or iterate over some arbitrary restriction set by the tools. Paper prototyping makes it easy to "kill your darlings" without regret.
More than that, the second and probably more important idea is to avoid the customer to get attached to an un-iterated design, and the "but it's almost done!" effect that can be devastating when negotiating times.
I don't doubt it...at least not for desktop or web apps, which are the kind that I build most of the time.
Just this past Thursday, we found a new task that our call center would have to perform. I opened Visual Studio, created a new WinForms app and layed out the UI within 20 minutes. I emailed the screenshots to all the principles and got responses back within the hour.
And the idea behind paper prototyping is to be able to discard without regret. Once you code, you can get attached to your first ideas and not iterate, or iterate over some arbitrary restriction set by the tools. Paper prototyping makes it easy to "kill your darlings" without regret.
More than that, the second and probably more important idea is to avoid the customer to get attached to an un-iterated design, and the "but it's almost done!" effect that can be devastating when negotiating times.