Freedom to Invent

Build what you need. Then build the IP to support the business.

A friend who worked in Hewlett-Packard’s patent department once described his job:

Give the engineers freedom to invent.

That is the best description I have heard of what an in-house patent department is supposed to do. Patent competence is not a legal department’s side project. It is a C-suite responsibility.

A CEO does not ask a patent attorney for permission to build a product. A CEO decides what the business needs and tells IP strategy to clear the path.

Too many CEOs run this backward. They wait for the patent attorney to bless the roadmap, as if a green light were the attorney’s to give. It never was.

Giving engineers that freedom is one job, and it belongs to IP strategy. Doing it takes two inputs: what the product must do for the customer, from engineering, and where the company will compete, from the CEO.

Those inputs become a plan: which rights to create, acquire, or license; which patent risks need a challenge or insurance; which technical knowledge stays a trade secret; which competitor products the patents must cover; which pending applications stay open for future moves; and which outside attorneys handle which piece. Product redesign enters only after every other option has been priced.

The current product informs that plan, but the business drives it. The patent portfolio that comes out the other end is one output of the plan, not the plan itself.

Once management decides what the product needs to do, the mandate to IP strategy is clear:

Clear the path for us.

That is a directive, not a request for permission. IP strategy works backward from the course management has set, assembling and pricing the practical ways to preserve it: create patent leverage, buy needed rights, negotiate permission, challenge a patent, insure the financial exposure, restructure a commercial relationship, or use product redesign as a last resort. Management chooses among routes that require a business tradeoff.

Patent attorneys execute defined legal tasks within that strategy, and not always the same attorney. One may map patent requirements to the finished product. Another may render a validity opinion. If a dispute is active, patent litigators, a separate specialty from prosecution, build the litigation position. Their work serves the course. It does not set the course, define the product, or substitute for IP strategy.

Freedom to Invent preserves the division of responsibility. Engineering builds the product the business needs. The CEO sets the course. IP strategy clears the path. Patent attorneys perform the legal work required along that path.

Patent Litigation Is Different from Being a Patent Attorney

Being a patent attorney does not make someone a patent litigator.

The patent bar tests the statutes, rules, procedures, and Patent Office guidance used to prepare and pursue patent applications.^[1] Passing the patent-bar examination qualifies a lawyer to represent patent applicants before the Patent Office.

Patent litigation is a separate practice. Litigation requires experience with how judges interpret patent language, how juries respond to technical facts, what lawsuits cost, how opponents behave, and how a dispute affects the business. A Patent Office registration number does not establish litigation experience.

Yet companies routinely ask patent prosecutors to assess litigation exposure and then allow the assessment to control the product roadmap. Treating a prosecution analysis as a product decision is a category error.

A patent prosecutor can answer a defined prosecution or patent-scope question. A patent litigator can answer a defined litigation question. Neither decides whether the company should accept, insure, challenge, settle, litigate, or redesign. Those are choices within IP strategy. When they change the company’s course, they are management decisions.

The CEO Sets the Course

When a patent attorney’s risk assessment dictates the product roadmap, management has abdicated its responsibility.

Choosing the company’s course is extraordinarily difficult. The decision combines customer demand, product economics, available capital, engineering constraints, launch timing, competitive response, and the consequences of being wrong. The difficulty does not transfer responsibility for the decision to patent counsel.

The CEO knows the business in a way that an outside patent attorney cannot. Outside counsel usually does not attend customer interviews or product reviews. Counsel may not see lost-sale reports, pricing pressure, implementation problems, or the reasons customers choose one product over another. Counsel may know the competitor’s patents better than the competitor’s business.

The CEO owns the business decision. IP strategy owns the plan. The patent attorney executes the legal work it is given.

Management sometimes frames this backward: “What product can we build without patent risk?” That question hands the product decision to someone who does not know the business well enough to make it. State the decision instead: “This is the product the business needs.” The directive to IP strategy is equally direct: “Clear the path for us.” It then gives each patent attorney a defined legal task. The failure runs both directions: an attorney who refuses to decide is as much a problem as a CEO who asks permission.

The reversal becomes unmistakable when a narrow legal conclusion turns into a product instruction:

The competitor has a patent here. Do not build this feature.

That instruction treats the one risk it can see as the only risk that matters. Management sees additional risks: losing the customer, weakening the product, missing the market, conceding a critical capability, or giving a competitor years of uncontested advantage.

If IP strategy requires legal analysis, the attorney answers the question it was given and stops there. A conclusion about patent scope or validity does not become a product recommendation.

IP strategy turns “clear the path” into coordinated work:

Counsel maps the patent’s exact requirements and reports the legal position.
A patent search tests whether earlier work may undermine the patent.
Finance prices licenses, litigation, acquisitions, insurance, delay, and other responses.
Competitive intelligence identifies assets and relationships that can change the negotiating position.
Patent development creates positions the competitor may need.
Engineering identifies the customer value and technical requirements that management has decided to preserve.

IP strategy combines that work into routes for management. No patent attorney gets to convert one legal risk into a product veto.

