Most companies talk about moving fast. Revolut actually did it — and the difference between those two things is almost entirely about how you approach product execution.
When I was VP of Global Business, we were launching new products at a pace that most financial services companies couldn't comprehend. Not because we had more people, but because we had built a machine for iteration. The cycle from idea to live product was compressed to a degree that changed what was even possible strategically.
What made that velocity possible: ruthless prioritisation at the top, genuine autonomy at the team level, and a culture that treated a fast failure as strictly preferable to a slow one. We didn't launch perfect products. We launched products that were good enough to learn from — and then we iterated in public, quickly, based on real signal.
This is harder than it sounds. Most organisations slow down product development not because they lack talent, but because they lack clarity. Every layer of approval, every cross-functional dependency that isn't explicitly managed, every strategy that isn't specific enough to generate a clear "no" — all of it accumulates into drag. At scale, that drag becomes the defining constraint on what you can build.
The lesson I took from Revolut into how I work with founders today: product velocity isn't a function of effort. It's a function of organisational design. How decisions get made, how teams are structured around outcomes rather than functions, how you handle the tension between quality and speed — these are leadership choices, not engineering ones.
The companies that sustain high product velocity as they scale are the ones that treat it as an explicit priority — not an accident of a scrappy early team, but a system that's been deliberately built and protected as the company grows.