{"id":9764,"date":"2018-09-28T00:35:14","date_gmt":"2018-09-28T04:35:14","guid":{"rendered":"https:\/\/qxf2.com\/blog\/?p=9764"},"modified":"2018-09-28T00:35:14","modified_gmt":"2018-09-28T04:35:14","slug":"the-pros-and-cons-of-running-a-remote-first-company","status":"publish","type":"post","link":"https:\/\/qxf2.com\/blog\/the-pros-and-cons-of-running-a-remote-first-company\/","title":{"rendered":"The pros and cons of running a remote-first company"},"content":{"rendered":"

Remote work comes with its own set of trade-offs that need to be managed. This post is about the positives and negatives of running a remote-first company along with some of the tools we use and the adjustments that have worked for me.
\n <\/p>\n

About me<\/h3>\n

I am Arun and I run Qxf2 Services<\/a>. Qxf2 provides testing services for startups. We work well with small engineering teams and early-stage products. Since late 2015, all my employees have been working from home. We meet in person (Bangalore, India) four times a year. We meet as a group twice a year for half-yearly company updates, once a year for a Hackathon and once a year for a team outing. Additionally, every employee meets me in person for their first annual review. <\/p>\n

 <\/p>\n

\"remote
\n <\/p>\n

Advantages of running a remote company<\/h3>\n

1. I can hire experienced people from anywhere in India.<\/strong>
\nI limit employees to India because I am too small (12 employees) to deal with all the paperwork needed to employ people from all over the world.<\/p>\n

2. My employees do not waste time in traffic.<\/strong>
\nNot having to drive is a BIG perk for people living in India.<\/p>\n

3. I have fewer personality conflicts to deal with<\/strong>
\n… but this could just be a side effect of being a really small company.<\/p>\n

4. My employees develop better remote working skills.<\/strong>
\nThis helps a lot since all my clients are abroad. <\/p>\n

5. I save on office rent.<\/strong>
\nRenting commercial space is a relatively large overhead for a small company like mine.<\/p>\n

 <\/p>\n

Disadvantages of running a remote company<\/h3>\n

1. I find it hard to hire junior engineers.<\/strong>
\nIn India, folks with 0-3 years of experience prefer having a collegiate culture with their colleagues. I do not blame them. I’ve seen the culture work well for them. They share knowledge and split work amongst themselves. It is hard to cultivate a collegiate culture when you work remote. So junior engineers do not like working in fully remote companies. The inability to hire junior engineers hurts me as a services business because I get better margins on more junior folk.<\/p>\n

2. Many senior people do not want to join my company.<\/strong>
\nSenior people that I interview request me to be more flexible about being remote-only. They would like to have better visibility into their direct reports. They \u2018feel like they are managing\u2019 if they can see their direct reports working. This objection wasted so much time during the phone screens that I have had to list ‘we are a distributed team’ as a negative<\/a> on our careers page<\/a>.<\/p>\n

3. Swanky offices are a genuine status symbol.<\/strong>
\nThe lack of posh office space is a major downer for a lot of people. People would like to bring their relatives and show off a fancy office and well-dressed colleagues.<\/p>\n

4. We have weak personal connections with our colleagues.<\/strong>
\nMy employees often complain that “we do not really know our colleagues”, “we do not get together often enough”, etc. This is a genuine problem. I have heard this complaint from a majority of my employees.<\/p>\n

5. ‘Work from home’ is misinterpreted as ‘easy work’.<\/strong>
\nMany of our friends and relatives misinterpret ‘remote work’ to mean ‘less work’. E.g.: “I have this errand in the middle of a weekday. Come with me. You work from home anyway.”<\/p>\n

Bonus:<\/strong> You can read about the perspective of one my employee here<\/a>.
\n <\/p>\n

If you read through the downsides of running a remote company and are still open to the idea, I have a few extra pointers for you.<\/p>\n

I. Our toolbelt<\/h3>\n

We rely a lot on written communication – documentation, blogging, code, and drawings\/sketches to stay informed. We use Trello, BitBucket, Github, Google Calendar, Hangouts, Google Drive, Evernote, and Skype. We also meet (on Hangouts) every Friday for an hour to review the work from the past week. Everyone briefs the team about the work they did with clients or talks about internal Trello tickets they worked on during the week. Near the end of the meeting, we discuss upcoming leave plans and what to expect in the coming week.<\/p>\n

 <\/p>\n

II. Adjustments that worked for me<\/h3>\n

a. Framing remote work as a challenge and not as a perk.<\/strong>
\nEmphasize remote working challenges right from the first day. I have found that if I stay silent about the challenges of remote work on the first day, employees fill up that vacuum with their own mental models of remote work. So during our employee orientation, I mention adjusting to remote work as one of the hardest challenges that the new hire will face. That usually gets the new hire thinking and asking more questions about how to become a better remote worker.<\/p>\n

b. Being patient about temporary dips in productivity.<\/strong>
\nExpect a dip in employee productivity around the sixth month. My experience is that newly minted remote employees are super-productive for the first few weeks. But once the novelty wears off, there is a visible dip in their productivity. This phase, depending on the person, seems to last for about 2-8 weeks. Being patient with the employee during this phase has worked out well for me.<\/p>\n

c. Correcting poor writing habits quickly.<\/strong>
\nWhen all your colleagues are in one place, you get sloppy about leaving a written trail for your work. Often, it is enough to have a conversation in the hallway. Writing is not a big priority. But when you work remote, writing down ideas is critical. So make sure you correct any poor writing habits early. I still feel really odd nitpicking writing habits of experienced engineers but the results have been good. Note:<\/strong> I am not referring to grammatical mistakes here. I am more concerned about how well people communicate their ideas through writing.<\/p>\n

d. Helping people communicate error messages better.<\/strong>
\n“Hey, I have a problem. Can you come take a look at my screen” is a practical problem-solving approach when you are co-located with your colleagues. People who are new to remote working are going to be trying something similar and it is going to feel pretty jarring. Be patient and understand that they are not being lazy or dumb. They are just continuing old habits. Help new employees express their error messages better.
\n <\/p>\n

I hope this post has given you a more realistic idea about running a fully remote company!<\/p>\n

\n","protected":false},"excerpt":{"rendered":"

Remote work comes with its own set of trade-offs that need to be managed. This post is about the positives and negatives of running a remote-first company along with some of the tools we use and the adjustments that have worked for me.   About me I am Arun and I run Qxf2 Services. Qxf2 provides testing services for startups. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[70,128],"tags":[],"class_list":["post-9764","post","type-post","status-publish","format-standard","hentry","category-qxf2-culture","category-remote-work"],"_links":{"self":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/9764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/comments?post=9764"}],"version-history":[{"count":20,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/9764\/revisions"}],"predecessor-version":[{"id":9866,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/posts\/9764\/revisions\/9866"}],"wp:attachment":[{"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/media?parent=9764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/categories?post=9764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/qxf2.com\/blog\/wp-json\/wp\/v2\/tags?post=9764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}