Alex,
I don't find that rantful at all. In fact that is very much what I
was getting at, actually. a "process", not a "product". Continual
feedback. We must accept that we desire change, and plan up front
for it. We have identified a number of issues with the Blacklight
interface that demand change, immediately before its ready for prime
time. None of those changes are difficult to make, however effort is
to be expended to get there from here. If the mission is to "satisfy
your users", embracing their ever changing desires is by definition
all there is to it. Karen's point is starting with the user and
working backwards is the only logical way to build ultimately
satisfying systems.
I want to emphasize your point about users telling you what they
don't want. Don't make me think! It's not what you add, it's what
you take away. Simplicity is elegance. And it's effort. Here's my
rallying cry for us to push up our sleeves and get to work :)
Erik
p.s. I worked hard not to use any "but"'s in this message. Oops! ;)
On May 3, 2007, at 6:05 AM, Alexander Johannesen wrote:
>> > Give me a clear, definitive user-centric statement any day.
>
> On 5/3/07, Erik Hatcher <esh6h_at_virginia.edu> wrote:
>> how's this one? <http://code4lib.org/node/177>
>
> In a somewhat narrow definition of what users are and want, yes,
> that's very good, is as much as it's not so much user-centric
> statement as it is listening to feedback.
>
> rant/ (not directed at Eric at all)
>
> Very often, when doing user-centred design, for example, (which is
> highly relevant to Karens rant) you take a few steps back in the
> design process to that magical place before feedback is even
> generated. Often it can be summed up as "making iterations so small,
> the feedback-loop seems seemless".
>
> The thing with users is that they're not actually any good at telling
> you what they want, but they are extremly good at telling you what
> they don't want. This is why feedback has become so integral to our
> various development processes (be it software or otherwise) and
> project methodology. Unfortunately through this it becomes much harder
> to see that you should be aiming for removing it alltogether in
> working tightly with the users instead.
>
> /rant
>
>
> Alex
> --
> ----------------------------------------------------------------------
> -----
> Project Wrangler, SOA, Information Alchymist, UX, RESTafarian,
> Topic Maps
> ------------------------------------------ http://shelter.nu/blog/
> --------
Received on Thu May 03 2007 - 07:20:36 EDT