Navigation Menu

Skip to content

Commit

Permalink
High agency expansion (#1807)
Browse files Browse the repository at this point in the history
Expand comments on high agency to include insight from colleagues
  • Loading branch information
ElizabethStirling committed Oct 22, 2020
1 parent 0ee95e0 commit bd718e8
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion company/values.md
Expand Up @@ -36,7 +36,13 @@ Everyone at Sourcegraph has the power and the responsibility to improve Sourcegr
A few examples of how we encourage high agency are by being a [handbook-first](https://about.sourcegraph.com/handbook/usage#why-handbook-first) company, which allows anyone to change how the business operates, and by empowering engineers to spend time on projects they believe in through our policy of [innovation time](https://about.sourcegraph.com/handbook/engineering#innovation-time).

With agency comes responsibility; teammates are expected to take initiative and engage in collaboration when exercising their agency. If you feel that something is important, then advocate for it! If you feel like you're using the wrong tools for the job or doing the wrong thing, then you're responsible for quickly voicing that concern, and engaging with your teammates to find the solution that is the best for the team. This doesn't mean that you should make unilateral decisions. As an [open company](index.md#open-company), we value open discussion on important topics, and think that collaboration should be a large part of making things better. It is not a bad outcome if your proposal is not accepted or replaced with a better solution, because you took the initiative, started the conversation, and either reaffirmed that our current solution is good, or implemented an even better one!
With agency comes responsibility; teammates are expected to take initiative and engage in collaboration when exercising their agency. If you feel that something is important, then advocate for it! If you feel like you're using the wrong tools for the job or doing the wrong thing, then you're responsible for quickly voicing that concern, and engaging with your teammates to find the solution that is the best for the team. Do not ever assume or wait for top-down change. If something is broken for you or your team, then fix it for you or your team, and then share that fix in case other individuals or teams have the same problem.

This doesn't mean that you should make unilateral decisions. As an [open company](index.md#open-company), we value open discussion on important topics, and think that collaboration should be a large part of making things better. It is not a bad outcome if your proposal is not accepted or replaced with a better solution, because you took the initiative, started the conversation, and either reaffirmed that our current solution is good, or implemented an even better one! We're a startup, and if we take the safe path, we will most likely fail.

Fundamentally, agency isn't just good for the company, it's good for your career too. While it's easy to assume that getting better at your current responsibilities is how to get promoted and move up in your career, the real source of career growth is increasing impact. The way to have this impact is to take agency and make things happen. After all, responsibility is taken, not given. This is one of the reasons we don't have job titles at Sourcegraph. We think that career is measured by your impact, and how you take responsibility, not what prefix you add to your role.

> "What I ultimately came to realize was that *the real measure of my career growth was in having an ever-increasing impact*." [Chris Pine](https://about.sourcegraph.com/blog/software-engineer-career-paths/)
### High quality

Expand Down

0 comments on commit bd718e8

Please sign in to comment.