
Latest
-
7 principles for balancing agility and durability
Engineering is a game of trade-offs – move fast and break things, or build slow and last forever? Know when to do which.
-
The 6 warning signs of overengineering
How to look for the signs of overengineering in software, why it happens, and how to prevent unnecessary complexity to build maintainable systems.
-
How AI generated code compounds technical debt
“I don’t think I have ever seen so much technical debt being created in such a short period of time”
-
Culture, Clarity, Velocity
This session explores how leaders can examine proposed changes and prepare their teams to move from a culture that impedes progress to one that enables strategic change.
Editor’s picks
Productivity isn’t always fast
It can often feel like we aren’t being productive unless we’re working at max speed. But slow productivity is here to subvert that idea.
How to speed up code reviews
Code reviews don’t have to be painful. Here’s how to embrace tools and more collaborative processes to raise the bar on your review cycle.
Maintain team performance during unexpected change
You’ll have to experience change management at least once in your career. Make sure your teams can maintain performance through it all.

London • June 16 & 17, 2025
Speakers Gergely Orosz, Camille Fournier
and Lara Hogan confirmed
Essential reading

Should the daily stand-up die?
Will the real agile developers please stand up? Please stand up. Please, stand up.
On our Velocity playlist

Engineering owns velocity
In this talk, I’ll explore what engineering leaders need to do to credibly own velocity and deeply align their work with the company strategy.

Launching a Gen AI powered travel companion: A case for tiger teams
Explore Booking.com’s journey in launching a Gen AI travel companion in 3 months, powered by a tiger team approach for rapid, focused product development and innovation.

Goldilocks doesn’t need your story points or your t-shirts
Ben Murray believes there is only really one question you need to ask: is this task small enough?

How to drive pace in your team ??♀️
Alicia Collymore delivers actionable advice that’ll help you to improve your teams’ delivery and pace without a data-first approach.

Planning for success when scaling rapidly
Create goals, prioritize effectively, set expectations, and drive alignment.


The festival of engineering leadership
London • June 16 & 17, 2025
More about Velocity
-
How to develop engineering metrics with people, process, and tools in mind
Fostering a data-driven culture to increase your team’s productivity
-
Adopting an experimentation philosophy
How can companies maximize their investments and take full advantage of the resources they already have to achieve better performance?
-
Building stronger teams with AB testing
How a culture of experimentation can improve your team and your product
-
The challenges of introducing product experimentation
Moving your org from building first to testing first
-
Finding your groove: how to build your team’s operational cadence
Creating the rhythm of work that keeps your teams aligned and connected.
-
Debugging engineering velocity and leading high-performing teams
Looking beyond the speed of delivery to identify what’s really slowing your team down.
Top Velocity videos
-
Distributed teams: how to hone connection, communication, and collaboration
Psychological safety is one of the leading indicators of a high performing team. Yet, forging deep human relationships and building trust can be difficult when your team is distributed or largely interacts on screens.
-
Breaking down silos for better collaboration
Technology at Spotify is filled to the brim with talented, driven and passionate engineers, who together work to solve the challenges we face to reach our north star goals.
-
Driving architecture alignment across a fully-distributed engineering workforce
InVision started as a small startup several years ago with tens of engineers, small teams working independently as velocity was paramount. But as InVision grew to hundreds of engineers, all fully remote, we realized that this independence was actually slowing us down – teams resolving the same problems, inconsistent metrics, etc.
-
Crafting effective 1:1s for distributed engineering teams
Creating relationships with the individual humans on your distributed team is difficult since you rarely get to see them in person! But a team is much less likely to be effective and successful without a foundation of interpersonal relationships and trust.
-
Unlocking success: the components of high-performing teams
Do you have a great team & a great mission but don’t understand why the pace of delivery is so slow? Architecture & tech stack is only one part of the story.
-
Effective meeting facilitation techniques
We’ve all had that experience where we’ve planned the perfect discussion only to have it hijacked by a passionate side-person, lose focus halfway through, or produce the exact same takeaways as you had before you began the discussion.
-
Engaging your engineering team to achieve high performance faster
When bootstrapping new teams, they need to go through the standard process of forming, storming, norming and performing. And in the context of fast-growing companies, with their own level of uncertainty, how can we achieve high performance when teams and goals are constantly changing?
-
Taking a fresh look at setting objectives and key results for your engineering team
In 2013, Google famously published a leading reference for establishing Objectives and Key Results as a way to align teams and set short-term goals.