What do you think?
Rate this book
Frictionless: 7 Steps to Remove Barriers, Unlock Value, and Outpace Your Competition in the AI Era
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.
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.
312 pages, Paperback
Published November 12, 2025
327 people are currently reading
407 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 14 of 14 reviews
January 16, 2026
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.
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.
January 11, 2026
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.
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.
February 18, 2026
"Accelerate" was already overrated - the best part (75% of the value) was the diagram in the appendix :) Unfortunately, "Frictionless" is even worse. Why so?
1. I haven't read such a dry (tech) book for some time - it felt like yet-another-scientific paper written just because it was required for someone's PhD :( It doesn't tell any story, it doesn't try to capture DX in any new angle, it doesn't come with any inspiring examples
2. The "framework" is extremely enterprisey - like written by consultants for their corporate "victims". I couldn't help the feeling that its form is optimised for non-tekky business consultants, instead of actual engineers.
3. The formula here is just a prescription - list of activities peppered with buzzwords to compete in some bullshit bingo - it doesn't challenge you to think or ask good questions, but hands you in a checklist. It's both annoying and kinda pointless (even if effect is achieved, I don't believe it would be achieved long-term this way).
4. Frankly, even the approach to DX itself (its "aspects" and "dimensions") feels both dated and oversimplified. It got me bored around 30% tops.
This is NOT a good book about DX. Unless you're some corporate desperate, clueless about why things take so much time in your eng. teams. But even in this case, start talking to your engineers first ...
1. I haven't read such a dry (tech) book for some time - it felt like yet-another-scientific paper written just because it was required for someone's PhD :( It doesn't tell any story, it doesn't try to capture DX in any new angle, it doesn't come with any inspiring examples
2. The "framework" is extremely enterprisey - like written by consultants for their corporate "victims". I couldn't help the feeling that its form is optimised for non-tekky business consultants, instead of actual engineers.
3. The formula here is just a prescription - list of activities peppered with buzzwords to compete in some bullshit bingo - it doesn't challenge you to think or ask good questions, but hands you in a checklist. It's both annoying and kinda pointless (even if effect is achieved, I don't believe it would be achieved long-term this way).
4. Frankly, even the approach to DX itself (its "aspects" and "dimensions") feels both dated and oversimplified. It got me bored around 30% tops.
This is NOT a good book about DX. Unless you're some corporate desperate, clueless about why things take so much time in your eng. teams. But even in this case, start talking to your engineers first ...
April 3, 2026
Having read and enjoyed Nicole Forsgren’s earlier book Accelerate (coauthored with Jez Humble and Gene Kim), I had high expectations for Frictionless, her new book with Abi Noda.
The first ~40 pages, which introduce key concepts like Developer Experience, feedback loops, flow state, and cognitive load, were promising. Unfortunately, the rest of the book largely turns into a detailed manual on running surveys effectively, along with repeated advice on what to measure and pay attention to.
At nearly 300 pages, the book contains only two diagrams and about five tables—the remainder is dense, monotonous text focused on a 7-step process for improving DevEx. To make matters worse, there isn’t even an index, which is particularly frustrating for a book this long and reference-heavy. The presentation felt ponderous at times, and I nearly gave up on finishing it.
That said, I pushed through and found some genuinely useful sections: practical guidance on conducting surveys well, ranking potential DevEx initiatives, and adjusting metrics in light of AI-assisted development workflows. The core ideas have real value, but the authors could have conveyed them far more effectively in half as many pages, with additional visuals and a more engaging writing style.
I hope they refine it in a future edition—there’s clear potential here.
The first ~40 pages, which introduce key concepts like Developer Experience, feedback loops, flow state, and cognitive load, were promising. Unfortunately, the rest of the book largely turns into a detailed manual on running surveys effectively, along with repeated advice on what to measure and pay attention to.
At nearly 300 pages, the book contains only two diagrams and about five tables—the remainder is dense, monotonous text focused on a 7-step process for improving DevEx. To make matters worse, there isn’t even an index, which is particularly frustrating for a book this long and reference-heavy. The presentation felt ponderous at times, and I nearly gave up on finishing it.
That said, I pushed through and found some genuinely useful sections: practical guidance on conducting surveys well, ranking potential DevEx initiatives, and adjusting metrics in light of AI-assisted development workflows. The core ideas have real value, but the authors could have conveyed them far more effectively in half as many pages, with additional visuals and a more engaging writing style.
I hope they refine it in a future edition—there’s clear potential here.
January 10, 2026
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...
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...
January 17, 2026
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.
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.
December 19, 2025
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
January 7, 2026
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.)
December 28, 2025
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
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
January 20, 2026
Too much general 'tech initiative' advice and not enough DevEx examples. Read the worksheet on their site and not the book
January 24, 2026
Good book if you're looking to grow/manage dev acceleration in an org and build a business case, but if you're looking for technical recipes you'll be disappointed.
February 16, 2026
Feedback loops, flow state, and cognitive load.
February 25, 2026
More like 3.5 stars out of 5. The title includes "Outpace Your Competition in the AI Era" but the parts in the book that address AI seem to be tacked on.
March 6, 2026
The book could not capture me. It is written as a how-to. Could have been a couple of blog posts.
Displaying 1 - 14 of 14 reviews