Travel contrasts

Travel is an interesting and complex industry, particularly when you contrast air and lodging. The various US flag air carriers offer a virtually indistinguishable service offering, and are all seemingly racing to the bottom. Most airline news seems to be about an additional fee being tacked onto the ticket, a service being stripped from the offering, or a passenger, security agent, or employee becoming enraged by the process and doing something uncouth. My favorite quip from a flight attendant nicely sums up the whole experience: “We’re here for your safety and not your comfort.”

Contrast that with hotels, where there are a variety of product offerings at different price points and with different and diverse services. Even medium-sized cities offer everything from a $30/night basic room, to suites with butler service and Tiffany crystal chandeliers. I’m a frequent consumer of both air and hotel services, and the latter always seem happy to work with me, from telephone agents, to high-quality websites, to the housekeeper that’s quick with a “good morning” and a smile. Contrast that with the airlines where even decent customer service is an exception, and front-line employees treat customers as an inconvenience rather than their raison d’être.

My brand of choice, Starwood Hotels, even called me earlier this month to award me with lifetime membership in their elite club (all for the somewhat dubious distinction of having spent approximately three years of the last ten in their hotels), which entailed several new benefits, without action or prompting on my part. When designing your customer interaction points and service offerings, do you have a variety of levels of interaction? Do you offer new and exciting products, some of which are completely unbidden by the customer? In short, are you there for your customers’ comfort and safety?

Failure = Innovation

A nice quote I heard from one of the other speakers last week was this:

Reward success, celebrate failure, and punish inaction

Successful innovation, whether it is designing a compelling new product, or completing a technical challenge that gets your product released on time requires failure. Too many organizations create a culture where failure is severely punished, such that a fear of failure leads to inaction rather than a bias towards success.

With ethical and moral failings that damage lives being the rare exception, failure is one more step on the road to success, and truly a necessary ingredient for innovation.

Cloud Computing Benefits, Risks, and Applications

Patrick Gray discusses the benefits and risks of cloud computing, as well as how cloud could be relevant to your company. The discussion is presented at an executive level, without resorting to technical or vendor-specific details, perfect for CxO’s and board members that need a quick briefing on how the cloud might impact their organization.

IT: Utility or strategic function?

I frequently hear the argument that IT is a “strategic” corporate function since it is critical to most modern businesses. Unplug the servers, or send all the data jockeyed by IT into that great recycle bin in the sky, and the company is hosed, say the advocates of this theory. The problem is that you could apply the same concept to electricity. It’s critical to the success of most organizations, and most parts of an organization simply cannot function or grow without it. Yet, how many companies invite their local electric company to strategic discussions, or thank them for literally splitting atoms safely and cost effectively? A critical system is not necessarily a strategic one.

Where I see IT going wrong is that we expect a “seat at the table” for successfully performing utility functions. What we need to be doing, is demonstrating business results through strategic IT projects, then we get the seat at the table.

By way of example, I’d consider a strategic project something like marketing automation that decreases lead conversion times by X%, or even a receivables management system that decreases AR by Y%. In either case, the system can be directly tied to a financial result.

Getting that elusive “seat at the table”

There’s long been talk in IT management circles about getting a seat at the table when corporate strategy discussions are happening. The thinking goes that technology is such a central function to most modern companies, that IT should have input into strategic decisions, and help guide their implementation almost as a birthright. However, for many there is a cart before the horse problem at work here. CIOs want a seat at the strategic table, but they don’t demonstrate any strategic value. The CEO wants to talk about entering new markets, and the CIO wants to talk about upgrading Windows or the nuances between the HAL 9000 version 1.98845 versus 1.987234.

There are two prerequisites to getting that “seat at the table”. 1) The utility aspect of IT needs to be flawless, and you need to stop talking about it. When was the last time you called the power company and thanked them for safely splitting atoms so you could turn on your light switch and have it just work? Same goes for the utility element of IT. It’s complex and completely thankless, get over it.

2) The CIO needs to understand the business deeply, and be able to articulate and frame the challenges and opportunities facing the business. He or she then needs to explain in layman’s terms how technology might accelerate these strategic imperatives.

Do these two well, and the CIO will be sought out for his or her opinion. Spend every board meeting looking for accolades because you implemented some fancy disaster recovery plan, or installed a new security package, and you’ll soon be shown the door.

Patrick Gray on Tech Talk with Craig Peterson

I was recently on the radio in the Boston market on the Tech Talk with Craig Peterson radio show discussing my book, the invasion of consumer technology in the enterprise, and where technology is headed in the coming years. You can download the podcast version of the radio show here, and look for my comments around the 8:45 mark.

