How Doist Makes Remote Work Happen – Ambition & Balance
When I first started at Doist, we were 3 people working from 2 countries. Today, we’re 51 people working from 20 countries and counting. The idea of building a remote company wasn’t something we explicitly discussed at the start — it simply grew out of necessity.
One of the challenges when you start out as a bootstrapped company with an unknown brand and little cash on hand is access to talent. Amir and I were working from Santiago, Chile, and at that time we hadn’t come to understand the ins and outs of the country well enough to find the right people locally. When Amir decided it was finally time to hire someone to help answer support tickets, he struck gold with Doist’s first employee, David, on the global freelance platform Elance (now Upwork).
That first hire set us down the remote-first path. David was providing support out of Poland, and Roman was coding from Belarus. When Brenna, a contact of Amir’s from Start-Up Chile, was hired as Head of Marketing she never came to work from the office in Santiago even though she lived just 15 minutes away!
How do you build a high-functioning, united team without face-to-face interactions? This post is a reflection on our journey and the key things we’ve done that have been fundamental to thriving as a remote team. They’re issues all companies face, but ones that present unique challenges when you don’t see each other face-to-face every day. We’ve adapted with ways of working that we think any company could benefit from, but are especially pertinent for people looking to grow their own remote teams.
For us, it starts with a laser sharp focus on hiring the right people.
Hiring calmly & carefully
As a bootstrapped company, we’ve always had a conservative approach to scaling the team. We know that more people doesn’t necessarily equal greater output, and we don’t hire faster than the culture can absorb new team members. Employee headcount is something we consider a vanity number — it says little about how well the company is actually doing.
Screening for values
When we hire, we look specifically for people who share the same fundamental values as us. That’s not to say we hire cookie cutters replicas of ourselves — our diverse perspectives 100% lead to better decisions, a better product, and a better team culture — but everyone needs to be on the same page in terms of how we communicate and work.
Micromanaging is inefficient at any company, but at a remote company it’s simply not an option. You need to hire people you can trust from day one.
As in any growing company, we’ve made hiring mistakes, but we’ve worked hard to learn from them. One thing we’ve realized is that technical skills alone aren’t enough. If your teammates don’t truly believe in what you’re trying to accomplish as a company, it’s difficult to keep everyone on a remote team rowing in the same direction.
That’s why applications without a cover letter are an outright deal breaker for us. We reject it without even looking at the person’s resume. We’re often criticized for this and, yes, we miss out on candidates with great experience and technical skills. But we’re okay with it. Clear communication, passion, and craftsmanship are some of our core values, and a personal cover letter aids us in screening for these. A well-written cover letter gives a clear indication of whether the candidate is just interested in the prospect of a remote job, or if they’re excited about being part of the solution to the specific problems we’re working on.
After that initial application screening, we don’t make a job offer unless the person has undergone at least one test task and at least three interviews with three different Doisters. Interview questions are often directly related to our values. There aren’t necessarily right or wrong answers to these, but they are very helpful to raise red flags that might indicate a potential value mismatch.
Looking for “Jack & Jills of all trades”
When everyone on the team is remote, it’s vital to hire proactive, curious people who won’t wait for a specific set of instructions. That’s why one of the most important things we look for in interviews are “Jacks & Jills of all trades” — people who take ownership over learning new skills.
We ask questions to see not only if this person has the role-related knowledge necessary for the job, but will they be able to take on new responsibilities if needed? Do they have a general interest in expanding beyond their own field? Are they curious about things outside of what they’re already competent in? Some of our favorite interview questions are:
- “Tell us about something new you recently taught yourself.”
- “What’s something you want to get better at professionally?”
- “What’s something you’ve totally geeked out about recently (doesn’t have to be about work)?”
If it’s not a “Hell Yeah!”, it’s a no
In the end, all interviewers must vouch strongly for the candidate as a great fit. We refer back to Derek Sivers’ No “yes.” Either “HELL YEAH” or “no” mentality in making all hiring decisions. We don’t have an exit plan — we want to build a company that outlives us. This is an ambitious goal, and we only stand a chance to realize it if we manage to hire people who truly believe in what we’re doing.
An employee-centric, sustainable vision
One of the biggest challenges in adapting to remote work — particularly once you’ve been successful hiring smart, proactive people who are excited about the job they’re doing — is knowing where to draw the line between work and life. When you’re in complete control of how you spend your time, it’s hard to ever feel like you’ve done enough. However, we believe strongly that to be a sustainable business, employees need to be able to have rich lives outside of work too.
We set the expectation from the get-go that no one should be working long hours or during the weekends. (Support is the exception to the rule, but they get equivalent time off after a weekend shift.) Eight hours of effective work five days a week is more than enough to get everything done (we are in the productivity business, after all). We enforce this rule strictly! It’s never acceptable to post an out of office notice to the team that includes any type of phrasing like “I’ll be mostly offline, but if needed you can reach me at xxx.” We have some pretty creative writers on the team who never fail to rephrase offending posts with a funny touch.
We’re all role models and things like this can easily creep into the culture even if only a few people start breaking the rules. This means that if a team member responds to a message while they’re supposed to be off, the person is gently but firmly suggested to log the heck off!
To help hold ourselves accountable, we implemented a new vacation mode feature in Twist, our team communication tool, so that we can set ourselves as “away” ahead of time. While in vacation mode, all notifications are turned off and a special vacation avatar automatically replaces our normal one. It serves as a reminder for everyone to be mindful of their teammates’ time off and know that, if they do send a message, they shouldn’t expect a response until that person is back at work.
We’ve also tried to reflect a commitment to work-life balance in our employee perks. We need our team members to thrive for many years to come and it’s important we all stay mentally and physically healthy. Some of the perks we offer to support this philosophy are:
- Mandatory five weeks of paid vacation per year in addition to national holidays in your country of residence.
- Mandatory eighteen weeks of paid maternity leave and five weeks of paid paternity/adoption leave.
- Flexible work schedule with no requirement to be online at any certain time
- Work from the global location of your choice as long as there is access to a stable Internet connection
- A co-working office of your choice for anyone who needs to get out of the house and be around people
- Monthly reimbursement of exercise activities
- Healthy snack stipend
- Education stipend
- And more.
Making sure the way we communicate aligns with our values
Perks are great, but they only go so far in building a unified, productive remote team. The true cornerstone of our company and culture — the reason we’ve been able to become a leader in an incredibly crowded market — is the way we communicate.
Meetings are a rarity at Doist. We have very few regular meetings and generally only schedule ad hoc ones when we feel that “face-to-face” communication is necessary to move a project forward.
Nowadays, the only time we use internal email is when a new team member is onboarded.
95% of our team communication is asynchronous (as opposed to real-time like meetings or group chat) as well as transparent and searchable (unlike email). Keeping communication fully accessible to the whole team supports one of Doist’s core beliefs: the best argument always wins — regardless of who you are, your title, or your seniority. It’s impossible to live by such a rule in a remote structure unless you have a centralized place with full transparency around what’s going on, including decision-making.
Learning from Slack
Before we built Twist, we actually used Slack. It was a great tool — fun and easy-to-use (who doesn’t love a good GIF?). And it certainly helped us feel more like a team than disconnected individuals. But it had other negative side effects. Keeping up with Slack conversations started consuming more and more time. People felt they had to be online constantly to not miss out on something important. This quickly became a glaring problem.
Individuals in outlying timezones, or those who went offline for extended periods during the day to do deep work, were excluded from conversations. The work-life balance we cared so deeply about was under immense pressure. We realized that the kind of communication Slack was set up for didn’t support our values of clear communication, craftsmanship, balance, focus, and impact. We could see it was taking a toll on people, but when we looked for alternatives, it seemed that the whole market was following a similar real-time, group chat model.
It was then that we decided to double down on the product development of Twist. After just 4–5 months, we moved the entire team — and all of our company’s communication — from Slack to Twist in one go. It was rough. I recall having calls with colleagues about how we felt Twist just didn’t do it for us, we were missing Slack and all its bells and whistles.
Today the product has matured a lot, and I can honestly say that Twist has become the heartbeat of Doist. Threaded communication keeps all our conversations organized by topic so a designer in Taiwan can catch up and contribute to a discussion that happened 10 hours ago during US work hours. Work rarely happens outside of Twist, even in the small office we have for the contingent of six working from Porto, Portugal. Whenever issues are discussed offline or on calls, the outcome of these discussions is always shared with the relevant teammates on Twist.
Remote first = Async first
Everyone at Doist knows that asynchronous communication is the default, and no one should expect an immediate response from their teammates. Not only does this make working with people in other time zones possible, but it also gives people the freedom to disconnect to focus completely on their work and come back to respond later.
In Twist, threads keep everything separated by topic so people don’t get left out of entire conversations because the group chat moved on to other things. It’s how we’re able to strike a balance between meaningful productivity and productive communication.
Transparent and accessible
The vast majority of our Twist channels are public, so even teammates who weren’t directly notified about a discussion can browse or search for the whole conversation. Because everything’s organized by topic, it makes it easy for someone to search for the information they need and get all of the context of the original conversation without having to wait on someone else who might be asleep halfway across the world.
This accessibility of information has also had an unintended benefit of making new employee onboarding incredibly easy. We just add new teammates to relevant Twist channels and they can browse at their leisure to learn more about specific topics. They get to see exactly how we work together to get feedback, troubleshoot issues, and make decisions from start to finish. It’s been an awesome way to immerse new employees in how our company operates and for them to get up to speed on what’s currently going on without any added work on our end.
Of course, when anything in the conversation becomes actionable we add a task or create a new project in Todoist with a link back to the original Twist thread for reference.
Other tools in Doist’s remote work toolbox
We’re proud “dog-fooders” of our own products, but in a diverse and fully distributed team we can’t make do with just Todoist and Twist.
The design team consists of eight people located in six countries: Portugal, England, Germany, Spain, Greece and Taiwan. They use Sketch, Adobe Creative Suite, Dropbox, Dropbox Paper, Marvel & Zeplin for collaborating on everything from new feature UX/UI design to landing pages to blog post illustrations.
Our support team consists of people in Brazil, Canada, Jamaica, Poland, Spain, United Kingdom and the Philippines, and they collaborate to support our customers in Zendesk.
Of course, our developers use Github.
Team retreats
Since we don’t have what we consider a physical headquarters, we looked at what other companies did to bring people together. The outcome was to allocate money for a yearly retreat to bring everybody together in one place to get to know each other better, bond, and have face-to-face discussions.
In 2015 we went to Menorca in Spain, last year we flew everybody to Iceland, and just recently we met 50+ people in Athens and had a whale of time together. We spend a relatively small amount of time in formal work sessions, and the rest of the time exploring the beautiful places we’re in and having impromptu conversations with people across teams.
Those retreats undoubtedly help bond the team together and reignite energy in what we’re working toward, but the fact is that it’s just one week a year. Everything else we do throughout the year to live up to our professed values is much more important.
Current challenges and experimentation (a.k.a. growing pains)
As our team grew to 30–40 people last year, we started to feel the need for a system to keep everybody on the same page to maintain a high level of productivity. It got harder to follow what was going on and who was in charge of what. Deadlines weren’t getting met (or even set in some cases). We had to ask ourselves how we could stay productive and grow the team at the same time.
Initially we tried to implement an Objectives and Key Results (OKR) system similar to what Intel and Google use — it didn’t go well. OKRs helped promote transparency, but they didn’t help us define exactly what projects would ship across which teams and when. There was still no accountability to deadlines, tracking and updating the system added a lot of overhead, and it didn’t provide a clear framework for people to align their individual work priorities when there were dependencies in projects across teams.
To try and solve that last problem, we attempted to adopt Spotify’s Engineering Culture System which uses the concept of having Squads that consist of small, autonomous, cross-functional teams. That didn’t work super well “out of the package” either. Their system was optimized for teams located in the same office and for a large enough company where dedicated, multidisciplinary resources are available for each squad.
The DO system
Ultimately, we created our own hybrid of the two systems — goals and squads — in what we call the DO (Doist Objective) System. The system is output-focused rather than outcome-focused. That is, our quarterly goals consist of things we have full control over shipping. For example, one Quarter 2 goal is “ship version one of the Todoist Help Center redesign”.
A short-term, cross-functional squad is created for each DO — in the example above, a product marketer/copywriter, a designer, and a front-end developer. A squad leader is tasked with setting timelines and coordinating the project from start to finish. Each squad has a dedicated Todoist project to track tasks and deadlines and a Twist channel for high-level communication so there’s never a question of where to find the relevant information.
It’s still very early on in our implementation of DOs and we’re bound to run into new issues that we’ll have to adapt to (the way we work is always an iterative process after all). But we feel like the DO system is a better fit for how we work — light on process with a focus on shipping concrete things quickly — and addresses the big issues we face in coordinating a larger team. The whole company now knows which projects should receive the highest priority. Temporary squads are created as needed and are kept small to minimize communication overhead. And there’s a single person responsible for setting and enforcing deadlines.
We’re still learning, but we hope to evolve the DO system into a tested methodology that other remote teams can adopt and improve upon.
The future of work
We feel that we’ve managed to create a remote environment in which people can thrive, grow and strike a healthy work-life balance. In the six years Doist has existed as a commercial product, only three people have voluntarily left the company. All three of them went to start their own projects.
We believe that remote work is the future, but companies (Doist included) have a long way to go to develop all of the best practices and processes to support it. We’re excited to be a part of solving these problems and building the future we want to work in.
Have questions about the way we work? Ask away. We’re happy to share and learn from you too.