Upgrade to Pro — share decks privately, control downloads, hide ads and more …

We Should be Lovers

We Should be Lovers

Trust, Humility & Relationship. Three fundamental building blocks that help foster community. In this talk Matt gives examples what to look for inside your team, projects and self to help better the community you work in. Then shares details of how GitHub lives out community and relationship within its organization.

Matt Graham
PRO

June 21, 2013
Tweet

More Decks by Matt Graham

Other Decks in Design

Transcript

  1. View Slide

  2. View Slide

  3. View Slide

  4. View Slide

  5. View Slide

  6. View Slide

  7. View Slide

  8. View Slide

  9. View Slide

  10. View Slide

  11. View Slide

  12. View Slide

  13. View Slide

  14. View Slide

  15. View Slide

  16. View Slide

  17. View Slide

  18. View Slide

  19. View Slide

  20. View Slide

  21. View Slide

  22. View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. View Slide

  27. View Slide

  28. View Slide

  29. View Slide


  30. View Slide

  31. View Slide

  32. View Slide

  33. View Slide

  34. traumatic

    View Slide

  35. Design without Development

    View Slide

  36. Development without Deployment

    View Slide

  37. 41 Shades of Blue

    View Slide

  38. View Slide

  39. View Slide

  40. View Slide

  41. View Slide

  42. View Slide

  43. View Slide

  44. View Slide

  45. Who are these people?

    View Slide

  46. View Slide

  47. View Slide

  48. View Slide

  49. We are the industry craftsmen

    View Slide

  50. Craftsmen: a person who practices or is
    highly skilled in a craft;

    View Slide

  51. We want the same thing.

    View Slide

  52. "The way we work at Apple makes it critical
    to work collaboratively with different areas
    of expertise…
    ...we share the same goal, have exactly the
    same preoccupation, with making great
    products." - Jonny Ive

    View Slide

  53. View Slide

  54. Know the company vision

    View Slide

  55. and align yourself with it.

    View Slide

  56. Get to know your team

    View Slide

  57. What have they done?

    View Slide

  58. What are their skill sets?

    View Slide

  59. What are they passionate about?

    View Slide

  60. What drives them to want to
    punch co-workers in the FACE.

    View Slide

  61. Do not expect that they do things
    the way you do things.

    View Slide

  62. View Slide

  63. Understand Your Projects

    View Slide

  64. Develop a SHARED understanding
    of the project/requirements

    View Slide

  65. View Slide

  66. Document all things

    View Slide

  67. Identify technical challenges

    View Slide

  68. Expose expectations

    View Slide

  69. Estimate time and effort

    View Slide

  70. Divide and Conquer

    View Slide

  71. Understand yourself

    View Slide

  72. What are you passionate about?

    View Slide

  73. How you work best?

    View Slide

  74. Be aware of your insides.

    View Slide

  75. Be aware of your blindspots, and
    that you don't know them all.

    View Slide

  76. You can’t control the company
    atmosphere, but with mindfulness
    you can know how you effect it.

    View Slide

  77. Community Adjustments

    View Slide

  78. Trust Your Team

    View Slide

  79. Repent Quickly

    View Slide

  80. “Why are you so afraid of
    something you’ve done so often?”
    -W

    View Slide

  81. View Slide

  82. Forgive Often

    View Slide

  83. View Slide

  84. "Avoid attacking people, attack
    problems." - Tom Preston-Werner

    View Slide

  85. Relate with your team

    View Slide

  86. Communicate Transparently

    View Slide

  87. You don't need to know how to
    write the code, you need to know
    how to communicate with the
    developer who does.

    View Slide

  88. Be involved in as much of the
    project as you can.

    View Slide

  89. Love your ideas
    but, be willing to change them

    View Slide

  90. Don’t Stop Learning

    View Slide

  91. Community works when your
    willing to put the team above
    yourself.

    View Slide

  92. View Slide

  93. View Slide

  94. Hire for Community

    View Slide

  95. View Slide

  96. Transparent Communication

    View Slide

  97. 118 Chat Rooms (with search)
    Danger Room
    Ops Room
    Midwest Room
    CodeBass Room
    The Outreach Room
    The Design Room
    The .com Room
    Cheddar

    View Slide

  98. Transparent Expenses

    View Slide

  99. Cerebro
    Documents

    View Slide

  100. Pull Request Community

    View Slide

  101. Automate Everything

    View Slide

  102. Boxen

    View Slide

  103. View Slide

  104. hubot deploy speakerkdeck/dark-side to production
    Deployments

    View Slide

  105. Ship Early. Ship Often.

    View Slide

  106. Finding people who are passionate
    about your idea.

    View Slide

  107. Drink Beers

    View Slide

  108. Relate with each other, understand
    each others joys, pains and
    headaches. Community solves the
    problem.

    View Slide

  109. Austin, Texas
    Montevarchi, Italy
    Portland, Maine
    South Bend, Indiana
    Kona, Hawaii
    Manzanillo, Mexico
    Punta del Este, Uruguay
    GitHub Destinations
    Pa Tong Kathu Phuket, Thailand

    View Slide

  110. Mini-Summits

    View Slide

  111. View Slide

  112. View Slide

  113. View Slide

  114. View Slide

  115. "The best software is made by
    happy people working together." -
    Brian Doll

    View Slide

  116. Trust. Humility. Relationship.

    View Slide

  117. View Slide