1.
@joshuaxlsJoshua Slaytonangel.co/joshuaxlsDOING THE WRONG THINGS THE RIGHT WAY

2.
IN THREE YEARSOver $2 billion raised$9 million invested online50,000 introductions between talent and startups200,000 submissions to over 100 incubatorsMillions of API requests per day

3.
SECRET?BIGWHAT’S THE

4.
WHAT WE PLANNED ONOver $2 billion raised$9 million invested online50,000 introductions between talent and startups200,000 submissions to over 100 incubatorsMillions of API requests per day

5.
WHAT WE DIDN’T PLAN ONOver $2 billion raised$9 million invested online50,000 introductions between talent and startups200,000 submissions to over 100 incubatorsMillions of API requests per day

6.
WE MOVED FAST AND WE BROKE A LOTOF RULES.THROUGH TRIAL AND ERROR, WEDISCOVERED HOW TO RUN A SMALLPRODUCT TEAM.

7.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

8.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

9.
IF SOMEONE NEEDS TO BE MANAGED, THEY SHOULDN’T BEAT YOUR STARTUP.

10.
MANAGERS CREATE UNNECESSARY WORK.

11.
GOOGLE “VALVE EMPLOYEE HANDBOOK” AND READ IT.

12.
* low resolution image stolen from Valve’s Employee Handbook

13.
ALL BEGAN AS SIDE PROJECTSOver $2 billion raised$9 million invested online50,000 introductions between talent and startups200,000 submissions to over 100 incubatorsMillions of API requests per day

14.
CREATE CUSTOMERS, NOT JUST FEATURES.

15.
No ManagementEveryone is a managerEveryone owns their workFoster interpersonal skillsValue customer, not feature, creationRecruiting is the hardest thing to do

16.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

17.
EVERYONE RECRUITS.EVERY DAY.EVERYONE HAS VETO POWER.

18.
HIRE OTHER FOUNDERS.

19.
* low resolution image stolen from Valve’s Employee Handbook

20.
YOU MUST LET GO OF PEOPLE THAT DON’T WORK OUT.YES, IT SUCKS.

21.
Constant RecruitingHire founders, generalistsEveryone recruits all the timeRelease the bad fitsImprove your recruiting process

22.
NOManagementSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

23.
YOU CAN’T SCHEDULE CREATIVITY.SOME PEOPLE COME IN AT DAWN.SOME PEOPLE COME IN AFTER LUNCH.SOME PEOPLE WON’T COME IN.

24.
VALUE RESULTS, NOT TIME IN THE OFFICE.

25.
COMMUNICATING PRE-INTERNET

26.
COMMUNICATING IN 2013

27.
STILL, FACE TIME BREEDS SPONTANEITY.BUILD A FUN OFFICE.TAKE CARE OF YOUR TEAM.

28.
No SchedulesKeep asynchronous channels openKeep synchronous channels openHave an office people enjoy being inValue results, not time in the office

29.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

30.
Even good code stinks.Learn to deal with it, and keep moving forward.

31.
SET EXAMPLESSPEND TIME WITH NEW HIRESCOMPANY WIKICODE COMMENTS“MASTERSTROKES”INTERNAL PRESENTATIONS

32.
THE BOY SCOUT RULEALWAYSLEAVECODECLEANERTHAN YOUFOUND IT!

33.
CRISES WILL HAPPENIT MEANS THAT YOUR TEAM ISMOVING AT AN APPROPRIATESPEED.

34.
“Smooth seas do not makeskillful sailors”

35.
No Code ReviewsTeach by exampleDocument everythingLeave code cleaner than you found itCrises will happen, learn from them

36.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

37.
WE BEGAN WITH ATEST-DRIVEN DEVELOPMENTMETHODOLOGY.

38.
TEST-DRIVEN DEVELOPMENTTOO SLOW

39.
TEST-DRIVEN DEVELOPMENTTOO FOREIGN

40.
TEST-DRIVEN DEVELOPMENTTOO DOGMATIC

41.
JUST BE READY FOR...

42.
No TestsAlarms on everythingPipe them to email, chat, SMSBug fixes must be a top priorityTests are fine, just not cumpulsory

43.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

44.
Constant CustomerSupportCustomers are priority #1Everyone does customer serviceRespond to customers immediatelyTurn negative experiences into loyalcustomers

45.
NOManagersSchedulesCode ReviewsTestsCONSTANTDeploymentCustomer SupportHiring

46.
RELEASE CONSTANTLY.

47.
Seven DeploysTwo Hours

48.
That’s 30,660 releases per year!** we don’t actually release that much

49.
OUR REPOSITORYmaster commitcommitcommitcommit***** ready to deploy

50.
IF YOU MUSTmaster commitcommitcommitcommitfeature

51.
DON’T DO BIG FEATURES.SHIP AN MVP IMMEDIATELY, THEN ITERATE.

52.
Constant Deploymentmaster is always deployableOptimize deploys to be quickRolling deploys, users see nothingNo big releases, iterate instead

53.
SO WHAT’S THEBIG PICTURE?

54.
ELIMINATE PROCESSLEVERAGE CREATIVITY

55.
TECHNICALDEBTYOU CAN PAY IT DOWN LATER.BE SMART ABOUT IT.USE IT TO MOVE QUICKLY.

56.
THE ONLY ADVANTAGE YOU’RE GUARANTEEDOVER THE BIG GUYSSPEED

57.
TEAM TEAM TEAM TEAM TEAM TEAM TEAMTEAM TEAM TEAM TEAM TEAM TEAM TEAMTEAM TEAM TEAM TEAM TEAM TEAM TEAMTEAM TEAM TEAM TEAM TEAM TEAM TEAMTEAM TEAM TEAM TETEAMIS EVERYTHING

58.
GOOD LUCK!(and I hope to see you all on AngelList)

59.
THANK YOU!@joshuaxlsJoshua Slaytonangel.co/joshuaxls