The transition from senior SE to SE manager is one of the steeper pivots in enterprise tech. You've spent years building credibility as the person who knows the product, handles the hardest technical conversations, and wins deals. Now you're being measured on things that are harder to see: whether your team is developing, whether your territory is healthy, whether you're building the kind of environment people want to stay in.
Most new SE managers spend their first 90 days doing too much of the wrong thing and not enough of the right thing. Here's what the first three months should actually look like.
The first mistake: staying in the deal too long
When you were a senior SE, you were the person in the deal. Now you're the person supporting the person in the deal. That distinction sounds obvious but it's hard to live in practice.
The pull toward staying hands-on in deals is strong. You know the product better than your newer SEs. You have relationships the team doesn't have yet. It feels efficient to just jump in. But every hour you spend doing SE work is an hour you're not spending building the conditions that make your whole team better. And when you jump in, you rob your SEs of the reps they need to develop.
The rule of thumb I've landed on: your role in a deal is to help your SE think through it, not to think through it for them. Ask questions. Challenge their framing. Push them to prepare better. But let them own the execution. The deals you save by staying hands-on won't matter as much as the SEs you develop by staying out of the way.
The first 30 days: listen and learn
Your first month as an SE manager should be almost entirely diagnostic. You're learning the team, the territory, the existing relationships, the patterns in the pipeline, and the dynamics with the AE org. You're not yet fixing things, you're understanding what's actually going on.
This requires a specific kind of discipline. New managers often feel pressure to demonstrate value quickly, to launch initiatives, change processes, and make their mark. Resist that pressure. Changes made without understanding the existing state often create problems rather than solving them. The 30-day listening period is how you avoid that failure mode.
What does listening look like in practice? Ride-alongs on customer calls, with a genuine intent to observe rather than contribute. One-on-ones with each SE that are heavy on questions, what's working, what's frustrating, what do they need more of, what do they wish leadership understood better. Conversations with the AE counterparts about how the partnership is working. A careful read of the pipeline with attention to what's moving and what's stuck.
Days 30 to 60: build the operating model
By day 30 you should have enough context to identify the two or three highest-leverage changes you want to make. Not a long list, a short, prioritized one. This is where many new managers overreach, trying to fix everything they identified in month one rather than sequencing carefully.
The areas that usually pay off first: how the team allocates its time to deals, how POVs are set up and tracked, and how feedback flows between the team and the product org. These aren't glamorous, but they're load-bearing. Getting them right creates the conditions for everything else.
This is also when you establish your 1:1 cadence and your approach to deal reviews. Both should feel like development conversations, not status updates. If your SEs are preparing for 1:1s by pulling together metrics and activity logs, something is off. The goal is for them to bring their real challenges, the deal they're not sure about, the champion relationship they're worried about, the product question they can't get a clean answer on, and to get your genuine input.
Days 60 to 90: start making calls
By the end of 90 days you should have a clear view of how each SE on your team is performing and what they need to get better. Some of that will be training and coaching. Some of it will be territory or deal structure. Some of it will be harder conversations about fit or performance.
New managers often wait too long to have the hard conversations. The instinct is to avoid conflict while you're still establishing yourself. But waiting too long on a performance issue sends a signal to the rest of the team that you're not paying attention, or that you're willing to let low performance slide. Neither helps you build the trust you need.
The 90-day mark isn't a destination. It's a checkpoint. You should have enough credibility, context, and operational clarity to start making real decisions and having real conversations. The learning doesn't stop, but the mode shifts from diagnostic to active.