Google, Apple, and the Permanent Beta

One of the most interesting features of Apple’s new iPhone 4GS is Siri, a voice-recognition “assistant” that is able to take colloquial spoken English commands. For example you can tell Siri to “book and appointment with John tomorrow” and “she” will check your calendar for available times. There are plenty of reviews of this feature, and that’s not the crux of this article. What is however is that Apple has introduced Siri as “beta” software: a product that the manufacturer believes is complete, but hasn’t been fully vetted and tested on a large scale.

This is nothing new in the technology world, and the preponderance of Google’s free online offerings also fall into this category despite widespread usage. Many other companies in the technology world generate consumer angst when they release what’s perceived as poorly-tested “beta” software to meet a release deadline, co-opting users as involuntary testers in the process and fixing the problems later, however they are usually selling what is billed as “complete” software rather than clearly denoting its beta status.

There’s no harm in a corporate setting to launching some “beta” initiatives, as long as the beta status is clearly spelled out to the user community, and not used as an excuse to release half-baked work for business-critical functions. No one has the resources to pursue every initiative to the fullest, but beta initiatives can test new technologies, or get you 60% of the way there on a problem that needed to be solved yesterday, bridging the gap to a more prefect solution. In short, if you’re not experimenting with a handful of beta initiatives, preferring to do everything “perfectly”, you are probably missing opportunities.

The Utility Aspect of IT

There will always be a utility aspect of IT, and in the corporate world, it’s a utility from the consumer’s perspective. No matter what accounting or organizational gyrations you go through, basic services like email, network connectivity, phones, etc., are going to be treated like electricity, water, or sewage: No one cares how complicated it is (when was the last time you thanked the power company for splitting atoms), and everyone wants it as cheaply as possible.

The mistake I see is trying to treat the utility and strategic aspects of IT as one and the same. The other mistake is trying to advance IT as a strategic partner, when you’re not running the utility side of the house flawlessly and cost-effectively.

The “alignment” problem

There’s an interesting debate on Linked In about why we’re still talking about IT “alignment” after doing so for nearly 30 years, and like many of these conversations, there are questions about what exactly “alignment” means in this context.

Some definitions have been offered, but in my mind, it’s rather simple: alignment is using IT as a tool to solve a business problem, not an end in itself.
While that’s conceptually simple, many IT organizations don’t do it well. Look at all the people saying “Cloud is our technology strategy”. It’s like hiring an expensive builder to make you a custom home, who keeps saying “The Makita Sawzall 9000 is my strategy to give you a great home”. The focus is on the tool, not the outcome or value provided.

The IT departments that are seemingly naturally aligned are the ones where all the technology happens behind the scenes, and the CIO is called in to help solve a business problem. If your C-level peers run away when they see you approach, or start snoring in your meetings, you’re probably focusing on the tools rather than outcomes.

Corporate Narcissism

Netflix, a US company that started life as a DVD-by-mail rental service, then added digital movie streaming to its offering recently announced a poorly-received corporate restructuring. In addition to a price increase for the mail and streaming services, the company split the offering into not only two products, but two separate companies with their own billing, recommendation, and customer account systems. Whereas a customer could formerly login to the Netflix website and manage a queue of movies for mailing or streaming, the split would create two different, non-integrated places for customers to do the same tasks, and even charge two separate items to a customer’s credit card each month, a move akin to a restaurant forcing you to go into a different room, with a different waiter, and pay a separate bill for your appetizer and entrée.

Historically, the company has often been regarded as consumer-friendly, and technologically advanced, so the move legitimately offended a highly vocal group of customers. The CEO of the company offered a non-apology, and attempted to convince customers that splitting their service, creating more administrative hassle, and effectively increasing the price for less convenience were in their favor.

These types of maneuvers can best be described as a kind of corporate narcissism, where companies focus internally and treat customers as an inconvenience, rather than the reason they are in existence. The US-based airlines have been guilty of this for years, with flight attendants literally rolling their eyes while dealing with customers as if the flight was scheduled for the airline staff’s personal amusement, and then those pesky paying customers rained on the party.

This narcissism can also occur internally, with corporate divisions passing inane policies and procedures that scratch some parochial itch, while inflicting hours of extra administrative burden on the larger organization.

While the customer (external or internal) is not always right, they are almost always the ones that provide the financial lifeblood of your company. When you consider some elaborate strategic shift and there is nary a mention of how it will impact paying customers, make sure you’re not preening in front of the mirror while the building around you burns down.

Follow

Get every new post delivered to your Inbox.

Join 303 other followers