You\u2019re an engineering manager of a growing medium-sized company. You\u2019re sitting at your desk and looking at your team, which is slowly outgrowing its allotted office space. You\u2019re pretty sure you\u2019re going to have to downsize desks or move to a bigger space to accommodate your team\u2019s new size.<\/p>\n\n\n\n
What if, however, you didn\u2019t have to look for a new office or get smaller desks? What if your office could embrace remote work or even, gasp<\/em>, become a distributed team? What are the benefits and drawbacks to each of these options?<\/p>\n\n\n\n We\u2019re going to look at the how different types of engineering teams (on-site, distributed, and remote) stack up in terms of culture<\/strong>, communication<\/strong>, hiring<\/strong>, and flexibility<\/strong>.<\/p>\n\n\n\n We’ll compare on-site teams to distributed teams to see what the major differences are between them and how to cope with the challenges of each model. We’ll then examine the major difference between remote and distributed teams and how to deal with one major challenge remote teams face.<\/p>\n\n\n\n By the end of this post, you\u2019ll know whether or not the grass really is<\/em> greener on the other side.<\/p>\n\n\n\n Looking for top talent fast? See how <\/em>Arc<\/a> can help you:<\/em><\/p>\n\n\n\n \u26a1\ufe0f Find developers, designers, marketers, and more Hire top talent with Arc risk-free \u2192<\/strong><\/a><\/p>\n\n\n\n Just to make sure we\u2019re on the same page, we will be using the following definitions:<\/p>\n\n\n\n Examples of on-site teams<\/strong>: Bank of America, Aetna, IBM, Yahoo, and Best Buy On-site teams, for the most part, have an advantage when it comes to cultivating a strong culture (although many distributed companies are giving them a run for their money). For one, it\u2019s easier to plan meetups, team dinners, and bonding activities when everyone is in the same place. Whether it\u2019s the same uniform, the same time zone, or the same air they\u2019re breathing, on-site teams have an easier time creating a strong culture.<\/p>\n\n\n\n While many big-name distributed companies use Slack (or other chatting applications) and have annual retreats to make up for team members not being in the same space, for people used to working on-site, working for distributed companies can feel lonely at times.<\/p>\n\n\n\n Though underrated, office cooler interactions contribute to company culture, team bonding, and can improve mood and productivity, which motivates distributed companies to try to make up for this gap as much as possible through electronic means.<\/p>\n\n\n\n On-site teams might suffer from culture issues if their corporate office (or startup founder) doesn\u2019t prioritize culture. If your company isn\u2019t invested in fomenting a strong culture, as an engineering manager, you can take it upon yourself to create one by planning dinners, after-work drinks, or weekend activities with your own team.<\/p>\n\n\n\n Big players in the distributed team realm have tried alleviating culture problems with annual retreats (all expenses paid), office cooler Slack channels, common strong values, or virtual events and team chats. While annual retreats are certainly easier to plan if your company has money to spare, Slack channels, Google Hangouts, and other virtual team bonding events are possible even with a limited budget.<\/p>\n\n\n\n Read More<\/strong>: Freelance Web Developer vs Dev Agency: Which is Best for My Project?<\/a><\/p>\n\n\n\n Communication is another area where on-site teams have an advantage. Need to talk to a coworker? Walk a few cubicles down. Disaster strikes? Emergency team meeting in 20 minutes. With an on-site team, you can discuss ideas together in front of a whiteboard, brainstorm for a new feature, or simply chat about your current project without having to wait for time zones to match.<\/p>\n\n\n\n With distributed teams, communication can be an issue, especially if employees are literally spread around the world. Technologically speaking, while we have whiteboards, screen sharing, and other ways around communication difficulties, unless there\u2019s a clear policy on working asynchronously, distributed teams might experience more delays in responses and feedback compared to on-site teams.<\/p>\n\n\n\n As an on-site team, if what you\u2019re doing is working, then you do you. If you need to catch up as an engineering team more often, consider holding daily scrums, weekly stand-up meetings, or just chatting informally as a team.<\/p>\n\n\n\n As a distributed team, invest in communication software, such as Slack, Zoom, Google Hangouts, etc., to help your team communicate as quickly and as efficiently as possible.<\/p>\n\n\n\n One other possibility is adjusting your mindset to working asynchronously. Consider making it official policy to empower team members to act rather than being on standby for another coworker\u2019s responses, which could make things run more smoothly and prevent bottlenecks.<\/p>\n\n\n\n Read More<\/strong>: 10+ Senior Software Engineer Interview Questions to Ask Your Candidates<\/a><\/p>\n\n\n\n As an engineering manager of an on-site team, if you\u2019re located in a tech hub, major city, or a town that people want to move to, you\u2019re probably doing better than most people.<\/p>\n\n\n\n While your candidate pool is limited to the people who want to relocate to your city, or who are already living there, it\u2019s not a death knell for hiring new talent if your location is trendy or desirable. However, if you\u2019re living in a smaller town, it might be harder (but not impossible) to convince top talent to move to your city just to work for you.<\/p>\n\n\n\n One benefit of a distributed engineering team is that you\u2019re not limited by geographical location when it comes to hiring. If your organization doesn\u2019t have rules stipulating employee citizenship or immigration status, the world is literally your oyster when it comes to hiring.<\/p>\n\n\n\n According to Eilon Reshef, co-founder and CTO of Gong.io, “Instead of taking the mediocre candidate in your area, you can hire the superstar who lives on the other side of the country. Limiting yourself to hiring within your locality restricts you to a small talent pool. You may be forced to settle for mediocre talent simply because you need the position filled. Companies that hire remote workers have a larger pool of top-notch talent.”<\/p>\n\n\n\n If you\u2019re living in a smaller town and need talent quickly to complete a project, consider hiring freelance developers to help you achieve your next deliverable if you\u2019re short-handed. Hiring a freelance developer can be a cost-effective and reliable solution to your need for talent if the local candidate pool isn\u2019t fulfilling your needs.<\/p>\n\n\n\n If you\u2019re an engineering manager for a distributed team, you have less of a supply problem. If you\u2019re having trouble onboarding hires, this article on how to onboard developers should help you bring your new distributed hire up to speed<\/a>.<\/p>\n\n\n\n Read More<\/strong>: Go Beyond the Whiteboard & Coding Skills to Find Talented Developers<\/a><\/p>\n\n\n\n One potential downside to being an on-site team is a lack of flexibility when it comes to employee retention. You\u2019ve probably experienced this if you\u2019ve had a stellar employee who everyone loved resigning because their family obligations necessitated a move. Unless your company allows some remote work, it\u2019s not uncommon to have to say goodbye to team members who can\u2019t stay local.<\/p>\n\n\n\n Imagine waking up out of bed, going through your morning routine, and being able to work without having to fight your way through traffic. According to studies, long commutes are big hits on health and productivity<\/a>.<\/p>\n\n\n\n Being able to work without fighting traffic means your patience levels are higher, your mood is better, and you generally feel more ready to work because it doesn\u2019t feel like half a day has passed already. That\u2019s one benefit to working for a distributed team, along with the freedom to move anywhere you want (although most companies would prefer overlapping time zones).<\/p>\n\n\n\n Unfortunately, unless your company supports remote work for employees, it might be difficult for you, as an engineering manager of an on-site team, to accommodate team members who need to relocate.<\/p>\n\n\n\n As a member of a distributed team, if your company offers flexible hours, no commute, and housing\/coworking space stipends, I don\u2019t know why you\u2019re reading this section about coping with distributed team drawbacks \ud83d\ude09<\/p>\n\n\n\n Read More<\/strong>: How & Why Hiring Remote Developers Builds Strong and Diverse Teams<\/a><\/p>\n\n\n\n If you\u2019re not sure what the difference is between a remote or distributed team, you\u2019re not alone \u2014 they have a lot in common.<\/p>\n\n\n\n Examples of remote<\/strong> teams: Basecamp, Help Scout, Trello, Clevertech, and Balsamiq<\/p>\n\n\n\n Remote and distributed teams face many of the same benefits and drawbacks, compared to on-site teams. Remote and distributed teams both offer flexibility and a bigger hiring pool while posing challenges when it comes to communication and forging a company culture.<\/p>\n\n\n\n One challenge that remote teams face that distributed teams may not is the potential isolation of remote team members. This is because of the nature of a remote team: they\u2019re somewhere in between on-site and distributed teams on the modern engineering team spectrum.<\/p>\n\n\n\n Unlike on-site teams, not all team members work at headquarters. Unlike a distributed team, some team members work at headquarters while some don\u2019t. For team members who used to work at headquarters and became remote to remain at their company, the transition to remote work can be jarring.<\/p>\n\n\n\n The challenge that remote engineering teams face is the potential isolation of remote team members. While not everybody prefers working on-site and chatting around a water cooler, some team members do enjoy a strong culture.<\/p>\n\n\n\n They are the team members who may feel isolated and out of the loop if they can no longer be included in team conversations because of time zone differences or their not being physically present.<\/p>\n\n\n\n Read More<\/strong>: 10+ Robert Half Alternatives: A Comparison of Top Staffing Agencies<\/a><\/p>\n\n\n\n One way to cope with this challenge is to borrow policies of inclusion from distributed teams to help remote team members feel like they still belong to the engineering team and company. Distributed teams make extensive use of Slack channels or virtual hangouts, and remote teams can borrow from this.<\/p>\n\n\n\n Creating a #watercooler channel, a #random channel, or #general channel can help remote team members feel in the loop and included in company events (we do this at Codementor!). Virtual hangout sessions once a month, invitations to scrum meetings, and all hands on deck meetings that remote employees attend with on-site teammates build cohesion and facilitate team bonding.<\/p>\n\n\n\n Some remote-friendly companies even go the extra mile and fly in remote team members to headquarters once or twice a year so that remote team members can meet the rest of the team and feel included.<\/p>\n\n\n\n Understandably, not every remote company can afford to fly in a team to headquarters or an exotic locale for bonding purposes. That being said, virtual events, hangout sessions, or even a chat room can go a long way in fostering a positive environment, strengthening culture, and improving morale among all members of a remote engineering team.<\/p>\n\n\n\n Read More<\/strong>: 21+ Important Freelance Interview Questions to Ask Software Engineers<\/a><\/p>\n\n\n\n While, of course, every company has its own needs, culture, and budget, hopefully these pros and cons have given you food for thought or fodder for a conversation with the head honcho.<\/p>\n\n\n\n At the end of the day though, there is no one size fits all \u2014 in fact, there are many factors behind a company\u2019s decision to have an on-site, remote, or distributed engineering team \u2014 so enjoy growing with your team with whatever model fits you best.<\/p>\n\n\n\n Do you have a preference for on-site, remote, or distributed teams? Are you thinking about transitioning from one type to the other(s)? Let us know in the comments!<\/p>\n\n\n\n You can also try <\/em>Arc<\/a>, your<\/em> shortcut to the world’s best remote talent:<\/em><\/p>\n\n\n\n \u26a1\ufe0f Access 450,000 top developers, designers, and marketers <\/a>Try Arc and hire top talent now \u2192<\/strong><\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Read about the pros and cons of on-site, remote, and distributed engineering teams to find which structure would work best for your needs.<\/p>\n","protected":false},"author":4,"featured_media":1224,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,5],"tags":[],"class_list":["post-1223","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-hiring","category-management"],"yoast_head":"\n
\u26a1\ufe0f Freelance or full-time remote + fully vetted<\/em>
\u26a1\ufe0f Save up to 80% with global hires<\/em><\/p>\n\n\n\nOn-Site Team vs Distributed Teams<\/h2>\n\n\n\n
Examples of distributed teams<\/strong>: Zapier, Buffer, Hotjar, Automattic, and InVision<\/p>\n\n\n\nBuilding a Strong Culture<\/h2>\n\n\n\n
On-site Teams<\/h3>\n\n\n\n
Distributed Team<\/h3>\n\n\n\n
How to Cope<\/h3>\n\n\n\n
Improving Communication<\/h2>\n\n\n\n
On-site Team<\/h3>\n\n\n\n
Distributed Team<\/h3>\n\n\n\n
How to Cope<\/h3>\n\n\n\n
How to Hire Talent<\/h2>\n\n\n\n
On-site Team<\/h3>\n\n\n\n
Distributed Team<\/h3>\n\n\n\n
How to Cope<\/h3>\n\n\n\n
With Great Flexibility Comes Great Responsibility<\/h2>\n\n\n\n
On-site Team<\/h3>\n\n\n\n
Distributed Team<\/h3>\n\n\n\n
How to Cope<\/h3>\n\n\n\n
Remote Teams vs. Distributed Teams<\/h2>\n\n\n\n
A Specific Challenge for Remote Teams<\/h2>\n\n\n\n
How to Cope with This Challenge<\/h2>\n\n\n\n
Conclusion<\/h2>\n\n\n\n
\u26a1\ufe0f Vetted and ready to interview<\/em>
\u26a1\ufe0f Freelance or full-time<\/em><\/p>\n\n\n\n