http://wireframes.linowski.ca/2009/04/structure-juxtoposed-wireframe/ Because every IA has something funky up their sleeve Wed, 28 Jul 2010 06:45:14 +0000 hourly 1 http://wordpress.org/?v=3.0 http://wireframes.linowski.ca/2009/04/structure-juxtoposed-wireframe/comment-page-1/#comment-751 Andrew Schechterman Mon, 13 Apr 2009 17:32:28 +0000 http://wireframes.linowski.ca/?p=755#comment-751 I'm a big fan of this (kudos Dawn) but have not done anything like it for years. On one of the very early banking applications we designed (about 1999), for Seniors who were also "Novices," we exposed the navigation and site structure, as modest as it was, to the user. We had made the mistake of going to users with a medium-fidelity prototype (clickable, resident database) but found ourselves showing our Senior users our concept models, flows, and wireframes, to help them succeed in the tasks. Based on their participatory design methods, we then decided to simplify those above-elements and delivered them as part of the design, essentially exposing what was under the hood. The user group loved it, and so did our clients who wanted to reach this latent group. The only downside, we found users relying on it a lot rather then, for example, learning from it and advancing to a more in-head model. I'm a big fan of this (kudos Dawn) but have not done anything like it for years. On one of the very early banking applications we designed (about 1999), for Seniors who were also "Novices," we exposed the navigation and site structure, as modest as it was, to the user. We had made the mistake of going to users with a medium-fidelity prototype (clickable, resident database) but found ourselves showing our Senior users our concept models, flows, and wireframes, to help them succeed in the tasks. Based on their participatory design methods, we then decided to simplify those above-elements and delivered them as part of the design, essentially exposing what was under the hood. The user group loved it, and so did our clients who wanted to reach this latent group. The only downside, we found users relying on it a lot rather then, for example, learning from it and advancing to a more in-head model.

]]>