This Guide is made under the sea by www.sirena.app.

Glossary:

SSOT (Wiki) = Single source of truth.

Why remote?        1

Physical Setup:        1

Space:        2

Do Not Disturb:        2

Infrastructure:        2

How do others see you?        2

Own your calendar:        3

About emergencies:        3

About the meeting:        3

Meeting Moderator and team players:        3

SSOT (Wiki) (“single source of truth”) AKA --> WIKI:        4

Cultural change:        4

About project management:        4

Communication:        5

Prioritized communication channels from more to least urgent:        5

Tips        5

Recruiting        5

Onboarding:        5

General Suggestions:        6

When you are working and traveling at the same time        6

Why remote?

Claims that open-plan offices encourage interaction between coworkers frequently ignore complaints about how these informal interrupts make it hard to do any focused work.

We’ve found that remote allows us to have the best talent for Sirena, while improving our productivity.

Physical Setup:

  • Avoid making calls from locations where you can be interrupted or interrupt others.
  • Make it easy for others to see if you are OK to interrupt, versus “Do Not Disturb”

Space:

  • Setup a dedicated professional home office space with an ergonomically correct desk, good cameras and microphones, and a door you can close.
  • Share with the whole team to give ideas, so everyone knows how is your space.

Home Office by Andres Bruzzoni

  • Make sure the things you see in your office space are all work related to avoid procrastinating.

Home Office by Andres Bruzzoni

Do Not Disturb:

  • Use big headphones (even if you are not listening to music). People think twice before interrupting someone with big headphones.
  • Use a cardboard letter in your desktop that says “Busy/Available” if you work in a place with people that may interrupt you without realizing

Infrastructure:

  • Make sure you have good internet quality.

In Mac:

  • You can try by opening a terminal and entering the following command: ping 8.8.8.8

You should get a delay under 40.000ms on average to be able to have a good call quality. If there are peaks of more than 100.000 ms, you have a bad connection and will probably have a very bad video call.

In Windows:

https://support.siteserver.com/kb/a85/how-to-perform-a-ping-test.aspx

During Meetings: How do others see & hear you?

  • For VideoCalls, sit with your back to solid walls or whiteboards - Not glass walls, windows or mirrors.
  • ALWAYS ask every participant to use their own camera and individual headphones
  • Can people clearly see expressions on your face? If not reposition your camera, lighting or yourself.
  • Schedule every meeting as a video call
  • Use group chat backchannel and nonverbal communication to speed up video calls.
  • When a meeting attendee loses video or audio, use a backchannel to debug the problem while the meeting continues.
  • The meeting moderator must actively ensure that everyone who raises their hand has a chance to speak in turn.
  • If everyone in the group starts signaling to “Speed up” by moving their hands in circles, just do it and avoid context.

Own your calendar:

  • Keep your calendar accurate, including all non-meeting events and personal events. This helps others schedule meetings with you without calendar haggling.
  • Use calendly for externals.
  • Use timezone GMT-3 as default for scheduling inside the company.
  • Setup your calendar for 30 minutes meetings with small gaps of 15 minutes between each meeting.
  • Alternate meeting days and “maker” days. It helps you have a more predictable week and you know when you are going to be able to work. If not possible, at least try to break your day into big chunks of creative work vs. operative work.
  • Keep a realistic calendar.
  • If someone invites you to a meeting without explanation or agenda, politely decline it.
  • Treat your calendar as an accurate Single Source of truth record of where you spend your time.

About emergencies:

The main rule: If you repeatedly drop everything to help other people’s emergencies, you would be making a significant unproductive choice.

  • If there is a real emergency, do what you can to help your coworkers.
  • First, decide objectively if you think this is a genuine storm.
  • If it is a storm, be clear about how much time commitment is likely needed so you can replan your other tasks.

About the meeting:

The main rule: Before organizing one, stop and ask: “Does this topic actually need a meeting?”

  • Ask yourself, “How will I know if the meeting was a success?
  • Be very intentional about which invitees are required and which are welcome-if-curious.
  • Don’t have more people into a meeting than the ones a big Pizza could feed.
  • Every meeting must have a clear agenda into the calendar invite or into the L10 file
  • Always document the output of the meeting and clear next steps in a file or tool. If something was a key decision for the company, it must be added to the SSOT (Wiki).
  • Start and stop on TIME.

Meeting Moderator and team players:

Main Rule: Setup a shared, editable agenda in advance into the calendar invite or other files, and have everyone append items to the agenda.

  • Cancel meeting if shared agenda is empty
  • The role is to prevent meeting hijacking or “coming-to-a-meeting-just-in-case-itis”
  • Because everyone keeps the agenda open, they can see notes as they are being written.
  • Before closing take a look at the notes.
  • In the end, copy the entire agenda into your group official SSOT (Wiki).
  • The person who organized the meeting is the agenda owner.

SSOT (Wiki) (“single source of truth”) AKA --> WIKI:

Is about fostering a shared human mindset and culture where everyone obsessively tracks all information for a given project or task in one well-defined location. When done consistently, the SSOT (Wiki) shares information rapidly and accurately to any interested human across the organization.

Main Rule: When you need information, look in the single source of truth before asking a human.

  • If someone asks you for information that you know is already in the SSOT (Wiki), don’t repeat what is already written. Instead, respond with the link to that information.
  • If someone has questions after reading your SSOT (Wiki), immediately update it with your response, so others will not need to ask you the same question.
  • Encourage your team to follow these steps.
  • As a group, be obsessively consistent about keeping the SSOT (Wiki) 100% up to date. Wherever you hear or discuss something that is important enough to tell others, add it to the SSOT (Wiki) immediately., Your work is not finished until you update the SSOT (Wiki).
  • Don’t write a thesis. You don’t have time for that, and others don’t have time to read it. Instead, keep it short. Very Short. Use bullet points. Write the shortest update and cover all the important facts, accurate to the best of tour knowledge. Imagine the other person is reading on a smartphone.
  • If you need detailed notes, first write a summary so the non-interested people, don’t have to read everything.

Cultural change:

  • If someone offers to tell you the status of something, stop them and tell them you will read in the SSOT (Wiki) and then ask if you have any questions.
  • If you still have questions after reading, ask them to update the SSOT (Wiki) with the answer.
  • Start every day by reading your team’s private group chat channels in full and watch the Project Management tool to understand what is everyone doing.

About project management:

  • Ensure everyone has uploaded their priorities to the PM tool
  • Urgent - something that must be done today
  • High - This week
  • Normal - Backlog.

Communication:

Next time you want to contact someone, try asking yourself “What is the urgency if this situation, and what's the appropriate communication channel for it?”

Prioritized communication channels from more to least urgent:

  1. In-person meet
  2. Cell Phone call
  3. WhatsApp
  4. Slack message/Project management tool mention
  5. Email

Tips

  • Write like a journalist: the first paragraph gives the reader an overall context in the shortest possible number of words so readers can decide if they care enough to continue reading.
  • Make the subject match the reality. If the subject changed during a thread, ask to open a new thread with a new subject.
  • Avoid long threads where no one makes decisions and everyone trow ideas in. For that is better to open a slack conversation for ideas.
  • Everyone uses the same group chat system
  • Use public channels by default, private team channels when appropriate, and private one-one direct messages when needed. Group channel eliminates overhead and repetition errors due to multiple separate on to one chat.
  • Communicate your status to the team (slack):
  • I’m at the computer - Seconds.
  • Be right back - 15 minutes
  • Meeting - 30-60 minutes
  • Do not disturb - Don’t expect an answer soon.
  • Holidays - week or more.

Recruiting

When recruiting:

  • Ensure to write “Remote welcome” in the application form.
  • Pay attention to the smallest connection problems during the interview. It is a red flag of the person not adapted to this type of work.

Onboarding:

  • Keep in mind that when your new hire starts, your team will be net negative one half-person for the first 3 months, because an existing team member needs to spend time helping the new hire get up to speed.
  • Never hire people who might work out. If you hire you will have 50% of a key employee lost for 3 months and will need to clean the unfinished work left behind when the new hire leaves.

General Suggestions:

  • Moderate all channels
  • Consider all chat as temporary. Copy important discussions to SSOT (Wiki).
  • Everyone must see the team channel every day quickly once to be updated on what happened the day before.
  • Set explicit expectations on response times, so others can plan accordingly.
  • If you repeatedly hire the wrong person, your team will lose confidence in your ability to attract and hire good people.
  • Bring your team together once in a while.

When you are working and traveling at the same time

Sometimes it occurs that you want to have a trip to a vacation location with your friends or family but you are not on holiday.

In Sirena, we consider this an option, but you have to ensure that:

  • You will commit to your duties. People is expecting you to act the same way as you will perform if you are at your regular location. That means, same work hours and responsibilities.
  • If you have to make some adjustments to your calendar and you need some flexibility you MUST ensure your manager approves it and your team will not be stuck or delayed because of this.
  • You must update your calendar and set clear timelines where you are connected, at a suitable location in order to ensure you perform right (good internet, not a lot of noise)
  • Being at the beach and answering WhatsApp is not considered working, nor being online. We will consider this a holiday.
  • We are a flexible remote company, this doesn’t mean we can distort the concept.

Team Activities:

Digital lunch

  • Ideally have every day a slot into the calendar to run digital lunches. A digital lunch is a space where every person of the team is having lunch together. You must setup a zoom room for that and share the moment. It’s like a normal lunch, but virtual :)

Digital physical training

  • Someone from the team can reserve a slot to deliver a digital physical training.

Hands-off/Town Halls:

  • It is highly recommended to run a monthly virtual hands-off to talk about business issues, goals updates and general news.

Picture of our team during a remote Hands-off