From One Team to Three Accounts — What I Had to Unlearn

Two years ago, I managed one project team with eight engineers. Today I manage three accounts with over forty team members. The skills that made me effective at the first level almost sabotaged me at the second.

Unlearning Deep Involvement

With one team, I knew every ticket, every blocker, every engineer's current task. I could context-switch into any conversation and contribute meaningfully. With three accounts, that level of detail is impossible. I had to learn to trust my engineering leads and manage through outcomes instead of activities.

This was genuinely difficult. Letting go of detail felt like losing control. But the reality is that trying to maintain detail across forty people is not control. It is noise.

Unlearning Solo Decision-Making

With one team, I made most operational decisions quickly. Sprint scope, escalation paths, resource allocation — I handled them in real time. With three accounts, I cannot be the bottleneck for every decision. I had to build decision-making frameworks that my leads could use without me.

I created simple decision trees for common scenarios: when to escalate to the client, when to pull in additional resources, and when to cut scope versus extend timelines. This delegation felt risky at first, but it was the only way to scale.

Unlearning Being the Expert

With one team, I was the domain expert on the product. I knew the business rules, the technical constraints, and the client relationships intimately. Across three accounts, I cannot be the expert on everything. I had to become the person who asks the right questions instead of the person who has all the answers.

The Pattern

Every scale transition requires unlearning. The habits that got you promoted are often the habits that will hold you back at the next level. The hardest part is not learning new skills. It is releasing the old ones that feel like core parts of your identity.