# Internal communication
- Open exchange of information
- How to criticize correctly
- Our routines
- Slack channels
# Open exchange of information
- Use public channels when it's possible. Avoid direct messages at all cost.
- Show decision-making process transparent (Transparency).
- Put down comments to Jira with the process of solving the issue. If there will be a need to reassign a task your teammate will be able to dig in quickly.
- Record reports and presentations. Those who weren't able to present will watch it recorded.
- Duplicate important decisions that made in threads to
- Put down and publish follow-ups of common calls.
# Internal wiki
For the information that must be private, we use internal wiki (opens new window).
If you doubt where to publish new information, ask yourself 'Will that information would produce harm to our company or anyone?'.
- If answer is "No" - use public handbook.
- If answer is "Yes" - use internal wiki.
- Talk about others only what you could say to their eyes.
- If you've noticed that the discussion turned into an argument - offer a call.
- If the call requires the participation of more than 2 people, it is better to create an event in calendar and invite participants to it. This reduces the likelihood that someone will forget about the meeting.
- Say thanks to your colleagues.
# Distraction free workspace
- Check notification settings in Slack.
- Real-time sometimes, asynchronous most of the time.
- Avoid using direct messages. Insist the same for others.
- If you want to propose a complex idea, write a RFC rather than starting a discussion in Slack.
- When you're starting a new thread, mention only people who you want to take part in the discussion.
- Respect everyone's right to uninterrupted work. Your colleagues have work to be done too.
# How to criticize correctly
Good criticism helps you to look at the problem from the outside and make better decisions.
For the critic:
- Seek to help. Explain how a change in behaviour will help the person or the entire team.
- Suggest specific measures. Specify exactly what the addressee should change.
For the addressee:
- Say thanks for the critic. You must clearly show that anyone can and should speak up.
- Decide for yourself what to do with the advice.
# Our routines
# Bug Day
Why: We're having the Bug Day for all teams on Monday. This process helps to continuously and regularly improve the quality of our products.
Who: Dev-team, Infra-team.
Every Monday there's
Bug Day Digestin a
Take a bug and post a message in a thread.
If you complete the task and feel enough energy to take more, take the next one! Good luck!
# Automatic daily: Support help requests
- When: if there are open tasks in a SUPPORT project.
- What: SUPPORT project tasks are considered the most important and we strive to complete them ASAP.
# Automatic daily: "What did you work on today?"
- Who: Everyone.
After the work day we answer a question "What did you work on today?". That helps us to reflect on what we spend time on.
One optional question "What (if anything) is blocking your progress?".
- Why: To share new features and get feedback from other teams.
- Who: At least one member of each team.
- What: Anyone can demonstrate something that might be interested for other teams, i.e. new features.
# Monthly: Roadmap meeting
- Why: We must review our objectives and sync key result statuses.
- Who: Everyone else who wants to participate.
- When: The first
Tuesday of every month.
# Monthly: Support checkpoint meeting
- When: every Monday at 13 Moscow timezone.
- Who: Customer Success team. Development team participation is at will.
- What: we discuss last week's relevant issues, customer feedback - frequently asked questions, feature requests, current affiliate marketing trends, and upcoming tasks.
- The recording of the meeting is recommended to be viewed by a development team. This is important as our support is our sales team and is the main source of information about customer satisfaction. We learn about the most frequent problems and pains of our users from the support team, so we can adjust our roadmap, or help solve the most frequent problems that users are writing about.
- Add the link to the meeting recording to an
#announcementschannel, mention everyone in a thread if necessary.
# Weekly: Squad meeting
Why: To sync on what we're done and what we're working on.
Who: Each squad schedule its own meeting.
# Weekly: Company call
- When: Every Friday.
- Who: Everyone.
- What: We have a time-space for free talks, to cool down after the workweek.
# 1:1s (One-on-Ones)
- Why: To connect personally with each other.
- Who: Each E-team member with each team member individually.
- What: It's better to prepare agenda and share it before the meeting.
# Slack channels
#announcementseverything you must know about the changes is posted here.
#tech-questionsCS-team asks Dev- and Infra-teams questions.
#learningbooks, interesting articles and blogs.
#music-and-gamesto share some music or gather together to play games.
#proposalswe post any proposals on everything here.
#work-doneeveryday reflection on done work.
#english-clubwhen we talk about English rules and share interesting topics.
# Meeting checklist
- Prepare and publish agenda in advance.
- Try to publish a brief and materials in Slack in advance.
- Schedule a meeting through Zoom and add en event in your personal calendar. Invite only persons who really must participate.
- Remember to record the meeting.
- Upload recording to Google Drive.
- Publish summary
#annoucementsfor other squads.
# How to schedule a meeting
- Open Zoom.
- Fill settings:
- Start and end time.
Only authenticated users can join.
- Calendar - Google Calendar.
- (Important!) Advanced ->
Automaticcaly record meeting.
- Add an event and add persons or groups who really must participate in. Use you personal calendar to strore the event.
- (Optional) If it's a public event duplicate it to an