Chapter 03 / 20
3. Diagnose the Engineering System
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
Before prescribing a tool, follow a change. Choose a customer-facing request, a production defect, or an incident with a start and an end. When did somebody know what was needed? When was the first test written, the review requested, approval granted, release completed, and customer result checked? Who was waiting at each boundary? A team may be busy at every instant and still deliver slowly because no one owns the wait between teams.
The engineering competency framework gives nine places to look: delivery, quality and reliability, flow and developer experience, architecture, product focus, learning, people, collaboration, and security. These are not nine independent dials. An unclear customer promise makes planning unstable; an opaque architecture makes review slow; missing ownership prolongs an incident. Raise the competency that constrains the outcome, not the one most amenable to an AI demonstration.
Suppose the longest wait is a change-approval queue. Ask whether the delay is a protective control, an external dependency, or avoidable manual handoff. Removing a control without understanding its failure mode may shorten a chart and worsen the customer's experience. If the constraint is missing product clarity, generating implementation faster simply makes wrong work arrive earlier. If the constraint is poor documentation, retrieval can make stale answers easier to find; first establish current ownership and source-of-truth rules.
Do not assume the first bottleneck stays put. In its Hyperforce account, Salesforce describes faster local development alongside review and approval pressure, then changes to its surrounding workflow. Its before/after cycle-time figures also reflect approval-process improvements, so they cannot isolate AI's contribution. Follow arrivals, work-in-progress, service capacity, and queue age through all gates rather than attributing a whole-system gain to a single new tool.
The guide names effective, efficient, innovative, engaging as organizational goals. This book names reliable separately as an explicit countermeasure to rushing. A maturity level is a description of operating capability, not a target number of autonomous agents. An organization that can decline an unsafe automation may be more mature than one that deploys it everywhere.
Try the map: Draw one outcome's timeline on a page. Put a name at each handoff, a reason beside each safeguard, and a question mark where timestamps or customer evidence are missing. Interview the people who receive the work as well as those who generate it. Then choose a constraint to test.