Look at how most companies run IP today, and it starts to resemble a car from 2005.
Separate knobs for the fan. A stereo that’s its own universe. A map system that needs a new CD to update. Everything works, technically. Nothing talks to anything else.
That’s IP in most organizations. Disjointed. Fragmented. Full of cracks.
The wrong default user
Here’s the uncomfortable truth: patent systems were never designed around the person who actually creates the IP. They were designed around the lawyer, and around the process the lawyer needs to follow.
Engineers have zero interest in navigating patent databases. And honestly? They shouldn’t have to. Ask anyone who has spent time on the R&D side, and they’ll tell you the same thing.
A patent database is not a Google search. It is a hostile environment for a creator. Complex classifications, dense legal language, search logic built for examiners — none of it maps to how an engineer actually thinks about a problem.
Why the gap matters
But here’s the catch: you cannot innovate effectively if you don’t understand what already exists. You need to know how your work differs from the state of the art to decide whether to file a patent or pivot to something genuinely new.
The conventional fix — send the engineer to learn patent search — fails every time. It’s not their job, and it slows down exactly the people who need the answer fastest. Forcing a creator to become a search expert doesn’t produce better search. It produces a reluctant engineer and a neglected database.
Three systems, three mindsets
Walk through how this usually plays out inside a company:
An engineer has an idea worth protecting? Someone needs to schedule an interview to extract it from their head.
Want to know what patents your own company holds? Ask the lawyer for a list. Wait.
Infringement risk appears in the market? Hope someone notices it and routes it to the right attorney before it becomes expensive.
Idea handling, protection, and defense end up living in three different systems, three different workflows, three different mindsets — with almost nothing connecting them. The engine (R&D) is disconnected from the fuel (sales). The dashboard doesn’t talk to the navigation. Everyone is driving, but nobody’s instruments agree with each other.
That’s not a tooling problem. That’s a design problem. IP has been built around the process, and the process has cracks everywhere an idea can quietly die.
What actually works: personalize, then integrate
The alternative isn’t more dashboards bolted onto the old system. It’s rethinking who the system is for.
Personalize the signal. A power electronics engineer doesn’t care about mechanical dampers — that information is noise to them. But if that same document lands on a colleague’s desk, the mechanical damper expert, that’s exactly where it matters. Automating retrieval isn’t enough on its own. You have to filter with precision, so the right patent reaches the right person instead of everyone getting the same undifferentiated report.
Integrate the workflow. Imagine an environment that adapts to who’s using it — the way a car recognizes driver one versus driver two. If an engineer concludes their idea is genuinely new, the system should help them shape it into a first invention disclosure automatically, no interview scheduling required. If infringement risk appears, the attorney gets notified the way a warning light tells you exactly what’s wrong — not a vague alert buried in an inbox.
Personalization without integration is just a better newsletter. Integration without personalization is just more noise, routed faster. You need both.
The Figaro moment
There’s a version of this that goes beyond efficiency. Engineers are naturally curious — think of it like being a fan of your own company’s team. You want to know how your side is performing, and what the competitors are fielding right now. When intelligence flows directly and automatically to the engineer, you’re not just checking a compliance box. You’re feeding the thing that already drives them: the desire to win.
Too often, engineers get information too late, get it wrong, or are excluded from the process entirely until it’s time to talk to the lawyers. That’s a broken model. It treats the people closest to the invention as the last to know about it.
What we should be aiming for is closer to harmony than compliance — the data reaching the engineer at the exact moment of creation, not after the fact. That’s the moment innovation actually blooms. Everything before that is just paperwork moving through a pipeline.
What this looks like in practice
Uhlmann Group was a real version of this problem. Patent searches and analysis used to run through a single person — the company’s Corporate Head of IP — with everyone else working from Excel lists and PDFs. The fix wasn’t a better tool for that one expert. It was delegating monitoring out to business units and letting engineers and project managers check IP considerations directly, without needing a legal background to do it.
What this means for IP and R&D leaders
If you’re responsible for how IP moves through your organization, a few things follow directly from this:
- Design around the engineer and the decision-maker — not the lawyer. The lawyer’s needs matter, but they shouldn’t be the default interface for everyone else.
- Kill the handoff gaps. Every crack between R&D and legal is a place where a promising idea quietly dies before anyone with authority ever sees it.
- Make the system predictive, not just archival. It should help answer whether to file, abandon, or license — not simply store documents for someone to search later.
- Treat role-based access as a baseline, not a luxury feature. Different people need different views of the same underlying intelligence, delivered at different moments.
The future of IP tooling isn’t more knobs on the dashboard. It’s one integrated view, where R&D is the engine, sales is the fuel, and the system connects them — telling you when to charge and why you should keep driving.
No more separate stereos. No more CD updates. One system, built for the people actually doing the inventing.
If your current IP workflow still looks more like a 2005 dashboard than an integrated cockpit, book a demo and see what it looks like when your engineers stop waiting for the report.
Insights by Dimitris Giannoccaro
