Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
How design happens at GitHub (Osaka, 2014)
Search
Coby Chapple
June 03, 2014
Design
0
48
How design happens at GitHub (Osaka, 2014)
Here are the slides for a talk I gave in Osaka, Japan, in 2014, about how design happens at GitHub.
Coby Chapple
June 03, 2014
Tweet
Share
More Decks by Coby Chapple
See All by Coby Chapple
Product thinking with JTBD
cobyism
0
190
GitHub Flow for Designers
cobyism
1
340
Asynchronous Communication For The Win!
cobyism
0
270
GitHub Flow — AWS Summit Tokyo 2015
cobyism
16
4.3k
Belfast Ruby - Interesting things from the GitHub codebase
cobyism
3
320
Static Sites with Jekyll and GitHub Pages
cobyism
9
1.5k
How GitHub Works (GitHub Kaigi, Tokyo, 2014)
cobyism
93
34k
Remote by default (BACON 2014)
cobyism
3
1.4k
How design happens at GitHub (ScotlandJS, 2014)
cobyism
5
1.2k
Other Decks in Design
See All in Design
Дизайн современной услуги с Картой процесса-опыта
ashapiro
0
110
志ある事業の種を社会に開花させるための挑戦/ Designship2024_Nishimura
root_recruit
0
260
ENEOS社事例|アプリ事業を加速させるデザイナーの取り組み / dx-eneos-design
cyberagentdevelopers
PRO
1
820
東急URBAN HACKSのデザイナーって何やってるの? 〜Designer Night #1〜 組織横断のデザインの 取り組みについて
sig
1
270
ゲーム開発における、Figma活用事例の紹介 / applibot-figma
cyberagentdevelopers
PRO
2
620
マルチプロダクトにおけるデザイナーの挑戦-デザイン初め新年会2025
u_ri_ta
1
140
プロダクトデザインの「守破離」の「破」について
hayashirine
0
310
ビジョン実現を加速させるデザインプログラムマネージャーの視座とキャリア/ Designship2024_Sato
root_recruit
0
250
NAHO SHIMONO_Portfolio2025
nahohphp
0
120
How to go from research data to insights?
mastervicedesign
0
220
コンセプトで経営・事業・組織を動かす、 Ameba20周年ブランディング / ameba-20th-branding
cyberagentdevelopers
PRO
1
550
パンくずリストかわいい(breadcrumb so cute)
ysuda
0
160
Featured
See All Featured
Raft: Consensus for Rubyists
vanstee
137
6.8k
No one is an island. Learnings from fostering a developers community.
thoeni
21
3.1k
[Rails World 2023 - Day 1 Closing Keynote] - The Magic of Rails
eileencodes
33
2.1k
We Have a Design System, Now What?
morganepeng
51
7.4k
Building Your Own Lightsaber
phodgson
104
6.2k
Code Review Best Practice
trishagee
66
17k
Art, The Web, and Tiny UX
lynnandtonic
298
20k
The MySQL Ecosystem @ GitHub 2015
samlambert
250
12k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
132
33k
Building Better People: How to give real-time feedback that sticks.
wjessup
366
19k
Fashionably flexible responsive web design (full day workshop)
malarkey
406
66k
Build your cross-platform service in a week with App Engine
jlugia
229
18k
Transcript
! cobyism — Osaka, 2014 HOW DESIGN HAPPENS AT GITHUB
@cobyism
ࢲGitHubͷσβΠφʔͱ։ൃऀͰ͢
GitHubɺαϯϑϥϯγείʹڌΛஔ͕͘ɺࢲ ΞΠϧϥϯυʹॅΜͰ͍·͢
ࢲɺϦϞʔτͰಇ͘ଟ͘ͷࣾһͷதͷҰਓͰ͢
60ˋ͕ϦϞʔτͰ͢ɻ
DESIGN How it works at GitHub ํ๏ઃܭGitHubͷ࣌ʹى͜Γ·͢
σβΠϯɺίʔυͰൃੜͨ͠
σβΠϯɺϓϧཁٻͰൃੜ
Pull Requests help settle arguments. ϓϧཁٻɺҾΛղܾ͢Δखॿ͚
Pull Requests keep you grounded in reality. ϓϧཁٻɺ͋ͳ͕ͨݱ࣮ʹযΛ͓ͯͯ͘
Design happens in ... σβΠϯɺϒϥβͰى͜Δ
Design here is real. ϒϥβʔͰߦ͏σβΠϯݱ࣮ɻ
Design it once, not twice ઃܭҰɺೋͰͳ͍
Design here is always current. ϒϥβͰߦ͏ઃܭৗʹ࠷৽Ͱ͋Δɻ
Just commit. ίϛοτɺ͓ΑͼͦΕ͕͘ͳΔ
big picture Focus on the first ࠷ॳશମ૾͔Βݟ·͠ΐ͏
Design happens with prototyping. σβΠϯϓϩτλΠϓΛ͍ͬͺ͍࡞Δ͜ͱʹΑͬͯߦΘΕΔ
[ REDACTED ] ൿີ!
Design happens with lorem ipsum dolor sit amet. ϓϨʔεϗϧμςΩετ?
Design happens with real data. σβΠϯʹຊͷσʔλ͕ඞཁ
None
Design happens hidden behind feature flags. σβΠϯػೳϑϥάͰӅͯ͠ຊ൪ڥͰςετ͞Ε͍ͯΔɻ
def new_feature_enabled? … end
def new_feature_enabled? preview_features? end
def new_feature_enabled? preview_features? && team_access?(:some_team) end
None
def new_feature_enabled? true end
Beware of feature flags. ػೳϑϥάΛ͏ͱԿΛӅ͍ͯͯ͠Կ͕ग़ՙ͞Εͯ ͍Δ͔͕Θ͔Βͳ͘͜ͱ͋Δɻ
Dogfooding is powerful, but it has it’s limits. ࣗͰࣗͷϓϩμΫτΛςετ͢Δͷڧྗ͚ͩͲɺݶք͋Δ
Design happens with feedback. ϑΟʔυόοΫ͕͋ͬͯͦ͜σβΠϯى͜Δ
Design happens with quantitative feedback. σβΠϯɺఆྔతͳϑΟʔυόοΫͰൃੜ
Design happens with qualitative feedback. σβΠϯɺఆੑతͳϑΟʔυόοΫͰൃੜ
Design is everyone’s responsibility. σβΠϯΈΜͳͷɻ
Design often begins without any designer input. σβΠϯ݁ߏසൟʹσβΠφʔ͕ؔΘΒͳͯ࢝͘·Δɻ
Beware of design by committee. ҕһձʹΑΔσβΠϯ͚͞·͠ΐ͏ʂ
Beware of drive-by comments. ௨ߦਓ͔Βͷίϝϯτʹҙ͍ͯͩ͘͠͞
Design should be an open process. σβΠϯɺಁ໌ͳϓϩηεͰ͋Δ͖
Open design is the future. ಁ໌σβΠϯະདྷ͕͋Δ
Open design is really hard. ಁ໌ੑͷ͋ΔσβΠϯ࣮ݱ͢Δͷຊʹ͍͠
Open design requires making at paradigm shift. ಁ໌ͳσβΠϯɺύϥμΠϜγϑτ͕ඞཁͰ͢
Open design means showing work early. ಁ໌ੑͷ͋ΔσβΠϯʹૣ͍ஈ֊ʹσβΠϯΛݟͤΔ ඞཁ͕͋Γ·͢ɻ
Open design means accepting imperfection. ಁ໌ੑͷ͋ΔσβΠϯʹᘳͰͳ͍͜ͱΛड͚ ೖΕΔඞཁ͕͋Δɻ
Open design helps build empathy. ಁ໌ੑͷ͋ΔσβΠϯʹڞײ͋͑͠ΔؔΛߏங ͢Δඞཁ͕͋Δ
Open design means articulating design decisions. σβΠϯʹࢸΔҙࢥܾఆΛ໌֬ʹදݱͰ͖Δ ඞཁ͕͋Δɻ
Open design means sacrificing your pride. ಁ໌ੑͷ͋ΔσβΠϯʹࣗͷϓϥΠυΛࣺͯΔ ඞཁ͕͋Δɻ
Open design means trusting people. ಁ໌ੑͷ͋ΔσβΠϯʹνʔϜϝʔτΛ৴པ͢Δ ඞཁ͕͋Δɻ
Open design means being respectful. ಁ໌ੑͷ͋ΔσβΠϯʹϑΟʔυόοΫΛ ݴ͏࣌ʹ૬खΛଚॏ͢Δඞཁ͕͋Δɻ
Open design takes constant work. ಁ໌ੑͷ͋ΔσβΠϯʹৗʹྗͯ͠վળ ͢Δඞཁ͕͋Δɻ
Thank you!
[email protected]
@cobyism Ͳ͏͋Γ͕ͱ͏͍͟͝·ͨ͠ʂ