Hi there! 👋

Someone from our team probably linked you here to share more about how we think about meetings and time.

Our primary focus is solving the metabolic health crisis – but ****we're also building a remote-first company from the ground up. That means we're doing things a little differently than most companies.


Remote-first culture

We're an all-remote team, with members distributed in timezones across Canada, the United States, Europe, and Latin America.

Everyone on our team works whenever and wherever is most conducive for them. Designing this culture creates many benefits for our team members and partners, but requires effort to maintain.


Synchronous time is expensive

Since we don't have an office and can't rely on everyone being in the same place at the same time, we tend to lean on asynchronous processes instead of synchronous meetings**.**

We keep meetings of all kinds to a minimum, both inside and outside of the company. Recurring status meetings were the first to go when we set out to build this culture, and we've set a very high bar for scheduling ad-hoc meetings.

We've been surprised at how effective work can still be without those meetings, and we hope you find the benefits of working with us in this way, too.

If someone asks for a meeting that might be better suited with asynchronous work, consider writing them back with something like, "My synchronous time for meetings is pretty limited the next couple weeks. Mind if we trade some notes by email to start?"


So, what do you do instead?*

Rather than schedule meetings as our default for coordinating on projects and discussing information internally, we resort to three processes that suit this workflow. They include:

Here's an example of a Memo

Levels Press Strategy - July 2020

****The purpose of this document was to get alignment around how we approach press at Levels.

****We put this together without a single meeting, and every person in the company had a chance to contribute to it. It only took a few hours of time to write, revise and ship, and it was completed from start to finish in two days.

Here's a Loom that was created in reply to an email requesting to meet. It didn't require any scheduling or waiting, and can be shared repeatedly.

****🤝 Request to Meet Loom Response

Sam Corcos, Levels CEO and co-founder, often gets asked to meet. When mentorship opportunities come up, he loves to act on them, but only has so much time to process all the requests. As such, he recorded a Loom for some students that were requesting to meet and learn about Levels.

Here's an example of a well-crafted email that we would send to our internal team

The email outlines a clear purpose, action, and timeline for next steps.

It is easy to digest for anyone who reads it, and there isn't confusion about what to do next.