Skip to content
Tiatra, LLCTiatra, LLC
Tiatra, LLC
Information Technology Solutions for Washington, DC Government Agencies
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact
 
  • Home
  • About Us
  • Services
    • IT Engineering and Support
    • Software Development
    • Information Assurance and Testing
    • Project and Program Management
  • Clients & Partners
  • Careers
  • News
  • Contact

5 IT management practices certain to kill IT productivity

Successful CIOs, like all highly placed executives, must be adept at running an organization that’s good at getting work out the door.

Unfortunately, many of the most popular management techniques for fixing poor organizational performance don’t work. Or worse.

If you want better guidance, start with Peter Drucker’s observation that, “Most of what we call management consists of making it difficult for people to get their work done.”

Which should encourage you to take the next logical step: To improve IT’s performance, figure out which of your organization’s management practices are best at making getting work done difficult, and stop doing them. Here are some likely places to start.

Bad fix #1: Reorganize

What it is: The ever-popular Titanic iceberg collision remediation strategy of rearranging the deck chairs.

Why it’s a problem: Reorganizations don’t change how work gets done.

The usual rationale is that realigning reporting relationships removes barriers. Which it does, most often by replacing one set of barriers with a different set of barriers.

Meanwhile, reorganizations change the unwritten rules by which IT operates, as employees have to learn how to work with their new management.

Why it’s a temptation: It’s tempting because it’s easy. Just announce the new reporting relationships and leave it to everyone else to make it work.

It’s especially tempting when you have an ineffective manager — you can avoid the unpleasant conversation that tells them so, instead placing them someplace safe in the new organization to minimize the damage they inflict.

What to do instead: Just about anything.

Bad fix #2: Rely on multitasking

What it is: Asking employees to juggle multiple responsibilities.

Why it’s a problem: Employees divide their time into two buckets — orienting to the task at hand, and performing the task at hand. The more employees have to multitask, the more time they lose to reorienting, reducing the time they can devote to productive work.

Why it’s a temptation: Multitasking means never having to say no to a request. You can always promise to squeeze something in. Also, it improves IT’s performance on employee utilization — a bad but popular metric.

What to do instead: Eliminating multitasking is too much to shoot for, because there are, inevitably, more bits and pieces of work than there are staff to work on them. Also, the political pressure to squeeze something in usually overrules the logic of multitasking less. So instead of trying to stamp it out, attack the problem at the demand side instead of the supply side by enforcing a “Nothing-Is-Free” rule.

Bad fix #3: Ignore bad processes

What it is: The way work gets done is disorganized, ineffective, uncoordinated, undocumented, inconsistent, and idiosyncratic.

Why it’s a problem: When each employee independently figures out the way to get something done, IT’s practices are, in effect, in a perpetual state of alpha testing. Processes never improve because no two people ever do them the same way or build on past successes.

Why it’s a temptation: Defining, documenting, training, and insisting everyone follows well-defined processes is a lot of work, not to mention that it can make a manager unpopular. After all, for most employees doing things the way they want is a whole lot more fun than doing things the institution’s way. Worse, doing things the institution’s way and insisting on it will lead to accusations that you’re turning IT into a stifling, choking bureaucracy.

What to do instead: Encourage a “culture of process” throughout your organization.

Yes, this is just the headline, and there’s a whole lot of thought and work associated with making it real. Not everything can be reduced to an e-zine article. Sorry.

Bad fix #4: Holding people accountable

What it is: According to its proponents, it’s how to make sure everyone does their best to avoid making mistakes and do whatever it takes to get the job done.

Why it’s a problem: Holding people accountable is root cause analysis predicated on the assumption that if something goes wrong it must be someone’s fault. It’s a flawed assumption because most often, when something goes wrong, it’s the result of bad systems and processes, not someone screwing up.

When a manager holds someone accountable they’re really just blame-shifting. Managers are, after all, accountable for their organization’s systems and processes, aren’t they?

Second problem: If you hold people accountable when something goes wrong, they’ll do their best to conceal the problem from you. And the longer nobody deals with a problem, the worse it gets.

One more: If you hold people accountable whenever something doesn’t work, they’re unlikely to take any risks, because why would they?

Why it’s a temptation: Finding someone to blame is, compared to serious root cause analysis, easy, and fixing the “problem” is, compared to improving systems and practices, child’s play. As someone once said, hard work pays off sometime in the indefinite future, but laziness pays off right now.

What to do instead: Whenever something goes wrong, first fix the immediate problem — aka “stop the bleeding.” Then, figure out which systems and processes failed to prevent the problem and fix them so the organization is better prepared next time.

