I became the manager. Why do I still want to fix it myself?
You know how to fix a server. You do not yet know, or will not admit, that fixing servers was never the whole job — it was always people depending on you, just fewer of them. Now there are more people, and the dependency has a budget and a calendar attached to it. What you call drift is not drift. It is the actual work, arriving late and unwelcome. You miss the ticket queue because it had a clean answer. Budgets and people rarely do. That discomfort is not proof you took the wrong job — it is proof the job changed and you have not yet changed with it. Your team feels this too. They watch you reach for the keyboard instead of the roadmap, and they learn, correctly, that you do not yet trust them with the real work. Fix that, and you fix more than your own week.
You were promoted because you kept the system alive with your own hands. That is over. Your job now is to keep people alive — their attention, their disputes, their growth. Choose to do this work on purpose. The tickets are not beneath you; commanding people is simply the harder craft.
What changes unlock by starting
- You stop being the single point of failure for every fix.
- Your team solves problems without waiting on you first.
- You spend real hours on budget and planning instead of firefighting.
- You start to feel the authority of the role, not just carry its title.