Live data from Hacker News

One cost engineers and product managers don't consider

firstround.com

61–70 of 102 posts

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

#61
post #15

For years, the two things that most frustrated me to hear from product managers were "how hard would it be..." and "can't you just..." It took me quite a while to figure out why I had such a strong, visceral reaction to these phrases. Oh, man. When it comes to my natural reaction to this, the words 'strong and visceral' doesn't even do justice. It took me a really long time to understand why I had such a deep-seated…

I've had some luck defusing these kinds of remarks by calmly but firmly stating that "with though simplifying assumptions, anything is trivial". YMMV.

"with though simplifying" doesn't sound right to me....did you mean something else?

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

#62
post #59
post #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 Gn…

We hit this at MSN: we removed the "print" button from all articles. Result? Engagement in Japan fell. Why? Apparently, printing out a sheaf of articles to peruse on the train is (or was) a thing. Solution? Re-enabled the "print" button in Japan; everyone else was saved from downloaded the unused-in-market "print" button, lowering PLT. Please keep in mind I'm talking about stuff from about five years ago when you run…

Seriously doubt this has changed, even now Japan sells millions of fax machines a year domestically, Japan loves paper.

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

#63
post #59
post #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 Gn…

We hit this at MSN: we removed the "print" button from all articles. Result? Engagement in Japan fell. Why? Apparently, printing out a sheaf of articles to peruse on the train is (or was) a thing. Solution? Re-enabled the "print" button in Japan; everyone else was saved from downloaded the unused-in-market "print" button, lowering PLT. Please keep in mind I'm talking about stuff from about five years ago when you run…

Problem is then that you have two cases that need to be tested and taken into consideration when designing etc.

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

#64

Earlier quoted context omitted.

I've had some luck defusing these kinds of remarks by calmly but firmly stating that "with though simplifying assumptions, anything is trivial". YMMV.

"with though simplifying" doesn't sound right to me....did you mean something else?

Context tells me he meant "with enough"... touch screens are a wonder for us fat fingered folks.

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

#65
post #15

For years, the two things that most frustrated me to hear from product managers were "how hard would it be..." and "can't you just..." It took me quite a while to figure out why I had such a strong, visceral reaction to these phrases. Oh, man. When it comes to my natural reaction to this, the words 'strong and visceral' doesn't even do justice. It took me a really long time to understand why I had such a deep-seated…

A designer I worked with had lots of interesting stuff taped to his door, and rotated it regularly.

My favorite was probably the following:

“Can you just...”

no.

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

#66
post #64

Earlier quoted context omitted.

"with though simplifying" doesn't sound right to me....did you mean something else?

Context tells me he meant "with enough"... touch screens are a wonder for us fat fingered folks.

The mobile experience on HN sucks.

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

#67

I've frequently heard designers, developers and VPs of Engineering -- which I'll collectively call "builders" -- argue that a product should have fewer features and thus should be "simple." But I honestly can't remember reading once when a user has said they want fewer features. Users want it to easy , yes, but they also want the features that make their lives, well, easier; see how that works? Whenever I hear builde…

What users say they want and what they will actually use are often completely different.

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

#68
Totally agree. The last company I worked for would agree to add basically any feature someone requested, even if it was of no use to anyone else. Most of the time spent implementing these odd features was making sure they'd work with all the other possible combinations of odd features, just in case they were ever used in tandem. They never were. The project I worked on was in its 4th total overhaul when I left, and they still hadn't actually sold a single copy.

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

#69

Earlier quoted context omitted.

That's how I feel about Apple deeming unimportant my Home, End, PgUp, PgDn, and front-delete keys.

Just in case you’re not aware: the Fn key, in conjunction with the arrow keys or the delete key, let you type those keys. Though that’s certainly not as convenient as having dedicated keys. Also, you can remap different keys to those keys with the free software KeyRemap4MacBook ( https://pqrs.org/macosx/keyremap4macbook/index.html.en ). For instance, you can remap \ to be forward-delete and Fn+\ to be typing ‘\’.

That's fine and good, until you want to use key combinations that include the missing keys, particularly selection type stuff. For me, it comes up a lot in programming, writing, and file/photo management.

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

#70
post #13

The first comment on that page sort of made me face palm... but then it got me thinking. "Simplicity of usage should always win over simplicity of coding. The purpose of a product is to solve the end user's pain, no one should give a dime about the engineer's problem. IMHO that was the genius of Steve Jobs, he could take any pre-exiting product and increase its complexity by 50x while simplifying its usage by 10x." I…

Look up "worse is better"
Post reply on HN