[Sigia-l] Internal usability/UE teams

[Donna Timara]

On 6/25/05, Scott Nelson <skot at penguinstorm.com> wrote:
>> It is vague problem. I am not sure how will you calculate number of
>> toilet seats unless you know if you are talking about Regan Building,
>> MOMA, or the 12 story apartment building that I own in Boston?
>>
>> Probably you may look at rephrasing your questions. Vague questions
>> like this can't get you anywhere.

> overly specific questions result in answers of limited use to most,
> and have value for only a few.
> 
> it's quite common, and good practice, for those who answer questions
> to provide some context for those answers.
> --
> Skot Nelson

Skot, you are making a humble suggestion. However, spining the healthy
discussion that leads to closer to what you may deserve (by raising
the question), onus in on the person who raises the question. In this
context, person asking something is not making clear how will he use
the information, what industry is he talking about(?), what he means
by USability/ID(?) or what he means about averages(?), (cos' if Std.
Dev. is so huge, asking questions about averages/ratios is essentially
stupid thing to look at). Answer can't be anything but, hinting you to
rephrase it, norrow down, focus and structure your thouhgts.

This is a problem of "STRUCTURED THINKING". You have to phrase the
question to have answers fall in expected domain. I am all for those
who play devils advocate, to give you chance to correct.

So far I have enjoyed seeing how everyone reacted to the question. Ask
the question to yourself, Did you get the answer you expected? If not,
will you blame the poeple who did not answer, or to yourself for not
making it clear enough?

Your call, but I thought you suggested something good.

Donna