Getting Clueful: Nine Things CIOs Should Know About Computer Consulting and Contracting

The hired guns of IT explain (in gory detail) the mistakes that enterprise IT managers make, and how to get the most out of the consulting budget.

Consultants and contractors can provide specialized technical or business expertise, additional bodies to help lift an IT project's immense weight or—at worst—another bucket to bail water out of a sinking ship. However, most CIOs and IT managers have horror stories about consultants gone bad: consultants who didn't deliver what they promised on time, gave bad advice, fought with (or fraternized with) the full-time employees. Usually, these problems result from a lack of understanding between the two parties and their divergent business interests. Surely, someone has advice to share about how to get the most out of consultants and contractors?

Settle down and get comfortable, as you're about to get a load of very frank feedback. In several online forums, asked these IT service providers what one thing they wished IT managers understood about consulting and contracting. This article presents their most fervent desires, including technology ramp time, project scope and long-term project planning.

In this article, I sometimes use the terms "consultant" and "contractor" interchangeably. Many practitioners make a distinction, however. Generally, a contractor is someone hired on a short-term basis (such as three months or to finish the Web forms) and works on a very specific project. Consultants often have more latitude, examining and enhancing systems or processes rather than an individual application. They're also paid differently. Contractors are billed by the hour. Consultants submit invoices per project.

1. Be aware of—and honest about—the reasons you're bringing someone in.

Many managers imagine that their motivation in calling a consultant is purely technical: The application is broken, the server is hiccupping, the project is late. Savvy managers—and experienced consultants—know better.

"Almost every problem that I've been asked to solve has, at the core, been a people problem, not a technology problem," says David Moskowitz, principal consultant at Productivity Solutions in Bala Cynwyd, Pa. "Even if the immediate symptom appears to be a technology problem, someone made the decision to adopt, purchase, code/implement, create the schedule, include (or exclude) a requirement, include the wrong stakeholders, exclude the right stakeholders, didn't consult the stakeholders, etc."

And that's how conflicts between IT managers and consultants arise: The CIO or IT manager thinks the problem at hand is technical, and so hires consultants to solve a technology problem. But when the issue is one of personalities and politics, a consultant can't do much about it. The consultant's business is service, so he wants to help (and to make some money); he does his best, but really can't solve the core problem. Six months later, the problem hasn't gone away and the IT manager has much less money in the budget. Tensions flare.

IT service providers advise IT leaders to get clear on the problem at hand, why they're bringing in consultants, and what kind of consultants they need. Independent consultant David Cressey says CIOs must understand the difference between seeking a contractor or consultant for staff augmentation versus adding expertise that isn't part of the company's core knowledge set.

There are legitimate reasons for both endeavors. But, cautions Cressey, the two situations affect the way you vet the agency and the individual consultant, the terms and conditions you should seek, and the amount you should expect to pay. "If you don't know which you are doing, you are likely to either pay too much, or hire a person or an agency that just isn't up to meeting your needs," he says.

2. Few consultants generate wisdom the first day.

Your company probably has an orientation process for new employees. They're added to the All_Developers e-mail distribution; they're introduced to people in other departments whom they might need to rely upon, and so on. But many enterprise IT departments drop a contractor into the office with no orientation whatsoever—either in assigning-a-desk logistics or in technology ramp time. Yet, management expects the consultant to offer brilliant suggestions on the first day, even though she's had no introduction to the IT organization's specific challenges or to the company's broader business goals.

Consultant Brian Marick says it's impossible to hit the ground running when no one has planned for your arrival. "The first half day or more of my week at their company is spent discovering that there's no meeting room for an introductory session, no place to pair, a key person is out for a dentist appointment, no one's downloaded tools yet, etc.... I'm not the only person whose time is being wasted," he says.

Clients need to organize an onboarding process for consultants that's similar to the experience for new employees. Management consultant John Lowe says, "I cannot make an effective contribution in a vacuum.... I need to get up to speed somehow on complex issues. I need data and inputs. Brief me. Dump data. Send me files. I don't care how. Just recognize that the beginning [of the engagement] will be a learning phase. Pushing for solutions before I understand [the problem] just leads to mistakes."

Let's repeat that: Few consultants generate wisdom the first day.

Companies have unrealistic expectations of consultants because of a common myth, says Gloria Willadsen, a freelance UNIX and Linux applications developer. Since the consultant is an expert, the client believes she therefore does not have to do any research; she can just walk through the door, sit down, and implement the very specialized solution the company needs, says Willadsen. But, she points out, "A consultant always needs time to assess the problems and test the various solutions."

When you brief a new consultant, include the big picture. Consultants believe they can do a better job for their clients when they are given insight into the purpose of the IT project as a business driver. Willadsen says many businesses believe that consultants have keyhole vision into the project, and can therefore only work on very specific, narrowly scoped tasks. This is not only false, she adds, but also leads to a self-fulfilling prophecy. "If you choose not to expose your consultant to the entire business model and all of its problems and intricacy, you debilitate your consultant and prevent them from making the best design and development decisions," she says.

