HI.
HI.
EVERY MISTAKE.
THREE SESSIONS
1. Launch Without Code
2. Working with a Dev
3. How the Web Works
HOW TO
WORK WITH
DEVELOPERS
Innovative development
Change
Uncertainty
Options
Ambiguity
Surprises
Who do you need
How do you find them
How to work together
WHO DO
YOU NEED
Business Vision
Product Manager
Developer
Designer
Tester
Communication
Community involvement
Product/business thinker
Technical
Advisor
RELATIONSHIP
o
C

t
n

r
to
c
ra

C

fo
o

r
e
d
n
u
Change
Uncertainty
Options
Ambiguity
Surprises
o
C

t
n

r
to
c
ra

C

fo
o

r
e
d
n
u
c
ra

t
n

o
C

r
to

• By project or by hour?
• Involved management
fo
o

r
e
d
n
u

C

• Ideal
• A marriage
• Vesting; symmetry
o
C

t
n

r
to
c
ra

C

fo
o

r
e
d
n
u
g
in
d
n yee
u o
o l
F p
m
E
FINDING
GOOD
PEOPLE
Tech meetups
Startup weekends
New role
Coworking spaces
Learn to code
Contribute
Went to Meetups
Phone calls
Customer list
Simple landing page
Blog
Following, audience
Industry events
Research
Long term community member
You don’t find a good cofounder,

You earn one.
Jason Freedman, 42floors
“To find a great technical cofounder, you need to convince
them of the following:
Your idea is better than
all of their ideas
...The equity is worth
spending all of their
spare time working for
no money...
...You are worth 50% of
the equity of the company
You will execute and
convert an idea into a
big successful business
...You’re better than all of
the other biz people
pitching them.”
-Vinicius Vacanti
EVALUATING
DEVELOPERS
TWO WAYS

Reputation
Work with them
Interviewing is
broken in tech
"I've fired one out of every three
people I've hired. That might make
people think I'm bad.... but I think
I'm quite good....
Short Paid Projects

http://humbledmba.com/everyone-sucks-at-interviewing-everyone
Chemistry
Communication
What do they ask
What don’t they ask
Openness
Gut feeling
Persuasive: “I can do that!”
Easy to continue
Easy to stop
Technical
Advisor
COMMUNICATION
KNOW WHAT YOU WANT

• Think small; user stories
• Define milestones
• Own the product
• Be available
As a

,

when I

,

I would like to

.
VERSION 1.0

•

Is this feature
absolutely critical to
my first sale?

•

Succinct overview +
super detailed flow
STAY CONSISTENT
To me there is nothing as frustrating
as having to deal with someone,
who all of a sudden wants things
cha...
EMPATHY

• Development is not
wizardry, it’s a craft

• Development is not an

obstacle to overcome, it
is the path

• Diffi...
“....having unrealistic
expectations about how
quick and easy it should be.”
George Cheng
MANAGEMENT
Change
Uncertainty
Options
Ambiguity
Surprises
AGILE
“A common mistake I see people
make: A founder will ship product
specs off to a developer, trusting
that everything will be...
AGILE
•

Frequent releases of
working product

•

Constant
communication

•

Break large tasks into
small tasks
Text
TOOLS

Trello
Asana
Flow
Pivotal Tracker
TOOLS

“Above all else,
agile is about
people”
ASK STUPID QUESTIONS
"Don't be afraid to say, So what does
that mean?
...we found that often we've
uncovered, 'Oh, wait; I...
BEST PRACTICES

Testing
Documentation
Clean code

Technical
Advisor
OUTSOURCING
GO FOR IT
Non-core
Clearly defined + evaluated
Time to manage
Lack of control is fine
NO WAY
Core business
To save money
Innovative/Flexible
Ambiguity
ODESK/ELANCE/ETC
VERY IMPORTANT PHRASE
Don’t go for the lowest bid
Hire two at first
Derek Sivers
Thank you to Daniel
Szmulewicz (and all the
developers I’ve worked with)
Questions!
THREE SESSIONS
1. Launch Without Code
2. Working with a Dev
3. How the Web Works
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Working with great developers
Upcoming SlideShare
Loading in …5
×

Working with great developers

