Many teams believe their biggest problem is a lack of time.

I’m not so sure.

After several years of coordinating projects, I think the scarcest resource is usually something else:

Capacity.

Because you can have time.

But if people are already overloaded, distracted, or split across too many priorities, the outcome will be the same.

That’s why great PMs don’t just manage calendars.

They manage capacity.

They understand what a team can realistically absorb without compromising quality, speed, or operational health.

And that conversation is often far more uncomfortable than simply moving a deadline.

A question I asked myself recently:

How do you trust someone who proposes solutions for a project they’re not involved in on a day-to-day basis?

My answer: you don’t have to trust them blindly.

You can listen to the proposal, evaluate it on its actual merits, and if it doesn’t fit the context, say so clearly. That’s not shutting the door—it’s leadership.

The difference between a team that moves forward and one that gets stuck isn’t always a lack of ideas.

Sometimes it’s an excess of ideas that are disconnected from operational reality.

A good leader knows when to listen—and when to stay committed to the path that’s already been defined. 😉

👉🏻 No one tells you that working remotely requires a completely different skill set than working in person.

It’s not just about having a good internet connection and a comfortable chair.

It’s about learning to communicate without body language.

To provide enough context in a written message.

To assume positive intent when you can’t hear someone’s tone.

To respect response times without interpreting them as a lack of interest.

The tools are easy to learn.

The hard part is building trust within a team that rarely—or never—meets face to face.

And that doesn’t happen on its own.

It requires intention, clear agreements, and a strong culture.

P.S. Some people have been working remotely for years and do it exceptionally well. Others are still adapting, and that’s perfectly valid too.

There’s no single right way to do remote work well.

If someone asked me what the most valuable skill for leading complex projects has been, my answer would probably surprise them.

❌ It wouldn’t be Scrum.

It wouldn’t be Agile.

It wouldn’t be time management.

✅ It would be observation.

Learning to observe people.

To observe patterns.

To observe conversations.

To observe what someone says… and what they choose not to say.

Because when you work with diverse teams, the most valuable information rarely shows up in reports.

It shows up in the nuances.

And many times, a five-minute conversation tells you more about the future of a project than an entire week of metrics.

Operations run on processes.

👉🏻 But leadership runs on human understanding.

A Project Manager is not the person who tells you what to do 🥴

That’s what many people believe, and it’s exactly why the role is so often misunderstood.

A Project Manager is the person who:

→ Designs and builds the processes that allow the team to deliver without friction.

→ Monitors every moving piece of the project—because if one domino starts to wobble, someone has to catch it before everything falls.

→ Documents absolutely everything—yes, everything. It sounds obvious, but when something goes wrong, the first questions are always: Was it documented? Is there any record?

I often compare that last part to the work of an executive assistant—and I say that with the utmost respect, because it’s a critical role that is often underestimated.

A PM is the person who keeps everything standing when no one else is looking.

Do you know someone who does all of this and still doesn’t get recognized for the role they play?

Después de coordinar lanzamientos de $2M+ con equipos de más de 20 personas, te puedo decir que ser Project Manager de lanzamientos no es lo que la mayoría piensa.

No necesitas certificaciones fancy. No necesitas años de experiencia corporativa. Lo que sí necesitas:

1. Gestión de timelines bajo presión

Un lanzamiento tiene fecha inamovible. Si el webinar es el jueves, todo tiene que estar listo el jueves. Punto. Necesitas saber crear cronogramas inversos y gestionar dependencias sin que nada se caiga.

2. Comunicación con equipos diversos

En un lanzamiento típico coordinas copywriters, diseñadores, media buyers, devs, soporte y el experto del producto. Cada uno habla un idioma diferente. Tu trabajo es ser el traductor.

3. Troubleshooting en tiempo real

La página de ventas se cayó a las 2am antes del lanzamiento. El email se fue con el link equivocado. El procesador de pagos falló. Estas cosas PASAN. Un buen PM tiene protocolos para cada escenario.

4. Conocimiento técnico básico

No necesitas programar, pero sí entender funnels, email marketing, plataformas de pago, landing pages y automatizaciones. Lo suficiente para hablar con el equipo técnico sin depender de ellos.

5. Documentación obsesiva

SOPs, checklists, post-mortems. La diferencia entre un PM junior y uno que cobra $8K/mes es que el segundo documenta TODO y puede replicar resultados consistentemente.

¿La buena noticia? Todas estas habilidades se pueden aprender. Muchos de los mejores PMs que conozco empezaron como VAs o freelancers.

Si esto te resonó, en Launch Ops Academy enseño exactamente cómo desarrollar cada una y conseguir tu primer (o mejor) trabajo remoto como PM. 🚀