Category Archives: Technology

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.

Infinite Scroll

Infinite scroll, I just can’t abide.
Infinity is hard to comprehend.
You wouldn’t hear my screams,
Even in your wildest dreams.

Suffocation as I scroll the page.
Scared to load the next site
In case the scroll begins again.
Content changing, it will not fix.
Ever flashing, nightmare’s Styx.
Online haze, when will it end?
And will I transcend?

Restless browse, the mind’s in turmoil!
One nightmare ends another fertile.
Getting to me, too drained to surf.
But scared to leave now, too immersed.

Now that it has reached new heights,
I do not like the restless nights.
It makes me wonder, it makes me think,
How’d we get to this? We’re on the brink!
We should be scared of what’s beyond.
Someday our brains might not respond.
We had an interest almost craving,
but do we want to get too far in?

It can’t be all coincidence!
Too many things are evident.
You tell me you’re an unbeliever.
Technophobic? Well me I’m neither!
But wouldn’t you like to know the truth,
Of what’s beyond, to have the proof!
And find out just where we’re heading’?
Techtopia? Or to Armageddon?

Help me, help me to find
the true path without seeing the future.
Save us, oh save us from
torturing ourselves, unnecessarily.

There’s got to be
More to it than this.
Or tell me why the web exists?
I’d like to think that we evolved,
and our sins have been absolved,
as technology resolved,
limitations of the past
and evolved to the point where it can be grasped!

With many, many apologies to Harris.

And, in case it isn’t totally obvious, the doctor, who has already asked what idiots brought back infinite scrolling websites, would really like to see those idiots tarred and feathered. (If they can bring back infinite scroll, which is where we started back when all we had was HTML 1.0, then we can bring back tar and feathering!)

Happy 20th, Java!

That’s right, 20 yeas ago today the first version of the Java programming language was released, and the web was changed forever. (And with the exception of James Gosling, Mike Sheridan, Patrick Naughton, and their development team who worked on Oak [which was the beginning of the Java language project] between 1991 and 1995, the doctor becomes one of the few individuals who can honestly claim 20 years experience in Java and the Java platform — as he downloaded it in May, 1995 and was teaching it in Data Structures and Comparative Languages courses as far back as June, 1995.)

It might be hard to fathom that Java didn’t exist 20 years ago considering that the vast majority of desktops run Java, that it’s been the top rated development language (on the Tiobe index, for e.g.) for most of its existence, and that many enterprise systems (including many supply chain systems) run on Java, but it didn’t.

So while you’re having your cup of Java today, think about this and wish Java a happy birthday. Especially considering that it’s ancient in internet years and still going strong!

The First Four Questions to Ask During Any Mega-Acquisition

A recent guest post over on Spend Matters on “Four Questions to Ask … During Any Mega-Acquisition” was really good. These are becoming all too common and each and every one impacts your organization, often in negative ways.

But the post could have been better. More specifically, the questions could have been more direct.

To make sure that you understand the very important intent behind each of the four questions, SI is going to rephrase them in such a way that there will be no confusion.

1. How will we get screwed over on price?

Every acquisition brings with it the promise of economy of scale and lower price, but it typically takes years to understand overlap, redefine responsibilities and organizational boundaries, and identify staff reductions. And since, in the interim, change management experts, process consultants, and other resources need to be brought on board, overhead goes up and costs go up accordingly.

2. How will we get screwed over on quality of service?

The biggest fish in the combined company gets the best resources. And just because your current organization was a big fish in the old company, that does not mean your company will be a big fish in the merged company. Your company might just be a medium sized fish that gets the “B” Team, if it is lucky.

3. How will we get screwed out of innovation?

Will the merged company continue to develop the platform our company is on or will we remain locked in to a multi-year deal as the technology we bought withers and dies?

4. How will we get screwed in new and interesting ways?

What additional layers of complexity and confusion will the new, combined, legal team try to weasel into the contract and how will that bite your organization in its backside down the road?

Sometimes acquisitions are good, but mega-acquisitions often bring mega-problems and, at least in the short term, don’t’ end up being good for anyone.