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 ⁠[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!

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!

One of the skills that I see an increasing demand for Business Analysts is data analysis. Especially when “new” tools like Process Mining shift the landscape towards data-driven analysis.

And besides the need to learn these new skills, I also see multiple tools that are very pricey and might be cost prohibitive for some organizations, so they fall back to the universal Swiss knife in business… Excel.

One of the tools that beats that trend is KNIME, which not only is open-source but also has a great community and great training offerings. Besides the fact that the tool is great, if you have ever watched a video from KNIME you will recognize the voice of our guest, Rosaria Silipo, immediately.

Rosaria has been a researcher in applications of AI and Machine Learning for over a decade. Application fields include biomedical systems, IoT, customer intelligence, financial services, social media, cybersecurity, and automatic speech processing. She is currently based in Constance (Germany) / Zurich (Switzerland).

In this episode of the podcast, we talk about:

• Rosaria's background—she brings decades of experience, from early neural networks in the 1990s to shaping the KNIME community.
• A journey through data science history: hardware limits, Big Data, GPUs, deep learning, and today’s AI-driven shift.
• From building models to consuming and fine-tuning AI: why modern analytics is now more engineering than research.
• Tool evolution matters: visual, low-code platforms lower the barrier without blocking advanced use cases.
• Open source as an accelerator: community, shared extensions, education, and faster innovation.
• Why Excel breaks at scale—and how reproducible data pipelines outperform spreadsheet heroics.
• KNIME’s strength: step-by-step logic, transparency, and workflows you can explain to stakeholders.
• Education over hype: tools are powerful, but data literacy and validation remain non-negotiable.
• Rosaria’s focus forward: growing AI learning communities and mentoring young entrepreneurs.
• AI realities: hype is real, but fundamentals still matter—especially for tabular and business data.
• Community beats lock-in: ecosystems outlast tools and make practitioners better.
• Final takeaway: better analytics isn’t about smarter tools—it’s about people, clarity, and shared understanding.

You can reach Rosaria via LinkedIn here: https://www.linkedin.com/in/rosaria/.

PS: Please reach out to us by either sending an email to [email protected]. And meanwhile, don't forget to subscribe to the What's Your Baseline? podcast on your favorite platform.

And if you like what you see here and want to support “the little podcast that could,” please check out our Patreon at https://patreon.com/whatsyourbaseline.

Happy New Year!

We are back from our regular break, in which we really did not do a lot for the podcast but were working on other things that you will discover throughout 2026. We are super excited about our plans, but it is not the time to talk about it … as we say in Germany, “lay the egg first, and then cackle.”

However, for our first episode of Season 10 (who would have guessed that?), we have a very special guest and an exceptional co-host: Michael Hill and Caspar Jans. Both are very well known in our industry, and Caspar is still polishing his medals that he received from the PEX network ;-)

Michael is a journalist and editor with experience in various mediums, including print, digital, video, webinars, and podcasts. He is passionate about the editorial and publishing processes and enjoys working creatively to produce media that has the biggest possible impact on the audience.
And he is also the editor of the Process Excellence Network, an outlet that many of us know :-)

In this episode of the podcast, we talk about:

• Michael explains PEX Network’s role as a content and community platform for process excellence, transformation, automation, and AI leaders.
• His journey into journalism started with a love for storytelling, creative writing at university, and a less-glamorous detour into insurance. Eight years covering cybersecurity journalism shaped Michael’s editorial approach before he transitioned into the process excellence space.
• PEX Network is positioned as more than a publication: it blends daily news, thought leadership, reports, webinars, and virtual events.
• The discussion highlights PEX’ push to become a trusted news source for the process and transformation community.
• Michael walks through a “day in the life” of an editor—balancing breaking news, long-form reports, contributor management, and vendor collaboration.
• The group explores how AI is reshaping content consumption search behavior and what “quality content” means in a zero-click world.
• A candid look at different content formats shows why virtual All Access events drive the strongest engagement across the community.
• The PEX Leaders Lists are unpacked as a mix of community recognition, inspiration, and organic reach, not paid promotion.
• Sponsored content and vendor partnerships are discussed openly, emphasizing editorial integrity, trust, and mutual value.
• Looking ahead, Michael outlines PECS’ future focus: video-first formats, broader transformation topics, and the “Future of BPM,” starting with the February All Access event.

You can reach Michael via LinkedIn here: https://www.linkedin.com/in/michael-hill-1a17b08b/.

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

