Global Sources
EE Times-Asia
Stay in touch with EE Times Asia
EE Times-Asia > EDA/IP

Engineers do more of D in R&D

Posted: 18 Feb 2008 ?? ?Print Version ?Bookmark and Share

Keywords:R&D? technology companies? discovering algorithms? smooth signals?

Research and Development. R&D. It's the lifeblood of technology companies, and it's what we engineers do all day, everyday.

That's non-sense. There's no such thing as R&D. There's R, and there's D. And the two are completely separate activities.

Research is all about discovering new things. It's the science that ultimately enables the products we build, the metaphorical man-behind-the-curtain pulling the levers to control the machines we create.

Research might also involve discovering new algorithms, like new ways to smooth signals or compress data. "New" might mean new to us but not to the world. So we research an idea or a need, and then we switch to development mode. The result of research is an approach that one can then implement.

Bulk of engineering work
Development is taking known ideas and using them to build products. That's the bulk of an engineer's work. We transform an algorithm to something physical, like converting a CRC algorithm to C code, to VHDL inside an FPGA or to logic components.

One of my top 10 reasons for failed projects is "bad science" or the inability to separate R from D. When one starts building a product before really understanding what is being measured, the schedule is doomed. Start coding an algorithm without it being sharply defined and, at best, you'll wander aimlessly until--with luck--settling on an approach that works.

Research simply can't be scheduled. If you don't believe that, please develop a realistic schedule for discovering the cure for cancer.

You might be able to guesstimate simple research schedules, like doing a search for a known algorithm. But even that isin my experiencevery difficult to estimate. The first "Eureka" is often followed by disappointment when a little experimenting reveals some fatal flaw, requiring more research to find a better approach.

Yet I constantly see teams conflating R and D, leading inevitably to late or failed projects. Sure, some projects necessarily pursue R and D in parallel. But those can rarely be scheduled with any accuracy.

What do you think? Have you ever had a project disaster because you were doing R the same time as D?

-Jack Ganssle

Article Comments - Engineers do more of D in R&D
*? You can enter [0] more charecters.
*Verify code:


Visit Asia Webinars to learn about the latest in technology and get practical design tips.

Back to Top