In contrast, the more transparent you are about your business with your consultant, the better able she'll be to create more reusable, more versatile code, and the better equipped she'll be to contribute to the creative process of helping your business model flourish, says Willadsen. "The more information the consultants have about your field, the easier it is for them to draw on their experience with tried and tested parallels in other fields. This will save you time and money on testing and prototype phase development and get you a better solution faster."

3. If you hire a subject matter expert, pay attention to her advice.

Managers who don't understand basic technologies are a nightmare for consultants to work with because they can't articulate the problem that needs to be solved or the work that needs to be done. Everyone is best served when the IT manager has a teensy-weensy idea about the subject the consultant is hired to address.

Ignorance costs money, says Bob Reselman, an application architect and test-driven development evangelist in Los Angeles. He's seen it firsthand. Reselman worked for a manager at a client company that believed that a significant, highly customized subsystem of its customer relationship management (CRM) system could be upgraded for $10,000 by purchasing an off-the-shelf package. In reality, says Reselman, even if the client could identify a package, the client would incur additional costs for integration and subsequent testing. "What seemed to be a simple $10,000 expense turns out to be much more. The C just didn't know enough to understand the true costs involved," says Reselman.

If you don't know the knowledge domain, consultants urge, don't try to insist on the right way to solve a problem, shove a solution down the specialist's throat or decide how long the project should take. Don't make pronouncements and estimations based on what may be very optimistic—or uneducated—assumptions. They'll only come back to haunt you.

Another problem with technology-ignorant managers is that they are more likely to pull in consultants to do something that could be accomplished by someone already on the staff, says Der.Hans, an independent consultant who specializes in UNIX and free software system administration and development. And that's a waste of money.

4. Think about tomorrow.

It may surprise you to realize that the people you bring in for short-term help give a great deal of attention to benefiting your company over the long run. They're not all just in it (solely) for the money.

Before you turn to consulting as a solution, make sure that the external skills you're acquiring benefit your company in the long run. George Dinwiddie, a solo consultant and coach with 20 years of experience in professional software development, owns iDIA Computing. He points out that a company's long-term success is more likely to result from investing in its own capabilities, and any business that primarily depends on external help for core development functions will be left begging when times are hard.

"By all means, bring in outside contractors and consultants to help where needed, but bring them into your organization in such a way that your employees learn from them," says Dinwiddie. "Those you bring in should not only increase your capacity while they're there, but leave behind an increased capacity after they've gone."

If you want the consultant's solution to continue to benefit the enterprise long after the engagement is over, establish better lines of communication between departments. Lack of enterprise-wide standards and planning is the key irritation for Ish Singh, a systems architect and integration consultant who provides IT strategy and enterprise application integration (EAI) advisory services. He explains, "I have seen many organizations start multiple projects side by side without any interaction or knowledge sharing among the project teams and without implementing any common or enterprise-wide standards. In almost all cases, this results in duplication of effort and inefficient systems that are harder to maintain and do not work with each other."

5. Scope creep is sometimes unavoidable.

Managers bring in a consultant when they want the specialist's expertise in defining, implementing or fixing a project. Usually, the manager has a fixed idea of the nature of the solution (i.e., the software requirements, as expressed in the contract's "statement of work") and the project plan (i.e., budget and time). Often, consultants feel that managers don't have the right idea about application scope, project length and the mutability of software requirements—and that's a recipe for conflict. The consultant, as subject matter expert, may identify real problems, but managers (who have an innate distrust of anyone who has additional services to sell) can be tied too closely to the original project plan.

Also see: Five Things IT Managers Should Know About Software Requirements

Statements of work are necessary elements, particularly in project definition and negotiation. However, points out Terrence Gargiulo, president of, statements of work should be treated as living, breathing, evolving documents that reflect a collaborative relationship between the consultant and client. Otherwise, he cautions, "Projects can too easily turn into an 'us versus them' dynamic in which no one wins."

Scope creep is sometimes unavoidable. For example, search engine optimization (SEO) efforts are dogged by constantly changing search engine algorithms, competitor behavior or unethical trickery—things that can change the initial assumptions about the project, explains SEO specialist Ash Nallawalla. However, part of the consultant's expertise should be in estimating the time necessary to resolve the situation once it's identified. "Don't accept delays without full explanations," suggests Nallawalla, and remember that some delays are the fault of neither party.

6. Be clear about expectations—in the contract and in person.

Good contracts prevent disagreements and hard feelings. When a contract clearly lays out what happens in a given situation, there are no disputes. (Hard feelings, maybe, but no disagreements.) Contract problems ensue when the paperwork doesn't address an issue—and then each party has to define the best option (for himself) under stress.

Consultant Jeremy Singer says parties to a contract need to be clear about their expectations, and they need to deliver on those expectations. According to Singer, the contract should define the expected working conditions (e.g., number of hours expected, on or off site, materials to be provided, deadlines), the expected products of the engagement (e.g., specs, programs to do something, advice, encouragement) and payment (When does the consultant bill? How does the consultant bill? How soon is the consultant paid?).

1 2 Page 1
Page 1 of 2
Download CIO's Roadmap Report: Data and analytics at scale