We had episodes about BPM education on the show before, but this time we speak with someone who is from a different generation than your regular hosts.
And our guest Daniel Matka is building a “Process Academy” to bring process management knowledge to the next generation. And while doing this, he's building modern ways of structuring content that will speak to this audience.

Daniel was a product owner/project manager in the field of process automation at Robert Bosch GmbH. Today, mastering highly complex processes and automating networked business processes are at the center of my vision for a user-friendly workflow suite. This requires, among other things, creativity, which I demonstrate as the managing director of the music label Madstep even outside work hours.

One of Daniel's main goals is to share the knowledge and experiences he has gathered throughout his career with others and support them on their journey.

In this episode of the podcast, we talk about:

• Daniel Matka returns to What’s Your Baseline? to discuss a bold idea: rethinking BPM education so it actually scales beyond workshops and slide decks. Coming from a mechanical engineering background at Bosch, Daniel explains how process automation projects grew from a two-person experiment into a 40-person automation team with real business impact.
• A key trigger for Process Academy was the challenge of educating 15,000 people, not just a handful of BPM experts, without relying on repetitive, trainer-dependent workshops.
• Daniel argues that traditional BPM training doesn’t scale: it’s expensive, inconsistent, and often depends more on the trainer’s skills than on a shared, reliable curriculum. One major pain point: “No one wants to teach BPM fundamentals 100 times.” Experts want to solve real problems, not repeat the same basics over and over.
• Inspired by Duolingo, Daniel and his co-founder Matus envisioned microlearning for BPM—small, daily learning units that fit into real workdays.
• Process Academy is built around skill trees, not linear courses, allowing learners to unlock capabilities step by step based on their role, maturity, and interests. The focus is on T-shaped skills: broad BPM fundamentals for everyone, with deeper specialization paths for modeling, automation, mining, or architecture.
• Daniel emphasizes that learning must be continuous, not event-based: five to ten minutes a day beats a two-day workshop once a year. Gamification isn’t about points—it’s about motivation and momentum, such as streaks, progress visibility, and clear skill progression.
• Process Academy is intentionally set up as a nonprofit to attract top BPM experts who contribute out of conviction, not just commercial interest. “Nonprofit doesn’t mean no money,” Daniel clarifies—it means no cashing out at the expense of the community or inflated license models.
  The long-term vision is a community-endorsed curriculum, where respected practitioners stand behind the content and skill definitions.
• Rather than chasing hypergrowth, Process Academy follows a long-term path, focusing on quality, credibility, and shared ownership by the BPM community.
• Daniel sums it up with a generational perspective: building something that still matters decades from now—not just the next funding round.

Daniel can be found on LinkedIn here: https://www.linkedin.com/in/danielmatka/.

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

There has been a lot of consolidation in the process/architecture space in the last few years, mostly driven by PE firms. But why is that so, and why does it seem that there is no alternative to this business model?
Back in the day there were foundations behind the companies, or they were privately held, and the only thing (besides a few smaller players you might not even have heard of) that I see are some open-source projects in the automation space … mostly driven by the decision to go closed-source by Camunda.

One of these projects is SpiffWorks, and we invited the CEO of the company behind it, Dan Funk, to our little show. He is an expert in identifying organizational and technological patterns, using visualizations and written communication to build consensus around technical directions. Dan is committed to aligning technology initiatives with business objectives, fostering a culture of continuous improvement, and mentoring engineering talent.

Dan is also a thought leader and co-authored numerous publications as the technical lead for a web-based research application promoting healthier patterns of thinking using interpretation bias training. In addition to this, Dan is the co-founder of the Makerplace in Staunton, VA, where he established a makerspace offering low-cost access to state-of-the-art electronics tools, laser cutters, CNC machines, a pottery studio, and woodworking equipment.

In this episode of the podcast, we talk about:

• Dan's background
• Open-source projects require community support to thrive—SpiffWorks aims to bridge the gap between business and technical teams; Python is chosen for its readability and ease of use in process automation.
• Building a sustainable open-source project involves finding a viable business model, and community engagement is crucial for the success of open-source initiatives.
• Open-source software is foundational to modern technology infrastructure.
• The future of process automation lies in making technology accessible to non-technical users.
• Effective communication is key to resolving conflicts between business and technical teams.
• The open-source model can be compared to a city with shared infrastructure. Support for open-source projects can (and should) come from larger companies benefiting from them.

You can take a look at Spiff Works at https://spiff.works/ and reach out to Dan via LinkedIn: https://www.linkedin.com/in/funkdan/.

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

