Podcast/Salesforce at Scale/ 17 Flows on One Object: How Salesforce Orgs Get Sick and How to Fix Them

Salesforce at Scale

Episode 86 · Season 1

17 Flows on One Object: How Salesforce Orgs Get Sick and How to Fix Them

Andy GallNovember 13, 202643:58

Most Salesforce consultants walk into a new engagement treating it as a technical problem, and the org they inherit was built by three or four teams before them for a problem set that no longer exists. Andy Gall, Solution Architect at Cirrius Solutions, joins Greg Banks and Al Huerta to lay out what he checks before the kickoff call, how he delivers the bad news when the foundation cannot carry the build, and why code is pulling ahead of flows again in the age of large language models.

What you’ll learn:

  • The fifteen-minute org health check Andy runs before a first meeting: paused and failed flow interviews, the Apex jobs queue, stacked after-save flows on one object, queries and updates inside loops
  • How to turn a hard “fix the foundation first” conversation into a value statement, with evidence the client can see for themselves and spend you can offset along the way
  • Why orgs get sick (no single owner, no architecture review board, every department writing its own flow) and why 75 percent code coverage was never the point of a test class

Who it’s for:
Salesforce admins, developers, architects, and delivery leads who inherit orgs they did not build, and the business stakeholders deciding whether to fund remediation before the next project.

Guest + credibility:
Andy Gall is a Solution Architect at Cirrius Solutions who started as a .NET developer roughly twenty-five years ago, doing in-house consulting for a manufacturing company outside Pittsburgh before a ServiceMax and Salesforce implementation pulled him into the platform. He has since worked for customers, for Salesforce partners, and for ServiceMax directly, so he has seen a challenging engagement from every side of the table. Speed is now very cheap with regard to writing code, but quality is the expensive thing.

Primary CTA:
If you have inherited an org that fights you every sprint, or you want a second opinion before the next build, reach out and start the conversation with the Cirrius Talk team.

Recommended Links & Resources:
Andy Gall on LinkedIn
Al Huerta on LinkedIn



Greg Banks on LinkedIn
Jason Fowler Music
Cirrius Solutions
Salesforce at Scale Episodes

Any Questions:

Reach out to us at CirriusTalk@cirriussolutions.com

We cover

  • Ownership and Accountability in Salesforce Development
  • Meet Andy: Path into Salesforce
  • Challenging Engagements: Setting the Stage
  • Step Zero: Walking Into the First Meeting
  • Popping the Hood on an Inherited Org
  • Delivering Hard News & the Cost of Tech Debt

Chapters

  • 0:00Introduction to Salesforce Challenges
  • 0:26Ownership and Accountability in Salesforce Development
  • 0:32Introduction to the Conversation
  • 0:32Welcome to Sirius Talk
  • 0:41Meet Andy: Path into Salesforce
  • 2:23Challenging Engagements: Setting the Stage
  • 3:36Step Zero: Walking Into the First Meeting
  • 6:55Popping the Hood on an Inherited Org
  • 9:10Delivering Hard News & the Cost of Tech Debt
  • 14:16Best Practice and the Flow Bloat Epidemic
  • 20:02Flows vs. Code in the Age of LLMs
  • 23:05How Orgs Get Sick
  • 26:59Passing UAT vs. Building to Scale
  • 31:05The License Is the Beginning
  • 32:48Testing the Full Business Process
  • 35:16Don’t Be an Order Taker
  • 36:43Custom Code, Clicks, and AI
  • 40:47Consulting as Counsel
  • 41:53Wrap-Up & How to Reach Us
  • 42:58Building a Healthy Salesforce Organization
  • 43:26Quality Over Speed in Salesforce Management
  • 43:54Planning for Scale in Salesforce

Andy Gall

Cirrius Solutions