Signs of an IT Uprising?

2

In a previous post, I described the ever-elusive goal of achieving alignment between Business and IT. On the one hand, we see some struggle between these groups, and on the other hand, we see that the lines between Business and IT are increasingly blurred. In fact, my conversations with CIOs and senior executive IT professionals also unearthed interesting strategies to address the colliding worlds of Business and IT.

There is a trend toward staffing IT departments with non-technical employees or “hybrids” (e.g., MBAs with some tech background). More and more, the pervasive thought of CIOs seems to be “I can teach the technology. But getting staff who understand business drivers and speak the same language as the business side of the house is harder to come by.”

One executive actually put it to the test. His team was responsible for technical requirements and for interfacing with the various business units within his organization. For multiple projects, he assigned two different types from his team (one IT and one MBA/business-oriented) to meet with the same business unit head.

This executive said that, invariably, his tech representatives would default to technical jargon in meetings with the business heads. By contrast, the business-oriented professionals were less sophisticated about the technology, but were successful in communicating with the business heads. The business guys glazed over when “Tech-ese” is being spoken. The result? The exec pulled the IT guys from those projects and has actively sought to staff his team with that rare, but highly-sought-after creature – MBAs with some background in technology.

For a more traditional approach – one CIO told me that his organization spends a lot of time training his IT team to think in terms of how they can further their organization’s business objectives.

This emphasis on the importance of being able to speak the language of business is understandable. However, I wonder about the flip side. If technology can be taught to MBAs, is business acumen somehow inherently out-of-reach for technologists? Of course that can’t be universally true. But the conventional wisdom seems to be that it is more difficult to get technologists to think like the business side. You can teach some of the business-speak, but ultimately, technologists fall back into the jargon where they are most comfortable.

So if you’re replacing the technologists with those hybrid business types, isn’t it logical to expect an IT backlash? I mean someone has to get down and dirty with the technology to make it all work. At some point more than a cursory knowledge is required, and no amount of business savvy can replace that.

If not outright replaced, what of the resentments of having business acumen prized over technology abilities? Perhaps it plays out that the technologists are there, but they are led by those trained in business. In my experience, technologists – the same as any group of specialized professionals – are resentful when their direct managers have little knowledge of the field in which they work.

Are we at an impasse? Is IT motivated to adapt to the business or die? Or, is this just a trend of the moment, and yet another point as to why IT and Business will remain separate and distinct – destined to continue a symbiotic, yet slightly dysfunctional relationship.

I’m keenly interested to hear the voice of technologists here. Is this a trend you recognize in your day-to-day world or is this a non-issue? Is the point about IT being out of touch with business overstated? What say you?

Share

About Author

Ericka Wilcher

Sr. Marketing Specialist

Ericka Wilcher is a Senior Marketing Specialist at SAS, specializing in developing and executing innovative marketing campaigns for brand awareness and lead generation. Ericka specializes in digital strategies for advertising, content creation and syndication, and interactive promotional technologies. Follow @ErickaWilcher on Twitter for more!

2 Comments

  1. Hello Ericka,
    Wow - that's another great article. Thank you.
    I have been focused on building a language for the Business and IT community to come together for the past seven years (since 2001 when I was the corporate planner and VP of e-business development at a $4 billion dollar insurance company).
    Fortunately, it turns out that Michael E. Porter provided the needed ideas to bring the Business & IT organizations together in his classic book "Competitive Advantage," which could have been titled: "A Structured Approach to Corporate & Business Unit Planning for Competitive Advantage and for Providing IT With Needed Business Input."
    Using Porter's ideas and seven years of research and development, we ( eCompetitors Inc) provide an informational web service that describes the top 10,000 global industries using Porter's five forces industry analysis framework for each industry. The average Global 1,000 company competes in approximately 52 lines of business. Significantly, a CIO and the IT team armed with the list of their corporate businesses and a Porter-style industry analysis for each is knowledgeable enough to speak the business language. Using the common framework for each industry makes it easier and faster to learn new businesses, the same way it's easier and faster to do another IT project using the same IT framework (such as Microsoft's .NET framework).
    Cheers,
    Alan S. Michaels
    President, eCompetitors Inc.

  2. David Colbourn on

    An IT backlash has a connotation of dichotomy that is counter productive. The observation that business types conversent in technologiy are replacing technologists is valid. The IT staff traditionally provides the use of best practices and industry standards from a technologiy perspective but that is of decreasing value as CPU speeds increases and memory cost falls.
    That said there is a big quality difference between making it all work and doing it right. The key is that this trend you mentioned favors short term ROI views of IT projects rather then long term growth and sustainability. This approach increases the reliance on prototypes lacking; security, documentation, scalability, supportability, back up and recovery. By limiting project scope to the business need at hand we jepordizes data quality interoperability leveraging of systems and long term maintainability. It is a classic short term vs long term approach to ROI.
    It is a lot like dieting in that trimming fat is good but building muscle is better. I once heard it said that quality doesn’t really cost anything extra it is the lack of quality that cost.

Back to Top