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

6 signs it’s time to restructure your IT organization

Nothing lasts forever in IT, and that includes your organizational structure.

Deciding on whether to scrap or keep existing infrastructure of any stripe isn’t easy. A complete rebuild can be disruptive, time-consuming, and risky. And if the initiative misses its goal, or runs over budget, the CIO’s job may be at stake.

Yet, as any IT leader knows, when technical infrastructure fails to meet enterprise needs, hampering productivity and innovation, it’s often time to rebuild from scratch. The same can be said for how IT operations, workflows, and teams are structured. Knowing when it’s time for a wholesale reorg requires even more from an IT leader than knowing when the bits and bytes have worn out their shelf life.

Has your organization’s IT structure outlasted its usefulness? To find out, check out the following danger signals.

1. Past incremental restructuring attempts have failed

Updates and improvised rearrangements can keep an aging organizational structure tottering along for a while, but the repair bucket eventually runs dry. At that point, the way work is done, including who does what and with whom, starts damaging workflows, decision-making, collaboration, customer service, and other critical processes.

When reorganizing any infrastructure, it’s important to understand what will be essential to retain. The same can be said for IT operations itself. “The goal isn’t to restructure with nothing remaining from what was valuable and meaningful,” says Andrew Sinclair, a managing director in consulting firm Accenture’s technology strategy and advisory practice. “Change requires something that is stable and durable.”

Restructuring can create uncertainty and stress in an organization, and it shouldn’t be used lightly or regularly, Sinclair explains. Yet a radical change is sometimes necessary. “Consider new ways of structuring how work is done, breaking down existing functional and organizational silos so teams can be combined with the full set of skills to be successful, while also reducing dependencies that can slow work.”

2. You’re fixing problems instead of delivering results

A department that lives in conflict typically struggles to efficiently execute strategies and tasks, observes Eric Lefebvre, CTO at Sovos, a tax compliance and regulatory reporting software provider. He notes that IT organizations can usually work through almost any problem as long as the parties grow together. “But if the design or role clarity is a constant source of friction, the results will inevitably be suboptimal.”

The restructuring plan’s first step should be assessing the existing environment as well as the ideal end state. “A solid understanding of the environment informs the structure and enables drilling into the next level of detail,” Lefebvre explains.

As the restructuring strategy takes shape, Lefebvre advises coordinating plans and decisions with the enterprise’s human resources leader to ensure that compliance and other important mandates will be met. “External peers in your network that have performed similar [restructuring] efforts are also a great resource for information on approaches and pitfalls to avoid,” he adds.

3. There’s been a major enterprise shakeup

Whenever a significant enterprise change occurs, such as a merger, major acquisition, or radical new business direction, the IT organization may have to be rebuilt to accommodate the new reality.

An important first step, once the decision to restructure IT has been made, is to be open and transparent with team members about the current situation, says Dena Campbell, CIO at Vaco, a global consulting firm. “Employees will want to know what it means for them and their roles,” she explains.

Campbell suggests that IT should work closely with HR to develop a comprehensive communication plan that ensures all parties fully understand what’s happening. “If you’re communicating with employees, any frustration or anxiety will be mitigated,” she says.

Establishing a realistic transition timeline is also necessary. The best way to set a timeline is to understand IT’s current position and then identify the restructuring goals, Campbell says. It’s also important to understand, and factor into the plan, that productivity and efficiency will dip when there’s so much sudden change. “Everyone will need time to adjust,” she advises. “Be realistic about setting a timeline and include time for the disruption itself, since it can take a while for the dust to settle and to get buy-in for the new plan going forward.”

4. An unhappy IT team

An obvious — and ominous — sign of org structure failure is when IT team leaders and members begin complaining about their tasks. “That’s something C-suite executives need to listen to,” says Tom Kirkham, CEO and CISO of cybersecurity firm IronTech Security.

The CIO in particular should know how to respond to internal strife. “A company culture that’s toxic will render less productivity and subpar outcomes, which will ultimately compromise the bottom line,” Kirkham warns. “A good executive, one who practices servant leadership, knows that, and how to respond to internal strife quickly and deliberately.”

As the restructuring planning begins, all stakeholders should be given the opportunity to voice their concerns and needs equally. “This is the only way to establish an IT culture that doesn’t erode from within,” Kirkham says. The restructuring should also establish priorities that contribute to the enterprise’s overall well-being, including its internal and external security.

5. Essential tasks are forever stuck in neutral

IT has fallen into a rut. Critical attributes, such as innovation, initiative, and transformation, are either absent or rarely seen. Decisions are made slowly, reluctantly, and infrequently. Meetings may be held to discuss critical issues, but end without resolution.

Meanwhile, necessary changes remain in limbo, as previous decisions are questioned during the execution phase. “These [signs] often signal there’s confusion as to who the key stakeholders are, where authority lies, or [there’s] a mismatch between organizational structure and how work is intended to flow,” says Ola Chowning, a partner with global technology research and advisory firm ISG.

“Delays or erratic workflows may be the result of organizational confusion,” Chowning observes. She notes that confusion is usually caused by a disconnect between the organizational structure and the operating model, and typically manifests over time. “This may be due to a new way of operating — such as a move to agile or product-oriented delivery, the distribution or centralization of major functions, or the influx and/or outflux of people,” Chowning says.

Full restructuring is a drastic move. Chowning believes that it’s a decision never to be made lightly. “Departments should make sure a reorganization is being done for a specific reason or need, and not as a knee-jerk reaction when a key leader exits, when a new CIO enters, or because it hasn’t been done in a while,” she explains. “Reorganization should signal to the entire department that you are expecting changes to outcomes and ways of working.”

Creating the new operating model will require a significant amount of time. “My experience has been anywhere from five to eight weeks for the complete design,” Chowning says. “Placing names in frames and selecting leaders, if that’s required, would follow, and that timeline is most often dependent on the HR practices of the enterprise.”

6. IT has a lousy internal reputation

The most important sign that something needs to change is when C-suite colleagues begin harboring a negative perception of the IT department, says Ben Grinnell, managing director at business and IT consulting firm North Highland. “Common perception issues include when IT is viewed as a cost center by the CFO; when IT is the last place the business turns to for help with digital innovation of its products and services; and when IT has more roles that don’t work directly with the business than those that do.”

To counter negative perceptions, the CIO should consider reconfiguring IT into a more flexible structure. “The organization’s efforts should be outward facing, with the goal of changing the perception of IT,” Grinnell explains. He advises CIOs to tap into discussions about how IT can drive revenue and increase margins through innovation, and what investments will be needed to enable change.

IT is an ecosystem, Grinnell states. “Any restructuring needs to include the entire workforce, including the employees, consultants, contractors, system integrators, and outsourced elements.”

Grinnell believes that IT restructuring should never treated as just another project. “It should be viewed as an always-on transformation, not a project that will one day be finished,” he explains. “That’s an unrealistic goal that sets the team up for failure.”

IT Leadership, IT Strategy
Read More from This Article: 6 signs it’s time to restructure your IT organization
Source: News

Category: NewsMarch 15, 2023
Tags: art

Post navigation

PreviousPrevious post:SD-WAN & SASE call for smarter IT service managementNextNext post:Don’t do IT yourself: The trick to ensuring business alignment

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.