I think there are two different discussions here. Rob and tekochip ended up discussing how features do (or don't) end up in a product. But the missing magnet is not a feature: it's a design flaw. Jim and I were talking about what are, in effect, organizational structures that can blur the lines between brands, in the context of situations that dilute responsibility for product QA and testing and lead to the problem discussed in the article, the design flaw of the missing magnet.
So that means they are trying to anticipate features their customers will desire before their customers are able to articulate that desire. Are the engineers involved in the process to determine what features to develop?
In my experience Marketing writes the specification of what the device does and Engineering determines how to make the product. Features don't come from Engineering they come from Marketing. Certainly, there is a relationship between the two departments and a product benefits from technical and non-technical people brainstorming on what to include in the latest widget, but the specification on what a button does and where the button is located comes from Marketing.
Is that common, Tekochip, that with retail products marketing makes the final decision? On what basis would they make the decision? Seems the needing it out in the market is not a sufficient reason to make a determination that the product is OK to produce ship.
Perhaps you're right, Tekochip. Yet sometimes it doesn't seem like they've tested their systems sufficiently. Sometimes it seems they haven't worked out all of the quality issues with their equipment. Otherwise there would be no Made by Monkeys column. It could be that manufacturers have worked out most of the bugs, and then faulty components lead the system to fail.
Festo's BionicKangaroo combines pneumatic and electrical drive technology, plus very precise controls and condition monitoring. Like a real kangaroo, the BionicKangaroo robot harvests the kinetic energy of each takeoff and immediately uses it to power the next jump.
Design News and Digi-Key presents: Creating & Testing Your First RTOS Application Using MQX, a crash course that will look at defining a project, selecting a target processor, blocking code, defining tasks, completing code, and debugging.
Focus on Fundamentals consists of 45-minute on-line classes that cover a host of technologies. You learn without leaving the comfort of your desk. All classes are taught by subject-matter experts and all are archived. So if you can't attend live, attend at your convenience.