Re: [agile-usability] New poll for agile-usability
- On 10 May 2007, at 12:58, Pascal Roy wrote:
> Another experience I've had (two practical cases to be exact),[snip]
> which is a little bit infuriating is customers insisting on UI
> designs with known usability issues (not talking about fuzzy things
> here, talking about really practical stuff that I can pinpoint in
> the textbooks). They listen, seem to understand the consequences,
> but in the end insist and justify it saying that since they are
> paying for it...
Don't worry - I've seen this a lot. Even when I've been employed
primarily for my user experience hat :-)
The absolute best way I've found to convince folk is by
demonstration. Show them a real user having problems with the "bad"
system. Show them having no problems with the "right" system.
- That's just it. They don't want to pay you to spend the time do it right just so you can eventually show them the right way... ;-)I guess I'll have to do it for free...Le 07-05-10 à 08:30, Adrian Howard a écrit :
> -----Original Message-----Oh, sorry. I didn't have time to follow this thread from the beginning.
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Adrian Howard
> Sent: May 10, 2007 8:00 AM
> To: firstname.lastname@example.org
> Subject: Re: [agile-usability] New poll for agile-usability
> On 10 May 2007, at 12:40, Desilets, Alain wrote:
> > I agree wholeheartedly.
> > It's not your user's job to find usability problems, no
> more than it
> > is their job to find bugs in your system.
> I read the original post as referring to having an onsite
> customer using the system.
I was just reacting to Robert's post.
> I'm not saying that this is a complete replacement for moreYes, I agree. I even weed out lots of usability issues by using the
> formal tests (coz it isn't :-) and I've certainly seen a sort
> of Stockholm Syndrome type relationship set in with the
> customer adapting to a UI that becomes worse as it evolves
> during a project.
> However, even with these issues, observing somebody who isn't
> a developer using the system on a daily basis can help an
> enormous amount in both spotting, and raising the priority
> of, usability issues within the team.
system myself even though I'm the one who built it. I guess I can do
that because I'm a very impatient user. So even when I use software I
built, I will get annoyed rapidly at anything that is not really easy to
- On 11 May 2007, at 03:02, Desilets, Alain wrote:
>> [mailto:email@example.com] On Behalf Of Adrian Howard[snip]
>> I read the original post as referring to having an onsite[snip]
>> customer using the system.
> Oh, sorry. I didn't have time to follow this thread from the
> I was just reacting to Robert's post.
Don't apologies - I could be wrong! I think you could read it either