Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not-used-useless value feedback #1308

Merged
merged 2 commits into from
Jul 31, 2020
Merged

not-used-useless value feedback #1308

merged 2 commits into from
Jul 31, 2020

Conversation

sqs
Copy link
Member

@sqs sqs commented Jul 30, 2020

I removed this value because it is not actually lived by the team, based on feedback from several people. It is aspirational. We will propose adding it back once we feel we are living it more or are ready to do so. This is the point of our values - to be accurate and regularly updated/reviewed.

The marketing team had good feedback about this value. I'd love to hear more feedback from marketing folks here so we can revise this value.
@adaaaam
Copy link
Contributor

adaaaam commented Jul 30, 2020

"If it's not used, it's useless" seems more relevant to product and engineering teams. With marketing, we often ideate and try new things. Sometimes those things don't work and we need to iterate based on feedback and other learnings. But it is important for us to keep that "useless" plan to then improve the next plan. The term "useless" is quite strong diction and invalidates the learning process from running experiments. The notion of how "useless" something is could also be argued in terms of how many people (including both users and colleagues) use it.

For me, language like "Prioritize and pivot" applies to more teams' work, and aligns with our new Goals process. We discuss and agree on goals with our colleagues and leadership. We are encouraged to recognize if that goal is the wrong goal, so we can abandon it and start working on a new goal. Measuring the usefulness of a goal in terms of delivering value (both to our users and colleagues) should be part of that continuous review process.

This value is not actually lived by the team. It is aspirational. We will propose adding it back once we feel we are living it more or are ready to do so.
@sqs
Copy link
Member Author

sqs commented Jul 31, 2020

I removed this value because it is not actually lived by the team, based on feedback from several people. It is aspirational. We will propose adding it back once we feel we are living it more or are ready to do so. This is the point of our values - to be accurate and regularly updated/reviewed.

@sqs sqs merged commit fe8db02 into master Jul 31, 2020
@sqs sqs deleted the used-useless-value-feedback branch July 31, 2020 18:22
@mrnugget
Copy link
Contributor

mrnugget commented Aug 3, 2020

I understand why you removed it, but just for the record: I really liked it. I think it's a nice reminder to have a "sense of urgency" (which is something I've heard a lot) and a good counterbalance to an engineering-driven roadmap, because we all know that engineers are easily tempted to build things that are fun to build and cool to have, but not necessarily something a customer asked for or will use.

@sqs
Copy link
Member Author

sqs commented Aug 3, 2020

@mrnugget Yeah, thanks for sharing this! I do think it is an important thing to be mindful of, and I hope we can feel like we're all living this value enough to put it in the handbook.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants