Yes, I think it often depends on someone's mood or what type of person they are. Some people just don't like working with other people. I myself am a people person in general, so find collaboration very helpful. That said, in the work I do now, I work alone and in quite a solitary way, so collaboration doesn't come into play. But I'm not an inventor...so I would think bouncing ideas off of others definitely has its place. That's an interesting story about Edison! It's nice to think it's true...often it is people with no formal education who have the type of mind to think outside of the box.
Collaboration can be a good or bad thing, depending on the collaborators and the reason for the collaboration. When a previous employer mandated "cross-functional development teams," it was an example of the bad kind. When the "collaborators" are assigned by management, to a product "we absolutely have to have" because the VP of marketing saw our competitor with it at a trade show, you're liable to get "design by committee" - no real originality because there's no real "buy-in". With no real "buy-in" you compete, not for credit for a successful product, but to avoid the blame for one you expect to fail.
On the other hand, when one seeks out collaborators of his own choosing, and they voluntarily help make his idea real, a great idea can turn into a great product very quickly. I'm an electronics type, and from the start I realized that I needed help... not in my own area of expertise, but in areas where I'm not expected to have much of a clue. I had my own "cross-functional team" long before it entered the lexicon of management buzzwords.
I'm not a software engineer, but my friend Ed is: Let's get his input on processor selection and I/O pin assignments. Let's both talk to Jim, in field service: what can we do, in hardware and software, to make his job easier? Jay's a mechanical engineer - he's got to mount the board, let's talk to him and to John, in industrial design, and make sure we're all on the same page before we start layout. Consult with Fred, in purchasing, before the BOM is finalized. Lean on Mike, in subassembly test, while I'm drawing the schematic, and Bob in board assembly while we're actually doing the layout. That collaboration led to what became a "cash-cow" product for that company.
Based on my own experience, collaboration is useful even if the other(s) involved have no clue what problem you are attempting to solve or how you are trying to solve it. I can't count how many times I've observed or experienced the ability to creatively solve a problem by simply talking it out with someone else. And in my experience, it doesn't seem to matter if collaboration is with a PhD or my 14 yr old daughter. Ideas build on ideas and when and the very act of having to convey the idea to someone else seems to spawn the next layer of ideas.
Edison was a great man, no doubt about it. He invented things people didn't even know they needed or wanted. For instance who knew they needed a phonograph? So knowing what people want or need is not necessarily the best approach to inventing something great.
Edison did not have a good reputation as far as collaboration goes. For example, Nicola Tesla collaborated with Edison but it didn't turn out too well for Tesla.
Nice column. But if the intent of the author is to get rid of the stigma around her great-grand uncle, why does she pass one on to us: "Engineers ... fall in love with their technologies ... You should ... find out what the customer's needs are". True, but as far as customers go, let me ask you the following. Do you know of any engineer that is not concerned with his customers' needs? And if so, is that the rule?
By the way I believe Edison was brilliant ... No need to cover for his harsh work environment ...
If anyone truly becomes a more effective engineer from this book, I would certainly like to hear about it; and then I would know to stay away from that person.
Elizabeth, - Dittos on your "both methods" comment. Well said. There are times when you need to put your feet up on your desk, listen to your iPod, and think. And there are times when you need to collaborate. Knowing the difference is a sign of wisdom. Also, I have heard an urban legend that Edison highly valued the input of a particular technician of his, a man with far less education, who was actually the one who developed the method by which tungsten could be drawn into a filiment. Don't know if it is true, but his anti-collaboration with Westinghouse and Tesla were a marque of the age! If I were a betting man, I would wager that Edison followed your "both methods" comment.
I can see how collaboration is a better way in some aspects than working in a vacuum, but I also think there is something to be said for both methods, and it depends on what kind of person you're dealing with. Interesting to think Edison had so many collaborators, but not surprising. I wonder if anyone ever felt bad or jealous because he got all the credit for something they also contributed to?
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.