Velocity over Everything

Notes on Geoff Charles (VP Product at Ramp) on team velocity and single-threaded teams — and why we're taking a calculated bet on a similar structure at instacar.

#product

One of the best content pieces I’ve seen in a while features Geoff Charles, VP of Product at Ramp, and his in-depth thinking on team velocity.

Velocity is Not Optional, It’s Essential#

At Ramp, velocity is more than a metric; it’s a culture. In just two years, they’ve reached an annual run rate of over $100 million, and they attribute much of this to their relentless focus on speed. The question we should all be asking is: how can we embed a culture of velocity in our own product and tech teams?

The Magic of Single-Threaded Teams#

In a traditional organizational structure, teams often juggle multiple projects, priorities, and stakeholders. Ramp’s approach to “single-threaded teams” makes each team responsible for one specific goal or project. They are the “single thread” that runs through that initiative, from conception to execution.

Why it seems to work:

Despite the higher cost often associated with single-threaded teams compared to traditional structures, we — at instacar — are taking a calculated risk. Alongside Dimitris Togias (CTO), we’re adopting a similar team structure, though on a more modest scale, and aiming to implement these changes in the near future. Our main goal is to accelerate the shipping of products for both our consumer app and our internal fleet management tool. I have strong confidence that the outcomes will more than justify the additional expense.

Watch the full conversation on Lenny’s Podcast →

License

CC BY-NC-SA 4.0 This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

Related Posts