Category Archives: Technology

Technology Damnation 89: IP & Patents

Intellectual property and patents are a good thing, right? They protect your inventions and prevent your competitors from stealing your innovation and making money off of them, right? Wrong. That’s the theory, anyway, but the reality is considerably different. They don’t stop your competition from stealing your ideas and inventions, they only give you the right to go after your competitors in court for damages if they steal your inventions. And moreover, they make it easy for your competitors to duplicate your invention.

Remember, in order to patent an invention, you have to completely define the invention in enough detail for someone to easily reproduce it. (And it clarifies why many companies would like to keep as much as they can trade secret for as long as they can.) It’s like handing a car thief the keys to your brand new custom made Ferrari and asking him if he’d like a joyride.

But that’s not the worst part. Let’s say your competitor fully replicates your invention and starts selling it to your customers and making all the profit. Your only recourse is a lawsuit, and if your competitor is bigger than you, has deeper coffers, and more expensive lawyers, it’s going to be an expensive lawsuit. Even if you know you are in the right and there is a very good chance that you could recover legal fees in the award (after multiple appeals), you might not be able to afford the suit. In fact, even initiating a lawsuit might bankrupt you.

But this is far from the worst of it. The worst of it is that many companies file, or buy, patents not to protect their IP, but to prevent you from selling yours (and this has been going on for a decade as per SI’s classic post on how the patent pirates will plunder away. Since patent clerks are not experts in anything but the rules associated with filing patents, and the reviewers are typically not experts either, many patents that are much broader than they should be, and that actually patent innovations that exist in prior art as part, or all, of the invention, get pushed through by firms with big pockets and persistent lawyers. These patents are then used by companies, known as patent trolls, with no intention of actually developing or selling such products to go after companies with similar technology, like yours, for patent infringement, even if these technologies and companies are not actually infringing the patent. The idea is that, since you know how much a patent lawsuit will cost, you’ll simply cave and pay a small license fee to “license” the patent you are not already using. These patent trolls know that all they have to do to bring you to court (in Marshall, Texas) is make a reasonable sounding (not reasonably effective) case to a non-technical judge who will allow them to bring you before a jury. Now, it is true that the US is finally trying to put a stop to these trolls (who make the nasty trolls who live under bridges look like oversized benevolent gnomes) with a a new bill (S. 1137) that requires that trolls not only stipulate what patents are being infringed, but precisely how, before a case can be filed (and prevent filing of vague claims that are enough to get you on a Texas or Delaware docket on-demand) (and also requires that all claimants be listed and expensive discovery delayed until prosecution has progressed). It’s a good start, and will minimize the tens of billions of dollars of damage these trolls do every year (as these trolls do over 1 Billion in damage to the economy every two weeks as summarized in this post on how the US is still letting the patent pirates plunder away), but you know that, since the bill already passed the US Senate Judiciary Committee, the patent trolls already have their legal team looking for loopholes to use against you.

The reality is that the US is just not as smart as the EU Parliament, which quashed the Computer Implemented Inventions Directive 648 to 14 when it was introduced (and a significant portion of bullsh!t patents these days are computer related), and, for a big enough payday, the patent lawyers will become more and more creative and manipulative. Since the US allows business process patents (which, in the doctor‘s view, is a bullsh!t patent), this insanity is here to stay. So, you’re damned and you have to play the damnation game (and spend tens, if not hundreds, of thousands filing your own bullsh!t patent just to prepare a defense against the bullsh!t claims you know are coming if you get big, or threatening, enough).

Twenty Years Ago Today

The Boeing 777 entered service as the world’s largest twinjet. This particular twinjet had a number of different variants, including the 777 Freighter which was an all-cargo version that had a payload of 103,000 kg (226,000 lbs) and a range of 9,070 km at maximum payload.

While not the capacity of the 747 200F which could handle a MTOW of 378,000 kg, which had a range of about 8,000 kms at full payload, the improved operating economics not only offered new options for long-range, lower-cost air freight.

It was yet another advance in the long line of aircraft advancements leading up to the recent 787 Dreamliner which, despite being a prime example of a supply chain fiasco as chronicled in Supply Chain Digest’s “The Boeing 787 Dreamliner: A tale of TERRIBLE supply chain management”, is still a technological innovation.

M&A: Confusion or Clarity?

There’s been a lot of M&A in the past few years, with companies like SciQuest, Selectica, Xchanging, etc. gobbling up a number of smaller companies with offerings that the acquirer believes could be used to make a full S2S (Source to Settle) suite, and with the recent investment announcements, including this week’s announcement of an 80M investment in Coupa (at a 1 Billion valuation, which the doctor still finds unbelievable), there is sure to be a return to the M&A frenzy of the late noughts that will likely equal, if not exceed, the scale (and occasional absurdity) of the APE Circus. (Which I hope will be accompanied by a return of the Sourcing Maniacs, but alas, the doctor has not heard from them since they told us they were on their way back from their African vacation on New Year’s day five years ago.)

But will it be worth it? First of all, many acquisitions end up being overvalued. (For example, the doctor believes CombineNet is still far in the red, and this can’t be helping SciQuest.) Secondly, many acquisitions have overlap in functionality and offering. Thirdly, many acquirees often use different platforms. Right now, .NET, true C++, Java, and Ruby on Rail frameworks are all quite likely in the space and many acquisition frenzies result in a the merged company having three or more platforms to deal with.

Since, for example, a Source to Pay offering is only valuable if there is more integration than a company could achieve on its own by acquiring separate sourcing and procurement, and, if necessary, contract management and spend analysis platforms, this last point presents a major headache for the newly merged companies. Simply defining the push-pull endpoints and automating the data transfer doesn’t add that much value. A third party integrator can do that. Value comes from real-time end-to-end visibility through the source to pay process for every invoice, shipment, purchase order, contract, supplier, etc.

And the functionality overlap presents another hurdle. Each customer that uses a platform will expect all of the functionality of that platform, so you can’t even consider killing a platform component until all of the functionality is in another platform component. Not only will this take development time and effort while the organization has to support two platforms, but considerable time will be required as bruised egos try to decide which is best to keep and which to discard if both “endpoint” modules appear to be equally valuable.

And then there is the balance of how far to take integration in the short term when sales are rapidly needed to justify the expenditure, pay for the overhead loss as reorganizations occur, and support new personnel to plan development of the next version which will, someday, integrate everything on one underlying stack.

Sometimes it’s quicker, easier, and more cost effective to be patient, just build everything in house from the ground up, and go to market with a truly integrated solution which offers end-to-end visibility because it takes top talent to pull off a successful technology integration. And, by definition, not every company will have top talent with enough expertise across the source-to-pay process to make the right decisions.

the doctor is sure there will be some great success stories in a few years, but there will also be some mega failures as well. And in the interim, we’ll likely have more confusion than clarity.

Any differing opinions?

Technological Damnation 84: Dashboards

This is another damnation that should not be unexpected, as the doctor has been proclaiming the dangers and dysfunctions of dashboards since 2007. As per the doctor‘s classic post, a dashboard CAN NOT tell you how well you’re doing. It does not, and can not, know everything your organization is not doing well or how much the lack of efficiency is impacting overall organizational performance. As a result, it can not report on this ever important metric.

As the doctor said in his classic post, the best [a dashboard] can do is capture the data it’s been programmed to capture, roll-up the metrics it’s been programmed to roll up, and do the built in calculations of efficiency based on those roll-ups. Whatever went undefined goes undefined and stays undefined. The best that a dashboard can do is provide an upper bound on how well you’re doing — and this is useless. In particular, a dashboard that says you’re warehouse efficiency is 98% when it is only 92% is useless as it is totally unactionable. (the doctor can tell you that your efficiency is at most 100%, always be correct, and he doesn’t need an overpriced software hack to tell you that!)

And it’s not just the doctor who has this view. About five (5) years ago, Robert D. Austin, author of Measuring and Managing Performance in Organizations, penned an article in Intelligent Enterprise on how “metrics can lead [us] in the wrong direction” which echoed many of the doctor‘s concerns. Mr. Austin states:

Kaplan and Norton’s cockpit analogy would be accurate if it included a multitude of tiny gremlins controlling wing flaps, fuel flow, and so on of a plane being buffeted by winds and generally struggling against nature, but with the gremlins always controlling information flow back to the cockpit instruments, for fear that the pilot might find gremlin replacements. It would not be surprising if airplanes guided this way occasionally flew into mountains when they seemed to be progressing smoothly toward their destinations.

It’s as the doctor said. Not only will your staff be lulled into a false sense of security when all of the gages in the dashboard are in the “safe” zone (and not look for the faulty wiring about to spark a devastating explosion), but, and this is especially true if their compensation is based on those numbers, they’ll start to perform dysfunctionally if such behaviour improves the score. For example, many call centres once thought (and some still do) that number of calls processed was a good metric. The result? The reps, who do their best to get you off the phone as soon as possible, don’t take the time to understand the true nature of your problem and instead focus on a “quick fix” to get you going again (even if such a fix, like “reboot”, doesn’t fix the issue and will only result in the problem re-occurring again and again). As a result, not only did the number of calls processed a day increase, but the total number of calls processed by the organization increased, because people have to call multiple times to get their problem solved. Not good. Not good at all.

And while an integrated view is necessary, the doctor was right when he said that integrated dashboards are deadly. Common issues are inconsistent views, propagated errors, and the overconfidence they instill. Despite the fact that they always increase risk, dashboards do not always improve visibility. Unlike a top-of-the-line spend/data analysis tool, dashboards do not give you real intelligence. You should ditch the dashboards before they are your downfall.

Technological Damnation 83: Spreadsheets

Spreadsheets. You can’t run your business off of them. But you still can’t run your business without them. Despite the fact that it’s 2015, and that better, customized, back-office systems exist for every facet of your business, most business still run at least one key aspect of their business on spreadsheets.

This is, literally, the only technology worse to run your business, and supply chain, on than the ERP (which, as we pointed out in a recent post, is a supply chain disaster waiting to happen. Do you have to remind you again that Spreadsheets Will Cost You Billions? That Fidelity lost 2.6 Billion due to a simple spreadsheet error? That 1.13 Billion in Fannie Mae Shareholder Equity went out the window due to an honest spreadsheet mistake?

And do we need to remind you that trying to run a business off of spreadsheets is fraught with peril and could result in your organization tossing 20 Million into the trash on an annual basis? That your new support centre could be woefully understaffed upon switchover? That unavoidable delays will result in your projects as a result of spreadsheet gaps?

You know spreadsheets are a damnation because they still exist, five years after the Harvard Business Review told us why good spreadsheets make bad strategies. There’s just no such thing as good spreedsheets. All spreadsheets of any level of complexity contain errors. The most recent statistic, as reported in Forbes last year in Sorry, Your Spreadsheet Has Errors, 88% contain errors (and the vast majority are human. But what can one expect when one in one hundred keystrokes is erroneous?) And so will 88%+ of spreadsheets going forward as forecasts, models, and financial statements just keep getting more complex.

As long as they exist, spreadsheets will be an eternal damnation that might just burn your business to the ground if the sea of red isn’t detected, due to a human error, until it is too late. If it’s the last thing you do, get rid of them.