The Better Business Analyst Podcast

The episode carries one genuinely useful central argument - vague organisational language hides accountability and produces bloated solutions - but the same point is restated multiple times with filler and rhetorical padding rather than layered with additional ideas. The practical reframes are the densest section but occupy only a fraction of the runtime.

“The business is not a stakeholder, a decision maker, a source of truth. It's actually a fog.”

“Abstract language feels safe. Specific language focuses commitment.”

The core critique of vague requirements language is well-trodden territory in BA and product circles; the episode offers no genuinely contrarian or counterintuitive angle. Leaning on the SMART framework as a reframe is a recycled move, and the CRR (customers, revenue, risk) lens is simple rather than fresh.

“it's like the smart framework. So we need to start to move away from ever saying the business.”

“better BA makes things uncomfortable to be provide clarity through consequences and trade off”

This is a solo monologue with no guest whatsoever; the host references personal practitioner experience but provides almost no evidence of operating at meaningful scale, seniority, or domain breadth. A single vague anecdote about documentation feedback is the only first-hand credential offered.

“recently I just had some of my documentation given to leaders. I wasn't in the meeting, but, uh, something I came up with that they wanted to see. And I heard the feedback wasn't that great on one area of it.”

The illustrative numbers (14 approval paths, 27 edge cases, 15% SLA reduction) are useful for concreteness but are clearly fabricated teaching examples rather than real data; the hedged 'maybe 20 or 50k' figure undercuts credibility. No named companies, actual projects, or sourced metrics appear.

“The solution becomes a, uh, bloated workflow. 14 approval paths, 27 edge cases, and everyone hates it.”

“sales want fewer approval steps for deals under maybe 20 or 50k to reduce churn”

As a solo monologue there is no interviewing, no follow-up, and no pushback dynamic to evaluate; the host's own delivery is marred by frequent filler, incomplete sentences, and self-correction mid-thought, which reduces the clarity and authority that a structured monologue format demands.

“Clear clarity, uh, um, making things concise. Accountability. You know, it's like the smart framework.”

“Not sugar voting it. You're not summarizing.”