512 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
512
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Working with great developers

  1. 1. HI.
  2. 2. HI.
  3. 3. EVERY MISTAKE.
  4. 4. THREE SESSIONS 1. Launch Without Code 2. Working with a Dev 3. How the Web Works
  5. 5. HOW TO WORK WITH DEVELOPERS
  6. 6. Innovative development
  7. 7. Change Uncertainty Options Ambiguity Surprises
  8. 8. Who do you need How do you find them How to work together
  9. 9. WHO DO YOU NEED
  10. 10. Business Vision Product Manager Developer Designer Tester
  11. 11. Communication Community involvement Product/business thinker
  12. 12. Technical Advisor
  13. 13. RELATIONSHIP
  14. 14. o C t n r to c ra C fo o r e d n u
  15. 15. Change Uncertainty Options Ambiguity Surprises
  16. 16. o C t n r to c ra C fo o r e d n u
  17. 17. c ra t n o C r to • By project or by hour? • Involved management
  18. 18. fo o r e d n u C • Ideal • A marriage • Vesting; symmetry
  19. 19. o C t n r to c ra C fo o r e d n u
  20. 20. g in d n yee u o o l F p m E
  21. 21. FINDING GOOD PEOPLE
  22. 22. Tech meetups Startup weekends New role Coworking spaces Learn to code Contribute
  23. 23. Went to Meetups
  24. 24. Phone calls Customer list Simple landing page Blog Following, audience Industry events Research Long term community member
  25. 25. You don’t find a good cofounder, You earn one. Jason Freedman, 42floors
  26. 26. “To find a great technical cofounder, you need to convince them of the following:
  27. 27. Your idea is better than all of their ideas
  28. 28. ...The equity is worth spending all of their spare time working for no money...
  29. 29. ...You are worth 50% of the equity of the company
  30. 30. You will execute and convert an idea into a big successful business
  31. 31. ...You’re better than all of the other biz people pitching them.” -Vinicius Vacanti
  32. 32. EVALUATING DEVELOPERS
  33. 33. TWO WAYS Reputation Work with them
  34. 34. Interviewing is broken in tech
  35. 35. "I've fired one out of every three people I've hired. That might make people think I'm bad.... but I think I'm quite good.” Paul English, CTO of Kayak.com
  36. 36. Short Paid Projects http://humbledmba.com/everyone-sucks-at-interviewing-everyone
  37. 37. Chemistry Communication What do they ask What don’t they ask Openness Gut feeling
  38. 38. Persuasive: “I can do that!” Easy to continue Easy to stop
  39. 39. Technical Advisor
  40. 40. COMMUNICATION
  41. 41. KNOW WHAT YOU WANT • Think small; user stories • Define milestones • Own the product • Be available
  42. 42. As a , when I , I would like to .
  43. 43. VERSION 1.0 • Is this feature absolutely critical to my first sale? • Succinct overview + super detailed flow
  44. 44. STAY CONSISTENT To me there is nothing as frustrating as having to deal with someone, who all of a sudden wants things changed thinking it to be "as easy" as nailing a extra bit of wood onto [a] closet. Michael Bruggeman
  45. 45. EMPATHY • Development is not wizardry, it’s a craft • Development is not an obstacle to overcome, it is the path • Difficulties hard to relate
  46. 46. “....having unrealistic expectations about how quick and easy it should be.” George Cheng
  47. 47. MANAGEMENT
  48. 48. Change Uncertainty Options Ambiguity Surprises
  49. 49. AGILE
  50. 50. “A common mistake I see people make: A founder will ship product specs off to a developer, trusting that everything will be done the way the founder sees it in her head, and only check back in when the final product is ready.” Nelly Yusupova, TechSpeak
  51. 51. AGILE • Frequent releases of working product • Constant communication • Break large tasks into small tasks
  52. 52. Text
  53. 53. TOOLS Trello Asana Flow Pivotal Tracker
  54. 54. TOOLS “Above all else, agile is about people”
  55. 55. ASK STUPID QUESTIONS "Don't be afraid to say, So what does that mean? ...we found that often we've uncovered, 'Oh, wait; I actually don't want to do it that way, and here's why.' Katie Finnegan, Hukkster
  56. 56. BEST PRACTICES Testing Documentation Clean code Technical Advisor
  57. 57. OUTSOURCING
  58. 58. GO FOR IT Non-core Clearly defined + evaluated Time to manage Lack of control is fine
  59. 59. NO WAY Core business To save money Innovative/Flexible Ambiguity
  60. 60. ODESK/ELANCE/ETC VERY IMPORTANT PHRASE Don’t go for the lowest bid Hire two at first Derek Sivers
  61. 61. Thank you to Daniel Szmulewicz (and all the developers I’ve worked with)
  62. 62. Questions!
  63. 63. THREE SESSIONS 1. Launch Without Code 2. Working with a Dev 3. How the Web Works

×