And if it turns out the problem really was that someone messed up, figure out if they need better training and coaching, if they just got unlucky, if they took a calculated risk, or if they really are a problem employee you need to punish — what “holding people accountable” means in practice.

Bad fix #5: Keeping you in the loop

What it is: A consequence of the no-surprises rule — if something happens in your department, you’re supposed to know about it before it becomes visible to your peers and management.

Why it’s a problem: It isn’t a problem. Unless, that is, you make keeping you in the loop a higher priority than fixing what’s gone wrong, and especially if it means whoever is trying to fix the problem has to get managerial approval before taking whatever steps they need to take.

Why it’s a temptation: Being kept in the loop reduces the fear that a manager will be blindsided and look bad to their management. Also, it makes a manager feel important: “I have to take this call” is almost as compelling as, back in the old days, having their pager start to buzz.

What to do instead: This is a softball, isn’t it? Just make sure everyone knows that, should a problem arise, priority #1 is fixing it. Briefing you is priority #2 or #3. Or maybe #27.

Not everything is hard to figure out.

And, a suggestion

Set up an anonymous one-question survey. Invite all IT employees to participate. The one question builds on the aforementioned Peter Drucker observation: “What are we in IT management doing that interferes with your ability to do your work?

Publicize the most common responses, take them seriously, and repeat the survey quarterly.

And if any of the common responses surprise you, revisit your organizational listening program, because clearly the one you have in place isn’t working.

IT Leadership
Read More from This Article: 5 IT management practices certain to kill IT productivity
Source: News

Category: NewsMay 16, 2023
Tags: art

Post navigation

PreviousPrevious post:SAP to add generative AI, industry smarts to CX toolsNextNext post:BCBSNC builds a better IT workplace through DEI

Related posts

Barb Wixom and MIT CISR on managing data like a product
May 30, 2025
Avery Dennison takes culture-first approach to AI transformation
May 30, 2025
The agentic AI assist Stanford University cancer care staff needed
May 30, 2025
Los desafíos de la era de la ‘IA en todas partes’, a fondo en Data & AI Summit 2025
May 30, 2025
“AI 비서가 팀 단위로 지원하는 효과”···퍼플렉시티, AI 프로젝트 10분 완성 도구 ‘랩스’ 출시
May 30, 2025
“ROI는 어디에?” AI 도입을 재고하게 만드는 실패 사례
May 30, 2025
Recent Posts
  • Barb Wixom and MIT CISR on managing data like a product
  • Avery Dennison takes culture-first approach to AI transformation
  • The agentic AI assist Stanford University cancer care staff needed
  • Los desafíos de la era de la ‘IA en todas partes’, a fondo en Data & AI Summit 2025
  • “AI 비서가 팀 단위로 지원하는 효과”···퍼플렉시티, AI 프로젝트 10분 완성 도구 ‘랩스’ 출시
Recent Comments
    Archives
    • May 2025
    • April 2025
    • March 2025
    • February 2025
    • January 2025
    • December 2024
    • November 2024
    • October 2024
    • September 2024
    • August 2024
    • July 2024
    • June 2024
    • May 2024
    • April 2024
    • March 2024
    • February 2024
    • January 2024
    • December 2023
    • November 2023
    • October 2023
    • September 2023
    • August 2023
    • July 2023
    • June 2023
    • May 2023
    • April 2023
    • March 2023
    • February 2023
    • January 2023
    • December 2022
    • November 2022
    • October 2022
    • September 2022
    • August 2022
    • July 2022
    • June 2022
    • May 2022
    • April 2022
    • March 2022
    • February 2022
    • January 2022
    • December 2021
    • November 2021
    • October 2021
    • September 2021
    • August 2021
    • July 2021
    • June 2021
    • May 2021
    • April 2021
    • March 2021
    • February 2021
    • January 2021
    • December 2020
    • November 2020
    • October 2020
    • September 2020
    • August 2020
    • July 2020
    • June 2020
    • May 2020
    • April 2020
    • January 2020
    • December 2019
    • November 2019
    • October 2019
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • April 2019
    • March 2019
    • February 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • January 2018
    • December 2017
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • July 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    Categories
    • News
    Meta
    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Tiatra LLC.

    Tiatra, LLC, based in the Washington, DC metropolitan area, proudly serves federal government agencies, organizations that work with the government and other commercial businesses and organizations. Tiatra specializes in a broad range of information technology (IT) development and management services incorporating solid engineering, attention to client needs, and meeting or exceeding any security parameters required. Our small yet innovative company is structured with a full complement of the necessary technical experts, working with hands-on management, to provide a high level of service and competitive pricing for your systems and engineering requirements.

    Find us on:

    FacebookTwitterLinkedin

    Submitclear

    Tiatra, LLC
    Copyright 2016. All rights reserved.