About The Salesforce PM

---

The Salesforce PM was born out of observation.

After years of working in the tech industry, somewhere I found myself almost by accident, a pattern started to emerge across the projects and programs I was part of.

No matter the organization or scale, the same gaps kept appearing.

Not in effort, but in alignment.

Not in capability, but in how roles interacted, how decisions were made, and how understanding broke down between teams.

At the same time, I kept seeing the same conversations repeated.

Scrum Master vs. Project Manager.

Project Manager vs. Program Manager.

Debates that stayed at the surface, rarely digging into how delivery actually works in practice, especially in complex environments.

Meanwhile, on the Salesforce side, the conversation leaned heavily technical.

Flows. Apex. Architecture.

All important. But for those of us working on the functional and delivery side, translating business needs, navigating stakeholders, and holding the structure of a project together, there wasn’t a clear space that reflected that reality.

This is that space.

A place to think more deeply about Salesforce delivery, project management, and leadership, not as isolated disciplines, but as interconnected parts of how work actually gets done.

It also recognizes that delivery does not happen in a vacuum.

The dynamics of leadership, voice, and visibility, especially for women in technology, shape how decisions are made and how projects move forward.

The goal here is simple:

To move beyond the polished version of project delivery, and speak to the reality underneath it.

This is a space for thinking clearly about how projects actually run, especially within Salesforce environments, where delivery is often complex, cross-functional, and quietly high-stakes.