Competitive Strategy
How to Design Around a Patent
A patent gives its holder a monopoly on a specific implementation — not on the underlying idea. Designing around a patent means developing a different implementation that achieves a similar result without practicing the patent's claims. It is legal, common, and exactly what the patent system is meant to encourage.
Educational guide. Design-around analysis for a specific patent requires a patent attorney or agent.
The foundation: the all-elements rule
Patent infringement requires that the accused product or process practice every element of at least one claim. This is the all-elements rule. If your implementation is missing even one element of every independent claim, you do not literally infringe.
This rule is the foundation of all design-around strategy. Your goal is to find a way to achieve a similar technical result by using an approach that doesn't require practicing at least one element of every independent claim.
The analysis must be done claim by claim. A patent may have multiple independent claims with different element sets. A successful design-around must avoid infringing ALL independent claims (and any dependent claims built on them), not just one.
Step 1: Read the claims carefully — especially the narrowest limitations
Start with the independent claims. These are the claims that stand alone without reference to other claims. Find the element or limitation that appears most specific, most structural, or most uncommon. That limitation is your design-around target.
Look for: specific numerical ranges (a temperature 'between 100°C and 200°C' can be avoided by operating outside that range); specific structural components ('comprising a widget attached to a flange' can be avoided by using a different attachment mechanism); method steps performed in a specific order (avoiding the specific order may avoid infringement); specific materials or compounds.
Dependent claims add limitations to independent claims — they are narrower. If you infringe an independent claim, you may or may not infringe dependent claims. But the converse is useful: the specific limitations added in dependent claims tell you what the patent holder considered preferred embodiments, which often also reveals what the most important elements are.
Step 2: Identify alternative implementations
Once you identify the target limitation, brainstorm alternative implementations. The question is: what other ways exist to achieve the same technical result without using that specific element?
Prior art is your friend here. Prior art (inventions predating the patent) is not only relevant for invalidity — it's a source of alternative approaches. What methods existed before the patent was filed? Those pre-existing approaches are generally safe (they may be in the public domain) and may achieve a similar result by different means.
Consider: can you achieve the same result by adding a step the claim doesn't require? Can you remove an element the claim requires without significant performance loss? Can you substitute a different component that achieves the same function by a fundamentally different mechanism?
Step 3: Watch for the doctrine of equivalents
Literal non-infringement is not always the end of the analysis. The doctrine of equivalents can extend patent coverage beyond the literal claim language to cover alternatives that perform substantially the same function, in substantially the same way, to achieve substantially the same result (the 'function-way-result' test).
An effective design-around should avoid literal infringement AND avoid the doctrine of equivalents. The best design-arounds use fundamentally different mechanisms — not trivial substitutions. If you replace element X with element X' that works by the same principle in the same way, the patent holder may argue equivalence.
Prosecution history estoppel limits the doctrine of equivalents. If the patent holder narrowed a claim during prosecution (to overcome a rejection), they cannot later use the doctrine of equivalents to recapture that surrendered scope. Reviewing the prosecution history (available free on the USPTO Patent Center) can show exactly what scope was given up and cannot be recaptured through equivalents.
Step 4: Evaluate whether design-around is worth it
Design-around is not always the right answer. Consider: how central is the patented feature to your product? How costly is redesign? How close are the alternative implementations to your technical goals?
Sometimes licensing is better than designing around. If the patented approach is genuinely the best solution and alternatives require significant performance tradeoffs, a license may be cheaper than the engineering cost of redesign. Calculate: engineering cost of design-around vs. royalty rate × projected sales.
Sometimes invalidity is better. If the patent is weak — the claims are broad, prior art exists, or the specification doesn't adequately support the claims — challenging validity through IPR or litigation may be more effective than designing around a claim that shouldn't have issued.
Step 5: Freedom-to-operate (FTO) analysis
After implementing your design-around, conduct a freedom-to-operate analysis to confirm your new implementation doesn't infringe the patent (or other patents in the same family). FTO analysis compares your implementation against the claims of relevant patents.
FTO analysis should also check: continuation applications still pending (which may issue with claims targeting your design-around), divisional applications, and continuation-in-part applications that may cover the new approach you've implemented.
For high-stakes products, get a written FTO opinion from a registered patent attorney. A written opinion obtained before launch provides evidence of good faith, which can reduce willful infringement damages if you are sued.