Leadership - Scaling Engineering Team From 3 to 40

  At around 15–20 project managers, the ground shifts beneath your feet. You aren’t leading PMs anymore, you’re leading PM Leads. It’s a transition that catches even the most seasoned leaders off guard, mostly because the skills that got you here, technical precision and tactical oversight, suddenly become the very things that hold you back. At this scale, your success isn’t measured by how well you manage tasks. It’s measured by how well you manage intent . Context Over Instructions Leadership in this space is about providing context, not giving orders. You’ll find yourself spending significantly more time explaining the "why" than the "what." You invest your energy in calibration: defining what "good" looks like, deciding where acceptable risk ends, and clarifying exactly when an issue needs to reach your desk. This requires a new kind of discipline: the power of restraint. Not every mistake needs your correction. In fact, some mistakes must run their ...

After scaling your team and building trust, a new challenge emerges: multiple programs, multiple OEMs, each with their own priorities, expectations, and timelines. Suddenly, your team isn’t just managing ten projects, it is managing ten projects for three different OEMs , spanning legacy programs, new launches, and proof-of-concept initiatives, all competing for attention. Everything feels urgent, and pressure comes from all directions. This is the stage where many PMs and even experienced managers get stuck. When every customer thinks their program is the most important, it’s easy to default to reactive mode, answering the loudest voice, firefighting whichever crisis surfaces first. The result is chaos, misaligned priorities, and exhausted teams. The first step to handling this is objective prioritization . Not “I feel like this matters more,” but systematic evaluation of impact, risk, and dependencies . Questions that help: Which program has the most critical deadlines for certi...