Re-Skilling Via Remote Work With Laurel Farrer of Distribute Consulting

reskilling via remote work with distribute consulting laurel farrer podcast episode
Summary:

Laurel Farrer shared how remote work can reinvigorate rural areas and how you can qualitatively measure the impact of remote work.

Summary: Remote work compliance, productivity measurement, and reskilling employees for remote jobs aren’t new problems in 2026; they’re the same ones Laurel Farrer, CEO of Distribute Consulting, has been solving for over a decade. Here’s what her foundational advice still gets right.

Large companies spent the back half of 2025 pulling people back into the office, with the share of Fortune 100 employees under a five-day in-office mandate jumping from 11% to 54% in a single year. By 2026, the mandate itself had shifted again: JLL’s own newer data show “structured hybrid” (three to four office days a week) becoming the default rather than full-time RTO, with fully remote work shrinking to just 10% of the workforce. 

It’s the same underlying argument that played out with Yahoo in 2013 and IBM in 2017, just settling somewhere messier than either extreme: remote work remains a real, sizable share of paid workdays, and RTO mandates still correlate with higher attrition among the senior engineers companies can least afford to lose.

Laurel Farrer has watched this cycle before. She’s been a remote worker for over a decade, ran a fully distributed 500-person company through a toxic executive culture, and used what she learned to found Distribute Consulting and the Remote Work Association. Her writing on remote work, management, and organizational development has been a recurring feature on Forbes.

What follows isn’t a novelty pitch for remote work. It’s the compliance, measurement, and culture groundwork Farrer says most companies skip, whether they went remote in 2020 or are weighing a hybrid policy right now. If you’re building or defending a distributed team in 2026, in an environment where the “does remote work work” argument has resurfaced rather than settled, this is the foundation that argument keeps missing.

Looking for top talent fast? See how Arc can help you:

⚡️ Find developers, designers, marketers, and more
⚡️ Freelance or full-time remote + fully vetted
⚡️ Save up to 80% with global hires

Hire top talent with Arc risk-free →

What you’ll learn from Laurel Farrer:

The Non-Negotiables: Compliance and Measurement

