What is IP Management Software and who needs it?

May 19th, 2009 Greg Daines Posted in IP Management Software, Intellectual Property No Comments »

The short answer: it’s a lot of things, and a lot of people need it.

I’ll just say it… The concept of managing intellectual property is a bit elusive. For that matter, the idea of intellectual property itself is often a bit vague for many. This can make explaining what IP management software is to those with little knowledge about IP extremely challenging. But it may surprise you that it can be just as difficult to describe IP management software to people who are experts in the field of IP. Why is this? I think it’s because there are a lot of different things that various people do with IP and a lot of different people involved. My goal here is to break that down into some very simple categories to make it easier to understand what IP management is and what kinds of software you can get to support it. Before we can do that, I have to explain a few things…

First, IP means different things to different people. Just Google the term “IP Management Software” and you will see what I mean. For starters, you will see that “IP” itself has multiple meanings. For instance, to a bunch of people out there IP stands for “Internet Protocol”, and they have their own management software to help them do whatever it is they do. Beyond that you will find software for the media and entertainment industries, software for lawyers, and even software for software companies among a variety of other things. It almost feels like “IP Management Software” is a grab-bag: reach in and you never know what you might find!

Secondly, there are multiple kinds of intellectual property: patents, trademark, service mark, registered designs, trade secrets, and more. To complicate matters more, intellectual property has even become a kind of catch-phrase associated with corporate innovation and competitiveness and is often used almost interchangeably with the word “innovation”. At this stage in the computer “revolution” it should surprise no one that there is a software application for just about everything and therefore we are not surprised to find “management software” for virtually every flavor of intellectual property, as well as for virtually every role and activity associated with it.

Lawyer or No? At my company, we get a lot of calls and email inquiries about our IP management software from people who are actually looking for something completely different. I can usually tell right away which ones are actually interested in “Internet Protocol” management and happily inform them of their wrong turn. However, for a long time I had a more difficult time determining whether the rest has found the right place or not. That is until in desperation one day I seized on a simple diagnostic which I now use every day that helps immensely to organize this mess. It is a simple question that divides the IP (intellectual property) world into two major camps. I simply ask, “Are you an attorney or patent agent?” If the answer is no, then it is possible that have found the right place and a few follow-up questions will easily determine if they have. If the answer is yes, it is almost certain that they are in the wrong place.

A bit of background helps… Historically intellectual property was always primarily a legal process. It was something lawyers do. IP is a legal entity. Filing, amending, prosecuting, maintaining, litigating - these have been the processes people associate with IP for generations. Companies and other organizations have almost universally thought of IP as a legal process, and therefore responsibility for it was almost always given to the general counsel’s office. The main purpose of having IP was to protect the competitive position of the company’s products and markets.

Then, something happened: people started to make money directly on IP. Of course this was already happening in media such as music and movies and in software among others. But other people got in the game. For instance, universities started to make money licensing their patents. And their “commercialization” efforts led to the Bayh-Dole act and a lot more “technology transfer”. In industries where IP is relatively more important such as pharmaceuticals, patent licensing has become a major industry and has earned sometimes stunning amounts of money for the inventors and their employers. Small technology companies have come to see this as a viable business model in its own right. Trademark licensing is now a big and sophisticated global industry. Suffice it to say that a whole range of business processes have grown up to support making money on IP.

The 2 Kinds of IP Management Software

So, that’s how I divide the world of IP management software: it is either designed to support legal processes or it is built to enable business processes. This makes a lot of sense anyway because these processes are quite different. But, you might say, they both ultimately serve the same purposes and must be integrated in some way to be effective. This is absolutely true. It is impossible to imagine including IP considerations in the business decisions, strategies, and even business model of the organization without that having a direct and profound impact on the legal processes: which IP to obtain, what types, in what jurisdictions, how much, and so on.

However, I think it becomes clear that these decisions are precisely what the business processes of IP ought to support. Therefore, the managing IP is really just whatever the business does to make smart decisions about IP that support the organization’s key objectives and strategies. Said another way, managing IP is all about integratinge the legal processes of IP with your business strategies and objectives.

It turns out that although this is really a very simple concept, it is easier said than done. There are a number of things businesses do when they “manage” something that have historically been foreign to IP. Management requires a lot of visibility and control over the object of management. For instance, managers typically want to know things like: why do we need it, what will it cost, what has it earned (or will it earn), what business objectives does it support, who is using it and how, who else has some, and even, what it is worth? Questions like these are not easily answered by lawyers. They’ll be happy to give you their best guess of course, and they are used to doing it because so few companies can answer these questions for themselves, but it’s really not what they exist to do.

The 2 Kinds of IP Management Software Customers

