Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The Good, The Bad, The Ugly of Growth

The Good, The Bad, The Ugly of Growth

In 5 years Paperless Post went from 5 to over 100 people and from a dev team of 2 to 40. I was there for the entire ride as the CTO and not only helped shape the technology but also the culture and structure of the team. We constantly were changing and developing new strategies to achieve our goals. We called this "Continuous Process Delivery", in which we were never satisfied by not only the end product, but the way we were getting there.

Through my time as CTO of Paperless I've seen first-hand the triumphs and tragedies of growth. We did some great things that let people improve as individuals and ship a massive amount of product. We were self-reflective the entire time and that let us see that what we made a bunch of mistakes a long the way as well.

I'd like to take you on a very honest journey of one teams story.

Aaron Quint

June 10, 2015
Tweet

More Decks by Aaron Quint

Other Decks in Programming

Transcript

  1. The Good, The Bad, and
    The Ugly of Growth
    Aaron Quint / @aq / QCon NY 2015

    View Slide

  2. What follows is a true story, from an
    individual’s perspective
    #sincewebeinhonest

    View Slide

  3. View Slide

  4. View Slide

  5. View Slide

  6. In 2015
    • > 1M receivers every week
    • Revenue in the 10s of $M
    • > 110 Employees, > 40 Dev/Ops
    • Office across 2 floors in FiDi

    View Slide

  7. In 2009
    • 0 Receivers Weekly
    • $0 Revenue
    • 4 Full Time Employees, 1 Full time dev + a
    number of consultants (including myself)
    • Using a set of 4 free (windowless)
    cubicles in one of our investors offices
    (which happened to be a women’s
    lingerie co)

    View Slide

  8. 3 Full-Time Devs,
    0 Ops,
    11 total Employees
    I became CTO
    March 2010

    View Slide

  9. Good begets Great
    Bad begets Ugly

    View Slide

  10. So many features, so little time
    In the beginning it was
    all about :shipping:

    View Slide

  11. Good Thing #1:
    Creeds

    View Slide

  12. Started as an oral tradition,
    turned into a written guide

    View Slide

  13. We all live with the choices we all make
    Fixing > Complaining

    View Slide

  14. Roadies > Rock stars
    Helping > Winning

    View Slide

  15. Push for a balance of quality and quantity
    Working > Perfect

    View Slide

  16. Win in pieces, not all at once
    Small changes > Big refactors

    View Slide

  17. The only best practice is that best practices
    change
    Understandable Working Code ==
    Best Practice

    View Slide

  18. agile deployment, focus on end-users
    #=> getting things done and
    constantly improving

    View Slide

  19. But very necessary
    Hiring was a painful and
    stressful process

    View Slide

  20. Find people who could work in as many places
    as possible, and were OK with uncertainty
    We tried to grow cautiously

    View Slide

  21. Good Thing #2:
    Interns!

    View Slide

  22. Ah, the boundless
    ambition
    and energy
    of youth!

    View Slide

  23. Started with 2 Dev Interns
    Grew to ~10 each summer

    View Slide

  24. View Slide

  25. Good Thing #3:
    Mentorship

    View Slide

  26. I like to think that I helped
    Over 5 years I got to
    watch individuals grow

    View Slide

  27. Good devs know they can always improve
    Individual growth is key
    to group growth

    View Slide

  28. Not my first rodeo, but I’m not a grizzled
    commando either
    We were all [relative] noobs

    View Slide

  29. We were open to criticism.
    We knew as a team that we were
    probably doing a lot of bad things

    View Slide

  30. Good Thing #4:
    Self-awareness

    View Slide

  31. Sourced from peers, managers, team
    Biannual Performance
    Reviews

    View Slide

  32. Not afraid to make changes to make our
    process better
    Continuous Process
    Delivery

    View Slide

  33. But we were constantly aware of
    what wasn’t working.
    This is not to say that we did a
    great job implementing change

    View Slide

  34. Great Thing #1:
    Mentorship as a Tree

    View Slide

  35. 3rd and now 4th Generation Mentors
    Each one
    Teach one

    View Slide

  36. Great Thing #2:
    Open Feedback Loop

    View Slide

  37. Meaningful feedback -> Meaningful Progress
    Changes came from reviews
    and turned into action

    View Slide

  38. Great Thing #3:
    Big Shippin’

    View Slide

  39. Create Tool, PAPER, iOS Apps
    Countless impactful features
    that improved our bottom line

    View Slide

  40. What is really?
    Not all rosy

    View Slide

  41. And making changes sometimes
    means redirection
    Moving fast means
    making changes

    View Slide

  42. Bad Thing #1:
    Top-Down Track Correction

    View Slide

  43. Also dangerous, people get hurt
    More People =
    More intentions =
    Harder to shift focus

    View Slide

  44. From written reviews/1-1s
    Collecting feedback
    into themes

    View Slide

  45. (or lack there of)
    A theme emerges:
    Transparency

    View Slide

  46. Bad Thing #2:
    Misunderstanding
    Transparency

    View Slide

  47. Who needs to know what?
    MGMT team was initially
    hesitant

    View Slide

  48. Which garnered respect, but not necessarily
    motivation/better work
    My understanding/method was
    to try to be open and upfront

    View Slide

  49. You can be “open” but if your message isn't
    clear, it’s not going to help
    Transparency actually
    necessitates clarity

    View Slide

  50. Transparency is about
    intention not action

    View Slide

  51. Goals are good
    But we tried to set goals
    through metrics

    View Slide

  52. Bad Thing #3:
    Metrics in the
    wrong direction

    View Slide

  53. Take it in stride?
    What happens when you set an
    arbitrary and potentially unrealistic
    goal and Fail?

    View Slide

  54. The list keeps growing!
    Maybe you feel like you
    didn't get enough done

    View Slide

  55. Bad Thing #4:
    Hiring under duress

    View Slide

  56. Do they? Define desperate
    Desperate times need
    Desperate measures

    View Slide

  57. Ugly Thing #1:
    Bad, Destructive Hires

    View Slide

  58. It means the wrong people
    for the wrong situation.
    That doesn't even mean
    bad developers

    View Slide

  59. Huge expense of time and energy
    Desperate to
    “Make it work”

    View Slide

  60. Ugly Thing #2:
    Burnout

    View Slide

  61. This brings us to my story

    View Slide

  62. There’s a new CTO
    I’m now Chief Scientist

    View Slide

  63. Life, babies, balance, etc.
    I stepped down for a many reasons
    that won’t fit into a single talk

    View Slide

  64. And all are working to address
    the bad and ugly
    Paperless Post is in
    amazing hands right now

    View Slide

  65. Please do so!
    Learning and sharing what
    you’ve learned is crucial

    View Slide

  66. View Slide

  67. CatskillsConf.com Oct 23-25, 2015

    View Slide

  68. Aaron Quint
    @aq
    quirkey.com/hireme
    github.com/quirkey
    beatsryetypes.com
    catskillsconf.com
    THANKS!

    View Slide