It is often heard during first inventor meetings that the concept feels “too simple” to deserve a patent. This hesitation usually comes from seeing everyday products that look obvious in hindsight. In patent law, hindsight is filtered out. A simple idea can be patentable if it solves a technical problem in a way that was not obvious at the time of filing. The real question is not whether the idea looks simple today, but whether a skilled person could have arrived at it yesterday without inventive effort.
The legal yardsticks, briefly
Under the Patents Act, an “invention” is a new product or process that involves an inventive step and is capable of industrial application. Inventive step means a feature that shows technical advance or economic significance, or both, and makes the invention not obvious to a person skilled in the art. These definitions set the stage for analysing “simple” ideas correctly.
How Indian courts separate simplicity from obviousness
The Supreme Court’s decision in Biswanath Prasad Radhey Shyam v. Hindustan Metal Industries (Supreme Court, 1979) remains a touchstone. The Court explained that obviousness is judged through the eyes of the notional skilled worker and warned that a mere workshop improvement is not patentable. At the same time, a combination of known integers can be inventive if their working inter-relation produces a new or better result. Ratio in one line: simplicity is not fatal, but obvious simplicity is.
Delhi High Court decisions have applied structured methods to avoid hindsight. In F. Hoffmann-La Roche v. Cipla (Delhi High Court, 2015), the Court assessed obviousness using steps aligned with the Windsurfing/Pozzoli framework, which asks, among other things, what the common general knowledge was and whether the difference from prior art would be obvious to the skilled person. This discipline helps simple yet non-obvious advances survive.
Section 3 filters that trip up “simple” ideas
Even before inventive step is examined, Section 3 excludes categories that often appear simple by design. Common pitfalls include:
Section 3(e), a mere admixture that only aggregates properties of its components. A new mixture must show a synergistic effect, not just the sum of parts.
Section 3(f), a mere arrangement or re-arrangement or duplication of known devices, each performing its known function. Many “plug-and-play” combinations fail here unless the combination achieves a new functional interplay.
Section 3(k), mathematical or business methods or computer program per se. Software claims may still be patentable if they demonstrate a technical effect or technical contribution, as recognised in Ferid Allani v. Union of India (Delhi High Court, 2019).
Section 3(p), an invention that is, in effect, traditional knowledge or an aggregation of known properties of traditionally known components. If the advance draws only on long-known properties without a new technical effect, it will be filtered out.
When a simple idea succeeds: the winning patterns
Simple inventions clear the bar when they fit one or more of these patterns, supported by the specification and data:
A small structural tweak with a big technical payoff. If a minor change removes a failure mode, reduces energy use, or delivers measurable performance gains, and that benefit was not predictable to the skilled person, the simplicity helps rather than hurts. This aligns with the Act’s allowance for economic significance as an alternative to technical advance.
Non-obvious selection. Choosing a narrow range or a specific configuration from a broad field can be inventive if the selection yields an advantage that the art did not foreshadow.
True combination invention. Bringing together known parts so that they functionally interact to produce a new result avoids Section 3(f). The Supreme Court in Biswanath Prasad acknowledged that such synergy can be patentable.
How inventive step is actually examined, step by step
In prosecution and litigation, decision-makers commonly follow a structured analysis:
Identify the person skilled in the art and the common general knowledge.
Pin down the closest prior art and the differences from your claim.
Ask whether those differences would have been obvious to try with a reasonable expectation of success.
Guard against hindsight by using contemporaneous documents and problem–solution reasoning.
Consider secondary indicia, such as long-felt need or commercial success, only as supporting evidence.
Delhi High Court has used this discipline in cases like Roche v. Cipla to avoid substituting hindsight for analysis. The Supreme Court’s Biswanath Prasad decision is frequently cited for the core obviousness lens.
FAQs that come up in every “simple idea” conversation
If no one has done it, is that enough?
No. Novelty is necessary but not sufficient. The question is whether, starting from the prior art, the skilled person would have arrived at your solution without invention. Sections 2(1)(j) and 2(1)(ja) make inventive step a separate, mandatory gate.Will commercial success rescue a simple idea?
Commercial success can support non-obviousness, but it is never decisive by itself. Indian courts, including the Supreme Court in Biswanath Prasad, treat it as a secondary consideration, not a substitute for technical analysis.Does software that automates a manual step qualify?
Only if it shows a technical effect beyond a business rule or algorithm. In Ferid Allani, the Delhi High Court emphasised that claims demonstrating technical contribution may be patentable despite Section 3(k). Draft to highlight architecture, system interactions, or resource-level improvements, not just the logic.Is a cheaper version of a known product enough under “economic significance”?
Cost reduction can count, but only where the claimed features cause the saving in a way that was not obvious. The statute allows economic significance to establish inventive step, yet the non-obviousness test still applies. Provide evidence that competitors could not readily foresee your cost-cutting route.Drafting your “simple” invention for success
Use your specification to convert simplicity into patent strength:
Tell the problem plainly. Describe the technical snag that practitioners faced, and why prior solutions did not fix it without new trade-offs.
Prove the effect. Include data, test protocols, or comparative examples that show the improvement due to your claimed feature, not mere optimisation.
Claim the interaction. If your advance lies in how parts work together, put that interplay into the independent claim to avoid a Section 3(f) objection.
Draft sensible fallback claims. Add dependent claims with specific ranges, sub-combination features, or operative parameters that can be defended as non-obvious selections.
Avoid drafting as a “result to be achieved”. Claim concrete technical features rather than aspirations, so the inventive step analysis has real anchors.
For software, emphasise the technical effect, for example latency reduction, memory footprint reduction, network throughput improvement, or hardware resource management, supported by architecture diagrams. Ferid Allani is a helpful anchor for this approach.
A quick self-check before you invest in filing
Can you point to prior art that tried and failed, or that taught away from your approach.
Does your change create a measurable advantage in performance, reliability, or cost, rather than convenience alone.
Would a skilled person, reading the best prior art, have had a clear motivation and a reasonable expectation of success to make your change. If not, you likely have an inventive step argument.
Does the claim avoid Section 3 exclusions, especially 3(e), 3(f) and 3(k) for many “simple” looking inventions.
A short comparative note, for context only
Courts worldwide treat simplicity with care. The UK’s Windsurfing/Pozzoli steps, echoed in Indian decisions like Roche v. Cipla, exist to discipline hindsight. The Indian statute adds a helpful nuance by expressly recognising economic significance alongside technical advance, which means a leaner, cheaper, non-obvious solution can qualify even if it looks modest.
Bottom line
A simple idea is not a weak idea. If it produces a real technical effect or economic significance that a skilled person would not have predicted from the prior art, Indian law is prepared to protect it. Anchor your application in the problem solved, the concrete technical features that solve it, and evidence of the effect. Simplicity then becomes a strength, not a liability.