From my experiences with Knowligent, organizations that are shopping for intellectual property management software generally fall into 2 categories. To determine which they are, when a customer contacts us I will always ask the following question before we even start the conversation: “Does your organization have internal patent attorneys, or do you rely on outside patent counsel?”

The reason I use this question is that almost universally the companies that have in-house patent attorneys are looking for software to support their legal processes. I don’t know exactly why, but it seems that when a company is conducting it’s own patent prosecution, this process seems to take center-stage and command the focus and attention of the organization. Or it may be the other way around. In any case I have found that companies doing their own patenting tend to think of it as primarily a legal process. There is no particular reason why these organizations don’t need to integrate it with their business decisions, but they generally don’t seem to think about it in that way.

In contrast, organizations that contact us who rely on outside patent counsel for their legal processes are almost always looking for software to better manage those processes from a business perspective, and to integrate it into their overall strategies and objectives. Sometimes they are focused on controlling or justifying the cost, and other times they are interested in increasing IP-related revenue, or (rarely) both. Whatever their goals, any organization that is outsourcing patent prosecution simply doesn’t need software for managing the minutia and legal details of IP. If they use outside counsel, it’s a safe bet they are looking for business IP management software.

It has been a consistent trend over the past decade or so for organizations to move the legal processes of patenting out to outside attorneys and agents. This may be because it has become so much more complex to obtain global IP protection, or it may be part of a larger trend toward outsourcing based on efficiencies. Either way, it means that fewer companies need legal IP management software, and more are ready to understand the value of business IP management software.

One note of caution: Most IP management software vendors will describe their offerings as containing both legal and business processes. To an extent this is true. Most IP management software contains some elements of both. However, in essence they all cater to one side or the other. If the offering is designed to support “docketing” (which is a common term for the legal processes), its other functionality will not be oriented to non-lawyers, and the reverse is also true.

In a future post I will present my own survey of the field of IP management software.

AddThis Social Bookmark Button

Video: Mark Johnson on The Innovator’s Guide To Growth

September 24th, 2008 Greg Daines Posted in Business, Disruptive Innovation, IP Management Software No Comments »

As promised, here is the first snippet of my interview of Mark Johnson, co-author of The Innovator’s Guide To Growth. Here he discusses briefly what led to the book, and what it is really for. Please to enjoy…


AddThis Social Bookmark Button

Do Customers Make You More or Less Innovative?

June 17th, 2008 Greg Daines Posted in Disruptive Innovation, IP Management Software, Open Innovation 3 Comments »

MIT SealThis spring I had the pleasure of lecturing at MIT in two different courses on innovation - both taught by the always fascinating Eric Von Hippel. The first was to a group of MBA students and Sloan Fellows at the MIT Sloan School of Management as part of a course entitled, “Innovation in the Internet Age: Emerging Trends“. The purpose of my lecture was to provide a real-world example of a company struggling to rapidly evolve an innovative web platform using as a case study, Knowligent’s IP Portfolio software for managing innovation and intellectual property.

In my session, I briefly recounted Knowligent’s experiences innovating a complex enterprise system and the way that customers essentially negotiate to introduce their ideas into the design of the product. Eric’s objective for bringing me in to lecture was to provide proof for his overarching thesis - which is essentially that a lot of innovation comes from end-users, and companies that embrace this reality are better off for it. Of course this is absolutely true, and Eric has become a sort of collector of cases and evidence in support of this “Open Innovation” idea. The students were very intellectually engaged and a lively discussion ensued over the basic issue of whether customer-driven ideas can be trusted to lead a company’s innovation in the right direction. It was typical of MIT - very probing, questioning, and spirited - and it was a lot of fun! A few things came out of the discussion and my subsequent pondering after that I feel are particularly interesting and useful…

1. Enterprise software is actually a pretty good example of an industry where innovation has been heavily user-driven. Many if not most business software companies originated out of home-grown IT projects within companies for from corporate “wish lists”. Even after a project has spun-out, the vendor tends to be dependent on a small group of corporate customers for at least the first few years of their development, and these customers can exercise enormous power over the development trajectory of the product.

2. However, although a majority of ideas for new features and capabilities originate with end-users, only a small subset tend to have broad appeal. That is, customers can quite easily produce a large volume of ideas for new functions mostly because they have so many jobs to do. But these features make for complex, and usually expensive, software. If the vendor isn’t vigilant in controlling the code base, this significantly restricts the appeal of the software and I think that this can be a very dangerous trap for a software company to fall into.

3. More importantly, it is arguable that these user-driven features aren’t really “innovation” at all. Just because a customer demands certain features doesn’t mean that they are innovating for you. Much of the time this is really just “invention” (as distinct from “innovation”), and often it isn’t even that. The danger is that companies may come to think that they are innovating because they are adding a lot of new “features” to their products.

