Behavior and language

  1. Do not make jokes or unfriendly remarks about race, ethnic origin, skin color, gender, sexual orientation, or religion/spirituality.
  2. Use inclusive language. For example, prefer “Hi everybody” or “Hi people” to “Hi guys”.
  3. Be aware that everyone has different personal pronouns. Share yours, and ask others about theirs.
  4. Share problems you run into, ask for help, be forthcoming with information, and speak up.
  5. Don’t display surprise when people say they don’t know something, as it is important that everyone feels comfortable saying “I don’t know” and “I don’t understand.” (As inspired by Recurse.)
  6. You can always refuse to deal with people who treat you badly and get out of situations that make you feel uncomfortable.
  7. Always be kind.

Everyone can remind anyone in the company about these guidelines. If there is a disagreement about the interpretations, the discussion can be escalated to more people within the company without repercussions. If you are unhappy with anything (your duties, your colleague, your boss, your salary, your location, your computer) please let your manager, or the CEO, know as soon as you realize it. We want to solve problems while they are small.

Make a conscious effort to recognize the constraints of others within the team. For example, sales is hard because you are dependent on another organization, and development is hard because you have to preserve the ability to quickly improve the product in the future.

MUI has a zero-tolerance policy regarding our standards as described above.

Anti-discrimination and harassment policy

Async

Always prefer async communication over sync communication. Sync communication is costly, and interrupts peoples’ thought processes and productive execution - that being said, sometimes it is indeed necessary to have a sync interaction, just make sure it is for the right reasons.

When using Slack or similar, try to communicate as much as possible in channels that everyone can access rather than private channels, whenever that can be avoided. We prime visibility and open dialog.

Private communication

Always communicate openly whenever possible. As we scale, this is a vital best practice, closeted opaque discussion removes the ability of other team members to collaborate. This is driven by our transparency value.

So if the conversation doesn’t need to be private, discussions should not happen privately. Where possible, create a document or a GitHub issue, a notion page first, and then start the discussion.