That’s a good point about the tradeoff of value to time spent. As an aside: while it’s true that there’s not a ton of value to knowing the total number of each rodent, there’s a secondary value that is very important: the value of not disappointing the user.

If I look at this list *without* numbers and click ‘Gerbils’ — then find only one gerbil listed — I’m bummed out. “Man, only one gerbil?” It makes the site look scrawny. I might even look at the other links and think, “Why should I click if they’ll only have one rodent per list?”

By pre-acknowledging the situation, as it were, with the numbers, we prevent user disappointment. We also give them a context — “Yeah, only one gerbil, but there are lots of hamsters.”

A good link lets you know what to expect before you click. That makes for comfortable users.

Man, I have to admit though, there have been times when I’ve been Tom and Terry out of laziness, even knowing what the right move is. I personally have to guard against that as well.

Same with my slacker programmer Matt, which is why I keep a short leash on him and give him no time to rest…

My main point was that Tom and Terry, deep in the technician’s laboratory, didn’t even consider the feature from the user’s perspective. When they were faced with a usability problem, they latched on to the first thing that came to them, which wasn’t even a real solution to the initial problem. That’s because it came from their technician brains.

Again, you have a real point about how much it costs. Good technicians will be able to provide information on trade-offs, as you did to your former boss. But good technicians also know when it’s time to take off the coder cap and spend a little extra effort making their tool easy to use.

Sometimes, the *best* solution is to have the number in parenthesis, like you’ve said, however, it also takes X 20 hours to complete, and only provides X 4 in value.

Now, I actually ended up quitting my old job because I constantly tried to protect my boss from paying for features that did not provide an adequate return on investment. Sure, I didn’t want to do the work, but I also knew that he was asking for things that in the end, would cost him money versus provide a benefit that outweighed the cost.

Lesson learned? Don’t protect the client, ever. However, it is our responsibility as the hired professional to sometimes inform the client/boss about costs and projected ROI. If you give them the opportunity to choose, they often prefer a cheaper solution rather than an expensive one if they realize the benefit is trivial.

In this case, what if the benefit of knowing the number of rodents in each category only helped 1 out of 83 users? It is obviously the better of the two, but what do you do when the cost far outweighs the usefulness? And what if the extra time Tom and Terry saved by not incorporating a insignificant feature allowed them to incorporate a truly valuable feature that benefited 54 out of 83?

I think I’ve confused myself…