Translating Research to Impact: Industry Considerations David Ott, Research Program Director Intel Labs September 21, 2012

2 Why do good research results often fail to make an impact?

3 An Industry Perspective Why no impact on the company? Well, could be Not enough technical leadership within company to champion the idea. Observation: Adoption of new product innovations often follow from the tireless effort from technical leaders who champion ideas within the company –Often a bottom up effort –Build awareness of innovation within company generally –Work to convince product teams, management, roadmap strategists –Work to connect research results to appropriate product teams Implication: Make sure your idea is connected with a strong champion within company. 2. Weak empirical case justifying benefits of the idea. Observation: Champion needs strong empirical case to convince management and peers of technical merits of the approach. –Theoretical argumentation appreciated, but typically requires empirical case quantifying the benefits –Modeling assumptions become major focus of discussion Implication: Equip your champion with a strong empirical case quantifying the benefits of your idea.

4 Notes on Modeling Theoretical Simplifying assumptions help focus fundamental nature of idea in generality Applied Application of ideas to highly realistic scenarios for quantifiable results. Remove simplifying assumptions. Consider additional real-world complexities (E.g., wireless network impediments – fading, shadowing, interference) Needed to understand the potential and limits of a new approach Needed to make empirical case for company adoption.

5 An Industry Perspective Why no impact on the company? Well, could be Weak business case. Observation: Champion needs a compelling business case to justify company investment in the innovation. Implication: Technical ideas must consider business incentives and context. 4.Killed by implementation challenges. Observation: Product teams have little time to prototype new ideas for the first time. Implication: Proof-of-concept reference code or implementation improves chances of adoption. 5.Lack of ecosystem adoption. Observation: Often a chicken-and-egg problem with no easy solution. Implication: Requires standards and/or industry consortium effort.