Christopher Justice · Project Management
The Ticket Took Longer Than the Work
45 minutes writing the ticket. Acceptance criteria. Technical details. Edge cases. Dependencies. Labels.
# The Ticket Took Longer Than the Work
45 minutes writing the ticket. Acceptance criteria. Technical details. Edge cases. Dependencies. Labels.
30 minutes implementing with AI.
The ticket took longer than the work.
This isn't an edge case anymore. It's increasingly common. And it raises a question: why are we still writing detailed tickets when the implementation is faster than the specification?
Detailed tickets made sense when:
- Work was handed off between people who didn't share context - Implementation took days or weeks - Requirements needed to be precise before coding started - Mistakes were expensive to fix
In that world, front-loading specification paid off. Better to spend an hour specifying than a week fixing miscommunication.
Related articles
- Agile Was Never Meant for This
- Coordination Overhead Is Killing Your AI Projects
- Heavyweight PM Is Technical Debt
- Your Process Is Optimized for 2015
- Why Your Sprint Velocity Metric Is Lying to You