Sitemaps
Assume Everyone Will Leave in Year One
Stop Listening to Investors
Was Mortgaging My Life Worth it?
What's My Startup Worth in an Acquisition?
When Our Ambition is Our Enemy
Are Startups in a "Silent Recession"?
The 5 Types of Startup Funding
What Is Startup Funding?
Do Founders Deserve Their Profit?
Michelle Glauser on Diversity and Inclusion
The Utter STUPIDITY of "Risking it All"
Committees Are Where Progress Goes to Die
More Money (Really Means) More Problems
Why Most Founders Don't Get Rich
Investors will be Obsolete
Why is a Founder so Hard to Replace?
We Can't Grow by Saying "No"
Do People Really Want Me to Succeed?
Is the Problem the Player or the Coach?
Will Investors Bail Me Out?
The Value of Actually Getting Paid
Why do Founders Suck at Asking for Help?
Wait a Minute before Giving Away Equity
You Only Think You Work Hard
SMALL is the New Big — Embracing Efficiency in the Age of AI
The 9 Best Growth Agencies for Startups
This is BOOTSTRAPPED — 3 Strategies to Build Your Startup Without Funding
Never Share Your Net Worth
A Steady Hand in the Middle of the Storm
Risk it All vs Steady Paycheck
How About a Startup that Just Makes Money?
How to Recruit a Rockstar Advisor
Why Having Zero Experience is a Huge Asset
My Competitor Got Funded — Am I Screwed?
The Hidden Treasure of Failed Startups
If It Makes Money, It Makes Sense
Why do VCs Keep Giving Failed Founders Money?
$10K Per Month isn't Just Revenue — It's Life Support
The Ridiculous Spectrum of Investor Feedback
Startup CEOs Aren't Really CEOs
Series A, B, C, D, and E Funding: How It Works
Best Pitch Decks Ever: The Most Successful Fundraising Pitches You Need to Know
When to Raise Funds
Why Aren't Investors Responding to Me?
Should I Regret Not Raising Capital?
Unemployment Cases — Why I LOOOOOVE To Win Them So Much.
How Much to Pay Yourself
Heat-Seeking Missile: WePay’s Journey to Product-Market Fit — Interview with Rich Aberman, Co-Founder of Wepay
The R&D technique for startups: Rip off & Duplicate
Why Some Startups Win.
Chapter #1: First Steps To Validate Your Business Idea
Product Users, Not Ideas, Will Determine Your Startup’s Fate
Drop Your Free Tier
Your Advisors Are Probably Wrong
Growth Isn't Always Good
How to Shut Down Gracefully
How Does My Startup Get Acquired?
Can Entrepreneurship Be Taught?
How to Pick the Wrong Co-Founder
Staying Small While Going Big
Investors are NOT on Our Side of the Table
Who am I Really Competing Against?
Why Can't Founders Replace Themselves?
Actually, We Have Plenty of Time
Quitting vs Letting Go
How Startups Actually Get Bought
What if I'm Building the Wrong Product?
Are Founders Driven by Fear or Greed?
Why I'm Either Working or Feeling Guilty
Startup Financial Assumptions
Why Every Kid Should be a Startup Founder
We Only Have to be Right Once
If a Startup Sinks, Founders Go Down With it
Founder Success: We Need a Strict Definition of Personal Success
Is Quiet Quitting a Problem at Startup Companies?
Founder Exits are Hard Work and Good Fortune, Not "Good Luck"
Finalizing Startup Projections
All Founders are Beloved In Good Times
Our Startup Culture of Entitlement
The Bullshit Case for Raising Capital
How do We Manage Our Founder Flaws?
What If my plan for retirement is "never retire"?
Startup Failure is just One Chapter in Founder Life
6 Similarities between Startup Founders and Pro Athletes
All Founders Make Bad Decisions — and That's OK
Startup Board Negotiations: How do I tell the board I need a new deal?
Founder Sacrifice — At What Point Have I Gone Too Far?
Youth Entrepreneurship: Can Middle Schoolers be Founders?
Living the Founder Legend Isn't so Fun
Why Do VC Funded Startups Love "Fake Growth?"
How Should I Share My Wealth with Family?
How Many Deaths Can a Startup Survive?
This is Probably Your Last Success
Why Do We Still Have Full-Time Employees?
The Case Against Full Transparency
Should I Feel Guilty for Failing?
Always Take Money off the Table
Founder Impostor Syndrome Never Goes Away
When is Founder Ego Too Much?
The Invention of the 20-Something-Year-Old Founder

The Difference Between “Remote” and “Remote-First” Companies

Paul Farnell

The Difference Between “Remote” and “Remote-First” Companies

One of my goals as the CEO of Litmus is to build the company I want to work for. It’s the reason we offer 28 days of paid vacation, the best equipment, Spotify accounts, retirement plans, stock options, and so on.

It’s also the reason we give our employees the freedom to work anywhere.

Remote Companies vs. Remote-First Companies

The decision to become a remote-first company — i.e. work wherever you feel empowered to do your best work — was an important inflection point for the organization. We’d spent years hiring local talent in Boston and London, all the while making exceptions for great people in other cities and countries.

Inequalities developed. Our remote workers felt comfortable taking a break to run a quick errand or go for a run. Our local employees adhered to a more traditional work schedule. I much prefer clarity — and I also prefer a flexible schedule — so in 2014 we decided to extend the option to work remotely to all of our employees.

One misconception about remote work is that it hinders collaboration. In my experience, the inverse is more likely: offices hinder independent work.

At Litmus, remote work isn’t about traveling the world (although we’re happy for our employees to work anywhere) or working without trousers (that’s fine too), it’s about creating an environment that empowers people do their best work and enjoy their lives.

We believe that remote-first companies are different than remote companies. Here’s a little more on our philosophy.

Remote is a mindset, not a place

We started Litmus with a few old computers and a dorm room internet connection. There was no need (or money) for an actual office, so we worked from wherever we could. We’d get together now and then, but the bulk of our work was done in solitude.

First Litmus Remote Office

These were formative years. We learned how to communicate and how to work independently. We learned to hire the best people, wherever they were. When we finally opened a real office, those principles were already established. We ended up working “remotely” from our individual offices in the Boston HQ instead of our homes or a coffee shop.

One misconception about remote work is that it hinders collaboration. In my experience, the inverse is more likely: offices hinder independent work. Collaboration tends to happen in short bursts, followed by longer periods of writing, designing, coding and thinking. It’s more important to give employees quiet time than it is to cram them into an open office.

The office still matters

Litmus is a remote company with a collective 15,000 square feet of office space. That might sound crazy, but I believe offices afford some benefits that distributed work simply can’t replace.

We’ve had a remote-first company mindset since the beginning, but we’ve also always had some kind of office space for meetings, collaboration and socializing. First it was a little corner of coworking space, then a small office and eventually a full-fledged HQ.

Just because an office exists doesn’t mean people should be required to work in it.

Today, just under half of our employees live in the Boston area. They are free to come to our HQ whenever they like. We encourage (but don’t require) people to spend Thursdays in the office to catch up, have meetings and grab a drink afterwards. I don’t love the 9–5 culture that offices seem to require, but I do really enjoy spending time with our team. We’ve hired so many great people, it would be a shame to never see them.

Litmus Band

The opposite is true, too. We’ve hired so many great people, it would be a shame to herd them into an office if they could work better somewhere else. Just because an office exists doesn’t mean people should be required to work in it.

Offices matter, but not as much as happy, productive employees.

We don’t have all the answers

There are a few challenges we haven’t quite figured out yet. It’s difficult, for example, to plan for office space. Our 7,000 square foot floor in Boston is cavernous for the ten or so people regularly working from it. On the other hand, when we have team meet-ups, space is so tight that people have to cram on couches.

Offering equal perks is also a challenge. Each morning, office-based employees get an email asking them what they’d like for lunch. At noon, their food arrives, courtesy of the company. We still haven’t figured out how to offer a similar benefit to remote employees. A $10 lunch voucher just isn’t the same — perks like this don’t translate well into cash.

When a CEO uses their lunch break to hit the gym, others feel empowered to do the same. And when a manager spends their entire vacation answering emails, it’s harder for others to disconnect in their own downtime.

It’s easy to cast these issues aside as “first world problems.” And yes, we are very lucky to be in a position to invest so much in our employees. It’s also part of our strategy to grow. The decisions we make now validate our current employees’ belief in our leadership team and will attract more great people in the future.

10 tenets of remote-first companies

Success begins with a philosophy. I believe in the remote-first company model, but there are plenty of nuts and bolts required to make it effective. Here are a few.

1.) Commit.

We’re a remote-first company 100% of the time. Unless every person is in the same room, all meetings are held over video conference. This is absolutely essential and was a game-changer for us.

2.) Communicate Deliberately.

Put processes in place for communication. Edits go in Google Docs, status updates go in Basecamp, files go in Dropbox, meetings happen on Blue Jeans. Make sure everyone knows where and how to communicate.

3.) Lead by example.

The behavior of the leadership team influences company culture more than a core values document. When a CEO uses their lunch break to hit the gym, others feel empowered to do the same. And when a manager spends their entire vacation answering emails, it’s harder for others to disconnect in their own downtime.

4.) Trust your team.

Hire smart people that can work autonomously to avoid creating a culture of micromanagement. Work only gets done when you allow people to make mistakes.

5.) Clarify expectations.

“Can I take a break to walk my dog?” “Can I do laundry between meetings?” We learned early on that it’s important to let people know it’s okay to embrace the remote company lifestyle. (The answer to both questions is a resounding “yes.”)

6.) Log out.

Tools like Slack help us communicate, but it’s okay to log out. We encourage our employees to disconnect so they can tackle their work without distractions. As Jason Fried wrote, “Treat [group] chat like a sauna — stay a while but then get out.”

7.) Make time for socialization.

A few times a year, we have company get-togethers and smaller teams meet in-person more often. Week to week, we get Coworker Coffees, drink beers on Skype, and play video games online. And we invite local employees to the office every Thursday.

8.) Expect push-back.

Not everyone loves remote work and that’s okay. That’s why we keep an office and offer WeWork memberships to anyone who lives near a location.

9.) Ask for feedback.

Problems do come up with remote work. We use Know Your Company to get a steady stream of feedback from our employees. Tools like this make it easy to be pro-active.

10.) Embrace the freedom.

You probably wouldn’t do yoga in your cubicle, but you can do it in your home office. You might feel like you need to skip your daughter’s 4pm soccer game because it’s during office hours. Go cheer her on! The remote office affords so much freedom. Embrace it.

Creating a great work culture isn’t a task to be checked off, it’s a seed to be nurtured. We’re serious about making Litmus a place to do work you’re proud of without burning out. And that’s just the reason I love working here.


This article was originally shared on ReadThink

No comments yet.

Upgrade to join the discussion.

Already a member? Login

Upgrade to Unlock