Building software is complicated. And it gets more so as the scope of the project increases – balancing legacy code and new features, velocity and quality, and a growing volume of user feedback. This means even small UX pain points become big issues. The session will explore how Venmo approaches these trade-offs to build great software while keeping users happy without being "reactionary."
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
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