IT Management

Today’s youth have a mind-boggling array of ways to communicate— social networking, Tweeting and SMSing simultaneously with other less important tasks such as driving. It’s fascinating to watch their abbreviated lingo—BRB (Be Right Back), TTYL (Talk To You Later), and, of course, the ever popular LOLWES (Laughing Out Loud While Eating Sushi). The acronyms make it so much easier to swap info about the critical moments of their lives. And easy is the point of acronyms—or is it?

Whether technical, scientific, academic or governmental, most industries develop a lexicon of their own. When overheard speaking their “language,” people from these industries sound as though they’re speaking “Greek” to the lay people around them. It may in fact make it easier to help associates of such industries communicate, and there are certainly other valid reasons to employ acronyms and lingo. But alas, in our beloved technology industry, the intent of acronyms in many cases is to complicate, not simplify.

1,624. That’s the number of acronyms found in the last issue of Mainframe Executive. And that’s not counting any of the ads. A simply staggering number to ask anyone to decipher; but we’re good at it—well-trained with years of speaking in TLAs (Three Letter Acronyms) and techno-speak.

The issue though is the gap that’s created when things are made more complicated than they need to be. In many cases, I see acronyms, abbreviations, and newly created words founded simply to give the appearance of complexity. Why? Because of a misperception developed in our industry that in order for a solution to be worthy of its desired price point, it must be complex, or heaven forbid, an “architecture.”

For example, Service-Oriented Architecture (SOA) is all the rage right now. And well it should be because of what it actually can do. But the term implies a level of complexity that needs to be explained. If we construct software that would easily and simply allow for the reuse and sharing of applications and data across multiple computers, wouldn’t that be incredibly valuable? All computers speaking the same language, in essence? That is, in fact, one of the premises of SOA. But no one understands that by the name. With an abundance of words just to digest and decode, many people never embrace what technology companies slave to deliver.

Imagine if someone proposed a Road Transport Architecture (RTA) to you, comprised of a design that combines computer electronics, steel, aluminum, and rubber components working with measured explosions. The RTA is built on decades of design and refinement, with layers of fault-tolerant systems to ensure efficient operation. Would you want it? Perhaps it would be better if we called it a car, and showed you that it can be used to move from place to place.

MIT professor and founder of the Simplicity Consortium at the MIT Media Lab, John Maeda, wrote The Laws of Simplicity. His book begins with the quote, “Technology has made our lives more full, yet at the same time we’ve become uncomfortably ‘full’.” Maeda’s book is dedicated to bringing the concepts of simplicity to product design across the landscape, and he states that simplicity itself is “bound to be a growth industry.” he also asks us to “imagine a world in which software companies simplified their programs every year by shipping with 10% fewer features at 10% higher cost due to the expense of simplification.” It may sound counterintuitive, but as The New York Times columnist David Pogue said in his 2008 presentation to the annual Technology, Entertainment, Design (TED) Conference, “Simplicity sells,” and he used Apple’s iPod as undeniable evidence.

Our industry as a whole must learn to posture technology differently. Users don’t want architecture. They want results. They want software to work, easily and simply. They want to use it, not have to be schooled in it. We need to change the way we talk about it, starting by speaking in plain language rather than abbreviated, contrived terms designed to imply creative complexity. Language has played a key role throughout history and it’s no different in our industry.

We need to make a stand. CxOs throughout the world are begging for less complexity. They want to run their businesses with what the technology community can provide, but we’re making it too difficult for them to grasp what we’re doing, simply by the terms we choose.

As Maeda concludes in his book, “Technology and life only become complex if you let it be so.”

This is a critical issue that we all we must strive to change. IMHO.

That Sums it up.