4. Enterprise/business software seems at the moment also to be a good example of another interesting theory of innovation - namely Clayton Christensen’s idea of “Disruptive Innovation”. Disruption usually happens when new products are introduced that actually offer less of the kind of functionality traditionally demanded by the existing (and influential) customers. So, running counter to the urge to create customer-driven “bloat-ware” is an urge to create software that is actually less functional but which may be easier and cheaper to deliver and use and is frequently innovative in other dimensions. For examples, I point to Google Docs, 37 Signals, and Mint.com as just a few of my personal favorites demonstrating this kind of disruptive innovation in the world of software. In other words, the current tide of “innovation” in software seems to be moving in the opposite direction than the one that big and influential enterprise customers may want to go. As the theory predicts, over time these offerings will likely become ever more functional and ultimately displace their predecessors. It’s this changing of the dimension of innovation that makes disruptive innovation so powerful.

The question that comes out of all this is whether your biggest and most influential customers are likely to lead you in a direction that makes you more or less innovative. My own feeling and experience (from the world of management software) is that involving customers and end-users in driving your product design usually makes you more inventive but can make your products less innovative overall. It is probably true that this will be different in other sectors. However, at the very least this supports the idea that there is a need to carefully evaluate the direction your customer input is driving you and to distinguish between “inventiveness” and “innovation”.

AddThis Social Bookmark Button

Top 5 Ways To Fail With IP Management Software

June 9th, 2008 Greg Daines Posted in IP Management Software No Comments »

I have been working on a couple of software projects recently, and I have been reminded once again why IP management software implementations so often fail. So, I have come up with five (facetious) things any organization can do to doom its new IP management software to failure.

1. Hold-on to the past
Redesign your new IP management software until it works exactly like your old IP management software.

You need new software because the old has made it very difficult to do your job. It has become a problem in virtually everything you do. After literally years of struggling with it, you have finally built-up enough organizational will to go through the pain and expense of moving to a completely new platform. But, as we all know, change is difficult (see #4 below), and there is always a countervailing pull to return back to the familiar. There are always people who will oppose change, and the pressure to remake the new system in the image of the old one will quickly be overwhelming. Give-in to the urge, and start pressuring your vendor to “adapt” their system to your “needs”. This is the most effective way to make a project expensive and time-consuming. Most importantly, this is how you make really bad, bloated, and buggy software.

2. Delegate
If you want to end up with IP management software that can’t support your IP management, then don’t involve your IP managers.

Make sure that you assign the project to your lowest-level support staff. Remind everyone that these are the people that are directly responsible for most of what the software does anyway. Because these people have no real authority, they will never be able to consolidate the necessary resources (see #3 below), make essential changes to the organization’s management processes (see #4 below), or compel anyone to use the software (see #5 below).

3. Focus on the cost
IP management software should be viewed merely as another cost of doing business that must be aggressively contained.

Other major expenditures such as patent filing fees and management salaries are obviously investments which ultimately are expected to produce tremendous returns. In this light, make sure that you find the cheapest vendor, or if not, then make sure to bully the vendor you do select into subsidizing your implementation. Remind them that you are a very important customer and that, if they make you “happy”, their business will ignite with the white-hot fury of a thousand melting suns. Later, when you are shouting at them for “under-delivering” be sure to hang-up before they remind you that you paid them for only about a fifth of their actual effort. Although you have plenty of direct evidence that this is true, you must balance this with the fact that everyone knows software vendors are notorious scam-artists.

4. Don’t change a thing
Avoid making essential changes to your IP management practices and processes.

Obviously most of the benefits of your new software cannot be realized without matching changes in how you do things. Your IP management processes have to change, or they won’t be any better than before. (It reminds me of the TV ad where the people think that their life will change because they have new telephone service.) But once you start down that road it can lead to a lot of unsavory outcomes. It can even mean changing people’s assignments! Of course, this cannot and must not happen. Change must be something that occurs only in the abstract - in the “software” realm.

5. Don’t turn it on
Ultimately, the most effective thing you can do to prevent a successful implementation is to simply refuse to turn the new IP management software on.

The most common, and easiest to use, method for doing this is to tell the vendor that you are not “happy” with the software. If they get pushy and want to know why you are unhappy, or what they can do to resolve it, just tell them that the whole experience has been “bad” and that you don’t “like” it. Remember that most of the pain of moving to new IP management software is the change that it will cause (see #4 above) - the monetary cost is nothing compared to that. So, even if you have gone through all the trouble and expense of getting new software, rebuilding it to match your old system, and bullying your vendor into doing most of the work for free, remember that most of the pain comes after you “go-live”. Just don’t do it ;-)

AddThis Social Bookmark Button