Nine months ago, most of us were working from offices. The abruptness still feels surreal. By mid-March, IT departments across the country were executing the largest remote work migration in history, not as a pilot program or strategic initiative, but as an emergency. We had weeks, sometimes days, to make it work. We did. And in doing so, we learned more about what IT work actually requires, and what we’re actually capable of, than years of normal operation would have taught us.

This isn’t a feel-good list of silver linings. 2020 was hard on IT workers, and we shouldn’t pretend otherwise. The burnout rate in our field reached 47%, with pandemic-related stress accounting for a 67% increase in those numbers. That’s not recovered optimism; that’s exhaustion wearing down resilience. But alongside that exhaustion sits something real: clarity about what matters, what actually works, and what we might do differently going forward.

The Transition We Actually Made

We talk about the remote work shift as though it were inevitable, as though we simply discovered what everyone secretly wanted. The truth is messier. In early April, roughly 70% of US workers found themselves working from home, according to Gallup data. By fall, that number settled to about 56%, meaning some people returned to offices while others stayed remote. It wasn’t a universal shift; it was a fragmented transition that exposed exactly which work can be done remotely and which genuinely requires presence.

For IT specifically, this mattered enormously. The majority of IT work proved to be location-agnostic. Infrastructure monitoring, coding, ticket management, and security work don’t inherently require you to be in a specific room. But the peripheral work, onboarding, certain hands-on hardware maintenance, emergency server room access, requires presence or good alternatives. By November, organizations had largely figured out hybrid approaches that worked. Some went all-in on remote-first operations, investing in remote hands, better documentation, and automated deployment systems. Others maintained essential on-site teams while moving the rest home.

What actually changed wasn’t IT’s capacity to work remotely; it was the permission structure around that capacity. For years, remote work in IT existed in the margins. Now, CFOs started planning permanent remote shifts. Gartner found in April that 74% of CFOs expected to maintain significantly higher levels of remote work long-term. That’s not a temporary accommodation. That’s a structural decision. The infrastructure is there, the tools work, the productivity is fine. The question now is whether we go backward because of habit or tradition, not because of necessity.

I wrote earlier this year about moving the entire company home in two weeks, and what struck me then, what still strikes me, is how much IT work was already designed for this, and how little had actually changed about the work itself. What changed was the meeting culture, the assumption that you had to be nearby to be available, and the unconscious bias that presence equals productivity. Those were never technical problems. They were organizational ones.

The Security Reckoning

Remote work force us to confront something we’d been deferring: the security implications of the legacy perimeter. When your employees were in the office, connected through a central network, security was about protecting the perimeter around that office. When your employees are distributed across home networks, secondary devices, and public wifi, the perimeter collapses. You can’t defend a border that no longer exists.

This became urgent in April, and it’s stayed urgent. Zero trust architecture, which relies on the assumption that no network is inherently trusted and that authentication and authorization are continuous rather than one-time, moved from theoretical best practice to practical necessity. Organizations that had spent years discussing zero trust frameworks suddenly had to implement them. It wasn’t a choice; it was an emergency response to a immediate threat surface.

The security industry expanded rapidly. CompTIA data from June showed 263,000 IT job postings in the market, with cybersecurity growing from 17% to 18% of all IT openings. That might sound incremental, but in absolute numbers, it meant more job opportunities for security-focused IT professionals. And those opportunities remain. The security work that 2020 created didn’t disappear when the emergency phase passed. It solidified into permanent infrastructure.

I’ve emphasized this before: security was always essential work, and what 2020 did was make that visibility undeniable. There was no option to defer security investments while the crisis was happening. Security had to scale with the remote workforce immediately, and that scale became the new baseline.

The Upskilling Surge

One thing became clear during the spring freeze: the job market for IT was volatile, but the demand for skilled IT workers remained strong. Organizations couldn’t run on existing staff and existing knowledge. They needed people who understood cloud infrastructure, zero trust security, and the new toolsets that emerged from the rapid remote work transition.

The response was dramatic. Coursera saw a 640% increase in enrollment between March 15 and April 15. Udemy reported a 425% increase in course completions during the same period. LinkedIn Learning users completed 1.7 million hours of learning in the first week of April alone. This wasn’t driven by career planning or long-term professional development strategy. This was driven by urgency. People sensed, correctly, that the skills gap was widening and that the job market would reward those who closed it.

