Working Remote vs. In-Person. Is there a balance?

December 2, 2019
Working Remote vs. In-Person. Is there a balance?

There’s a battle being waged around the world—a battle between companies all-in on working remotely and those who prefer the traditional model of showing up to work each day. Okay, maybe it's not quite a battle. But, in an increasingly connected world, a growing number of companies are struggling to decide if mobile is right for them.

Companies like Gitlab are so big on the idea of working remotely even their CEO works out of his apartment. Without even a single company office or workspace, Gitlab has built an entire organization around mobile. On the opposite front, companies like IBM are adopting policies requiring an in-person workforce: NBC News.

At Michigan Software Labs, the question on where we stand comes up often in the interview process, especially among developers. When you consider how many of our clients aren’t in the same city as our office, it’s a fair question. Given the already remote nature of our client interaction (apart from the valuable time when we visit our clients or they visit us), the more cohesive our internal team, the better we’re able to serve our clients.

Research suggests that, while full-time remote work may be great for individual productivity, engagement and collaboration tend to suffer. At Michigan Software Labs, we see a dichotomy at work: while our developers and designers require individual time, we depend on teamwork to create the best software products. We lean on collaboration so much that our organizational structure is referred to as “Teams at MichiganLabs.”

As a rule, we avoid putting an individual on any given project. And, rather than having managers or directors, we have project Leads who are a co-equal on the teams they serve. Working together is core to our DNA. Then again, so is empowering individuals to do their best work by providing quiet, uninterrupted time to enter into a flow state.

For us, the question isn’t whether it takes fully co-located teams to facilitate teamwork, or whether we go fully remote to get greater individual contribution—the question is how we can get the best of both worlds. To that end, we’ve put a few key practices into place.

1. Work-From-Home Wednesdays

Our balanced approach is best embodied by Work-From-Home Wednesdays. From the very beginning, team members could choose to stay home on Wednesdays. Actually, we let them choose their day at first, then quickly saw how it erodes team cohesiveness when people chose non-overlapping days.

Work-From-Home Wednesdays are ideal for intense, individual work. In fact, we avoid scheduling calls (apart from our morning standup), so team members have the flexibility they need. Team members also appreciate the added benefit of being able to schedule doctor appointments, home repairs, etc.

Another benefit of a consistent remote workday is that our entire IT infrastructure and business processes can support it. An occasional snow day or an afternoon out of the office for a home repair has little or no impact on how we operate as a team.

2. Do Not Disturb

On days when teams are fully present, we depend on working rhythms to balance individual work with collaboration. These rhythms are so important to us, we’ve installed Do No Disturb signs on each workstation. The system even goes so far as to deactivate Slack notifications. We found that when our company was smaller, working rhythms came naturally; coworkers knew what others were working on and the office fell into patterns of silence. After an hour or two, everyone lifted their heads for a break. As the number of teams occupying the same space has grown, we needed to come up with more intentional ways to cue company-wide deep work. Do Not Disturb has been an effective tool.

Michigan Software Labs
Team working together in Code Base

3. Space that fits how we work, not the other way around

Another way we equip co-located teams is with breakout spaces suited for longer meetings. Knowing that collaboration is ideally face-to-face, we balance spaces for interaction with spaces for individuals to focus. It’s not always easy, but by offering a variety of spaces (smaller enclaves, larger conference rooms) project teams are able to find their own working rhythms.

Ultimately, the challenge isn’t between in-person vs. remote work. It’s how to make room for both, so that teams feel supported and individuals have the flexibility they need to thrive. Over the years our practices have evolved (and will continue to as we pick up new ideas). What will never change is our focus on creating software that elevates business and makes life better for users.

Joshua Hulst
Joshua Hulst
Co-founder & Managing Partner

Stay in the loop with our latest content!

Select the topics you’re interested to receive our new relevant content in your inbox. Don’t worry, we won’t spam you.

App Architecture Series: Building a Better User Interface

App Architecture Series: Building a Better User Interface

October 21, 2019

At Michigan Software Labs, we don’t simply write code to satisfy requirements. We find ways to solve problems efficiently and effectively. Knowing that a well-structured application comes down to a set of techniques and patterns, I have been exploring design pattern theories and how they shape our thinking.

Read more
Michigan Software Labs #65 on Inc. Regionals Fastest-Growing Companies
Press Release

Michigan Software Labs #65 on Inc. Regionals Fastest-Growing Companies

March 11, 2022

Inc. magazine today revealed that Michigan Software Labs is No. 65 on its third annual Inc. 5000 Regionals Midwest list, the most prestigious ranking of the fastest-growing private companies based in Iowa, Illinois, Indiana, Kansas, Michigan, Minnesota, Missouri, North Dakota, Nebraska, Ohio, South Dakota, and Wisconsin. Born of the annual Inc. 5000 franchise, this regional list represents a unique look at the most successful companies within the Midwest region economy’s most dynamic segment–its independent small businesses.

Read more
Quickly Prototyping a Ktor HTTP API
Development Web

Quickly Prototyping a Ktor HTTP API

August 18, 2022

Whether it’s needing a quick REST API for a personal project, or quickly prototyping a mockup for a client, I like to look for web server frameworks that help me get up and running with minimal configuration and are easy to use. I recently converted a personal project’s API from an Express web server to a Ktor web server and it felt like a breeze. I’ll share below an example of what I found and how easy it is to get a Ktor server up and running.

Read more
View more articles