We have well-defined product teams that have domain expertise and product engineering and design collaborate in order to solve problems to put stuff out there as quickly as possible in order to gather feedback in an iterative fashion.

Collaboration so far between different teams has been very seamless and what I really enjoy about working here is that everyone is minding about the business outcome and how we build solutions that talk to the business outcome that we want to achieve. We have engineers, aspiring partners, that always question “Why?” and “What’s the value?” and “What’s the impact of what we’re building?” and it’s not a one directional situation coming from Product and this is how we build.

Our Engineering team is very involved in helping craft those outcomes and build technology and methodologies within our engineering organizations that drive to those outcomes. So, specifically, we take advantage of the continuous delivery, which allows us to get products in the customers hands faster, which then allows us to get that feedback that John was referring to back into our hands faster then iterate more rapidly; shortening the overall development cycles to allow us to build, measure, and learn and iterate at that high pace. There’s obviously more and more we want to do to mature that model, but we’re pretty happy with where we are while growing the team very rapidly.

We are also improving our internal processes to allow this, so we’re constantly improving as the team grows it’s a very happy problem to have － that we’re going too fast － that we need to support our teams, our processes in order to scale quickly and keep that agile experimentation drive to get results out quicker.