David Singleton

On Sunday evenings, I actually write a list for myself of if we got these things done this week, that is a good week. I make a list and honestly, then, that drives a lot of just where I decide to spend my time.

I personally will not be involved in really any of the decisions that matter and happen. There are thousands of decisions that an organization of any skill is making every single day. The most important thing is to really focus on hiring the right people, and that means hiring people that you can trust with a tremendous amount of autonomy.

Because we have operating principles of users first and being meticulous in our craft, we actually tend, all of our ways of building plans tend to be wired quite well around this idea that we're going to reserve enough time to really make the experience good.

I'll clear several days in a road, three or four days actually join a team, pick up a small task, hopefully a small feature that we can get all the way from start to finish in production and do that going through the exact experience the team has. While one does that, it's really valuable and important to keep a friction log because then what you want to do is write up the experience.

There's actually more code in the jobs that serve the Stripe API to handle those edge cases than in the actual main flow. And I think that's quite remarkable. Most people wouldn't do that, but it turns out not only was it something I was impressed with, but when I talk to Stripe users, this is very frequently something they tell me and delights them about the product.

We choose to design the way we work to hold those two things true at the same time. So we can operate very rapidly but also be extremely reliable and available for our users. It does take a lot of care and attention and it takes a lot of systems.

The way we think about product development at Stripe, it really is to find the correct set of early users to kind of co-create the product with. So we had shared Slack channels, we'd actually show them product on a very regular basis, get their feedback on it. And only when that original kind of Alpha group was super, super happy with the product did we then think it might be ready to go to a broader audience.

If you have a mechanism to listen to users, get something in their hands quite quickly and then get their feedback on it to run it back through a feedback loop, you're very unlikely to go wrong. It's actually very hard to go wrong if you have that feedback loop working really well.