As a consultant I took a web interface design class. The instructor was extremely knowledgable in this area. The on ething that I took away from that class was drawing the web pages on paper or making them on construction paper. She explained that by doing it this way the client would realize that this was indeed the design phase.

The other benefit of this was an initial usability testing phase. "People off the street" were asked to physically press buttons drawn on the paper to navigate the website after they were given a specific task. This indicated the "ease of use" of the layout.

The interesting thing about the class was that we never got near a computer. It was all paper. Big 3M sheets that stick to the wall, post-its, construction paper. Anything but a real computer and all of the class were web programmers.

I have found through experience that rapid prototyping also helps to manage client expectations when used properly. It kind of gives them that "Little Building" that architects model for their clients while they really design the thing. I am sure everyone is well aware of how much client expectation management plays into the daily stress level.

I my current position, rapid prototyping has put me light years ahead of other newcomers in regards to the product. It has helped me to ask the proper questions. When I started I knew nothing about the industry I am in now. Within a couple of months I was asking questions that others didn't ask until 6 to 9 months down the road.

Good thread to initiate Sherlock