Outside Counsel’s Conflicts Can Limit Execution

An in-house patent attorney has one client. A large outside firm may represent many companies in the same technical field, including competitors, suppliers, customers, and potential transaction partners. One of those companies can be the exact competitor asserting the patent.

That difference matters. IP strategy sometimes requires work that is adverse to another firm client.

An in-house CIPO lives with the business consequences of the plan. If the company cancels the product, the company lives with the lost revenue. If the company enters the market and receives a demand letter, the CIPO must coordinate the response. If the company needs patents to support a cross-license, the CIPO must build or acquire them.

The mandate remains clear: give the engineers freedom to invent. When a competitor’s patent creates a problem, clear the path.

Outside counsel may face another constraint. The firm may earn revenue from the company requesting work and from the competitor whose patents create the problem. An aggressive strategy for one client may force the firm to stop representing the other. The conflict rules may require consent, limit the work the firm can undertake, or prevent the firm from acting at all.^[2]

IP strategy might combine several responses:

Challenging the competitor’s patent.
Writing pending patent applications to cover the competitor’s products.
Buying patents that create an immediate counter-position.
Approaching another patent owner about a joint assertion or commercial alliance.
Seeking a court ruling that the competitor’s patent is invalid or does not cover the product.
Building the record and insurance position needed to withstand litigation.

If the competitor is also a firm client, some of that work may force the firm to confront the conflict, seek consent, decline the engagement, or lose one of the relationships.

A law firm answers a defined legal question. If it recommends product cancellation instead, it has crossed into management’s job. That answer may also let the firm avoid a conflict confrontation. No targeted patent work. No acquired rights aimed at the other client. No validity challenge. No adverse negotiation. The firm keeps both relationships, and the company gives up the market.

The recommendation will still sound like ordinary legal caution:

This appears to be a crowded patent area.

The competitor may have a strong position.

Litigation would be expensive.

The conservative approach is to avoid this feature.

Each statement may be true. None authorizes the firm to change the product or cancel the market.

IP strategy compares the patent risk with the product’s expected revenue, customer value, launch timing, competitive importance, and available countermeasures. If a law firm’s conflicts prevent it from executing part of the plan, that work moves to unconflicted counsel.

Before engaging an outside firm, the CIPO asks directly:

Does the firm represent the competitor, its parent, its subsidiaries, or another party whose interests may limit the work?
Has the firm checked conflicts for the countermeasures the company may need, rather than checking only the requested patent opinion?
Can the firm challenge the competitor’s patent?
Can the firm write and pursue patent rights that cover the competitor’s products?
Can the firm help acquire patents for use in that negotiation?
Can the firm represent the company if the discussion becomes adverse?
Which engagements must the firm decline, and why?

Sometimes the patent is strong, the alternatives are poor, and retreat is the right business decision. Management makes that decision after IP strategy has assembled and priced the practical routes. No outside law firm makes it for them. None of this requires the CEO to take over prosecution personally. That just trades one broken dynamic for another.

If one firm cannot execute the strategy the business needs, unconflicted counsel can handle the legal work. Excellent outside attorneys are valuable precisely because they can execute difficult engagements against a clear competitive target. They remain part of the strategy’s execution, not its source.

Start With the Product the Business Needs

The product team designs around customers, reliability, cost, manufacturability, timing, and competitive strategy. It does not design the product around patent risk. Management sets the product requirements before IP strategy begins its work.

Start with the product that the business would build if the patent did not exist.

Which feature creates the customer value? Which technical details are nonnegotiable? What revenue, timing, market position, and customer relationship depend on the launch?

Those answers become the directive to IP strategy. It works backward from the required outcome, assembles the assets and actions needed to preserve it, and commissions narrow legal work only where the plan requires it.

A patent does not own a general technical area. Its detailed requirements define a legal boundary.^[3] Patent analysis may document that boundary, but it does not send engineering back to the drawing board. Product change remains a management choice and a tertiary response.

The Strategies That Create Freedom to Invent

Strong companies rarely depend on one response. They assemble a position from several strategies and compare the economics of each combination.

The order begins with the business. Build or acquire an IP position that supports the market the company intends to serve. Add legal, commercial, and financial responses. Change the product only when management concludes that the change serves the business better than the alternatives.

Use pending applications to cover competitor products

A pending follow-on application can pursue new patent language supported by the original technical description as the market develops. When a competitor releases a product, the company can write patent language around observable features of the competitor’s implementation.

That tactic works only when the original application contains enough alternatives and technical detail to support the later language. A pending application cannot add technical material that was absent from the original description.^[4]

The first application therefore does more than document the current product. The application preserves positions the business may need after competitors reveal their designs.

Own the white space the competitor missed

A competitor’s portfolio shows what its patent team considered important. The portfolio also shows what the team overlooked.

Look for unowned architectures, integrations, operating modes, manufacturing methods, and improvements. Then compare those gaps with the direction of the market and the problems customers will demand that someone solve.

