Building and Scaling Technical Teams
-
Upload
jason-hoffman -
Category
Technology
-
view
1.674 -
download
1
description
Transcript of Building and Scaling Technical Teams
![Page 1: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/1.jpg)
Building and Scaling Technical TeamsJason A. Hoffman, CTO and Founder
1
![Page 2: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/2.jpg)
2
The only private systems companyAn operating system (smartOS)A runtime (node.js)A suite of middleware that leverages both
![Page 3: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/3.jpg)
3
Only private, large scale service providerPerformance and scale sufficient for large customers.Hardware lifecycle dominants COGS. Not people.
![Page 4: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/4.jpg)
4
A business. A company.Provides something of value in exchange for money.
![Page 5: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/5.jpg)
5
Companies don’t sell to people.People sell to people.
![Page 6: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/6.jpg)
6
Companies don’t innovate.People do.
![Page 7: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/7.jpg)
7
Companies don’t discover.People do.
![Page 8: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/8.jpg)
8
Companies don’t hire people.People do.
![Page 9: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/9.jpg)
9
People. Person.Psychology. Sociology. Anthropology. Matter too.
![Page 10: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/10.jpg)
10
Packard’s Law.“No company can consistently grow revenues faster than its ability to get enough of the right people to implement that growth and still become a great company.”
from Jim Collins, How The Mighty Fall (page 55-56)
![Page 11: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/11.jpg)
11
How do you convince the right people?To give years of their life. To direct their passion.
![Page 12: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/12.jpg)
12
Myself.Army. PhD Scientist. Academic. Founder. A “CTO”.
![Page 13: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/13.jpg)
13
Comfortable team structures.I believe a basic biological aspect to them. Something “tribal”.
![Page 14: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/14.jpg)
14
Fire Team.Four. Lead by a sergeant. Three team members. Two roles each.
![Page 15: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/15.jpg)
15
Squad.2-3 fire teams plus a Staff Sergeant 8-12 “staff ” plus one “leader”.
![Page 16: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/16.jpg)
16
Baseline: you need to be capable of being on a fire team.
![Page 17: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/17.jpg)
17
Baseline: you need to be capable of running a squad.
![Page 18: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/18.jpg)
18
You’ll only ever run a “squad”.The human brain can only manage up to 8-12 people and about 600 sq ft.
Adapted from Thomas Schweich’s Staying Power
![Page 19: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/19.jpg)
19
A Marine Colonel:“We don’t promote our micromanagers, we like them exactly where they are.”
Adapted from Thomas Schweich’s Staying Power
![Page 20: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/20.jpg)
20
PhD Scientist and Academic.Why? Why? Why? Why? Why? Why? Why? Why?
![Page 21: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/21.jpg)
21
Academic.People are willing to give years of their lives for something other than money.
![Page 22: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/22.jpg)
22
Scientist.Turns out to shape how I view everything. Let me take you through a series of observations.
![Page 23: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/23.jpg)
23
Scientists.Scientists don't work in a lab to "sequence DNA." They work in a lab to "cure cancer."
![Page 24: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/24.jpg)
24
Recognition.Is as important as a salary.
![Page 25: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/25.jpg)
25
Observation IHumans have a hard time thinking of the power law or punctuated equilibriums.
![Page 26: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/26.jpg)
26
Observation IIHumans have a hard time with the absolutism that's in binary states (live, dead).
![Page 27: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/27.jpg)
27
Observation IIIWe think that "evolution" is "optimization", when it's, in fact, it’s adaption to current conditions.
![Page 28: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/28.jpg)
28
Observation IVWe don't know how to change the dimensionality of a problem.
![Page 29: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/29.jpg)
29
Observation VWe have a hard time thinking of a complete system yet we can make connections, frameworks, simplifications that no computer can do.
![Page 30: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/30.jpg)
30
Observation VIWe often think that success is a thing, or it’s because of a thing.
![Page 31: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/31.jpg)
31
Diamond’s Anna Karenina Principle“Happy families are all alike; every unhappy family is unhappy in its own way.”
Jared Diamond, Guns, Germs and Steel
![Page 32: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/32.jpg)
32
Failed Domestication.Different species were domesticated because of the lack of negative reasons (traits) not because of a reason (a positive trait).
![Page 33: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/33.jpg)
33
Success.Is simply the absence of failure. It’s the absence of fatal mistakes.
![Page 34: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/34.jpg)
34
To study success.You must study failure and death.
![Page 35: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/35.jpg)
35
Models differ.Anti-patterns are the same. Know them.
![Page 36: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/36.jpg)
36
Founder.Noun. One who establishes something or formulates the basis for something.
![Page 37: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/37.jpg)
37
Founder. Foundering.Verb. Usage: “Oh yeah, I’m foundering!! Watch out.”(said by me)
![Page 38: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/38.jpg)
38
Foundering.Verb. To sink below the surface of the water: The ship struck a reef and foundered.
![Page 39: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/39.jpg)
39
Foundering.Verb. To cave in; sink: The platform swayed and then foundered.
![Page 40: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/40.jpg)
40
Foundering.Verb. To fail utterly; collapse: a marriage that soon foundered.
![Page 41: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/41.jpg)
41
Foundering.Verb. To stumble, especially to stumble and go lame. Used of horses.
![Page 42: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/42.jpg)
42
Foundering.Verb. To become ill from overeating. Used of livestock.
![Page 43: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/43.jpg)
43
Floundering?Verb. To move clumsily, thrash about. To proceed in confusion.
![Page 44: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/44.jpg)
44
OK what about Latin?Must be something positive there!
![Page 45: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/45.jpg)
45
Fundus.Noun (Latin). The bottom of or part farthest from the opening of a sac or hollow organ.
![Page 46: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/46.jpg)
46
OK. Well.Perhaps that is all closest to the verb to founder.
![Page 47: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/47.jpg)
47
CTO.Chief Technical Officer.
![Page 48: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/48.jpg)
48
Establishes.Vision, culture, organizational structure.
![Page 49: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/49.jpg)
49
CTOs are outward facing.Product and merchandising. Operational.
![Page 50: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/50.jpg)
50
Technical.Enough to validate, shape, dig in if broken. Know who is a dummy, who is a blessed unicorn.
![Page 51: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/51.jpg)
51
Vision needs to be inspiring.People do actually feel that they’re changing the world.
![Page 52: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/52.jpg)
52
Work hard.At being an exemplar and being exceptional at an aspect.
![Page 53: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/53.jpg)
53
Ideal disposition.Personal and professional humility coupled with thoughtful intellect and professional will.
Also from Jim Collins’s Level 5 leader idear.
![Page 54: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/54.jpg)
54
Culture: Don’t be an Asshole.Pricks get fired. Bullies get banished.
![Page 55: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/55.jpg)
55
Culture: TransparencyComplete, even when painful. Tough (not brutal) and honest.
![Page 56: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/56.jpg)
56
Culture: Peer ReviewAnd everyone is a peer.
![Page 57: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/57.jpg)
57
Culture: TitlesLet compensation and ownership reflect importance and contribution.
![Page 58: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/58.jpg)
58
Founding CTO. Biggest decision that you’ll make is to either become the VP of Engineering and hire a CTO, or hire the first VP of Engineering. It’s big, because can be fatal.
![Page 59: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/59.jpg)
59
VP of Engineering. Responsible for the development and delivery of the product, and recruitment.
![Page 60: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/60.jpg)
60
VP of Engineering. Has to be the Exemplar Engineer for the teams.
![Page 61: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/61.jpg)
61
Exemplar Engineer. Every single person that works for them wants to be them when they grow up. Critical for recruitment.
![Page 62: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/62.jpg)
62
Exemplar Knowledge. The teams must feel comfortable looking to them for thoughts and decisions on a wide range of technical problems.
![Page 63: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/63.jpg)
63
InnovationThen gets driven by the collaboration.
![Page 64: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/64.jpg)
64
OrganizationalYou must provide a framework and a structure. You must segment.
![Page 65: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/65.jpg)
65
Concluding Thoughts
![Page 66: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/66.jpg)
66
‣ Work hard yourself to be an exemplar.‣ Scientists don't work in a lab to "sequence DNA." They
work in a lab to "cure cancer." • Too often in the "IT" industry we focus on technology and
tools, not their higher purpose and relationship to the rest of the world. You must give your talent a higher purpose than the hammer that they're swinging.
![Page 67: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/67.jpg)
‣ What are they looking for in a leader? • Personal and professional humility coupled with thoughtful
intellect and professional will.
‣ When you do the above, you can be free to let them talk, teach, blog, write papers (i.e. do more than patents).
• You can let them become recognized (and perhaps even tech celebrities) and known in their field.
‣ Titles aren't what important. • Let compensation and ownership reflect importance and
contribution
67
![Page 68: Building and Scaling Technical Teams](https://reader034.fdocuments.net/reader034/viewer/2022051513/547db4e3b4af9fa5158b53d4/html5/thumbnails/68.jpg)
‣ Thanks for Bryan Cantrill for some of the CTO vs VP of Engineering ideas. Covered in a different presentation.
• http://www.youtube.com/watch?v=bAHItZ1cSNM
• http://www.slideshare.net/bcantrill/cto-vs-vp-of-engineering
68