If you think of our values as a north star, you can think of our key principles as our map for getting there.
A key principle is a building block to one or more values.
Write it or lose it. Having a single source of truth for everything we do helps us effectively communicate and build up institutional knowledge. This is the foundation that makes an async first, remote workplace culture possible and gives everyone a way to participate in the decision making process.
Things get lost in translation. Especially across timezones and across messaging apps. When in doubt, followup.
- when you send out a PR and haven't received a response within 24h, ping the PR owner in case they've missed it
- when you are writing documentation for some new process, make sure the rest of the team knows about it by scheduling an async
- when you get a message, acknowledge reading the message via a response or a 👍
- when you merge a github branch and have some outstanding comments, also ping the submitter
Leaders listen attentively, speak candidly, and treat others respectfully. They are vocally self-critical, even when doing so is awkward or embarrassing. Leaders do not believe their or their team’s body odor smells of perfume. They benchmark themselves and their teams against the best.
Adding on to this, earning trust means showing up on time and following through on promises that we make
Bias for Action
Speed matters in business. Many decisions and actions are reversible and do not need extensive study. We value calculated risk taking. Amazon Leadership Principle
Zero Cost Features
A zero cost feature is platonic ideal of a feature that has zero cost after launch. Zero bugs, zero issues, zero questions on how to best use or integrate, zero maintenance. The best way to approach this principle is as one would a rainbow - as a direction to go vs an end to accomplish.
- make sure user docs are up to date according to dendron hierarchy (Private)
- make sure developer docs is up to date according to pkg hierarchy (Private)
- add a product stage tag (Private) to features to set expectations
- have tests
- look over common Customer Support (Private) issues for the feature and find code fixes for persistent issues