To implement AI (and processes) correctly, you need good data. But what does that mean? Well, firstly it means that you can define your data product and to achieve that you need good data governance.

But are we now in a super-nerdy topic? No, this is what we all do in some form or another … but in different fidelities and maturities.

To shed some light on the topic of data governance, we invited Angelika Rinck for this episode. She started her career studying public administration and then served in the German federal police before switching to the regular industry (in the aerospace industry, and while that might not be enough, she studied economics in parallel).

Somehow she found her way into consulting and is working now in digitalization and IT projects. Her main focus here is product lifecycle management and data governance.

In this episode of the podcast, we talk about:

• Angelika’s career journey: from e-commerce working student in Hamburg to aerospace, engineering, and ultimately major IT and data governance initiatives.
• Her first agile project—complete with a physical Kanban box—sparked her love for IT project management and structured delivery.
• A detour into underwater orienteering reveals surprising parallels to data work: precision, navigation, and making decisions in the dark.
• Defining data governance: the framework of rules, processes, and responsibilities that guide how organizations create, use, secure, and improve data.
• Why it matters: Governance drives clarity, accountability, and value creation—not just control or compliance.
• Understanding the difference between data governance (framework and value creation) and data management (the operational “doing”).
• A common failure pattern: organizations naming “business data stewards” without training, tooling, or understanding the expectations.
• Governance only works when decentralized experts feed real issues into a central team—not when policies are pushed top-down in isolation.
• Data products demystified: they’re the outcome of well-governed data—reusable, high-value information assets that improve processes, decisions, speed, or cost.
• Real examples: using historical field data instead of simulation data to accelerate engineering calculations or using decades of bird-flight video to predict weather with AI.
• Risks of bad data with AI: incorrect system guidance, support tickets exploding, contradictions between outdated documents, and misplaced trust in “the easy button.”
• Governance foundations: critical data identification, metadata transparency, ownership, RASCI clarification, and understanding who creates, changes, and consumes data.
• The messy reality: access rights often don’t match process needs—leading to shortcuts, bypasses, and unintended process redesign opportunities.
• Final takeaway: data governance isn’t bureaucracy—it's a structured path to value, clarity, and safer AI adoption, but it requires real effort, definitions, ownership, and cultural change.

You can reach Angelika on LinkedIn here: https://www.linkedin.com/in/angelika-rinck-b93a7019b/.

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

In this episode, we welcome Finnish enterprise architect and author Eetu Niemi to explore what it means to make enterprise architecture (EA) “lightweight”—practical, collaborative, and relevant in the real world. From frameworks to fiction writing, from ivory towers to coffee-fueled collaboration, this conversation dives into how to make EA actually work for organizations.

With over 16 years of experience in architecture consulting at CGI, Coala, and Accenture, Eetu has guided more than 45 private and public organizations in transforming their business and IT landscapes. He specializes in enterprise and solution architecture, helping organizations align technology with strategy, improve EA practices and tools, and strengthen information security.

A published author and recognized thought leader, he wrote the first EA book in Finnish and two bestsellers on IT consulting and frequently shares insights through blogs, newsletters, and speaking engagements. Holding a PhD in enterprise architecture benefit realization and an MSc (Econ.), his cross-industry work spans finance, telecom, manufacturing, and the public sector—delivering results in EA modeling, governance, and tool implementation with platforms such as BiZZdesign, Ardoq, and Sparx EA.

In this episode of the podcast, we talk about:

• Eetu’s background — Author, architect, and advocate for democratizing enterprise architecture so it’s accessible beyond the ivory tower.
• Rethinking EA’s relevance — Success comes when EA shifts from being “nice diagrams” to being indispensable guidance that helps organizations plan, adapt, and reduce risk.
• Defining “lightweight EA” — It’s all about communication and cooperation, using models as tools for dialogue, not as ends in themselves.
• Avoiding EA’s common traps — Filling every box in a framework or modeling everything down to cables and servers misses the point. EA should focus on solving real business problems.
• Where to draw the line — Model at the logical level (applications, processes, data) — not every internal detail. EA is the layer above IT and process modeling, not a replacement for them.
• Kickstarting EA right — Start small, plan with stakeholders, and document goals and methods early. Collaboration beats over-engineering every time.
• Who to talk to first — Don’t wait for the C-suite; start where you have access, build trust, and work your way upward.
• Quick wins matter — Focus on tangible outcomes like system maps for upcoming projects — those early wins open doors and earn invitations “to the next party.”
• Light tools for light EA — Begin with approachable modeling tools instead of overcomplicated platforms. Save the big systems for when you truly need them.
• Governance without the grind — Keep EA blueprints current but concise. A handful of well-maintained diagrams is better than hundreds of forgotten files.
• Collaboration is key — EA succeeds through engagement: creating models with people, validating them with people, and helping those people make better decisions.
• Selling the value — Show how EA helps others succeed — whether that’s IT planning, compliance, or transformation — and you’ll overcome “I have no time for this” resistance.
• EA + AI = opportunity — Complexity is growing, not shrinking. AI can help classify, visualize, and assist — but architects still provide the judgment and storytelling.
• Making EA stick — Keep the practice alive through persistence and visibility. Even when budgets tighten, lightweight EA thrives by staying practical, connected, and useful.

You can reach Eetu on LinkedIn here: https://www.linkedin.com/in/eetuniemiphd/

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

Welcome to a very special episode of What’s Your Baseline? — where we demystify enterprise architecture and business process management. In this milestone 100th episode, we are joined by fellow BPM podcasters from Prozess Philosophen and BPM360 to celebrate, reflect, and talk about the wild ride of creating content in this niche space.

In this episode of the podcast, we talk about:

• Milestone celebration — 100 full-length episodes! A look back at the journey and what's ahead.
• Origin stories — How each podcast got started: from Munich restaurants to airport lounges, and "anonymous alcoholics for BPM enthusiasts."
• The evolution of podcasting — From rough first episodes to polished productions (or intentionally unpolished ones).
• Video vs. audio debate — The pros, cons, and time costs of adding video to podcasts; why some stick to one-take recording.
• Editing realities — 10 minutes vs. 8 hours: wildly different approaches to post-production and what works for each team.
• Authenticity over AI polish — Why staying real and soulful matters in an era of AI-generated, hyper-polished content.
• Community-driven content — Listener feedback shapes episodes; the power of niche audiences and recurring themes.
• Lessons learned — Top advice for aspiring podcasters: just start, don't overthink, make guests comfortable, and embrace imperfection.
• Underrated vs. Overrated — Change management (underrated), AI hype (overrated), process models (underrated), BPMN notation alone (overrated).
• The future of BPM podcasting — Where the medium is headed, from knowledge lexicons to safe spaces for authentic discussion.
• Listener challenge — What content do you consume? How do you consume it? What resonates with you and why?
• Gratitude and reflections — A heartfelt thank you to the audience, guests, and the BPM community for four years of support.

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.

Last week we took a deep(-er) look at what BPMN is today and pointed out the scope, difficulties, and misconceptions in the current specification.

But what are ideas for improvements?

I am glad that you asked, because this episode is exactly about this (with a slight twist to the business side of things). In this episode of the podcast, we talk about:

• Today’s topic: What should BPMN 3.0 look like? Spoiler—it's more than just dots and arrows.
• The hosts unpack the missing hierarchy in BPMN—why we need clear distinctions between high-level, process, and task models. Roland argues for flexibility and “N levels of process”—from value chains down to sub-processes.
• J-M pushes for decision levels—models as tools for making decisions, not just communication artifacts.
• Call activities: misused, misunderstood, and overcomplicated. The guys agree—most analysts don’t touch them right.
• A deep dive into lanes and pools—why they’re conceptually fine but practically messy. (Stop naming your pool after your process, people!)
• Both want organizational elements as first-class citizens—RACI, org roles, and system links built right into the spec.
• Execution vs. documentation: the eternal BPMN dilemma. Should the spec drive engines, or help humans? (Hint: both.)
• J-M dreams of BPMN models training AI agents. Roland gets heartburn just thinking about it.
• “Lanes need intelligence.” The duo agree that automation, RPA, and AI will force clarity in BPMN sooner rather than later.
• Roland throws shade at the spec’s quality control—gateways aren’t decisions, folks! Read the fine print.
• The conversation drifts into data, risks, and controls—areas where BPMN could learn a lot from EPC and real-world practice.
• We are discussing other objects: “page connectors” (process interfaces), groups, milestones, etc.
• Closing thoughts: BPMN 3.0 should unify the best of documentation and execution, EPC’s expressiveness, and OMG’s rigor—with a bit more consistency, please.

Please reach out to us by either sending an email to [email protected] or signing up for our newsletter and getting informed when we publish new episodes here: https://www.whatsyourbaseline.com/subscribe/.