@aad: i really like the examples! @matthew: Users ...

2010-01-29T10:11:52.267+01:00

@aad: i really like the examples!
@matthew: Users often don't know what they want...everything their neighbours have is better :) But if we ask what they need...maybe it helps..
However, maybe sometimes as developer we trapped in "what we believe" they would need, not the one that is trully come from them

I think you're absolutely right that too many ...

2010-01-21T18:53:44.782+01:00

I think you're absolutely right that too many developers forget about the end user and what they're actually looking for.. but I find sometimes, if you're too interested in what the user wants, that feature-fetishism can work in the opposite direction. I've lost count of how many times I've told a manager, "we should build feature x into the software because of y and z reasons," only to be told, "you're absolutely right, we should. Those are great reasons. However, the client didn't ask for it, so no dice."

I've found the important question isn't "what do you want the product to do", but "what do you want to do with the product". Whether you're asking the client directly, or asking your "inner client", it's still the same. Derive features from use cases. Not "it should have x because x is cool."

(On another note, I just found your blog today, and I really like what I've seen so far! It's hard to find like-minded developers talking on Blogger, so I'm glad I found you!)

Comments on Aad 't Hart: Why are we all feature crazy and forgetting the us...

@aad: i really like the examples! @matthew: Users ...

I think you're absolutely right that too many ...