Intellectual Property Basics

Some of the most valuable things a company owns can’t be touched: a logo everyone recognises, a recipe nobody else has, code that took years to write, a brand people trust. All of that lives under one umbrella called intellectual property, or IP. You don’t need to be a lawyer to handle it well — you just need to know the four main kinds, who tends to own them, and how to borrow other people’s IP without quietly creating a problem. This lesson keeps it plain. (Friendly note up front: this is general education, not legal advice — when real money or a real dispute is on the line, loop in your legal team.)

The four flavours of IP

A patent protects an invention — a new machine, a process, a genuinely novel way of doing something. It’s the strongest and slowest protection to get: you apply, you wait, and in exchange you get a time-limited monopoly. Most people never file one, but you might work alongside something that’s patented.

A trademark protects the things that identify a brand: a name, a logo, a slogan, sometimes even a colour or sound. The point of a trademark is to stop customers being confused about who they’re buying from. That little ™ or ® you see is a trademark flag.

A copyright protects creative expression the moment it’s fixed in some form — writing, images, music, video, and software code. You don’t have to register it; it exists automatically when the work is made. This is the kind of IP you brush against most often at work, because nearly everything you write or design is covered by it.

A trade secret is valuable information that stays protected precisely because it’s kept secret — a formula, a customer list, pricing logic, an internal method. Unlike a patent, there’s no public filing; the protection comes entirely from keeping it confidential. The moment it leaks, the protection evaporates.

Who owns what you create at work

Here’s the part that surprises people: when you create something as part of your job, your employer usually owns it, not you. This is the idea of work-for-hire. The deck you build, the code you commit, the article you draft on company time and for company purposes — under most employment contracts, that IP belongs to the company from the moment it’s made.

That cuts both ways and it’s worth understanding. It means you can’t take “your” work to a competitor and treat it as personal property. It also means the company carries the responsibility for it. Where things get murky is the grey zone: a side project on your own laptop and weekend, an idea sketched before you joined. Those edges are exactly where your contract and your legal team matter, so don’t assume — check.

Rule of thumb: if you made it for work, on work’s time or tools, assume work owns it. If you’re not sure where a project sits, ask before you build, not after.

Borrowing other people’s work

Most of the IP trouble ordinary employees run into isn’t about creating — it’s about using someone else’s material. Three areas deserve care.

Third-party content

That photo from a web search, the chart from a competitor’s report, the font you downloaded — they belong to someone. “It was online” is not permission. Before you reuse outside material in anything customer-facing, check the licence or use a properly licensed source. A stock image with a clear licence costs far less than a copyright claim.

Open-source software

Open-source code is free to use, but free is not the same as no-strings. Each open-source licence sets conditions: some are relaxed, others (often called “copyleft”) can require you to share your own code if you build on theirs. Engineers should check the licence before pulling a library into a product, because some licences are a poor fit for commercial software.

AI-generated content

AI tools are wonderful drafting partners, but treat their output with care. It may unintentionally echo someone else’s protected work, and ownership of purely AI-made content is still unsettled in many places. Don’t paste confidential company information or trade secrets into public AI tools — that can leak the very thing the protection depends on. Use AI to draft and accelerate, then review, edit, and make the work genuinely yours.

Spot it: IP types and ownership

Read each scenario and decide which type of IP it involves and who owns it, then tap a card to flip it and check your answer.

Sort the IP

Drag each item or scenario into the IP type it belongs to — or tap it, then tap a type. Hit Check placement when you’re done. (This is general education, not legal advice — for real decisions, ask your legal team.)

How to use it

You don’t need to memorise IP law; you need a few good reflexes and a few good questions. When you’re about to reuse something, ask: “Do we have the right to use this, and where’s the licence?” When you start a project, ask: “Is anything here going to belong to someone other than us?” When you reach for an AI tool, ask: “Is it safe to put this information in here?” Handy phrases: “Where did this image come from — is it licensed?” “Has someone checked the open-source licence on this library?” “Let’s keep anything confidential out of public AI tools.” None of these slow you down much, and all of them keep a small question from becoming a large one. And again — for anything high-stakes, your legal team is the real expert; this lesson just helps you spot when to call them.