- Something wholly new. - The dev team understands that their current UI may change radically. - We're working for a group of academic research institutes. This is their first project together.
Our normal approach is a wide one -- looking at the greater context around the client's perceived scope. As such, we're hesitant to get into the often distracting details of a prototype test. Thanks again. On Sun, Jan 10, 2010 at 10:42 AM, Alan Wexelblat <[email protected]> wrote: > On Fri, Jan 8, 2010 at 1:50 PM, Jonathan Abbett <[email protected]> wrote: >> Say you're brought in to do user research and feature definition for a >> software project that's already underway (i.e. development began on >> day one). >> >> You have your tried-and-true process where you interview users long >> before you write scenarios, nevermind write code, but the client >> suggests that you take the latest prototype along to show interview >> subjects. > > I think I don't know enough to answer this question. Is what they're > developing a new version of an existing product? Or something wholly > new? How does this new product relate to the company's existing > offerings? Do they have established users? Do they have users who > did things like beta test for them in the past? > > What I'm driving at with these questions is my sense that it may help > you to broaden your vision beyond the specific features of this > product and into a wider vision of this company's relationships with > its existing and intended users. That may help you fit the prototypes > better into your interviews, I hope. > > Best of luck, > --Alan > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [email protected] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
