Enterprise Drupal / March 2026
Production support and modernization run at different speeds inside the same system
Daily support does not stop because an upgrade is being planned. The important organizational task in March was separating urgent incidents from longer-term modernization without disconnecting the lessons between them.
Situation
In a live enterprise application, the same team receives production tickets, smaller change requests and strategic upgrade work. If everything shares one backlog and one priority model, long-term modernization always loses. If the team ignores operational work instead, service quality degrades.
Approach
I treated incidents, changes and modernization as distinct work types while feeding discoveries between them. A deprecation or configuration drift found during support entered the upgrade plan; dependency knowledge gained during upgrade work made daily incidents easier to diagnose. They were managed as different tempos of the same system rather than unrelated projects.
Outcome
Urgent failures received the focus they needed without completely consuming technical-debt reduction. The modernization backlog was grounded in real production behaviour, so it became a map of actual weak points instead of a theoretical cleanup list.