From your very first day here you can’t help but be struck by how much autonomy everyone has. With the support of my on-boarding team I was rolling out code to production and started my first A/B tests after 2 days. Just 2 days after joining my ideas were being used by millions of people from all over the world. I was trusted enough by my colleagues that this just wasn’t a big deal. “You came here to write code and make our products better so what is the big deal about you doing that?” The trust is so evident that everyone here was hired to do what they’re good at. Everyone here is trusted to do the stuff that they are good at and were hired to do.
Every change I make and every feature I ship I get to see what effect it has. I get to see how people react to the change and how it effects how they use our products. How my team act on this data can depend based on the context and the type of product we’re working with. The data can’t necessarily tell us what to do. It does, however, drastically reduce the chance that we will make a change that negatively affects the people who use and rely on our product. With A/B testing you get to see that the effect you hoped your design would create actually had a totally different or sometimes an exact opposite effect.