Ok. I contend I *didn't* understand what you were trying to say. I do now. We're in agreement.

Jared


On Mar 25, 2009, at 9:28 AM, Alan Wexelblat wrote:

*takes Jared's strawman and sets it on fire*

On Tue, Mar 24, 2009 at 6:11 PM, Jared Spool <[email protected]> wrote:
So, if I understand correctly, you're speaking in an ideal world, where everyone already has the data they need when they walk in the room and
everyone is on the same page with that data. Did I get that right?

No, and you know it.  I said no such thing.  What I said was that the
people in the room should be the vision-holders for the company. It is
possible (even probable) that there are organizations where such
people don't exist, or where they fail to do their jobs in this way.
In which case you have a different problem.

I then further postulate that people involved in a brainstorming
exercise will reach a stage where the brainstorming begins to coalesce
around a few accepted ideas/projections.  Given that, I believe that
the people in the room should be sufficiently familiar with their own
product that they can see how the results of the brainstorming
exercise differ from their current product.

I don't think either postulate is unrealistic or ideal (in the sense
of unobtainium). I'm sure we can both give counter-examples where this
wasn't true, but that doesn't discount the notion that Dave (and I)
are describing a design-driven process.  All process models are
ideals, as you well know.

Because, I've never stepped into that world. The world I live in has
stakeholders who have no clue what's happening with their designs outside
their perceptions of mythical users with mythical scenarios.

Right.  Which is why I suggested that data should be introduced into
the process, in the part of my message you didn't quote.  It's
important to understand how a new design concept may perform vis a vis
an existing design, how a new design might or might not address
deficiencies with a current design - all understandings for which data
are crucial.

However, none of those things go counter to the notion that you can in
fact have a design-driven process that incorporates data, and not just
a data-driven process that might happen to incorporate design
somewhere down in the pixel-fiddling range, which was the thrust of
the original complaint.

Best,
--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

Reply via email to