Sometimes (always?) the problem that we see in organizations is not technology or structures or something else—it is the inability of people to “get on the same page.”One way to fix this is to have people dedicated to Business Architecture who understand “how things are wired up” and where the value is created. And who also tries to solve the problem that is shown above … what do you mean with what you just said?And who could manage these problems better than Breanne Casteel, a catalyst for change enablement through collaboration and connections to drive empathetic business solutions?She is a passionate advocate with 20+ years of experience bringing awareness of Business Architecture and Business Analysis skills and mindset to numerous roles in the organization with an emphasis on communication, transparency, and collaboration across silos.Oh, and we had her on the podcast before :-)In this episode we are talking about:Breanne returns from her earlier appearance (Episode 71)—evolving from a solo business architect building a practice to working inside a larger enterprise architecture team.A key reality: maturity doesn’t eliminate advocacy—even established architecture practices must continuously prove value as stakeholders change.Breanne’s go-to definition of business architecture: “It’s a drama mitigator.” Replace opinions with facts about how the business actually works.The core value: map what the business does, how it works, and how it connects—then test decisions against reality instead of politics.A recurring misconception: business architecture vs. process management—it is not a turf war but a spectrum that must align across domains.Roland reframes architecture as structure over flow—like an aqueduct: the structure matters more than what runs through it.Behind every clean model lies the messy middle—whiteboards, ambiguity, iteration, and rework. Practitioner takeaway: Show the messy middle. Transparency builds credibility and helps others learn how outcomes actually emerge.The new YouTube series was born from frustration with overly theoretical content and a push toward practical, real-world usage.The series spans nine themes, including foundations, capabilities, value streams, context, adoption, and the future of the discipline.A standout insight: Stop talking architecture. Start solving problems. Stakeholders care about outcomes, not frameworks.Listening beats modeling: what looked like a process issue turned out to be a cross-functional value flow problem.Architecture success hinges less on models and more on understanding stakeholder pain points.A recurring failure mode: strong deliverables but weak storytelling—leading to the dreaded “ivory tower” perception.The meta takeaway: architecture doesn’t fail because of bad models—it fails when value isn’t made visible.You can find Breanne on LinkedIn here: https://www.linkedin.com/in/breannecasteel/.Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and reading articles about process and architecture on our Substack… Go and subscribe at whatsyourbaseline.substack.com.And if you like to support “the little podcast that could,” become a Patron at https://www.patreon.com/c/whatsyourbaseline. We appreciate you!

Ask this episode

“What did the council decide on item 42?” — answered with the speaker and the moment.

Transcript

Related