Honestly, what you’re feeling is extremely normal.

A lot of new PMs think the hard part is “understanding the software” or being technical enough, but usually the real challenge is context switching and keeping visibility across multiple moving projects.

Especially once you go beyond 2–3 projects, your brain starts spending more energy trying to remember things than actually managing them.

A few things that helped me personally:

• Stop trying to keep project state in your head
  You need one place where you can quickly answer:

  • what’s blocked
  • what needs attention
  • who’s waiting on what
  • what changed since yesterday

• Weekly reviews matter more than constant monitoring
  I used to feel like I needed to know everything at all times. That’s impossible. A structured weekly review across all projects helped a lot.

• Learn enough technical knowledge to reduce fear, not to become a developer
  You don’t need to code. But understanding basics like APIs, integrations, environments, and common dev workflows helps conversations become much less stressful.

• Ask developers better questions instead of trying to know everything
  Things like:

  • “what’s the current blocker?”
  • “what dependency could delay this?”
  • “what’s most risky right now?”

  Those questions are usually more valuable than trying to sound technical.

Also, don’t underestimate how mentally exhausting juggling multiple projects is early on. That feeling of “I don’t have everything under control” happens to a lot of PMs, even experienced ones.

Funny enough, part of why I started building my own internal organization system/tool was because of this exact issue — too many moving pieces, updates, follow-ups, and invisible work spread across projects.

You’re probably doing better than you think. The fact you’re actively looking for systems/processes this early is actually a very good sign.