Re: It's not about UI
- --- In email@example.com, "Jon Kern" <jonkern@c...>
> why the people paying get to decide what they want done first.How do they go about deciding?
> then you start haggling...
> -- jon
The requirements vs. design dilemma kicks in here. I'd argue the act
of deciding what to do is an act of design. And, that's the part of
design I see as most critical - the theme hinted at in the exagerated
subject line of my original post. My assertion is that interaction
designers bring critical skills to the task of designing what to do.
Certainly they've got great approaches of identifying the best ways
of meeting the goals of a target constituency. If I was paying for
software to be built, I think I'd consult with an interaction
designer first. From an XP perspective they'd be a critical part of
the customer team.
> -----Original Message-----
> From: Jeff Patton [mailto:jpatton@a...]
> Sent: Monday, August 02, 2004 3:39 PM
> To: firstname.lastname@example.org
> Subject: [agile-usability] Re: It's not about UI
> --- In email@example.com, "Jon Kern" <jonkern@c...>
> > could it be as simple as doing the most important features
> and not togo
> > the nth degree, i might add.
> Who decides what the features are? How do they go about that? Of
> those features who decides which are most important? How do they
> about that?details.
> Your're right, it's as simple as that. The devil's in the
- Heck, I'd lobby for copies for all the UI team in our shop - so bump
the number up to seven!
> Martha can tell prospective editors she has thehttp://industrialxp.org/community/bin/view/Main/TestFirstUserInterfac
> numbers. Three, so far!
> Do you Yahoo!?
> Express yourself with Y! Messenger! Free. Download now.