Technology Radar
Path-to-production mapping is a standard practice at Thoughtworks that has become newly relevant with the advent of agentic coding. Increased code throughput can expose or amplify bottlenecks elsewhere in the path-to-production, making it essential for teams to optimize the end-to-end flow of software rather than coding speed alone. The activity is most often done in a workshop that includes everyone involved in designing, developing, releasing and operating the software. First, participants list the steps in the process on a whiteboard, from the developer workstation all the way to production. In a second pass, they capture pain points. The activity is often eye-opening, as participants identify delays, risks and inconsistencies they weren’t previously aware of. Tackling those bottlenecks is key to improving overall delivery productivity.
Although path-to-production mapping has been a near-universal practice at Thoughtworks since codifying Continuous Delivery, we often come across organizations unfamiliar with the practice. The activity is most often done in a workshop with a cross-functional group of people — that includes everyone involved in designing, developing, releasing and operating the software — around a shared whiteboard (or virtual equivalent). First, the steps in the process are listed in order, from the developer workstation all the way to production. Then, a facilitated session is used to capture further information and pain points. The most common technique we see is based on value-stream mapping, although plenty of process map variants are equally valuable. The activity is often eye-opening for many of the participants, as they identify delays, risks and inconsistencies and continue to use the visual representation for the continuous improvement of the build and deploy process. We consider this technique so foundational that we were surprised to discover we hadn't blipped it before.
