Photo by Morgan Bryan on Unsplash
For years, I focused on building solutions. Now I focus on defining the right problems—and sometimes, that means saying no.
Not all requests belong in Salesforce. Not all automations need to exist. The mark of an administrator isn’t how much they build—it’s how strategically they build.
What I’ve learned to push back on:
Storing unrelated data just because “we already have Salesforce”
Automation requests that fix a broken process, not a tech gap
Code or Flow that bypasses governance just to “make it work”
The strongest design decisions I’ve made in the last year weren’t solutions—they were boundaries.
