Skip to content

Instantly share code, notes, and snippets.

@teddyzetterlund
Created May 29, 2016 06:37
Show Gist options
  • Save teddyzetterlund/8afd65bb11c51c86c8ae559049e89edd to your computer and use it in GitHub Desktop.
Save teddyzetterlund/8afd65bb11c51c86c8ae559049e89edd to your computer and use it in GitHub Desktop.

What do the words on the right tell our teams?

Some thoughts from John Cutler's tweet on the importance of words.

Ship: Value isn't delivered until it's shipped. Everything on the left-hand side is essential to find the right value, but it's no good as long as it's not in front of all your users.

Plan: Take a step back and think ahead. Don't jump straight into the solution. Truly consider the problem, then the solution you want to go with – but even then, think about your approach. If it's related to coding. Will someone have to review it? Can you do it smaller steps, so that review is faster and the change get to production faster?

Commit: Don't give up simply because it's hard. Work together to solve the problem you've all understood and decided is the right thing to spend your time on.

Accountability: Don't be afraid to question solutions, and each other. A design should have buy-in, and team behind it honors quality and responsible shipping.

Velocity: I don't like the word itself, but it can be used to as a parameter to help figure out feasibility. As in, what can we get done in this time frame – instead of how long will it take.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment