Frictionless: 7 Steps to Remove Barriers, Unlock Value, and Outpace Your Competition in the AI Era

by Nicole Forsgren, Abi Noda

In an era where AI can generate code in minutes, why do software teams still struggle to deliver?



While artificial intelligence transforms how we build software, most organizations remain trapped by friction that turns AI's promise of speed into bottleneck nightmares. Slow deployments, brittle systems, and frustrated developers create invisible drag on innovation—costing US companies $1.52 trillion annually in technical debt alone.



7 Steps to Remove Barriers, Unlock Value, and Outpace Your Competition in the AI Era reveals the strategic framework that separates high-performing software organizations from the rest. Authors Nicole Forsgren and Abi Noda show how eliminating development friction isn't just about happier developers—it's about unlocking competitive advantage.

Drawing from work with hundreds of software teams, this practical guide demonstrates how companies like LinkedIn transformed their trajectory by systematically removing friction, going from monthly deployments to multiple releases per day. You'll discover how poor developer experience hides catastrophic business risks and—most importantly—how to fix it.



Perfect for engineering leaders, CTOs, and anyone responsible for software delivery, this book provides everything needed to transform developer proven measurement frameworks, a 7-step implementation methodology, and real-world strategies that work whether teams embrace AI tools or use established workflows.



The organizations investing in developer experience today will move faster, build better, and lead tomorrow. Whether you're struggling with slow deployments, frustrated developers, or unrealized AI potential, Frictionless shows you how to remove the barriers limiting your success.

Genres: Technology, Leadership, Nonfiction, Business, Management, Programming

314 pages, Kindle Edition

Published November 12, 2025

Reviews

[Richard · Rating 2 out of 5]

20% actual devex 80% how to drive change in large organizations

Helpful for someone who hasn't driven large initiatives before. Could've been a blog post for people who just want devex-specific pointers. Very repetitive.

AI specific points seemed crammed in after it was already written.

[Eric · Rating 1 out of 5]

Let's be clear, this book is completely empty. There's no practical or technical advice in it. It's full of consultant speak like : "Share your progress", "Learn and improve", "Navigate conflicts", "The most important tools are the ones you use."

As much as Accelerate was pragmatic, we can clearly see that the authors don't have anything to say anymore, but they still want to sell some paper. I read until page 100 and then I skimmed through the rest to not waste more time.

Let me summarize DevEx for you :

- Fasten feedback loop
- Reduce cognitive load
- Improve flow state

That's it. If you know the SDLC, go through it, identify pain points and solve them. But this book won't tell you how, because it's empty. Or they will tell you stuff like "Interview developers", "Manage technical debt." and "Improve tooling." Duh...

What I recommend instead of wasting your money on this is to read Accelerate, the DORA Capabilities (free), and subscribe to The Pragmatic Engineer. These resources will tell you how to *actually* improve DevEx.

OK, next...

[Miguel Alho · Rating 5 out of 5]

This validates a lot of what I've observed taking on some DevEx and platform engineering initiatives over the past couple of years. Through it I can see a bunch of shortcomings in my current approach, and I now have a ton of pointers on how to adjust to maximize the effectiveness of the initiatives. I can revamp and improve the current approach very much with the ideas in this book.

Like Accelerate, this is dry and straight to the point. In some bits it was repetitive - the same points and justifications presented but in different steps of the process. Still, very valuable. there's no specific tech implementation recipe for getting this in place as it's wildly variable to the context your in, but some sort of companion "playbook" with recipes and patterns would be highly valuable, too, to reduce the getting started effort.

[Artem · Rating 3 out of 5]

This is a manual for people who need permission to be productive and do things right without toil. If you work in an environment that requires justification for common sense, this book is for you.
Coincidentally, I read this in parallel with Rework by Jason Fried and DHH. While both essentially discuss effective craft, they come from opposite viewpoints. Reading them together made me realize that Frictionless starts from an upside-down world where things have gone out of control, compared to the philosophy of Rework where the aim is to prevent this by design.

[kari · Rating 5 out of 5]

super timely read for me. the parts about framing devex initiatives to different audiences in the language they care about with specific examples of how to do that was fantastic. it really helped me puzzle out some of the framing problems i’ve had when trying to get traction on initiatives over the last year

[Davit · Rating 5 out of 5]

this books is very much different from what I have read before. it provides many practical suggestions and can be served as a playbook for companies 's tech transformation phase. The approaches can be used not only by DevX teams, but also by those which do global refactoring(breaking down monolith, going towards event driven architecture, etc.)

[Sebastian Sanio · Rating 4 out of 5]

The book explains what DevEx (developer experience) is and goes through steps and good practices to kickstart DevEx at any company
I found the book useful because I've been thinking about the topic for a few months now, but I also found it repetitive and shallow