3 ms·

The straw man is the "typical UCD process" diagram you put up. UCD doesn't just lump all of implementation into a black box like you imply. There's nothing in

The straw man is the "typical UCD process" diagram you put up. UCD doesn't just lump all of implementation into a black box like you imply. There's nothing in the UCD process that precludes testing on real customers. But the point of using UCD before testing on real customers is that it's a far cheaper way to provide basic realignment. Can I ask if you've ever done a paper prototyping exercise before? I've lead paper prototyping sessions both in classroom & commercial settings and it's common to find people who question their value before it's performed but rare to find anyone after they've experienced it. Often, paper prototyping sessions lead to a drastic reworking of the interface because the originally designed interface is practically unusable. It's far cheaper to get this feedback on paper than on final implementation, even as the cost of implementation continues to fall.

ThomPete 17y ago
I have done paper prototyping and any other possible permutation you can imagine of prototypes including developing fully fledged prototypes. Again what metrics are you setting your "drastic reworking" up against? How do you know that it needs reworking just because you have found issues in a paper-prototype? Issues that might be addressed in the visual phase or in the final phase. That is if anything the strawman IMHO. You are solving the very problems that is created by it being a paper prototype instead of the final product.
- pbhjpbhj 17y ago
  If the product is a website and the client decides at paper prototype stage they want 3 colums not 2, or they want a right-hand menu or a top-hand (!) search box then no amount of polish is suddenly going to add those things if they client doesn't tell you so they can be put in the design. Also producing fully finished designs for choosing between - aren't you completely ignoring economic reality there?
  - ThomPete 17y ago
    I don't want to sound rude but have you read the post? I think I answer that.

ThomPete 17y ago

I have done paper prototyping and any other possible permutation you can imagine of prototypes including developing fully fledged prototypes. Again what metrics are you setting your "drastic reworking" up against? How do you know that it needs reworking just because you have found issues in a paper-prototype? Issues that might be addressed in the visual phase or in the final phase. That is if anything the strawman IMHO. You are solving the very problems that is created by it being a paper prototype instead of the final product.

pbhjpbhj 17y ago
If the product is a website and the client decides at paper prototype stage they want 3 colums not 2, or they want a right-hand menu or a top-hand (!) search box then no amount of polish is suddenly going to add those things if they client doesn't tell you so they can be put in the design. Also producing fully finished designs for choosing between - aren't you completely ignoring economic reality there?
- ThomPete 17y ago
  I don't want to sound rude but have you read the post? I think I answer that.