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

June 21, 2013

More Decks by Matt Graham

Other Decks in Design


  1. None
  2. None
  3. None
  4. None
  5. None
  6. None
  7. None
  8. None
  9. None
  10. None
  11. None
  12. None
  13. None
  14. None
  15. None
  16. None
  17. None
  18. None
  19. None
  20. None
  21. None
  22. None
  23. None
  24. None
  25. None
  26. None
  27. None
  28. None
  29. None
  30. None
  31. None
  32. None
  33. traumatic

  34. Design without Development

  35. Development without Deployment

  36. 41 Shades of Blue

  37. None
  38. None
  39. None
  40. None
  41. None
  42. None
  43. None
  44. Who are these people?

  45. None
  46. None
  47. None
  48. We are the industry craftsmen

  49. Craftsmen: a person who practices or is highly skilled in

    a craft;
  50. We want the same thing.

  51. "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
  52. None
  53. Know the company vision

  54. and align yourself with it.

  55. Get to know your team

  56. What have they done?

  57. What are their skill sets?

  58. What are they passionate about?

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

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

    do things.
  61. None
  62. Understand Your Projects

  63. Develop a SHARED understanding of the project/requirements

  64. None
  65. Document all things

  66. Identify technical challenges

  67. Expose expectations

  68. Estimate time and effort

  69. Divide and Conquer

  70. Understand yourself

  71. What are you passionate about?

  72. How you work best?

  73. Be aware of your insides.

  74. Be aware of your blindspots, and that you don't know

    them all.
  75. You can’t control the company atmosphere, but with mindfulness you

    can know how you effect it.
  76. Community Adjustments

  77. Trust Your Team

  78. Repent Quickly

  79. “Why are you so afraid of something you’ve done so

    often?” -W
  80. None
  81. Forgive Often

  82. None
  83. "Avoid attacking people, attack problems." - Tom Preston-Werner

  84. Relate with your team

  85. Communicate Transparently

  86. You don't need to know how to write the code,

    you need to know how to communicate with the developer who does.
  87. Be involved in as much of the project as you

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

  89. Don’t Stop Learning

  90. Community works when your willing to put the team above

  91. None
  92. None
  93. Hire for Community

  94. None
  95. Transparent Communication

  96. 118 Chat Rooms (with search) Danger Room Ops Room Midwest

    Room CodeBass Room The Outreach Room The Design Room The .com Room Cheddar
  97. Transparent Expenses

  98. Cerebro Documents

  99. Pull Request Community

  100. Automate Everything

  101. Boxen

  102. None
  103. hubot deploy speakerkdeck/dark-side to production Deployments

  104. Ship Early. Ship Often.

  105. Finding people who are passionate about your idea.

  106. Drink Beers

  107. Relate with each other, understand each others joys, pains and

    headaches. Community solves the problem.
  108. Austin, Texas Montevarchi, Italy Portland, Maine South Bend, Indiana Kona,

    Hawaii Manzanillo, Mexico Punta del Este, Uruguay GitHub Destinations Pa Tong Kathu Phuket, Thailand
  109. Mini-Summits

  110. None
  111. None
  112. None
  113. None
  114. "The best software is made by happy people working together."

    - Brian Doll
  115. Trust. Humility. Relationship.

  116. None