One of my litmus tests for a company, and sometimes an interview question, is this: “You have to change a single word in legal copy on your production website and it’s critical. How quickly can you get that fix to production?”

The gap between answers is always interesting: minutes for some, hours or even days for others.

If it takes days to change a single word, the friction in that pipeline is the same friction slowing down every feature your team is trying to ship. Cycle time is one of the biggest enablers or drag points a team has.

The delays usually live in one of two places. The first is the engineering toolchain: build times and deployment automation that make anyone nervous about pushing quickly. The second is business and process governance: review queues and release approval chains that were designed for monthly software cycles and never kept pace when the team moved to continuous delivery.

A prior organization I worked for could accomplish that change in about 30 minutes on their newer platform. 2 hours on the older, much larger one. Those were numbers worth being proud of.

The question is loosely rooted in what the DORA framework surfaces as lead time for changes, one of the clearest signals of a healthy delivery pipeline. The one-word litmus test just makes it concrete enough to get an honest answer in a room.

If you can’t move a single word in minutes, both aspects of that pipeline are worth a deeper look.