The limitation of this approach is sample data. I can only really provide one level of data e.g. figures for a single day, which is limiting for solutions with lots of views.

So in those circumstances I either provide a detailed accompanying document or produce a fuller model in something like Expression Blend using sample data.

First, the conversations that go into the creation of the prototype or mockup contribute to the team’s understanding of what they are trying to build. Often, there is value that comes about even before the team has shown it to any prospective users.

Second, when watching users perform tasks with the prototype, it gives a way of exploring the interface between how the design performs and what users need. With a well constructed experiment, you can learn a lot. (Unfortunately, many experiments are not well constructed and often take teams down a wrong path. An article for another day.)

As for utilizing the code produced by the prototyping tool, that typically not really valuable. Those tools are not good at producing efficient, productive code. Plus, if it’s a prototype and not a mockup, then it won’t really represent what the user is likely to be delivered. The final design will look very different, so the code the tool produces isn’t valuable.

In any given project, the best teams use five or more formats of prototypes, including sketches, workflow diagrams, clickable prototypes in Acrobat or Keynote, JQuery-built HTML prototypes, or working code to test performance-type issues. Teams that think they can get away with a single tool and format probably aren’t using prototyping to its fullest.

“can we re-use the code”
(i.e., can the coders incorporate the prototype, as-is, into the “real” code).

Thoughts?

I’ve often seen designers create “prototypes” that work inside specific systems, either built in-house or bought, like PowerPoint. They test the design by having users go through, page by page, and ask them to indicate what they like and don’t like.

How does that approach – fixed step flow – fit into your model of prototyping?

Rapid prototyping is become an increasingly important skill set, so it’s great to see UIE emphasizing it.

Dan