Entering a Patent Thicket: Map the Blocking Claims First, Then Redesign the Principle

In my 20 years of practice as a patent attorney and patent litigator, my advice to clients entering a crowded technology field has stayed the same: do not try to manage a vague sense of "lots of patents out there." Turn it into a short list of specific claims, and then into specific engineering choices. The sequence below is how I do that.

This article describes a general working method. It is not legal advice; consult a qualified patent attorney for your situation.

What is the first step when a client enters a patent-dense field?

When a client tells me they are entering a field dense with patents, my first recommendation is a freedom-to-operate (FTO) analysis. The aim is not to count patents or draw a landscape. The aim is narrower and more useful: find the specific patents that could stop this product from reaching the market.

Then comes the part many teams skip. I map the product's structure and steps, item by item, against the valid claims of those patents. A claim is infringed only if the product contains every feature of the claim, literally or by an equivalent. So the mapping shows exactly which features of your product are carrying the risk, and which are irrelevant.

A patent thicket becomes manageable once it is reduced to a feature-by-feature comparison against a handful of live claims. The risk lives in specific features, so the solution has to be found in specific features too.

How do I decide what to remove, replace or license?

With the mapping in hand, I sit down with the R&D team and work through three questions for each risky feature:

1. Which features can be eliminated? A feature that the product does not actually need is the cheapest risk to remove.
2. Which functions can be achieved on a different principle? This is the most valuable question. A claim usually protects one way of doing something, not the need itself.
3. Which routes require a license? If a feature cannot be removed or re-engineered without losing what the product needs, it is better to know that early and negotiate than to discover it after launch.

This conversation only works when the engineers and the patent professional are in the same room. The patent professional knows what the claim covers; the engineers know what the product truly needs. Each side alone tends to get it wrong.

Why search again after you have a new design?

Once the new route is fixed, I always run a fresh search. It is entirely possible to step around one patent and land inside another. The new design has its own features, and those features need their own comparison against the claims that are in force in the target market, including an assessment of equivalents.

Skipping this step defeats the purpose of the whole exercise: escaping the first patent means little if nobody checks where the new design has landed.

What does a design-around on a different principle look like?

The following is an illustrative example, not a real client case. I use it to show how the method plays out.

A client plans to develop an industrial filter that cleans itself automatically. The FTO analysis finds a competitor's valid claim requiring features along the lines of: detecting pressure differential, closing the inlet valve, injecting water in reverse through a backwash line, and discharging the debris.

The client's first instinct is to adjust the valve position and the flushing time. This route still carries a high risk, because the product continues to detect, close, backwash and discharge. Changing positions and timings does not take it outside the logic of the claim, and an equivalence argument would be easy to make.

In the discussion with R&D, it turns out that what the client really needs is for the filter to recover its filtering capacity automatically once the screen clogs. Backwashing is one way to do that, not the only way.

So the R&D team switches to a rotating filter drum combined with a mechanical scraper, which scrapes surface debris into a collection trough. The inlet is not closed during normal filtration, and there is no backwash line at all.

The prototype is then verified against filtration efficiency and wear requirements. After a fresh search of the relevant patents in the target market, a comparison against their claims and an analysis of equivalent infringement risk, no valid claim is found that blocks this specific design, and the client adopts it.

The illustrative filter case shows the pattern I look for: stop asking how to tweak the competitor's solution and ask what the product actually needs. A different working principle is usually a sturdier design-around than a different position or a different timing.

How does this compare across jurisdictions?

The method is the same wherever you sell, but the legal detail is local. Infringement is assessed country by country, against patents in force in that country, under that country's rules on claim interpretation and equivalents. The United States, the European patent systems and China all recognize some form of the doctrine of equivalents, and their courts weigh it differently. That is why the fresh search and equivalents analysis should be done for each target market, not once for the world.

What should engineering leaders take away?

• Treat FTO as a design input at the start of a project, not a legal formality at the end.
• Insist on a feature-by-feature mapping; a list of "related patents" is not an answer.
• Give the R&D team the real need behind each risky feature, so they can look for a different principle.
• Re-search every new design before you commit tooling and production.
• Bring in a qualified patent attorney for the final opinion. Analysis tools speed up the work, but they do not replace a professional judgment on infringement.

This is not legal advice; consult a qualified patent attorney for your situation.