The Better Business Analyst Podcast

The episode delivers consistent, practical guidance on BA approach to Salesforce implementations with clear structural advice (6 numbered points). However, it relies heavily on established best practices (business-first thinking, vanilla implementations, change management) that are well-known in enterprise software circles. The gym franchise example adds minor texture but doesn't crack novel territory. Most insights are sound reiterations rather than surprising revelations.

“Don't start with the objects and the fields and automation. Start with why Salesforce? What problem is the organization trying to solve?”

“Configuration, not customization. Right? And this is until proven otherwise. So the whole point in Salesforce, the whole point in getting a Salesforce platform or a Dynamics platform is that you can configure the system.”

The core thesis - business-first BA approach to CRM - is sensible but standard industry guidance. The distinction between configuration and customization is valuable framing, and the emphasis on vanilla-first implementations resists common feature-creep temptations, but these are mature best practices, not fresh thinking. The episode offers no contrarian arguments, surprising data, or first-principles rethinking of CRM implementations.

“often the issue is poor process, not poor tools.”

“Purely vanilla Salesforce implementations can be brilliant opportunities for business analysts. It's actually very, very good because it's end to end, but only if you stay business first, not tool first.”

The speaker (Kendra Walsh) demonstrates practitioner experience with multiple CRM implementations across sectors including education and current client work. However, no co-guest is present; this is a solo monologue format. The speaker's credibility is credible but not exceptional - she references past work and current engagements without claiming transformative or market-leading expertise, and there's no interplay that typically enriches conversations.

“I've done a couple of Salesforce implementations actually back in the day and a lot of CRM implementations.”

“This is a, uh, process I'm doing at the moment for another client where there is an existing platform that decided to buy and now it's gap analysis.”

The episode is notably light on concrete examples, metrics, or named cases. The gym franchise scenario is entirely hypothetical ('let's say you're implementing Salesforce into a gym'). No real project data, timelines, budget figures, or actual client outcomes are provided. References to 'education space' and vague allusions to 'current client work' lack specificity, undermining credibility and learning value.

“let's say you're implementing Salesforce into a gym, uh, franchise, right. The owner thinks they need Salesforce to track members better”

“I've done a couple of Salesforce implementations actually back in the day and a lot of CRM implementations. And I uh, usually find two things. One, none of this upfront work was done by architecture.”

This is a solo-delivery episode with no guest or interviewer, eliminating opportunity for push-back, follow-up questions, or productive debate. The host reads through structured points without interrogation or challenge. No attempt to stress-test claims, probe for counterarguments, or dig into gray areas. While the structure is clear, the format is closer to a lecture than conversation, limiting the dynamic interplay that strengthens learning.

“So number one is to understand the business problem, not the Salesforce product.”

“Number five, at the same time, you need to map current data sources and ownership.”