Business transformation programs rarely fail because of technology. They fail because the organization is not aligned, not clear, and not ready for change.

There is an art, science, and emotional intelligence to leading successful business transformations, and our guest, Meherban Faroogh, has been helping clients for decades now to navigate this maze of major changes for organizations.

He founded PPS Partners in Toronto and has spent 20 years helping organizations navigate business transformations—with a particular focus on discovery and change management. Drawing on nine years across three major ERP implementations at Enbridge alone, Meherban brings hard-won clarity to why so many transformations fail and what to do instead.

In this episode we are talking about:

• Business transformation failure rates sit stubbornly at 70%+ regardless of which analyst report you pick up—and the root cause is rarely the technology itself.
• The three reasons organizations fail: lack of strategic alignment on the why of the transformation, insufficient clarity on the current state before signing large contracts, and inadequate change management throughout the journey.
• Successful transformation requires balancing three distinct dimensions—the science (methods and tools like Lean Six Sigma, BPMN, and TOGAF), the art (knowing when and how to apply those methods given the culture, scale, and politics), and emotional intelligence (building trust from the boardroom to the shop floor).
• There is no such thing as “digital transformation”—it is always business transformation, because technology is part of the business and should never be the tail that wags the dog. A CIO alone should never be the sole sponsor driving the shots.
• The Titanic analogy cuts through the noise: business transformation is turning the entire ship, not rearranging the deck chairs. Process improvement is fixing the supply chain for the rocket; transformation is the mission to the moon itself.
• BPM done well effectively eliminates the need for a lengthy discovery phase—because you are already doing it every single day. One client came back four years after implementing BPM ready to select a vendor, and told the integrator, “Here you go.” That is the value proposition in action.
• Strategic alignment cannot be assumed—even C-suite leaders are frequently not aligned with each other on the transformation why, and it is the consultant's job to surface and close those gaps through structured one-on-ones before the first workshop even begins.
• Identifying the right 15 to 25 core end-to-end processes—and assigning single, accountable process owners to each—sounds mundane but is precisely what keeps projects on scope, on time, and on budget.
• The central decision that gets made a thousand times during any transformation: do you change the organization to fit the tool, or change the tool to fit the organization? Clarity on the current state is the only thing that makes that decision an intelligent one.
• Trust is built through three things: empathy (genuinely listening, not just waiting to respond), logic (being quick on your feet and connecting the dots), and authenticity (being yourself rather than performing a role). Of the three, empathy is where things most often break down under the pressure of deadlines and cost overruns.

• Change management is not a workstream bolted on at the end—it is the continuous act of building trust and relationships across the entire organization so that people take ownership of the change rather than enduring it.

You can find Meherban on LinkedIn: linkedin.com/in/mehrabanfarooq.

Please reach out to us by either sending an email to ⁠⁠hello@whatsyourbaseline.com⁠⁠ 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!

Is quality management the most thankless job in the organization?

In many companies, QM teams want to be the Hermione Granger of the workplace—knowledgeable, prepared, and doing the right thing—but end up perceived as Argus Filch, the grumpy caretaker enforcing rules nobody asked for.

This week's guest, Regina Haar, works at Q.Wiki (Modell Aachen), where she helps quality managers move from being considered annoying compliance police to becoming genuine enablers. She joins Roland to unpack why this role is so often stuck—and what it takes to change it from the inside out.

In this episode we are talking about:

• The Harry Potter metaphor that lands every time: quality managers see themselves as Hermione (smart, principled, always prepared), but the organization experiences them as Filch—chasing people down, enforcing rules, and getting little recognition for it.
• The root cause of the image problem: when certification becomes the why of quality management, employees have no intrinsic motivation—usage spikes before audits and collapses after. Event-driven, not value-driven.
• Two formative lessons from Regina's career: a missing colleague's undocumented knowledge cratered a major production, and a well-meaning onboarding plan failed because it lacked a coherent big picture. Both point to the same conclusion—context and structure matter as much as content.
• The “Scribbler” trap: a LinkedIn poll found that 45% of respondents said only the quality or process management team designs processes—making QM the bottleneck and ensuring the business never emotionally owns what gets documented.
• The first lever for change is decentralized creation: replace “I write your processes” with “I coach you to write them.” Build a platform where content originates with the people doing the work.
• Intrinsic motivation requires three things—autonomy, self-efficacy, and social integration. Centralized modeling teams undermine all three and kill the very engagement QM is trying to build.
• The Marauder's Map metaphor: a management system should work like Fred and George Weasley's map—showing you where you are, where others are, and which hidden paths exist. Two clicks to the answer beats perfectly formatted documentation.
• Embedding process guidance into runtime systems—through a Chrome extension, a CRM integration, or a contextual sidebar—moves the mountain to the user instead of making users climb to the mountain.
• Combining knowledge management and process management is an underutilized power move: processes give structure, and knowledge gives detail. Together they raise relevance and adoption—but they typically live in separate tools and separate teams.
• Quality departments chronically underinvest in internal marketing. Projects die not because the work was bad, but because the wins were never communicated. The shift needed—from cost center to value creator—was told loudly, repeatedly, and in the language of business outcomes.

You can find Regina on LinkedIn here: https://www.linkedin.com/in/regina-haar/.

Please reach out to us by either sending an email to ⁠hello@whatsyourbaseline.com⁠ 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!

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 hello@whatsyourbaseline.com 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!