The objective is not to accumulate patents near a competitor. The objective is to own something the competitor’s business may need.

Own the competitor’s next move

Study the competitor as a business, not merely as a name on patent records.

What complaints are its customers making? Which technical limitation must disappear from the next generation? Which integrations are becoming mandatory? Which market is the competitor preparing to enter?

If your engineers solve those problems first, seek patents on the solutions. A patent on the current product records where your company operates today. A patent on the competitor’s next necessary move may influence where the competitor can go tomorrow.

Buy the patent position the business needs

Patent development takes years. A product decision may need an answer this quarter.

The company can buy the troubling patent, purchase patents that matter to the competitor’s revenue-producing products, acquire a portfolio before a hostile owner finds it, or acquire the business that owns the needed rights.

The test is not patent count. The test is whether ownership changes what the company can build or what the other side risks.

Add commercial, legal, and financial assets

Another patent is only one possible response. The company may:

Negotiate a license or cross-license.
Obtain patent-defense insurance before a demand arrives.
Require a supplier to accept responsibility for patent disputes involving the supplier’s component.
Form a joint venture with a company that owns complementary rights.
Partner with the patent owner on development.
Bring an independent inventor with a blocking patent into the company.
Acquire the inventor’s company, product, or portfolio.
Change which party performs a required step.
Build a challenge around earlier technology that covers the same ground.

Insurance can shift part of the defense costs, settlements, judgments, or damages to an insurer, depending on the policy.^[5] A license can preserve launch timing. A cross-license can turn one-sided exposure into mutual permission. A partnership or acquisition can change ownership and incentives while leaving the product intact.

These are management tools. The right combination depends on the importance of the product, the strength of the patent, the company’s resources, and the competitor’s vulnerability.

Use product redesign as a tertiary response

A design-around changes the product because of someone else’s patent. That option comes after management evaluates the business, legal, commercial, and financial responses.

Only after management chooses redesign does IP strategy commission a requirement-by-requirement patent analysis. Engineering owns the redesign. The attorney reports the legal requirements and does not design the product.

After engineering finishes, outside litigation counsel can prepare a Freedom to Operate opinion on the final design. The opinion documents the legal position for the product that management selected. It does not approve the product or direct the design.

The alternative architecture may improve cost, reliability, manufacturability, or performance. The company may seek patents on the new solution. Those benefits can make redesign an excellent answer. They do not make redesign the first answer.

Turn the Strategies Into a Management Decision

A practical Freedom to Invent analysis can fit in a decision brief the CIPO prepares.

The brief starts with the business objective, the product, and the customer value that must survive. It identifies the patent’s exact requirements and compares them with the planned design. It describes the available patent positions, acquisitions, licenses, challenges, insurance, partnerships, and possible product changes. It prices each path against expected revenue, launch timing, and strategic value.

The CEO sets the course. IP strategy selects and coordinates the tools needed to clear the path. Engineering builds the management-approved product. Finance prices the routes. Competitive intelligence identifies leverage. Patent attorneys execute the legal work within the selected plan.

The disciplines do not replace one another. They report to the strategy in the order management established.

The Business Remains in Control

The patent attorney does not set or reshape the company’s course; it executes a task within IP strategy. Unlike the CIPO, it does not live with the consequences if that task goes wrong.

Management weighs the importance of the product, expected revenue, launch timing, and competitive position. IP strategy turns those priorities into a coordinated plan:

Which pending application can reach the competitor’s product.
Which patent can be purchased.
Which earlier work supports a challenge.
Which partner or transaction changes the risk.
Which legal work requires outside counsel.

Product redesign stays at the end of the list. If management chooses it, engineering determines how to preserve the customer value and counsel later documents the legal position.

That is Freedom to Invent in practice.

The existence of a patent does not reopen the product decision for outside counsel.

The CEO sets the course. The engineers keep inventing. IP strategy clears the path. The patent attorneys execute.

The next article examines how Facebook, Synthes, and Liebel-Flarsheim used these strategies in public disputes. Subscribe to BlueIron IP to receive it.

¹ USPTO, General Requirements Bulletin for Admission to the Examination for Registration to Practice in Patent Cases Before the USPTO (explaining that the registration examination concerns service to patent applicants in preparing and pursuing patent applications and is based on patent laws, USPTO rules, the MPEP, and other USPTO policies and procedures). ↩

² ABA Model Rule 1.7(a)-(b), Conflict of Interest: Current Clients. The governing rule depends on the jurisdiction, but direct adversity and significant limits created by responsibilities to another client are standard conflict categories. ↩

³ 35 U.S.C. § 271; Warner-Jenkinson Co. v. Hilton Davis Chemical Co., 520 U.S. 17, 29-30, 40 (1997), reproduced in the Library of Congress U.S. Reports collection. ↩

⁴ MPEP § 201.07 and § 211.05; MPEP § 2163. ↩

⁵ IPISC, IP Defense Insurance; Aon, Intellectual Property Infringement Liability Insurance. Coverage depends on the policy’s terms, exclusions, limits, retention, and underwriting. ↩