Vani Jha
Engineering research and development (R&D) is often spoken about as a single discipline, but Zoho founder Sridhar Vembu offers a much clearer and more practical way to look at it. According to Vembu, engineering R&D broadly falls into two distinct kinds, and understanding the difference between them can change how companies innovate, invest, and build sustainable technology.
Zoho Founder Sridhar Vembu’s Thoughts on Engineering
The first kind of engineering R&D is problem-driven R&D. This approach starts with a real, clearly defined problem usually faced by customers, businesses, or society and works backwards to find an effective engineering solution. The focus here is not on novelty for its own sake, but on usefulness, reliability, and cost-efficiency. Engineers working in this mode ask questions like: What is broken? What is too expensive? What can be simplified?
Zoho itself is a strong example of problem-driven R&D. Instead of chasing cutting-edge but costly technologies, the company focuses on building practical, scalable software that solves everyday business problems. This type of R&D often leads to incremental innovation—steady improvements that compound over time. While it may not always grab headlines, it creates durable value, especially in price-sensitive and emerging markets.
The second kind is technology-driven R&D. Here, the starting point is a new or emerging technology rather than an immediate problem. Engineers explore what is possible before fully knowing where or how it will be used. This type of R&D is common in areas like advanced semiconductors, artificial intelligence research, aerospace, and deep science-based innovation.
Technology-driven R&D plays a critical role in pushing the boundaries of human capability. It can lead to breakthroughs that redefine industries, but it is also expensive, risky, and time-consuming. Outcomes are uncertain, and commercial applications may take years or decades to emerge. Vembu has often pointed out that this model favours organisations with deep pockets and long-term patience, such as governments or large global corporations.
What makes Vembu’s perspective especially valuable is his emphasis on context. He argues that countries like India and companies operating within them should be thoughtful about where they invest their R&D efforts. Blindly copying Western, capital-intensive R&D models may not always make sense. Instead, problem-driven engineering can deliver far greater impact by addressing local needs at scale, using limited resources intelligently.
This distinction also reshapes how we define “innovation.” Innovation is not only about inventing something radically new; it is also about making technology accessible, affordable, and reliable for millions of users. Problem-driven R&D excels at this form of innovation.
In essence, Sridhar Vembu’s explanation reminds us that both kinds of engineering R&D are important, but they serve different purposes. Technology-driven R&D expands what is possible, while problem-driven R&D ensures that what is possible becomes useful. Companies and nations that understand this balance are better positioned to build sustainable, meaningful technological progress.