Brent (of NetNewsWire reknown) writes a nice piece about how to convince developers to add your favorite feature. Bottom line: explain what you need to accomplish, not what you think the feature should look like. Task models are really good places to begin design, because the designer can use the model to place new development in a broader context of what you, as a user, need to do. As Brent says:
If you tell me good, specific stories about you and the software and the problem you want to solve, then I’ll know why the feature is important, and that makes it more likely I’ll get to it sooner.
(InqScribe users, take note.)
posted April 17, 2006 by eric
Add comment: