White Paper

Keys to a highly-efficient IT department

How to turn IT from a cost center into a business driver. Six habits high-performing IT teams build, six time-wasting practices worth cutting, and the reasoning behind each one, drawn from IT leaders who've made the shift.

Introduction

IT departments are evolving. In the past, IT was typically viewed as a back-office function that supported the business. Its main responsibility: Keeping the lights on. That's changing.

Gartner research captured the problem years ago, and it still rings true in many shops. Mark McDonald, then group vice president at Gartner Executive Programs, described IT's story as one "defined by IT's role as 'tender' of the IT garden of legacy applications, outsourced operations and limited value creation." In the same research, CIOs reported that their organizations realized only 43% of technology's potential.

That number needs to increase if organizations want to create value through technology. As technology plays a bigger role in every part of the business, modern IT departments must permanently shift their focus from maintenance to innovation. They must move quickly. They must drive the business forward.

We are witnessing the emergence of a new generation of CIOs, one that aims not so much to "run" IT as to ensure that the business achieves strategic value from the use of technology.

John Mahoney, VP and distinguished analyst at Gartner

The million-dollar question: How can IT departments shift out of the back-office role and into the role of technology driver? For most teams, the answer has two parts. It means adopting the practices that create high-performing IT departments, while abandoning the common tasks that traditionally hold IT back from its full potential.

This paper examines the issue from both angles: Do's and don'ts. The first section covers six practices IT departments must adopt. The second covers six practices they must abandon.

Do 01

Get on the same page

If IT and the business don't communicate constantly, IT cannot possibly drive the business.

The first step toward a high-performing IT department is communication. If the business and the IT department aren't on the same page, IT ends up building solutions for problems the business doesn't have, and missing the ones it does.

To ensure the IT department runs as efficiently as possible, they must be in lockstep with the business's goals and needs. If the department is not educated on the firm's strategy it will be impossible for them to efficiently deliver solutions.

Jed Pillion, Managing Director of IT at The Execu|Search Group

Proper communication goes beyond simply speaking with the business units. Often, the IT department and the business don't even use the same vocabulary.

The stakeholders and the developers must speak the same language. An "account" in one department is called a "liability" by another department, and an "obligation" in yet another department, while to the developers they're all "customers." If the developers understand the business environment using the same terms as the users, then conversations will be fruitful and multiply.

Steven Lowe, Founder and CEO of Innovator, LLC
Do 02

Adopt a startup mentality

Spend the minimum keeping the lights on. Pour the rest into what drives value.

The proper mindset is a critical, and difficult, component of a high-performing IT department. Many IT departments get caught up in the day-to-day routine and lose sight of the value-driving tasks. They keep themselves busy, yet ultimately unproductive. Others have developed such a convoluted mess of policies and red tape that getting anything accomplished is challenging at best.

Both cases require a fundamental shift in mindset. Modern IT departments must abandon the old "just keep the lights on" mentality and shift their focus to driving business value.

Approach everything with a startup mentality. Seek to answer the following two questions: What drives value and what keeps the lights on. I suggest adopting a minimum viable strategy for keeping the lights on. By satisfying the requirements without spending too much time, you make space to deliver value. Spend most of your time and effort on what really matters, what really drives value, what really makes a difference.

J Wolfgang Goerlich, VP of Consulting Services at VioPoint

What does this look like at successful companies? Forrester Research summed it up well: Small business startups don't build massive IT departments and big operations teams. They focus on the capabilities that truly differentiate them in the marketplace, hire experts in those capabilities, and source their more generic business capabilities from partners and technology service providers.

Do 03

Keep your focus in the right place

Start with the company's most pressing problems, then find technology to fix them. Never the reverse.

Minimize the cool factor. Many IT people want to invest in cool new tech. Be sure to buy technology that aligns with your company's needs and skills.

JJ DiGeronimo, technology executive, author, and STEM advocate

In the technology field, you're constantly bombarded with the latest and greatest devices and software. Unfortunately, that often leads to backwards problem-solving: We discover some shiny new technology, then go looking for problems it can address. That approach ends in failure.

Does that mean new technology isn't the answer? Not at all. Outdated technology itself frequently holds an IT department back. Tied to outdated enterprise software, the IT department spends most of its time and energy keeping the lights on. The maintenance requirements and inflexibility of the old system handcuff the team and keep them from providing the business with modern solutions.

Old technologies tethered to the on-premise delivery model are costly and burdensome to maintain, displacing higher value IT activities. Incompatibility with open data standards inhibits integration opportunities and business agility. The sequestration of IT from other departments inhibits alignment on business objectives.

Patrick Burns, VP of Product Management at Autotask Corporation

The key point: While new technology can address many of the issues facing IT departments, keep your focus in the right place. Technology for technology's sake is rarely a good idea. Start with the company's most pressing problems and seek out technology to fix them. That approach may not always involve the latest and greatest tech, but it vastly improves your chances of success.

Do 04

Keep learning

Stagnating skills can't push a business forward. And learning only counts once it's applied.

In the past, IT professionals largely focused on a single, specialized area. Programmers focused on their language of choice, DBAs focused only on the database, and so on. That's changing. The web doesn't allow for a single focus. IT professionals must keep broadening their skills to keep pace with a tech landscape that refuses to sit still.

The modern technology professional can't afford to live in a silo and needs to not only understand numerous technologies, but how to apply them to the business needs.

Aaron Skonnard, CEO of Pluralsight

The fact is, if your skills, or your IT staff's skills, are stuck in the past, how can you possibly push the business forward? How can you innovate when your own skills are stagnating? You can't.

It doesn't stop there. Learning is a two-step process. Attending training classes is the first step; the skills must then be applied in the business, and this is where many departments fall down.

IT departments have been very focused on certification for their employees, and the results have been terrible. Quality has not improved. These people come back to the office with a head full of knowledge but they are not using it, because they didn't learn the competencies of applying the knowledge.

Jan Schilt, Managing Director of GamingWorks
Do 05

Treat your staff well

The success of your IT department depends on the commitment of your crew.

There's a distinction often attributed to Theodore Roosevelt: "People ask the difference between a leader and a boss. The leader leads, and the boss drives."

It's an important point that gets lost in the shuffle. Some managers take an "I'm in charge, so you'll do as I say" approach. It might deliver short-term results, but it doesn't foster long-term motivation, and it certainly doesn't create a high-performing staff. The best leaders understand the importance of a committed team and treat their employees with respect.

Simply put, the success of your IT department depends on the commitment of your crew. You get great commitment by treating your staff like gold. When they needed time off, I gave it to them, because I knew we were going to be pulling some late nights getting servers moved or upgraded. There were times when we worked 24 hours straight to get problems resolved so the businesses could stay in business.

Joe Latrell, former IT leader and President of Photos to Space

This isn't just someone's opinion. Research backs it up. A study led by Andrew Oswald, professor of economics at Warwick Business School, concluded that "human happiness has large and positive causal effects on productivity." How large? The same research found unhappy workers were about 10% less productive, while happy workers were about 12% more productive. That's a swing of roughly 22% riding on how you treat your team.

Do 06

Put the right tools in place

IT can't drive innovation when nearly all of its resources go to supporting existing systems.

Gartner once estimated that 80% of IT resources are spent maintaining and supporting existing systems. With so much time and effort required just to keep the lights on, many IT departments can't possibly drive business innovation.

Typical IT team Maintaining existing systems (~80%) Innovation The goal Lights on Work that moves the business forward Gartner once put maintenance and support at 80% of IT resources
The maintenance trap: When keeping the lights on consumes most of IT's time, innovation gets whatever is left. The right tools flip the ratio.

Most enterprise IT departments are shackled to legacy system management by budgetary and personnel constraints. Looking at CIOs' priorities, topping the chart is their need to dedicate more resources to funding new research and development projects in support of their business units. By moving resources and human engineers away from mundane, automatable tasks, legacy system management constraints can be greatly reduced, freeing up human capital and budget dollars to invest in innovative and strategic technologies.

Jonathan Crane, CCO of IPsoft

The sad truth is, IT departments need resources to drive the business forward, but most are tied up supporting current systems. Outdated legacy applications require an inordinate amount of time to maintain and often don't work with modern technology. They don't just waste time; they keep the business from moving forward.

More often than not, IT groups are not able to allocate resources to support new business initiatives. Most IT resources are used to maintain and support existing legacy systems. If the IT group is truly going to push the business forward, they must put the tools in place that speed up development and application delivery to business units.

Tyler Wassell, Software Development Manager at mrc

Building the right habits is half the job. The other half is walking away from the practices that quietly eat your team's week. Here are the six worth cutting first.

Part two: The don'ts

Don't 01

Writing (or rewriting) applications from scratch

If the old application works fine and customers see no benefit, a rewrite is a costly hobby.

A common IT practice that wastes time and money is rewriting your app's code from scratch. Usually it comes from trying to use the latest technology, while the old one works perfectly fine. Rewriting the code is a time consuming process, and it can waste lots of time if your customers won't see any benefits. Always take careful consideration before rewriting your code from scratch.

Bartosz Olchowka, Head of Development at LiveChat

This wastes time on two fronts.

First, rewriting applications that work just fine is usually a waste of time. Besides the satisfaction of building the application from scratch, what value does it deliver? Unless the old application is holding your company or customers back in some way, developers should focus their attention on other tasks.

Second, writing or rewriting any application from scratch these days is a waste of time, full stop. There's simply too much good tooling available to justify re-inventing the wheel on every project.

Instead of trying to re-invent the wheel in each project, spend some time researching a web framework or development tool that eliminates the repetitive coding tasks and promotes stability, maintainability, and security. In the end it's all about delivering quality solutions in an efficient manner, and selecting the right tools will help save time and improve software reliability.

Tyler Wassell, Software Development Manager at mrc
Don't 02

Repeating low-level, manual tasks

Roughly a third of IT's time goes to low-level tasks. Most of them can be automated.

A big time waster is repeating manual tasks that could and should be automated. IT pros need to continually evaluate the repetitive tasks they are doing, such as checking logs, checking system emails, checking backups, spinning up servers, and see what they can do to automate these tasks.

Ski Kacoroski, Director, League of Professional System Administrators (LOPSA)

How much time do these manual tasks waste? The analyst firm Quocirca estimated that 30% of an IT team's time is spent on low-level tasks such as responding to minor user incidents, carrying out routine procedures, or checking for errors. Many IT departments get caught in a never-ending cycle of low-level, repetitive work. It keeps them busy, and it keeps them from accomplishing anything of importance.

The solution: Automate the repetitive tasks. If you're not sure where to start, Jonathan Crane of IPsoft suggested beginning with low-level tasks that are both time-consuming and frequent, and offered five candidates that most IT departments can and should automate:

  • Running diagnostics
  • Predictive incident management
  • Requesting permission
  • Service readiness checks
  • Password management

That's just the tip of the iceberg, and today's automation and AI tooling reaches much further than it did when that list was written. The point stands: Regularly evaluate your repetitive tasks and see what you can automate. You might be surprised at how much time you get back.

Don't 03

Creating reports for end users or executives

Reporting is essential. IT hand-building every report is not.

It's not that reporting isn't necessary. It's absolutely essential. The problem is that IT departments pour time and energy into a task that can easily be automated or turned over to the end users. Here's a story that illustrates the point nicely, from Oli Thordarson, CEO of Alvaka Networks:

I used to provide executive summary reports for customers on how the IT system is performing. I even bonused one of the engineers if he got the reports done by the end of the first week of the month. He was to create a one to two page executive summary that could be digested by the CFO, department manager, etc. We would then mail out those reports. After a few experiences talking with the report recipients and learning that they had never even unsealed the envelope, we quit doing them. Those executives don't care what happened last month. When something happens they only care about the status right now. What we did switch to is a real time reporting portal.

Oli Thordarson, CEO of Alvaka Networks, Inc.

Two big lessons sit inside that story.

First, without proper communication, the time-wasting cycle would never have been caught. It's easy to keep performing a task because "that's what we've always done." Maybe an executive asked for a weekly report a few years back, and you're still delivering it to this day. It might be time to circle back and make sure anyone still reads it.

Second, a reporting portal is a great solution to end-user reporting problems. Set up a secure area on your intranet where employees can log in and access their reports whenever they need them. Users get their data instantly, and IT escapes the treadmill of repetitive reporting requests.

Don't 04

Manual quality assurance

Hands-on functional testing doesn't scale, and it caps how fast you can ship.

Manual QA, that is the hands on functional testing done by humans, does not scale. When there are releases, the QA testers must swarm to test instead of testing new features. When new features are developed they generally can be developed as fast as they can be tested. For small organizations this isn't usually an issue. For large organizations this becomes much more apparent.