1. Compliance Is the Unsexy Foundation of a Remote Work Policy

    “The number one problem… is just HR compliance and making sure that employment laws are being met in every single region in which you have employees… You’re breaking about 15 to 20 different laws just by going off-site if you don’t update it correctly.”

    Most remote work conversations start with productivity or talent access. Farrer starts with whether the arrangement is even legal, and she’s right to. A remote work compliance policy has to account for tax jurisdiction, worker classification, information security, and workplace safety standards that companies spend “days and days and millions of dollars” building into a physical office and then quietly ignore the moment work moves off-site.

    This is also, per Farrer, why remote work policies get retracted: not because remote work failed, but because a leadership team never built the policy infrastructure to know if it was working, and got spooked by a compliance problem they didn’t see coming.

    2. How to Measure Remote Team Productivity Before You Decide to Retract a Policy

    “Productivity costs are actually the number one place where most companies see the greatest savings… [But] a lot of people are not understanding how impactful this is to their productivity, and so they’re not valuing remote work and flexibility policies as much as they should.”

    Farrer’s read lines up with where the data has landed since: Gallup’s most recent workplace research finds remote and hybrid employees report the highest engagement of any work arrangement, around 24-25%, compared to 17-18% for on-site staff, while manager quality remains one of the biggest single levers on engagement regardless of location. 

    In other words, the “good leadership vs. flexibility” debate Farrer references isn’t either-or. Gallup’s own data shows manager quality is doing most of the work either way, which means a bad RTO mandate won’t fix a bad management problem, and a good remote policy won’t survive a bad one either.

    If your company is deciding whether to keep, expand, or roll back a remote policy, calculate the actual number, real estate savings, productivity costs, and attrition costs before making the call. Farrer’s clients only preserve flexibility once they see the number attached to it.

    Read More: How to Measure Developer Productivity in 2026 (Without Breaking Your Team)

    Remote Work as Economic and Workforce Strategy

    3. Remote Work as an Economic Development Strategy for Rural Communities

      “We’re also dispersing industry, and we’re also dispersing opportunity… you can bring your industry, whatever it is, healthcare or manufacturing or entertainment or design, you can bring that also to your tiny little town that never would have been able to recruit a large healthcare company into their city.”

      Farrer’s work strategizing Utah’s Rural Online Initiative, a state-backed program that trains rural residents for remote roles and still runs cohorts today, is the clearest evidence for this argument. It’s not a talent-acquisition footnote. For regions facing manufacturing shutdowns and shrinking local tax bases, a remote-work economic development strategy can bring in outside industry and wealth without requiring anyone to relocate.

      4. Reskilling Employees for Remote Jobs: Translate the Skills They Already Have

        “If we just take away that phrase of ‘selling backpacks’ and we turn that into somebody at station A, somebody at station B, and somebody at station C is designing a website, it’s exactly the same process. Project management is project management.”

        This is Farrer’s most practical idea, and it holds up better in 2026 than it did when she first made it: someone who ran a factory line for 20 years has workflow management, performance review, and team-lead experience; it’s just described in manufacturing language instead of tech language. 

        Reskilling employees for remote jobs is often a translation problem. Employers who insist on “startup experience” as a proxy for capability are filtering out candidates who’ve already done the underlying work under a different job title.

        5. Widen Your Candidate Profile, Not Just Your Applicant Pool

        “Recruiting is just marketing… The first step every marketing director and sales manager takes is creating a consumer profile… Yet we’re not applying that at all to our recruiting… we’re saying, ‘Yeah, anybody from anywhere can work for us.'”

        Opening a role to remote applicants doesn’t automatically widen your talent pool in a useful way if you’re still only picturing the same candidate profile you’d have hired locally. Farrer’s point: get specific about who’s actually going to be great in the role, then use remote hiring to find more of exactly that person, including candidates from outside tech entirely, rather than defaulting to “anyone, anywhere.”

        Leading (Not Managing) a Distributed Team

        6. Self-Management Is a Skill You Have to Build Deliberately

        “When you are off-site, more self-management is required… you need to be in control of your own time, your own tasks, and your own energy.”

        Farrer’s framing of isolation is blunt: it’s a problem to solve, not just a feeling to sit with. If a new remote hire feels cut off, the fix is specific (a missing folder permission, a missing communication channel, a missing social outlet), not vague encouragement to “push through it.”

        What the original conversation doesn’t spell out, and what’s worth adding for 2026: self-management works both ways. If you’re asking new hires to manage their own time and energy, pair that with an explicit, written statement of your non-working hours and response-time expectations. 

        Farrer makes this point elsewhere in the interview about expectation-setting generally (a worker assuming they can leave at 3 pm, a manager assuming 9-to-5 availability, neither one said out loud), and it applies directly to burnout prevention, too. Self-management without a stated boundary just shifts the failure mode from isolation to overwork.

        7. Document Early: Building a Scalable Remote Work Infrastructure

        “It’s so critical to get your infrastructure in place and your protocols in place while you’re small, because it is easy for chaos to exist when you’re small… We’re always building our products to scale, but we’re not building our infrastructures to scale.”

        A five-person team can survive on tribal knowledge. A fifty-person team can’t, and the painful part is that the switch-over isn’t gradual; it’s a wall you hit. Building a scalable remote work infrastructure means writing things down before it feels necessary: not just accounts and repos, but communication norms, meeting philosophy, and decision logs. 

        Farrer’s framing is useful here too: a virtual business needs a deliberate “sense of place,” built with software and process instead of “bricks and mortar,” or new hires will wonder if they’ve joined a real company at all.

        Wrapping Up

        None of these seven principles are new, and that’s the point. Farrer’s foundational case for remote work (get compliant first, measure before you decide, document while you’re small, treat self-management as a trained skill rather than an assumption) predates the pandemic-era remote boom and has outlasted the current RTO backlash too. 

        Fortune 100 companies mandating five-day office weeks in 2026 are running the same experiment Yahoo ran in 2013, and IBM ran in 2017, largely without the compliance and measurement groundwork Farrer’s been arguing for the whole time.

        If you can only act on two things from this list, make it compliance and measurement. Everything else (culture, documentation, hiring strategy) is easier to fix once you actually know whether your remote policy is working and whether it’s legal. Guessing on either one is how policies get retracted for the wrong reasons.

        Read More: Return to Office in 2026: What the Data Means for Engineering Teams

        Have you had to make the case for (or against) remote work at your company recently? Hiring managers and remote workers alike: we’d like to hear what actually moved the decision, whether that was a hard number, a compliance scare, or something else entirely. Drop your experience in the comments.

        You can also try Arc, your shortcut to the world’s best remote talent:

        ⚡️ Access 450,000 top developers, designers, and marketers
        ⚡️ Vetted and ready to interview
        ⚡️ Freelance or full-time

        Try Arc and hire top talent now →

        Written by
        The Arc Team