Those courses were a form of insurance. In an environment where hiring was frozen and uncertainty was high, investing in certification and new skills was one of the few things individuals could control. It wasn’t guaranteed to work; it was a reasonable bet on a chaotic future.

Cloud spending is one concrete indicator of where organizations placed their bets. In Q1 2020, cloud infrastructure spending increased by 37% across major providers. That’s the spending that drove demand for cloud-certified professionals throughout the rest of the year. Organizations that had deferred cloud migration for years suddenly had to execute it rapidly, and they needed people who knew how to execute it well.

The Technology Acceleration

Before the pandemic, video conferencing technology was a niche. Teams had it, Zoom existed for specific use cases, and many organizations still defaulted to conference calls and conference rooms for complex discussions. That’s not because the technology was bad; it’s because there was no urgency to use it.

By April, urgency was absolute. Microsoft Teams grew from 20 million users in November 2019 to 75 million by April 2020. That’s not a gradual adoption curve; that’s organizational necessity forcing rapid change. Zoom became cultural shorthand. The video conferencing industry didn’t invent anything new in 2020; they just got thousands of organizations to finally use what already existed.

This pattern repeated across the infrastructure stack. Cloud providers, security vendors, collaboration tools, and monitoring systems all experienced growth, not because their offerings suddenly improved, but because organizations stopped postponing the transition and actually implemented solutions that had been on roadmaps for years.

The acceleration mattered. It broke organizational inertia. Once you’ve moved to Teams or Slack, moving back to email and phone calls feels broken. Once you’ve migrated to the cloud, on-premises infrastructure that was working fine suddenly looks inefficient. These tools didn’t become better in 2020; the organizations using them finally reached the threshold where the old way of working felt obviously wrong.

The Burnout Reality

The upskilling and technological change happened against a backdrop of exhaustion. The 47% burnout rate in IT, with a 67% pandemic-related increase, isn’t a footnote to the positive transformation story. It’s the cost of that transformation.

Rapid migration to remote work, continuous security threats, the expectation of always-on availability in a distributed workforce, the stress of maintaining infrastructure during a crisis, and the sheer volume of change happening at once created an environment where burnout wasn’t just possible, it became likely. IT professionals were asked to do more with unclear timeline, inadequate sleep, and the ambient anxiety that came from living through something genuinely frightening.

We should be direct about this: a lot of burnout in 2020 was unavoidable. Emergencies require effort. Some of it, though, was a choice. Organizations that maintained boundaries, that acknowledged the reality of working from home during a crisis, that didn’t treat “remote” as an excuse to remove all expectations of time off, handled this better. But many organizations didn’t. They asked for extra hours, continuous availability, and rapid skill development on top of the anxiety of the moment itself.

The upskilling boom wasn’t purely positive. A lot of that learning happened at night, on weekends, or carved out of whatever rest time people could claim. The burnout rate rose because people were trying to do their jobs, maintain their sanity, keep their families safe, and prepare for an uncertain future all at the same time.

Looking Forward

It’s December now, and there’s cautious optimism. Vaccines are being deployed in other countries, with distribution coming soon in the US. The emergency phase of the pandemic is transitioning into something more like living with ongoing crisis, which is not better, but is at least a different kind of difficult.

For IT careers, what changed in 2020 will largely stick. Remote work capability is proven. Cloud adoption is accelerated. Zero trust security is real infrastructure, not theoretical discussion. Upskilling is now table stakes; organizations expect their IT staff to evolve continuously. The tools that became essential are now normal.

The question for 2021 is whether we learn the right lessons. Remote work teaches us that presence isn’t productivity, that people can contribute effectively from anywhere, and that flexibility is professional, not lazy. Cloud adoption teaches us that migration, when it finally happens, happens fast, and that resisting change costs more than embracing it. The security lessons are about fundamentally rethinking what trust means. The burnout numbers teach us that speed and crisis aren’t forever sustainable, and that organizations need to invest in resilience and boundaries, not just in crisis response.

We learned a lot about what IT work actually is, what it demands, and what we’re capable of when we have no choice but to change. That knowledge is a genuine asset going forward, if we choose to use it wisely.