We have many teams that use Loop Team daily in different ways. Below are some of the most common best practices:

Invite your team

To experience the benefits of presence, it's important that your core group of team members be on Loop Team for collaboration. You don’t need to invite your whole company, but start with the 5 or 6 people that you frequently collaborate with to get started

Organize by timezone

If your team is globally distributed, organizing your view by timezone really helps to provide a sense of empathy in that you know it's almost end-of-day for your colleague or other.

Keep activity presence on

Seeing activity provides real presence. It makes you feel as if you're in the office and gives you context as to who is around and who you can shoulder-tap. Often, you can when someone might be working on something you were discussing previously making it an opportune time to connect and collaborate. You can also infer when someone might be in deep work and you don't want to interrupt. As a side note, we're making more improvements here to more reliably tell you when Loop Team thinks someone is in deep work.

Keep Loop Team on

It's no fun being in a virtual office if everyone is offline. You can control much of this through Loop Team, such as your status, office hours and more.

Create office hours

We have multiple buckets of teams using Loop Team in different ways but some do create office hours so random interruptions don't occur (which isn't a behavior we generally see). During these office hours, team members actively drop-in on each other, collaborate and then get back to deep work.

Create rooms for topics and small group recurring meetings

Start with rooms for daily standup but also create rooms for topics (eg onboarding, design or other).

Record and share conversations

Turn on recording and share the conversations. While recording is on, other team members can follow live and see topics being discussed without joining. This is the closest thing to experiencing real-life background conversations that drives much of the office serendipity.

Sharing the discussions after the conversation to the workspace feed allows team members to get context of what discussions may have ensued that they missed.

Did this answer your question?