Big Data. Big Decisions
InformationWeek
Special Coverage Series


4 Misconceptions About Managing Techies

From emotional style to project management style, techies have their own way of doing things. As an IT leader, you'd better understand common myths.

As important as it is for CIOs to treat all team members the same, there's no denying that IT professionals command a different set of leadership strategies.

"The reality is tech support people, engineers, and developers have more in common with each other than they do with anyone else," said Paul Glen, an IT management consultant and author of Leading Geeks: How to Manage and Lead People who Deliver Technology. "We see the world somewhat differently and we, as groups, interact differently."

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Such differences create challenges for software companies and auto manufacturers alike. According to Glen, 92% of technology professionals work for traditional, non-technical corporations and only 8% work in high-tech firms.

So how can senior-level executives effectively lead and manage IT professionals? The first hurdle, Glen said, is overcoming some common misconceptions about techies, their work style, and how to manage them properly.

Misconception #1: Techies approach projects the same way as everyone else.
Not so, according to Glen. "It really boils down to the fact that we actually see the world in fundamentally different ways," he said. "For geeks, work is about solving problems; that is the nature of our work. If we don't have a problem in front of us, we really don't know what to do. For non-geeks, they see the world much more about achieving a vision and what they want to accomplish." As a result, Glen said techies require "a very organized structure" with strict "rules of logics and proofs" to begin a project and see it through to its proper conclusion.

[ Your best and brightest are always at risk of jumping ship. Learn How To Keep Your Best Talent. ]

Misconception #2: Techies are simply being evasive when they refuse to commit to a timeline.
While non-techies are known for fudging the truth now and then about project costs and deliverables, Glen said techies see such haziness as outright lying and "a serious offense," especially when it comes to committing to an exact budget or product development timeline. "Geeks are constantly being pushed for a date and often they just say, 'Well, I don't know when it will be done.' Leaders have to recognize that businesspeople and technical people have very different definitions of lying."

For example, Glen said while a CIO might just "be asking for a target, geeks feel as if they're being asked for an absolute answer." As a result, he said, "leaders experience geeks as being evasive, non-committal, and unmotivated because they refuse to give them answers." However, by "being explicit" about simply desiring an estimate, Glen said leaders stand a much better chance of getting answers out of their truth-bearing techies.

Misconception #3: High-tech jargon makes techies poor communicators.
Despite being known for using "a certain amount of jargon," Glen said the communication breakdown between leaders and techies extends far beyond obscure acronyms. "It is a much deeper problem than not speaking the same language; it's not about specific words," said Glen. Instead, he said, "for geeks, language is all about transmitting information. For non-geeks, language is much more indefinite and ambiguous. It's much more about building relationships."

Because of these two distinct communication styles, Glen said techies and leaders alike have a tendency to "not understand what others are talking about and then just write them off." However, by "making allowances" for communication barriers, and "adjusting our understanding of how to present issues clearly to one another," Glen said techies can ensure they're being heard correctly.

Misconception #4: Techies rarely express emotion because they simply don't care.
IT leaders would be wise not to mistake techies' reserved disposition for apathy. Rather, Glen warned, "The cues that non-geeks look for in geeks, like enthusiasm or commitment, are subjective experiences. However, geeks work hard to avoid being subjective." At the same time, Glen said, techies need to learn that persuading IT leaders to rally behind a project takes more than cold, hard facts. A little bit of emotion-charged persuasion never hurt anyone.



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.