In Philip’s photo site I once read someone remark that photo equipment today looks like it is designed by Marketing MBAs and liability lawyers instead of by Photographers and Engineers (or something like that).

@Geoff B: Wouldn’t it be quite a bit easier to just tap your power button, scroll down to “Silent” and hit Select? Of course turning the phone off is still quicker, but the process to turn the ringer off in Nokia phones is much more simple than you describe. Check your manual for profiles.

This is precisely the attitude that makes offshore development cost effective…As an engineer you have to THINK.

And if you’ve worked in dunderheaded large corporate tech environments, an engineer who speaks up gets branded a ‘troublemaker’, ‘not a team player’ and such, more often than not.
A lot of us started out as conscientious speak-up-to-make-the-product-better idea-oriented types but learned the hard way to keep our mouths shut after getting reamed too many times. Try to improve the product or damage your career – which is more important?
Companies that treat these functions as commodities and offshore them (i.e. most of them) usually are indifferent to engineers’ ideas to start with. Our job has been defined as following orders and not making waves, or they’ll find someone in India who will do that.

I would bet that any suggested improvements in the design from engineering were quickly dismissed by the marketing guys. Stories like these are yet more proof that only the smartest people in the organization should be making decisions. But of course, the smartest people are almost certainly not in marketing (or product management, or the Oval Office).

A agree with these observations. I’m a software engineer of over 25 years (well, more of a conscientious hacker since I’m self-educated) – I am one of the few I know who care about the user experience for products I work on.

Much of the problem stems from the way products are ‘designed’ – as some have pointed out, products are designed by committee or specified by marketing in many cases, and there is no process for looking at the product useability as a whole. Often ‘features’ start out as somebody’s idea of something that will look cool in a demo, or as part of a prototype to get the project rolling, and they are left in the product due to inertia or just plain laziness.

User interaction design usually gets the short end of the stick, in my experience.

I am shocked by the huge difference in usability between different brands of cell phones, digital cameras, etc. Some of these products are just horrible, and I spread the word about them when I encounter them.

Hanan –

Good link.

How many “clicks” does it take for you to turn off the ringer on your cell phone? On my nokia, I have to hit Menu (1), scroll down to “Settings” (5), hit select (1), scroll down to “Tone settings” (6), hit select (1), hit “Ringing Options” (1), scroll down to “Silent” (4), hit “Select” (1).

Of course, I just turn it off – one click.

“The programmer was responsible for doing what he was told by management, no more and no less.”

This is precisely the attitude that makes offshore development cost effective. Management knows you just implement to the spec, so it makes sense to use the cheapest possible spec implementer you can find.

As an engineer you have to THINK. Personally, I’ve never just implemented the spec except for a couple of times where I felt it was completely right the first time. The largest part of being a professional engineer is challenging the assumptions and decisions to make the best possible product for the end user; otherwise you’re just a coder.

Philip, does your phone make a sound when you turn it off?

http://www.thisisbroken.com/b/2003/12/cellphone_shutt.html

I completely agree with Matti Kinnunen. As a Software Developer I always tell my managers if I think the feature they are asking me to implement is bad/incomplete/etc. I believe it is my responsibility to do so.

I totaly disagree with Ken. My wife just returned her new Motorolla cell phone to Cingular because it was asking her TWICE if she wanted to accept the person’s contact via Bluetooth, but it didn’t bother to ask AT ALL whether she really wanted to delete a contact or not!

Is this really strictly a software problem? It seems to me that you could just as easily cast this as a hardware problem, ie. “handset vibration is picked up by the microphone”.

The ideal solution to my mind is to change both the hardware and software, so that the handset has two vibrating modes, the first noticable when the phone is carried in a pocket and the second one noticable only when held in your hand, and the second is used when on a call. The microphone should also be sheilded sufficiently from the vibration so as not to pick up the second (softer) vibration mode while talking.

Unfortunately, this sort of intergrated hardware/software design is something few players in the industry are willing to invest in, in part because it *dis*-empowers the marketing and sales executives who hold the reins from being able to add their checklist of ‘bullet point’ features while squeezing the RD&D budget.