Work From Home Works—But Only When You Design It to Work

By a Mainfram Nerd with Two Monitors, a Standing Desk, and a Deep Respect for Team Whiteboards

When the world flipped its working rhythm in 2020, most of us in IT didn’t miss a beat. We kept the systems humming, patched the holes, scaled the VPNs, and figured out how to keep the company’s backbone alive without the benefit of hallway conversations and desk drive-bys.

Five years on, it’s time to get honest about what Work From Home (WFH) has become—and what it can and can’t be.

This isn’t a philosophical piece about remote work as a dream of digital liberation. Nor is it a rant about the need to “return to normal.” I’m an infrastructure person. I believe in design. WFH, like any system, needs to be engineered with intent.

And right now, too many organizations are getting it wrong in one of two ways: either they treat remote work as the universal default, or they act like office culture is the holy grail we somehow misplaced. The truth lies between the terminals.

1. Scoping WFH to the Job—Not the Hype

Let’s start with the obvious: in IT, not all jobs are the same. This matters.

“Terminal work”—think code commits, patch deployment, JCL tweaking, rule tuning, threat monitoring—these tasks are deeply suited to remote execution. Give me a good connection, access to my systems, my internal documentation, and I can do it just as well (if not better) from my home office. Add the lack of commute and the chance to grab a hot lunch without queuing, and the productivity boost is real.

But planning isn’t terminal work. Team retrospectives aren’t terminal work. Architecture reviews, security threat modeling sessions, or onboarding a new hire into our paranoid little corner of the world—those things need conversation. Whiteboards. Eyebrows. Context.

We can't scope every role into black-and-white rules, but we can scope tasks. And that's where most WFH policies fall short—they treat days of the week as the atomic unit of planning instead of the nature of the work.

2. One Day in Office, Not Because We Have To—But Because It’s Better

For my team, we made the decision to commit to one day a week in the office. No more, no less.

That’s the day we plan sprints, review incidents, do cross-training, argue about firewall changes, and sketch architecture diagrams with whiteboard markers that probably contain more alcohol than an after-hours team drink.

It’s also the day where someone brings in weird snacks from their recent vacation, where jokes fly across the table, and where you remember that these people—behind their avatars and Slack statuses—are real, complicated, brilliant humans. That part matters.

WFH works because we made that one day count. It’s the heartbeat of the week. Without it, the rest of the rhythm stumbles.

Is it mandatory? Technically, yes. But practically, we all want to be there—because it’s productive. Not performative. That’s the distinction a lot of companies miss.

3. WFH Fails When You’re New (and That's Okay)

The truth is, WFH is a luxury that grows with your experience.

If you’re onboarding a new team member—especially a junior one—letting them sit alone at home, facing a wall of VPN documentation and tribal knowledge buried in Confluence, is almost cruel.

I’ve seen bright, motivated interns spend their first weeks in confused silence, unsure whether to ping someone for help or try and brute-force their way through a legacy system they’ve never seen before. That’s not independence. That’s abandonment disguised as trust.

New hires and interns need proximity in the beginning. It’s not forever—but it’s real. Three days in the office the first two months isn’t “old-fashioned.” It’s support. And once they’re up to speed, they can do just as well from home as the rest of us.

Remote-first should never mean remote-only. Especially not for the people who don’t yet know what “normal” looked like.

4. Infrastructure Matters—At Home Too

Let’s talk about the elephant in the Zoom room: your home setup.

Not everyone has the same situation, and pretending otherwise is part of the problem.

If you’re single, in your late twenties, and have a spare room you can dedicate to work, WFH can be a dream. Close the door, pop the headphones on, fire up the VPN, and you’re locked in.

If you’re mid-career, sharing a two-bedroom flat with two toddlers and a partner who also works remote—suddenly, your productivity pipeline has latency spikes.

For WFH to work, your environment has to support it. That means a desk you can sit at for six hours without destroying your back, a webcam angle that doesn’t show your laundry pile, and, yes, the bandwidth to keep video calls smooth when three other people are watching Netflix, attending virtual school, or streaming Roblox.

In short: if you want to work from home, you need a room—not a corner. And if you can’t set that up (and not everyone can), then you need other options.

WFH should be enabled where it works, not enforced where it doesn’t.

5. Planning for Connection Is the New Planning for Capacity

Once upon a time, we talked about compute and memory when planning systems. Now we talk about team energy, shared context, and burnout.

Working from home can quietly deplete all three.

If we don’t plan for connection—real connection—we lose the glue that holds high-performing teams together. WFH strips away the ambient knowledge you pick up from hearing two colleagues arguing over a config setting. It removes the casual cross-pollination between teams that leads to accidental innovation.

A Slack channel is not a hallway. A weekly Zoom call is not a shared lunch.

The fix isn’t to bring everyone back to the office full-time. It’s to engineer the moments of connection that used to happen by accident. One-day-in-office rhythms help. Offsite meetups help. Even occasional co-working sessions or hackathons can inject the culture hit that remote teams need to thrive.

We’ve learned to plan infrastructure by usage patterns. Let’s learn to plan people systems the same way.

6. Security Has Never Been More Physical

I’d be remiss if I didn’t put my security hat on here.

Security in the remote era isn’t just about zero trust and endpoint protection—it’s also about the physical space where work happens.

From family members who overhear confidential calls, to unpatched home routers, to screens left unlocked while someone walks the dog—WFH introduces real, tangible risks. Especially in environments like mine, where data sensitivity isn't theoretical.

We’ve upgraded our software stack. But we haven’t upgraded our home habits.

There’s a reason banks used to have vaults. Some conversations—and some work—belong behind more than just a password.

That doesn’t mean dragging people back into the office. It means taking home security seriously. Locking screens. Using company-managed endpoints. Not taking production calls from a café.

Remote work has blurred the boundaries. Security needs to redraw them. Not with fear—but with realism.

7. The Future is Hybrid—But Built with Intention

What we’re heading toward isn’t a binary future of WFH vs. return-to-office. It’s a hybrid model.

But like any hybrid system, it requires proper interface design.

You can’t throw people into Teams meetings three days a week and then expect spontaneous innovation. Nor can you force people to commute daily when most of their value comes from deep, focused work that’s better done without headphones on.

The answer is to design your team’s week—just like you design a system.

• Use office days for planning, pairing, bonding, and strategic thinking.

• Use WFH days for focused tasks, deep debugging, documentation, and individual deliverables.

• Support new team members with more proximity at the start, then gradually taper down.

• Recognize that not everyone has the same home environment—and don’t punish people for it.

• Prioritize real connection, not just more meetings.

• And always revisit the design when the team’s structure changes.

This isn’t about being flexible. It’s about being deliberate.

Closing Thoughts: No Silver Bullet, Just Better Design

Work From Home isn’t a moral issue. It’s an engineering problem.

We don’t need blanket policies. We need thoughtful defaults. We need work setups designed around real tasks, not trends. And we need to support our teams—not just with VPNs and Slack—but with rhythms, rituals, and spaces that make sense.

The dream isn’t gone. It just needs better planning.

And maybe, one whiteboard marker with a little less alcohol.