📗
Processes
  • Intro
  • Getting Started
    • Your first day
    • General work ethic
    • Important contacts
    • Important Links
    • Team Communication
    • Remote work code of conduct
  • Product processes
    • Roles & Responsibilities
    • Meeting Structure
      • 1:1 Meetings
      • Design Kick-Off
      • Design Review
      • Dev Kick-Off
      • Estimation Meeting
    • How to Introduce a Feature
    • Writing Effective User Stories
    • Writing a Design Overview
    • Prioritization (with RICE)
    • How to roughly estimate as PM & Designer
    • Design Sprints
      • Setup/ Preparations
      • Monday
      • Tuesday
      • Wednesday
      • Thursday
      • Friday
      • Sprint Decision Making Process
      • Recruiting customers for Friday's interviews
    • Project Management - Product, Dev and Design
    • Definition of Ready (for development)
  • Stakeholder requests
  • Submit a Bug Report or Feature Request
  • Data Protection: User Deletion Requests
  • Testing structure
    • Testing mobile
    • Manual Regression Tests
  • Technology
    • Development Process
Powered by GitBook
On this page
  • Regarding the right to do remote work
  • Letting the team know
  • Be verbose
  • Be ready to join a call or remote meeting
  • Different timezones

Was this helpful?

  1. Getting Started

Remote work code of conduct

PreviousTeam CommunicationNextRoles & Responsibilities

Last updated 4 years ago

Was this helpful?

This page describe a few rules that are important to follow when working remote. In summary, communication is key.

Regarding the right to do remote work

  • Presence in the office is still important, remote work is considered to be an exception. This can change in the future, but for now that's the rule.

  • Remote work is possible, but needs to be done with responsibility. Discuss with your manager about the possibilities.

  • Take into account important meetings, company all hands and team events so you don't miss important discussions that are better done in person.

Letting the team know

Given that we are not 100% remote, people usually expect that you will be in the office, thus:

  • If you know that will be working remote, let your team know at least a day before. Even better if you share your plan in the beginning of the week.

  • Exceptions might happen only in urgent cases.

  • Book home office in Personio, see HR Rulebook.

Be verbose

  • Use slack to share your presence, use or post a message in the team channel (usually #team-XXXX in Slack).

  • During working hours you are expected to be available, unless you communicated otherwise.

  • Give preference to public channels over 1:1 messages.

  • Any change of presence availability needs to be communicated (ex.: going to lunch, back from lunch, started working, stopped, went to doctor, etc).

  • Communicate with the team your updates for the day. In situations when most of the team is remote, everyone should post an update on the chat.

  • React in chat messages to show you read, processed, understood, etc. Don’t let people without an answer.

  • Pay attention to email, calendar, projement management and github PRs for mentions and call to actions

Be ready to join a call or remote meeting

When a conversation is the best solution:

  • is preferable that every participant use a camera

Different timezones

  • Overlap your work hours with at least 4 hours.

  • If difference is too big, communicate with the team your availability

have systems in place and ready to be used ()

statuses
Google Meet