(Source: Anna Berkut/Alamy)
This week, Oracle announced the planned elimination of thousands of jobs, in yet another major layoff announcement from the tech industry. Some reports estimate that around 20,000 - 30,000 positions will be affected, although a final number has not been confirmed. Yet despite the reports of layoffs, the company also posted strong earnings this week, sending its stock soaring -- a sign that Oracle isn't in decline, but reallocating resources as it invests in more data centers.
Operating leaner teams has become something of a trend. Across the tech sector and beyond, companies are trimming headcount while continuing to push ambitious technology agendas. In many organizations, IT teams are being asked to support expanding cloud estates, rising cybersecurity threats, and new AI initiatives, all while budgets (and sometimes headcount) tighten.
The workforce is reduced, but the workload is not. When faced with managing smaller teams, CIOs have to decide what capabilities must remain protected, what work can be automated or simplified, and how remaining staff roles will evolve. Ultimately it comes down to a familiar but increasingly urgent question: how do you deliver more with fewer people?
Related:InformationWeek Podcast: Catching hidden errors in AI-powered code
When headcount falls, whether due to budgetary constraints or strategic streamlining, the instinct may be to distribute responsibilities evenly across the remaining staff. But technology leaders warn that some capabilities simply cannot be diluted without creating operational risk.
David Linthicum, a cloud and AI subject matter expert and founder of Linthicum Research, says certain functions must remain protected regardless of staffing levels. "You must protect mission-critical operations: security, incident response, cloud/platform operations, governance, and architecture," he said.
These responsibilities often operate behind the scenes, which can make them easy to underestimate during restructuring. Yet they represent the core mechanisms that allow enterprises to recover from outages, respond to security threats, and evolve their infrastructure over time.
Layoffs can also inadvertently remove institutional knowledge that took years to build, Linthicum noted. Experienced engineers are usually the ones who understand how systems interact, where dependencies exist, and how to troubleshoot complex failures. Plugging those gaps in the wake of their departure is much more burdensome than simply operating with one less pair of hands.
"AI can automate repeatable tasks, but it does not replace judgment, accountability or resilience planning," Linthicum said.
Related:Ask the Experts: The red flags that signal an AI project isn't worth pursuing
For CIOs, that means workforce reductions require careful analysis of which roles hold operational knowledge that cannot easily be replaced, before headcount decisions are made.
Automation and AI are frequently positioned as the technologies that allow organizations to operate with fewer people, with some companies directly referencing them as contributing factors to layoff decisions; Oracle said it expected AI to make up for some of the talent reduction. In many cases, AI does reduce the manual work involved in maintaining systems; monitoring, provisioning and basic operational tasks increasingly happen through automated processes.
Niel Nickolaisen, chairman of the CIO council at FC Centripetal and technology advisor at Valcom, sees automation as one useful mechanism for maintaining coverage when teams shrink. "If I can automate IT tasks, then I might have the same coverage but with fewer humans involved," he said.
But automation does not eliminate the responsibility for ensuring systems behave as expected. When some work is automated, human staff simply moves to other areas, often redirecting their focus from production to oversight.
Related:Shutterstock CTO's playbook for scaling AI without vendor sprawl
"The routine work goes first, meaning predictable, repeatable tasks measured by speed and consistency," Linthicum said. "What remains is higher-value work, so the remaining professionals become more strategic but also more accountable."
In practice, these engineers may spend less time executing routine work and more time on architecture, exception handling, governance, optimization, vendor management, and aligning technology with business outcomes. While important strategically, Linthicum warned that shifting people to oversee automation can be bad for morale, especially if staff were accustomed to doing the meat of the work themselves.
Another consequence of downsizing is the way expertise is distributed within the organization. Large IT departments can afford deep specialization; individual engineers might focus entirely on storage, networking, or identity systems. As teams shrink, however, those boundaries begin to blur.
Nickolaisen has observed that the transition happens quickly once staffing levels fall. "The smaller the department … [the more teams] lose expertise in certain areas and become more generalists than specialists," he said.
In many organizations, this shift is already underway as cloud platforms reduce the need for hands-on infrastructure management. Engineers who once managed a single technology stack may now oversee multiple services, applications, or environments.
Generalist teams can bring advantages: they often collaborate more easily and maintain a broader view of how systems interact. But Nickolaisen warned that individuals may exchange depth for breadth in terms of expertise, which can make troubleshooting or long-term architecture planning more difficult.
For CIOs, this dynamic influences both hiring and professional development. Instead of building narrowly specialized teams, organizations may prioritize adaptable engineers who can move between domains and understand the broader technology ecosystem. In some cases, IT teams may need to temporarily downsize further and then recruit more flexible candidates.
Beyond operational considerations, layoffs also reshape the culture within IT organizations. Employees who remain often face uncertainty about their own job security while simultaneously being asked to assume broader responsibilities. The emotional impact is one of the first issues leaders must address, Nickolaisen said
"How do I, with integrity, answer their questions about their future?" he asked.
Linthicum agreed, arguing that clear communication becomes critical during this period. Teams need to understand how priorities are shifting, what responsibilities they are expected to assume, and how leadership plans to support them. Focusing too much on the technical changes is a mistake, he believes.
"In the immediate aftermath, clarity matters as much as technology: people need to know what matters, what stops, and where they fit," Linthicum said.
Many organizations are encouraging staff to develop skills around automation, cloud operations, and AI tools, to better prepare themselves for these new environments. Investing in these capabilities can help employees manage broader workloads, while also strengthening their long-term career prospects, said Nickolaisen.
Ultimately, the long-term success of a leaner IT organization depends on whether leadership treats layoffs as a short-term financial measure or as a catalyst for broader change.
Simply removing headcount while leaving the rest of the operating model untouched often creates new pressures. Remaining staff inherit the same workload, systems remain complex, and operational risk can increase. The true test lies in whether organizations redesign how technology work gets done, explained Linthicum.
"The real issue is not layoffs … It is whether CIOs are redesigning the operating model or just cutting costs," he said.
Nickolaisen pointed to another strategic consideration. For decades, many companies assumed that IT resources would always be limited, forcing them to prioritize projects and maintain long backlogs of work. If automation and AI significantly increase productivity, that assumption may eventually change. Organizations could find themselves capable of delivering more technology initiatives without expanding headcount, which requires an entirely new approach to IT strategy.
For now, however, many CIOs are navigating a confined reality: sustaining reliability, security, and innovation with smaller teams.
Senior Editor, InformationWeek
Madeleine Streets is a senior editor at InformationWeek, where she shapes stories and contributes news analysis through a CIO lens.
She comes to InformationWeek from TechTarget’s Learning Content team, in which she authored explainers and features on a range of enterprise IT topics. Before moving to the field of enterprise technology, Madeleine spent several years covering retail, consumer finance, and ecommerce technology for fashion trade publication Footwear News. She has also been published in Women’s Wear Daily, TIME, Associated Press, SELF, and Observer, among others. The thread that ties her coverage together is a commitment to honest, impactful storytelling -- and insatiable curiosity.
Outside of writing, Madeleine can be found studying wine, singing in her local choir, and working her way towards her annual reading goal of 100 books. She is based in New York City, US.
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。