October 1, 2026

Who Really Owns Your IP?

Last week, Oasis did what Oasis tend to do best: create noise.

Not with a reunion rumour this time, but with lawyers.

According to Sky News, a set of unheard Oasis archive recordings was pulled from auction after the band filed legal proceedings against a former sound engineer, his son and the auction house. Source: Sky News, 'Oasis sue over auction of unheard recordings archive'.

Now, if you are a founder, CTO or COO reading that and thinking, 'Interesting, but I am not in Britpop', stay with me.

This is not a music story. It is an ownership story. And ownership stories have a nasty habit of turning into hiring stories, operational stories, and eventually very expensive messes.

Because when valuable assets leave through side doors, they rarely do it by accident. They usually slip out through vague contracts, fuzzy handovers, lazy governance, or that classic business strategy: 'We will sort it later.'

Lovely. Until later turns up wearing a solicitor's tie.

IP leaks do not start in legal

Most leaders think intellectual property risk lives in a contract folder somewhere between Legal and Finance.

It does not.

It lives in people, process, access, and behaviour.

That is why stories like this matter beyond celebrity headlines. Whether it is unreleased recordings, source code, infrastructure documentation, models, customer datasets, security architecture, or product roadmaps, the same question always sits beneath the drama:

Who owns the asset, who can access it, and who can walk away with it?

If you cannot answer that quickly, you do not have an IP policy. You have vibes.

And vibes are not much use in court.

Your best people can also be your biggest blind spot

Here is where leaders get uncomfortable.

The people closest to your most valuable assets are often the ones you trust most. Engineers. Architects. Data leads. Producers. Long-serving contractors. The person who knows where everything is buried and has not taken a proper holiday since 2019.

They are critical.

They are also risk concentration in human form.

Not because they are villains, but because businesses are often astonishingly casual about boundaries when someone is productive.

We let top performers build private systems of control around key assets. We let documentation become tribal knowledge. We let access rights linger long after projects end. We let ex-contractors keep copies 'just in case'. We skip formal transfer processes because everyone is busy and Karen from Ops wants this wrapped before quarter end.

This is how commercial value ends up in grey zones.

Bad actors exploit grey zones. Good people get caught in them. Neither is great.

The hiring mistake hiding inside the story

As a recruiter, I see a version of this problem all the time.

Companies hire for skill, then assume trust, ownership discipline and risk awareness will somehow arrive as part of the onboarding hamper.

They do not.

You can hire a brilliant Head of Data who can build your reporting engine in record time. Fantastic. But if they cannot create clear controls around data ownership, access and handover, you have not hired a leader. You have hired technical velocity with a delayed invoice attached.

Same goes for infrastructure, cyber, cloud and product engineering.

The market still over-rewards pure technical firepower and under-tests for stewardship.

That is a mistake.

Especially in start-ups and scale-ups, where one strong operator can architect your future or quietly create a dependency so awkward it survives three restructures and two therapy cycles.

Harsh? Maybe.

Accurate? Also yes.

The four things smart leaders tighten early

If this Oasis story has a business lesson, it is this: protect your crown jewels before they become someone else's side hustle, inheritance puzzle or auction lot.

Here is the practical bit.

Ownership

Spell out who owns what. Not in a vague, 'obviously the company owns it' way.

Be specific across:

• Employee-created work
• Contractor-created work
• Legacy assets
• Archived materials
• Jointly developed materials
• Copies, derivatives and backups

If your contracts are inconsistent across permanent staff, consultants and freelancers, that is not a paperwork issue. It is a value leakage issue.

Access

Audit who can reach critical assets.

Not just systems access, but practical access.

Ask:

• Who can download it?
• Who can duplicate it?
• Who can transfer it externally?
• Who can access archived material no one has checked in years?
• Who still has credentials they should not?

Every forgotten permission is a future headache with admin rights.

Handover

Most businesses are embarrassingly poor at offboarding.

A laptop return is not a handover. It is logistics.

A real handover covers:

• Asset transfer
• Documentation
• Password and credential reassignment
• Repository ownership
• Confirmation of deletion where appropriate
• Written sign-off from both sides

If your offboarding process fits on a sticky note, it is too thin.

Leadership fit

When hiring into critical functions, test for governance instinct as hard as you test for execution.

Interview for questions like:

• How have you protected business-critical IP in previous roles?
• What is your approach to access control and handover discipline?
• How do you prevent knowledge from sitting with one person?
• Tell me about a time you inherited messy ownership of systems or data. What did you do?

The strongest leaders do not just build. They de-risk while building.

A simple framework: Build, protect, prove

If you want an easy internal lens, use this.

Build: Create value through people, systems and ideas.

Protect: Put controls around who owns it, accesses it and transfers it.

Prove: Maintain the documentation, contracts and audit trail to show that protection actually exists.

Most firms manage step one.

Some manage step two.

Very few can prove step three under pressure.

That is where the pain begins.

Questions worth asking this week

If you are leading a team, here are a few useful questions for your next internal conversation:

• What are our most commercially sensitive assets?
• Who has access to them today?
• Where is ownership documented?
• Would that documentation survive scrutiny?
• Do any key assets depend too heavily on one person?
• How confident are we in our contractor and leaver processes?
• Have we hired leaders who understand stewardship, not just delivery?

You do not need a legal row with a famous band to justify asking them.

You just need common sense and a healthy dislike of avoidable chaos.

The real cost of getting this wrong

People tend to think the cost of weak IP governance is legal spend.

That is only the trailer.

The full film includes:

• Delayed funding or due diligence friction
• Operational disruption
• Messy exits
• Brand damage
• Lost leverage in disputes
• Internal mistrust
• Painful rework to clean up ownership later

And yes, hiring pain too.

Because once a business has been burned by a loose operator or poor controls, every future hire gets examined under a microscope. Recruitment slows. Confidence drops. Decision-making gets weird. Suddenly everyone wants a unicorn with immaculate governance habits, instant impact and the temperament of a Swiss watch.

Fair enough. But it is better to hire properly before the scar tissue forms.

Conclusion

The Oasis auction story is entertaining because it is famous, messy and a bit rock and roll.

But beneath it sits a very unglamorous truth: valuable assets walk when leaders get sloppy about ownership.

So yes, hire brilliant people. Of course.

But hire people who understand custody, not just creativity. Build systems that survive departures. Lock down what matters. Write it down properly.

Because if your most valuable IP can drift into dispute, then it is not really under control.

And if it is not under control, it is only a matter of time before someone else tries to put a price on it.

Back to news