/* Google Analytics */
Showing posts with label user innovation. Show all posts
Showing posts with label user innovation. Show all posts

Monday, August 11, 2008

Users becoming entrepreneurs

Last week I was at the HBS-MIT User and Open Innovation workshop. The conference is mostly (but not entirely) about user innovation in the footsteps of Eric von Hippel and his 1988 and 2005 books.

One of the major subthemes was on user innovators who become entrepreneurs. I’ve summarized the research I heard on the open innovation blog, but here wanted to comment on its applicability to facillitating engineering entrepreneurship.

One of the examples cited was Medtronic, the $14 billion/year firm founded by an electrical engineer and his brother-in-law to repair medical equipment. They were not user innovators, but to make their first pacemaker they involved doctors (i.e. pacemaker buyers, i.e. users) in the design.

This raises a question of how to best commercialize at the intersection of a highly technical user (in this case, MDs or scientists) and highly technical production processes (e.g. engineering of a human-wearable medical device). In this case, science is the customer — as with say instruments for radioastronomy — as opposed to being the input for the engineering (as with the WW II RadLab physicists enabling microwave radar).

So what if you have a product category that requires a combination of engineering competencies with deep knowledge of science, which belongs on the founding team? Are the engineers — who talk to doctors — more likely to succeed? Or does the advantage lie with a doctor-founder who hires engineers? The first is an example of a lead-user approach, while the second is user entrepreneurship.

My hunch (not immediately provable) is that the most important factor is none of the above. Instead, I suspect the driving force will be the same as with any other tech startup: how much business knowledge does the technical founder have — or, lacking such knowledge, how much is the founder willing to defer/listen to those with such knowledge?

Thursday, June 26, 2008

Product design and tech startups

The Wall Street Journal had a special section this week on the importance of product design. It’s currently available free, although (as with other stuff on their site) you can never tell what’s going to end up behind the pay wall.

I’m becoming increasingly convinced of the importance of product design in both the practice and teaching of technology-based startups. In general, firms that enter a high-tech market tend to enter based on innovation (Dell being the obvious exception). And — particularly given Apple’s influence with the iPod and iPhone — good product design is increasingly important as a differentiator.

This means that startups often need good design skills to have their products noticed in the market. We tend to think of industrial design — the shape of the device, placement of buttons, etc.

But as a Mac programmer of nearly 20 years, we also got drilled into us the importance of user interface design — which Xerox got (e.g. with the Mesa, Alto and SmallTalk systems), Apple refined, but many Windows software companies long ignored. Apple has carried this over to the iPhone: the features that the iPhone has are not exceptional, but the ease of use is. And from what I’ve seen, Apple’s high standards for Macintosh UIs have carried over to 3rd parties on the iPhone.

This also carries over into education. Stanford has an acclaimed (and AFAIK unique) Design Division within its Mechanical Engineering department. SJSU locates its design department within the combined School of Art and Design. As with other SJSU programs (like EE, CS and business), the design program provides the largest share of local design workers due to our size and that majority of our graduates end up in Santa Clara County. The design students were quite prominent in our recent Silicon Valley Business Plan Competition.

My favorite story in the special section was about the new masonry field saw developed by MK Diamond. It sounded like an important breakthrough in portability and usability for a very mature product category. More interestingly, it had elements of user innovation in the story, which was interesting both because the users got involved in developing the technology — and also that the manufacturer listened.