Accelerate by Nicole Forsgren, Jez Humble, and Gene Kim - A Summary

You’re receiving this because you signed up on our website. Want to unsubscribe? Just reply to this email with the words “no thanks.”

First-time reader? Join other business leaders for free.

Listen to this post here.

Sponsored by

Want to sell more?

Instead of paying salaries, many companies hire commission-only reps—experienced sellers who get paid only when they produce.

Post your opportunity on CommissionOnly.com.

Thousands of motivated reps are actively looking for performance-based roles.

Authors: Nicole Forsgren, Jez Humble, and Gene Kim

Nicole Forsgren is a technology researcher known for measuring software delivery performance, Jez Humble is a software delivery expert and coauthor of Continuous Delivery, and Gene Kim is an author and researcher focused on DevOps and high-performing technology organizations.

In Accelerate, the central idea is that software performance can be measured and improved. High-performing teams don’t have to choose between moving quickly and keeping systems reliable. The strongest organizations do both.

The book uses years of research to identify the technical practices, management systems, and cultural habits connected to better software delivery and stronger business results.

Technology teams create more value when they can deliver small improvements quickly, learn from real users, and recover fast when something goes wrong.

Large releases, long approval chains, manual work, and fear of failure make delivery slower and riskier. Smaller changes are easier to test, easier to review, and easier to repair.

This matters beyond the technology department. When software delivery improves, the business can respond faster to customers, test new ideas sooner, reduce costly outages, and turn strategy into working products more reliably.

If this idea resonated with you, share it with your network using the social sharing buttons at the top of this post.

Start by measuring the four delivery metrics for each major product or service: deployment frequency, lead time for changes, change failure rate, and time to restore service. Use them to understand how work flows through the system, not to rank individual employees.

Create a baseline before setting targets. Identify the largest source of delay or instability, then improve from the team’s current position instead of copying another company’s goals.

Reduce the size of each change. Smaller releases are easier to test, review, deploy, and repair. They also give the business faster feedback about what customers actually need.

Automate repetitive testing, security checks, deployments, and monitoring where practical. Reliable automation reduces manual errors and helps teams discover problems sooner.

Track where work waits. A change may require only a few hours of effort but spend weeks waiting for review, testing, approval, or another department. Remove approvals and handoffs that don’t reduce meaningful risk.

Give teams clear ownership of a product or service. When the same group can build, test, release, monitor, and improve its work, fewer problems disappear between departments.

Reduce unnecessary dependencies. If a team needs help from several other groups to make a small change, redesign responsibilities or systems so more work can be completed independently.

Invest in monitoring and recovery. Teams need useful logs, alerts, rollback procedures, and tested backups so they can understand failures and restore service quickly.

Review incidents without turning them into blame sessions. Examine the system conditions, missed warning signs, and weak safeguards that allowed the problem to happen. Accountability matters, but punishment shouldn’t replace learning.

Make bad news easy to share. Leaders should respond constructively when employees raise risks or admit mistakes. Hidden problems become more expensive than visible ones.

Build faster feedback into product decisions. Release smaller versions, observe customer behavior, and use what you learn to guide the next investment instead of spending months building from assumptions.

Limit work in progress. Starting too many projects slows all of them. Finish a smaller number of valuable changes before adding more work.

Connect technology metrics to business outcomes. Faster delivery matters when it improves customer experience, revenue, quality, compliance, or operating efficiency.

Finally, treat software delivery as an organizational capability. Leadership decisions about funding, team structure, incentives, risk, and culture shape how quickly technology can create business value.

Share the insights below on LinkedIn or X/Twitter and we’ll feature your business in the newsletter. Just use the hashtag #BizBookDaily. It’s as simple as that.

Muriithi Mwenda — Procurement, Sales & Operations Professional — Follow them on LinkedIn if you’re looking for practical insights on procurement, sales operations, and business growth.

We’ve been collecting standout business insights from experienced operators—short, practical ideas that hold up in the real world. Take a look at our Top Insights here.

Forsgren, Humble, and Kim provide a whole lot more useful info in Accelerate. Here are three reasons you might want to read the full book:

Consider skipping this book if you want a beginner’s guide to coding rather than a research-based book about technology organizations.

Hidden gems most people miss. One powerful idea from each.

BOOK 1: Relationship Intelligence by Richard Madden
THE INSIGHT: Relationships drive influence and long-term success.

BOOK 2: Retire in 10 Years or Less by Ryan Lee
THE INSIGHT: Fast retirement requires aggressive financial discipline.

Sponsored by

Many of the best business books begin as ideas leaders have been refining for years—frameworks, philosophies, or lessons learned the hard way. Writing the book forces those ideas into clear form, and once they’re on the page, they can travel far beyond a single conversation or presentation.

At MemoirGhostwriting.com we write memoirs and business books for entrepreneurs, founders, executives, and industry experts. Most of our clients have been meaning to write their book for years—they just don’t have the time to sit down and do it properly. We help them speak more frequently on stages, scale consulting practices, attract more leads and move them deeper down their marketing funnels, increase conversion rates in complex sales cycles, and position them for for-profit boards.

We don’t just help you write, we take the whole project off your plate and see it through to a finished, publishable book.

Our team handles the entire process:

If you’ve ever thought about what a best-selling business book could do for you, let's talk.

Learn more:

Know someone who likes smart business ideas?

Forward this email to one colleague or friend who would enjoy today’s lessons.

Or send them here:
BusinessBookDaily.com