Tom Barker, Senior Manager of Web Development at Comcast

Barker's recommendation: Manual QA testers should instead write test cases that can be automated by developers or test automation engineers. "Automating testing allows features to be created as fast as tests can be written for those features," he added. "Automated testing frees up the time for releases to allow nifty things like continual deployment."

This comes back to the earlier point: Automate the tasks that can be automated. Not all testing qualifies. Areas like the user interface and application design still require human judgment. But manual functional testing doesn't scale, only slows the IT department down, and is a prime candidate for automation.

Don't 05

Juggling multiple projects at once

Task-switching research puts the productivity cost as high as 40%.

The research on multitasking keeps arriving at the same conclusion: It kills productivity. Our brains can only focus on a single task at a time, and they struggle to switch from one task to another. How much does it hurt? Studies on task-switching have put the productivity cost as high as 40%. Switch between tasks all day, and you can waste close to half your time on the switching itself.

The same applies to IT projects. Bouncing between projects strains productivity, yet many IT departments try to run several at once with the same people. The result is higher cost and lower quality.

There will never be enough people to handle everything. Launching multiple projects and moving people back and forth among them is never a good idea. It often makes the final project cost more money, take more time and the resulting quality might not reach your standards. It is better to keep a stable team on each project. Once they finish it, then you can move them to another one.

Michael Good, CEO of IT New York, LLC
Don't 06

Individual desktop support

Physically visiting desks to fix machines is a habit the technology outgrew years ago.

Physical end-user support was always a time-consuming IT task, and it's less necessary than ever. IT departments can remotely fix issues and even provision new virtual desktops for their users in minutes. If your team is still providing hands-on desktop support as the default, it's time to explore more efficient options.

The world of the desktop has evolved. Virtual machines have enabled desktop teams to move away from individual desktop support. Whether your desktop has crashed or you need an upgrade, desktops via Virtual Machines can streamline desktop delivery to almost every type of device anywhere in the world. The support team, remotely and with a quick keyboard entry, can redirect devices to updated desktop profiles in minutes.

JJ DiGeronimo, technology executive, author, and STEM advocate

Summary

Forrester Research once noted that 70% of the companies on the Fortune 1,000 list a decade earlier had vanished, and pointed to one core reason: An inability to adapt to change.

As technology evolves, business agility beats size. More and more, the ability to adapt to change is critical to a company's success. From a technology perspective, that means IT departments must evolve too. Maintaining the status quo is no longer good enough. IT must break out of the back-office stigma and establish itself as a business driver rather than a business supporter. How? Build these six habits:

  • Get on the same page with the business: IT cannot deliver effective business solutions without constant communication with the business.
  • Adopt a startup mentality: Devote most of your time to tasks that drive value, and a minimum viable effort to keeping the lights on.
  • Keep your focus in the right place: Avoid the "technology for technology's sake" trap. Adopt technology that solves business problems.
  • Keep learning: Constantly hone your skills, then apply those skills in the business.
  • Treat your staff well: You're only as good as your team, so treat them accordingly.
  • Put the right tools in place: You can't drive the business forward with outdated legacy tools. Give your staff the tools they need to succeed.

At the same time, abandon the six practices that waste time and energy:

  • Writing (or rewriting) applications from scratch: With the frameworks and tools available today, coding applications from scratch is generally a waste of time.
  • Repeating low-level, manual tasks: Roughly a third of IT's time goes to low-level manual work that can be automated.
  • Creating reports for end users and executives: Give end users self-service options to create and manage their own reports.
  • Manual quality assurance: Manual QA doesn't scale. Automated testing frees developer time and speeds up delivery.
  • Juggling multiple projects at once: Jumping between projects wastes time and drastically reduces productivity.
  • Individual desktop support: Shift to remote support and virtual desktops, and free up your support staff's time.

As technology becomes increasingly important, IT departments face a great opportunity. They are in a prime position to take their technology knowledge and drive the business forward. Those that follow the points above will position themselves to do just that.

White paper updated July 2026

Free your team's time

Put the right tools in place

See how m-Power speeds up development and hands reporting to end users, so your team spends less time keeping the lights on. Set up a demo over your own data.