Building software is complicated. And as you grow, it gets more complicated – balancing legacy code and new features, velocity and quality, and a growing volume of user feedback means even small UX pain points are a big issue. This session will explore how Venmo approaches these trade-offs to build great software while keeping users happy without being "reactionary."

1. Scaling Client Engineering
Button @chrismaddern 1

2. Scaling building
int!ro a sto! ry some le!arnings Q&! A
Button @chrismaddern 2

3. Button @chrismaddern 3

4. Button @chrismaddern 4

5. Feature A Feature B
Button @chrismaddern 5

6. Scaling Platform
Button @chrismaddern 6

7. The cloud
Button @chrismaddern 7

8. Sharding Load Balancing
Distributed
Computing
Button @chrismaddern 8

9. Button @chrismaddern 9

10. Button @chrismaddern 10

11. Button @chrismaddern 11

12. Platform Client
Button @chrismaddern 12

13. ! Button @chrismaddern
13
Scaling building
intro a sto!
ry some le!arnings Q&! A

14. Making major changes to large products is hard
Button @chrismaddern 14

15. …or at least noisy
Button @chrismaddern 15

16. Button @chrismaddern 16

17. I really liked my "favorites" at the bottom. Now it seems I
have to search for the few people I pay every day? Am I
missing something?
~Venmo User
Please bring back the recent recipient bar at the bottom of the
screen. Most of my payments are to the same five people.
~Another Venmo User
Button @chrismaddern 17

18. Button @chrismaddern 18

19. Button @chrismaddern 19

20. Did we break, or diminish, a sensible user flow?
Button @chrismaddern 20

21. Users want a quicker way to pay
their closest friends
Button @chrismaddern 21

22. Well.. actually more like this
Button www.usebutton.com 22

23. Well.. actually more like this
Button www.usebutton.com 22

24. Well.. actually more like this
Button www.usebutton.com 22

25. Well.. actually more like this
Button www.usebutton.com 22

26. Hypothesis driven development
Finding root cause of user feedback -> feed into new features
Not reversions
Button @chrismaddern 23

27. Enabling ‘Product Engineers’ to ‘Have their say’
Button @chrismaddern 24

28. WHAT IF
Button @chrismaddern 25

29. A framework to put things in production, infront of small
numbers of users to validate ideas & designs.
Button @chrismaddern 26

30. 30-40 iterations later..
Button @chrismaddern 27

31. The recents drawer was born
Button @chrismaddern 28

32. Button @chrismaddern 29

33. Button @chrismaddern 30

34. Scaling building
! ! ! a story another story Q&A some le!arnings
Button @chrismaddern 31

35. Support-Product Tradeoff
Still Learning
Your FAQ is a tool to protect
yourself as you execute on the
vision.
!
Hiring a support person will
allow you the bandwidth to
focus on building what you
need to.
I can’t take it anymore
Feedback volume means that
bugfixes need to be
responsive and canned
responses / FAQ are a
necessity.
!
You also need to re-calibrate
your level for including
feedback in the product
process (you will hear about
everything!)
!
< 10,000 10k - 100k 100k - 500k 1,000,000 10M +
LEARN
You should be answering
every support request
personally, ship everything and
figure out what works.
!
Start building an FAQ and
have it inform your product
fixes and support proceses.
This is starting to hurt I have no idea. :s
Depending on the nature of
your business, you may be
;)
starting to feel a real burden
of customer support.
!
Key customer complaints
should be considered for fixes
or frame conversations
around broken UX.
Button @chrismaddern 32

36. Quality matters (a lot)
As your team grows, focus on what’s core
Button @chrismaddern 33

37. Build processes that empower engineers
(Data empowers everyone, including engineers)
Button @chrismaddern 34

38. Feedback must inform fixes!
Feedback cannot drive direction
Button @chrismaddern 35

39. Figuring out what to work on?
Clearly define vision & goals towards that
!
Collaboratively build a roadmap
!
Provide a framework for testing hypothesizes (from everyone)
Button @chrismaddern 36

40. Scaling building
! ! ! a story another story some
learnings
Q&! A
Button @chrismaddern 37