Field Notes · Always firefighting

Stop firefighting in your Salesforce Org

It is not normal for a Salesforce team to spend half its time on fires. The same failures keep coming back in different costumes: a Validation Rule blocking a valid edit, an old Flow still firing, a Trigger failing on a Field that changed meaning years ago. Debugging fixes what broke. Cleaning stops the next ten things from breaking the same way.

“Half my team is fixing bugs instead of building.”

8 field notes on always firefighting

Always firefighting · 1 min

Your CPU/SOQL Limit problems aren't a volume problem. They're a save-cycle problem

Most "messy org" automation problems come down to one mistake: people add automation to an Object without thinking about the save cycle.

Read field note
Always firefighting · 1 min

No, it is not normal to be firefighting all the time in your Salesforce Org

I know many Salesforce teams, maybe most, where the team spends half its time or more on fires. First level support. Bug fixing. Deployments that need three people and a weekend to get through.

Read field note
Always firefighting · 1 min

You want fewer bugs, have you tried cleaning?

Every Salesforce team believes the same thing: bugs get fixed by debugging.

Read field note
Always firefighting · 1 min

Your Org Shouldn't Have Any High or Medium Priority Bugs. Period

No, that's not an exaggeration, Bugs are not acceptable.

Read field note
Always firefighting · 1 min

More guardrails won't save you - Cleanup will!

The result? A sloppy user story got delivered. Most of it was fixed quickly, but a little technical debt remained in the org.

Read field note
Always firefighting · 1 min

Make wrong Salesforce logic look wrong

Teach them how to make wrong Salesforce logic stand out like a neon sign.

Read field note
Always firefighting · 1 min

A Clean Org for the Friday Afternoon Opportunity Bug

It's Friday afternoon. Opportunity creation is broken. Sales is shouting. A deployment is waiting. Nobody is going to spend two hours reading Confluence pages to understand why Flow V17…

Read field note
Always firefighting · 1 min

You want to reduce bug hunting from 4 Hours to 15 Minutes?

Debugging most Validation Rules can go two ways: Hours of debugging with trial and error OR a 15 minute read like a well written business requirement.

Read field note

More topics

Free · 60 minutes · No prep

Let's open your Org together.

You don't need to fix everything. You need to fix the right things first. In 60 minutes we find them, and you leave with a score you can take into your next leadership meeting.