Team communication optimized for deep work.
Meet Sarah, the founder of CoffeeKit and waffle lover. CoffeeKit helps boutique coffee shops manage their business operations.
The year is 2018 and coffee hipsterdom is spreading like a stream of espresso exiting a portafilter at 9 bars of pressure.
Mustache wax and fedora hats are in short supply.
If you were to be dropped into any American urban city from outer space, you’d think you were in Portland, Oregon.
Suffice to say, business is booming for CoffeeKit and its team of designers, developers, marketers, and support folks.
CoffeeKit uses Level to communicate.
Monday morning has arrived.
After eating a waffle, Sarah starts her workday by checking her Level Inbox.
First up, Joe Gibraltar posted a direct question for Sarah in the Engineering group. He made sure to @-mention her so that the post would land in her Inbox.
Joe’s question is important, but not immediately urgent — it can wait until Sarah has accurate info to pass along. Sarah decides to come back to it later, and she’s not afraid of forgetting because the message will remain in her Inbox until she takes action.
There’s a chance someone else on the Engineering team will see it and chime in to help in the meantime. But it won’t show up in anyone else’s Inbox unless they deliberately join the conversation.
The Inbox is like an extension of your brain. It remembers what’s on your plate, so you don’t have to.
One of Sarah’s older posts has also landed in her Inbox because her teammate Lisa replied to it.
Sarah fires off a response and dismisses the post from her Inbox. Dismissing the post keeps Sarah's "to-do list" clean. If someone replies again later, the post will scoot back into her Inbox.
Finished with her Inbox (for now), she jumps to her Activity feed to skim through other conversations that have happened around the space.
She sees one that interests her. It so happens that Kevin and Lisa are also there, and a spontaneous real-time conversation ensues!
Serendipity brought them together to hash out the details this time. But if Lisa and Kevin had been focusing on other tasks when Sarah stopped by, she could have just left a note for them to see later.
Level assumes that most conversations are not urgent enough to pull makers out of their deep work.
Once everyone is done chatting, Sarah marks the post as resolved to signal to the rest of the team that the conversation is done.
There’s a chance that Sarah won’t see every post like this one. That’s actually preferred! It’s neither possible nor necessary for any single person to follow every conversation.
Level encourages teams to be explicit about communicating who needs to see and respond to messages.
Now that she’s sufficiently caught up, Sarah closes the tab and gets to work.
No red dots will beckon Sarah to come back to Level. She will not receive any push notifications — unless a real emergency happens. No presence indicators will imply that she is “available” to interrupt.
When it’s time to get to work, Level leaves you alone.
Sarah can confidently get in The Zone, knowing that she will not have to deal with a hellscape of red dots and stress about missing important messages that are jumbled up with idle chit-chat.
Do you want your day to look more like Sarah’s?