Live data from Hacker News

One cost engineers and product managers don't consider

firstround.com

1–10 of 102 posts

Re: One cost engineers and product managers don't consider

#4
Good article, makes an important point about complexity.

Just want to add one extra thought though:

  he or she will run reports against the usage data to find
  out whether a given feature is often used. That data can
  then be run past the product managers who can help decide
  whether it's sensible to just drop the feature. 
It's important to be careful here, and it's one of the traps that is very easy to fall into (see Gnome). Just because a feature is only used by 1% of your users doesn't mean it's not important. You might have 100 features only used by 1% of your users each, but if you take out all 100 features, chances are you've taken out at least one feature that every single one of your users depends on, and now your product is a lot worse instead of better.

Re: One cost engineers and product managers don't consider

#5
like a commenter suggests on the original post, end users don't care how something is built, but how well it solves a problem of theirs. It's like drucker saying costs have nothing to do with price. So, you can build things with bloat but it'll put you out of business. You also have to do right by your users. Not doing stuff because it's hard isn't a good excuse (a lot of the time).

Re: One cost engineers and product managers don't consider

#10
post #9

Whammed in the face with: "Subscribe to receive future articles right to your inbox" Tab closed. To hell with them.

I kept reading but definitely found it annoying.

It also took a few seconds to load and the page scrolled back to the top, causing me to lose my place. Extra annoying.

Post reply on HN