At Paysend, we have a team spread out across 38 countries, building products to delight our 7 million customers around the world.
Having a remote and distributed team means that we need to put in place rituals to ensure that everyone in our team shares a common understanding of our product strategy and priorities, so that they can make the best decisions day to day on behalf of our customers and the company.
We would like to share one of our most important rituals, which is our monthly company Demo Day.
Before getting to our demo day, it’s important to know how we think about building products at Paysend. Every year we renew our company product strategy based on what we have learned over the past year: this includes our successes; our failures; new strengths we have acquired; and new opportunities that have opened up in the market. The outcome is a product strategy document that we share and discuss with the whole company, and something we give to new team members so that they have complete clarity on what we’re trying to achieve.
We then break this strategy apart into distinct and non-overlapping goals (we use the OKR framework at Paysend) and then create teams of Paysenders who then take ownership of identifying how to achieve these goals. These teams then fully absorb themselves in their assigned areas, and then work tirelessly to deliver for our customers.
However, when teams fully absorb themselves in their own areas, they can sometimes lose touch with what other teams are doing. This can lead to teams making product decisions that contradict one another; teams creating experiences that are not coherent with each other; or teams duplicating work. As a result, we needed to find a way to allow teams to come together regularly to understand what is happening across the company - therefore allowing teams to share ideas and feedback; and find opportunities to work together more efficiently.

While regularly demoing work is a common practice, and part of standard SCRUM rituals, they can become harder to manage as teams grow in size, and therefore can stop happening. Despite this, and having some unique challenges being a remote-first and distributed team, we decided that a Demo Day is crucial for our teams to stay close to one another, and deliver our product strategy together.
We launched our first company Demo Day in February, which is run monthly by Ksenia in our People & Culture team. Here are some of the things she has found are important in making them successful.
And here are some of the things our team says about our Demo Day: