通过用数据找到真正的瓶颈，改变一件事，并测量效果来改进流程——而不是批量导入某套方法论。流程存在是为了服务团队；当它不再起作用时，就改变它。
改进的循环
text
1. MEASURE → where does work actually slow down? (cycle time, review wait,
deploy frequency, incident rate)
2. FIND THE CONSTRAINT → optimizing anything but the bottleneck is wasted effort
3. CHANGE ONE THING → small, reversible experiments
4. MEASURE AGAIN → did it help? keep, adjust, or revert
5. INVOLVE THE TEAM → they know the pain; they'll own the fix
示例
如果功能需要三周时间，但只有两天是编码，那么约束是等待时间——code review队列、环境可用性、审批——而不是开发人员的速度。对编码施加压力将毫无作用。