Christopher Justice · Project Management
Your Process Is Optimized for 2015
In 2015, the bottleneck was writing code. Teams needed coordination, estimation mattered, documentation came after.
# Your Process Is Optimized for 2015
In 2015, the bottleneck was writing code. Teams needed coordination, estimation mattered, documentation came after.
AI shifted the constraint. Writing code is cheap now. Understanding code is expensive.
- From pre-coding investment to pre-understanding investment - From post-ship docs to real-time capture - From coordination overhead to minimal sync - From velocity metrics to understanding metrics - From large teams to lean teams
Look at your process. Ask for each element: What constraint was this designed for? Does that constraint still exist? Update accordingly.
Related articles
- Agile Was Never Meant for This
- Coordination Overhead Is Killing Your AI Projects
- Heavyweight PM Is Technical Debt
- Why Your Sprint Velocity Metric Is Lying to You
- The Standup That Could Have Been an Async Update