How to Explain Your Patent to Non-Technical People

To explain your patent to someone without a technical background, say what problem people had, what your invention does about it, and show one drawing. Add an everyday comparison if it helps, and be honest about what the patent does and doesn't cover. Leave out claim language, part numbers and the prior art unless someone asks.

This guide gives you a method you can use at a family dinner, in a team meeting or in a LinkedIn post.

Why it's hard

Patents are written for patent examiners and courts, not for people. The claims are a single long sentence each, precise about boundaries and silent about why anyone should care. The description is full of reference numerals and alternatives. After years of working in that language, it's easy to forget that "a substrate comprising a plurality of channels" means nothing to your aunt.

The five-part method

1. Start with the problem

Begin with something your listener can picture. Not "thermal management in high-density compute", but "computers in data centers get so hot that cooling them costs a fortune." People remember problems before solutions.

2. Say what the invention does, in one sentence

Use a verb, not a list of components. "It moves the heat out through the floor of the rack instead of blowing air across it." If you can't say it in one sentence, you haven't found the core yet. The patent's abstract (which USPTO rules ask to be preferably no more than 150 words) and its first independent claim are good places to look, but rewrite them in your own words.

3. Show one drawing

Your patent's figures are the best visual aid you have, and they are already public. Pick the one figure that shows the whole idea (often Figure 1). Point at two or three parts and name them in plain words. The reference numbers on the drawing match the description, so you can look up what each part is called and then translate it.

4. Offer an everyday comparison

A good comparison maps the unfamiliar onto something people already know. "It works like a sink drain for heat." Keep it to one, and say where it stops being accurate. Comparisons help people follow; they aren't what the patent covers.

5. Be honest about what it covers

People often hear "patent" and assume it means "nobody else can make anything like this." That's rarely true. A patent covers what its claims describe. In claims, "comprising" is an open-ended word meaning "including at least", so a claim covers anything that has all the listed parts, even with extras. But another product that solves the same problem differently may not be covered at all. A useful way to say it:

"My patent covers this particular way of doing it. Other people might find different ways."

You'll sound more credible, and you won't create expectations the patent can't meet.

Adjust for your audience

Family and friends. Lead with the story: how you noticed the problem, the moment it clicked, who you worked with. They care about you more than the mechanism. Keep it under a minute unless they ask questions.

Children. Use the drawing and a comparison, and let them guess what the parts do. "This part catches the heat, like a sponge catches water."

Non-technical colleagues. Sales, HR, finance and leadership want to know why it matters to customers or the company. Connect the problem to something they deal with, and avoid overstating the patent's reach.

A public post. One sentence on the problem, one on the invention, the main drawing, a link to the public record and a thank-you to your co-inventors. If the patent belongs to your employer, check your company's communications policy first.

Mistakes to avoid

• Reading claim language aloud. Accurate, but it loses everyone.
• Starting with the components. Start with the problem.
• Explaining every embodiment. The patent describes alternatives to make its coverage clear. Your listener needs the main one.
• Overclaiming. "Patented" doesn't mean "best", "proven" or "the only way".
• Sharing what isn't public. If you work for a company, stick to what the granted patent says. Unreleased products and unpublished applications are off limits.
• Forgetting your co-inventors. Name them. It's their patent too.

A worked example

Here's how the method applies to a familiar public patent, the 1986 squirt-gun patent (US 4,591,071) used in PatentFilm's sample films:

1. Problem: "A simple squirt gun fires one short squirt each time you pull the trigger."
2. Invention: "You fill it partway with water, then pump the slide to squeeze air into the space above the water. Pull the trigger and that pressure pushes out a strong, continuous stream."
3. Drawing: Figure 1, pointing to the slide pump and the scope-shaped air reservoir on top, which keeps a pocket of air in the gun.
4. Comparison: "Like a garden sprayer you pump up before you spray."
5. Limits: "It covers this particular design, as described in its claims, not every water toy that uses air pressure."

Five lines, and anyone at the table understands it.

Practice it out loud

Write your two-sentence version and say it to someone who isn't an engineer. Watch where they lose interest or ask "wait, what?" and fix that part. Most people need two or three tries. Once you have it, you'll use it for years: in interviews, on your profile, and every time someone asks what you do. For investor and licensing conversations, see how to explain your patent to investors and buyers.

Let your drawing do the talking

Want to see your own patent explained visually? Enter your patent number on PatentFilm's free trailer page and watch your real drawing ink onto the page in about ten seconds. It's a quick thing to send to the people you've been trying to explain it to.

Sources

• 37 CFR 1.72 (title and abstract), Cornell LII: https://www.law.cornell.edu/cfr/text/37/1.72
• 37 CFR 1.84 (standards for drawings, including reference characters), Cornell LII: https://www.law.cornell.edu/cfr/text/37/1.84
• USPTO, MPEP 2111.03, Transitional phrases: https://www.uspto.gov/web/offices/pac/mpep/s2111.html
• 35 U.S.C. 112 (specification and claims), Cornell LII: https://www.law.cornell.edu/uscode/text/35/112