Skip to main content
Settings
Color Mode
Theme Skin
Background

Appearance preferences are saved in this browser only.

Environment
Current Environment Production

Built with JEKYLL_ENV=production. Changes require deployment.

Theme & Build
Jekyll v3.10.0
Last Build Jul 12, 21:59
Page Location
Page Info
Layout article
Collection posts
Path _posts/corp/2025-08-12-remote-work-experiment.md
URL /posts/2025/08/12/remote-work-experiment/
Date 2025-08-12
Featured

Remote work three years later: what actually worked

The experiment nobody signed up for

In 2020, almost every Denver business that could send people home did so overnight. No pilot, no policy, no budget line. Three years later the dust has settled enough to ask a sharper question: which of those changes were real improvements, and which were band-aids we are still paying for?

This is the unglamorous version. Not “remote work is the future” or “everyone back to the office,” but what held up at small and medium businesses (SMBs) on the Front Range once the emergency faded and the invoices arrived.

Why this matters now for a Denver SMB

Two pressures collide on your desk. Talent expects flexibility: U.S. Bureau of Labor Statistics data on remote work and telework shows that the share of workers doing some work from home settled far above pre-2020 levels and has not snapped back. At the same time, the costs you took on during the scramble (extra software seats, second sets of hardware, a leased office you half-use) are now permanent unless you act.

For a 30-to-80-person firm, that gap is real money. Downtown Denver and Boulder Class-A office space still runs roughly $30-45 per square foot per year. If you are paying for 12,000 square feet that sits two-thirds empty on Mondays and Fridays, that is six figures a year buying air. Meanwhile, collaboration and security tooling that felt free in 2020 now lands at roughly $20-60 per employee per month once you add the licenses that actually keep you safe.

The decision in front of you is not “remote or not.” It is: what work model fits your roles, and what does it actually cost to run safely?

What actually worked

A few changes earned their keep across the SMBs we see:

  • Outcome-based management. Firms that stopped measuring hours and started measuring deliverables (jobs closed, tickets resolved, month-end close completed on time) kept the gains. This worked because it forced clarity that was overdue anyway.
  • A real collaboration stack. One messaging tool, one video tool, one document home (Microsoft 365 or Google Workspace), configured once. Not five overlapping apps bought in a panic.
  • Wider hiring radius. A Lakewood accounting firm can now hire a controller in Fort Collins or Pueblo without forcing a daily commute. For hard-to-fill back-office roles, that expanded pool is the single biggest durable win.
  • Documented processes. Remote work exposed every “just ask Susan” workflow. The firms that wrote things down got more resilient, full stop.

What was a band-aid

These did not survive contact with the invoice:

  • Tool sprawl. The free-trial pile of apps from 2020 became a security and billing mess. Most firms are now consolidating back to one or two vendors.
  • “Everyone fully remote forever.” All-remote knowledge-work shops are quietly adding in-person time for onboarding, complex problem-solving, and culture. The fix was rarely full reversal; it was structure.
  • One policy for every role. A field supervisor, a front-desk coordinator, and a staff accountant do not have the same needs. Uniform mandates (all-remote or all-in) created friction in both directions.
  • Assumed cost savings. The office-rent savings were real but smaller than expected once you add tooling, hardware refresh, and the management time hybrid coordination eats.

Building a hybrid policy that holds up

What we would actually do with a Denver SMB, in plain terms: design the model around roles and risk, not around what the loudest department wants.

  1. Map roles to a model (week 1-2). Sort every role into one of three buckets: on-site required (field, front desk, lab), hybrid (most office staff), and remote-eligible (specialized or back-office). Write the rule per bucket, not per person, so it is defensible and easy to administer.
  2. Pick anchor days, not a free-for-all (week 2-3). “In Tuesday and Thursday” beats “come in sometimes.” Anchor days are what make a smaller office and real collaboration possible; without them you pay for full capacity and get an empty room.
  3. Consolidate the stack (week 3-6). Standardize on one collaboration suite, retire the overlap, and document who owns what. This is also where you fix the security holes the scramble left behind.
  4. Right-size the office (ongoing). Treat space as a collaboration hub, not assigned seating. For many SMBs that means a smaller lease at renewal plus a flexible-workspace option in the suburbs where staff actually live.

Expect the policy-and-tooling phase to take 4-8 weeks for a typical SMB. The office-footprint decision usually waits for a lease event, so plan it 9-12 months ahead.

The part most SMBs skip: securing remote access

This is where small firms quietly carry the most risk. When you sent people home, you also pushed company data onto home networks, personal devices, and coffee-shop Wi-Fi. If you handle regulated data (Health Insurance Portability and Accountability Act, or HIPAA, for clinics; Payment Card Industry, or PCI, for retail), the remote setup is now part of your compliance posture whether you planned it or not.

The baseline we would insist on:

  • Multi-factor authentication (MFA) everywhere. Non-negotiable on email, accounting, and any remote login. The U.S. Cybersecurity and Infrastructure Security Agency treats it as a minimum control, and most cyber-insurance renewals now require it.
  • Managed devices, not the honor system. Endpoint management and disk encryption on company laptops; clear rules (or a hard no) on personal devices touching company data.
  • Identity over VPN where it fits. For cloud apps, conditional-access policies (who, from what device, from where) often protect better than a flat virtual private network (VPN) that trusts anyone on it.
  • Backup and recovery you have tested. Distributed work multiplies the places data lives. Know your recovery time objective (RTO) and recovery point objective (RPO), and actually test a restore.

Skipping this is the most expensive shortcut in the whole transition, because it stays invisible until a breach or a failed audit makes it very visible.

Watch-outs

  • Hybrid is the most expensive model to run badly. Two environments, scheduling overhead, and equity headaches between in-office and remote staff. It is worth it only if anchor days and a consolidated stack make it coherent.
  • Proximity bias quietly punishes remote staff. If promotions and good projects flow to whoever is in the room, your wider talent pool dries up. Build review criteria that do not reward hallway visibility.
  • The lease is the slow trap. Office decisions lock in your cost structure for years. Do not let an auto-renewal make a strategic decision for you.

Next step

Remote work did not end. It matured into a set of choices about roles, cost, and risk that reward firms who decide on purpose. If you are sorting out a hybrid policy, the tooling behind it, and whether your remote access would survive an audit, explore our [[IT strategy]] for Denver-area SMBs.