Removing the barriers to the architecture discipline
Have you ever been confused by jargon-y architect language? Things like “TOGAF”, “BPMN”, and “UML” — what do they mean, and why do they matter? Or suffered through a system implementation that had a lot of upfront planning, but ended up with scope creep?
Welcome to the What’s Your Baseline Podcast, where we explore these topics and more. This podcast is about Enterprise Architecture and Business Process Management, and how you can set up your practice to get the most out of it.
It is for:
newbies who just get started with these topics,
organizations who want to improve their EA/BPM groups and the value that they get from it,
as well as practitioners who want to get a different perspective and care about the discipline.
So what can you expect here? Each episode, we’ll be diving into a topic that is relevant for you. What it is, why it’s interesting and why you should care. We’ll also share stories from the road – how to implement best practices, and their value.
Join us on this bi-weekly journey with the What’s Your Baseline Podcast and companion blog.
Latest episodes
Ep. 111 — Successful Presales: Max Lüpertz
“Just go and show our tool in the best way possible.”
I have heard this sentence wayyyy too often coming from a salesperson, and the solution engineer on the receiving end …just died a little bit inside.
Of course you want to make a good impression when showing your tools to your customer, but more importantly, you want to start building a relationship and engage with them. For that you have to get them to a point where they open up and tell you what they *really* think—and a “no” is a good indicator that this relationship has formed.
And we are happy to have a pro in this field as the guest of this episode: Max Lüpertz. Max is a solution engineer who took over as account executive and grew until he led the whole sales organization of the UK for one of the companies he worked for.
Now he helps fast-growing SaaS companies close more deals by making their sales demos (and their general presales) better. He provides hands-on coaching and sets up a simple, repeatable demo process with his firm, PreSales Rockstars.
In this episode of the podcast, we talk about:
— Solution engineers are too often treated as “demo monkeys”—pulled in before proper discovery has happened because AEs need to show pipeline progress. There is no solution without a problem: if you don’t understand what the customer is trying to solve, any demo you run risks being irrelevant or overwhelming.
— Once a prospect has seen the functionality and shortlisted vendors, their mindset shifts entirely—from “Can it do this?” to “What happens to me personally if this goes wrong?” Drawing on the SPIN Selling framework, Max explains that risk becomes the dominant concern at this stage, and SEs who keep selling features after that point are talking past their audience.
— Oversharing is one of the most common and costly demo mistakes. Bombarding a prospect with features increases cognitive load, raises perceived risk, and dilutes the message. When perceived risk exceeds perceived benefit, customers don’t choose a competitor—they do nothing at all.
— Max’s lesson from an 18-month stalled deal: FOMO caused him to show 50 features when the customer only needed three. The extra complexity made the project feel like a burden, and the prospect concluded they weren’t ready. The “shotgun” method—showing everything and hoping something lands—is an AE-driven trap. Effective demos need a curated storyline built around confirmed needs, not a feature parade.
— Discovery is not a one-time AE activity. SEs need to run a secondary, deeper discovery to uncover the personal risks and motivations of individual stakeholders—not just the organizational problem. Good SEs ask uncomfortable questions, including ones that could surface a “no,” because proactively raising objections prevents them from becoming deal-breakers at the contract stage.
— How you introduce yourself sets the ceiling on your influence. Being framed as the “technical conscience” boxes you into a narrow role. Instead, position yourself as someone who knows the industry, has seen implementations succeed and fail, and will proactively surface the risks the customer doesn’t yet know about—the things they don’t know they don’t know.
— SEs act as a “human API” between customers and product management—translating vague feature requests into actionable feedback and pushing back on requests that turn out to be aspirational rather than genuine buying signals. The right question is always, what outcome are they trying to achieve, and is this feature actually the best way to get there?
— POCs are high-cost investments—often two people for two to four weeks—and should never be offered just because it’s “the next step.” Success criteria must be defined upfront, and the SE should use the POC as a “gift and get”: offer time and resources in exchange for early involvement in security review, legal, or procurement so both sides avoid losing months at the finish line.
— The value conversation must anchor every interaction. If a customer can’t explain why they want to model processes beyond “so that we have modeled processes,” they aren’t ready to buy. Every conversation needs to come back to outcomes—regulatory compliance, operational change, and team efficiency—not features. And on the buying side, prospects who show up without a clear brief fall into the paradox of choice, get overwhelmed, and make worse decisions.
Max is also on LinkedIn—check out his profile here: https://www.linkedin.com/in/max-luepertz/.
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!Show More
Now Playing
Ep. 111 — Successful Presales: Max Lüpertz
“Just go and show our tool in the best way possible.” I have heard …
“Just go and show our tool in the best way possible.”
I have heard this sentence wayyyy too often coming from a salesperson, and the solution engineer on the receiving end …just died a little bit inside.
Of course you want to make a good impression when showing your tools to your customer, but more importantly, you want to start building a relationship and engage with them. For that you have to get them to a point where they open up and tell you what they *really* think—and a “no” is a good indicator that this relationship has formed.
And we are happy to have a pro in this field as the guest of this episode: Max Lüpertz. Max is a solution engineer who took over as account executive and grew until he led the whole sales organization of the UK for one of the companies he worked for.
Now he helps fast-growing SaaS companies close more deals by making their sales demos (and their general presales) better. He provides hands-on coaching and sets up a simple, repeatable demo process with his firm, PreSales Rockstars.
In this episode of the podcast, we talk about:
— Solution engineers are too often treated as “demo monkeys”—pulled in before proper discovery has happened because AEs need to show pipeline progress. There is no solution without a problem: if you don’t understand what the customer is trying to solve, any demo you run risks being irrelevant or overwhelming.
— Once a prospect has seen the functionality and shortlisted vendors, their mindset shifts entirely—from “Can it do this?” to “What happens to me personally if this goes wrong?” Drawing on the SPIN Selling framework, Max explains that risk becomes the dominant concern at this stage, and SEs who keep selling features after that point are talking past their audience.
— Oversharing is one of the most common and costly demo mistakes. Bombarding a prospect with features increases cognitive load, raises perceived risk, and dilutes the message. When perceived risk exceeds perceived benefit, customers don’t choose a competitor—they do nothing at all.
— Max’s lesson from an 18-month stalled deal: FOMO caused him to show 50 features when the customer only needed three. The extra complexity made the project feel like a burden, and the prospect concluded they weren’t ready. The “shotgun” method—showing everything and hoping something lands—is an AE-driven trap. Effective demos need a curated storyline built around confirmed needs, not a feature parade.
— Discovery is not a one-time AE activity. SEs need to run a secondary, deeper discovery to uncover the personal risks and motivations of individual stakeholders—not just the organizational problem. Good SEs ask uncomfortable questions, including ones that could surface a “no,” because proactively raising objections prevents them from becoming deal-breakers at the contract stage.
— How you introduce yourself sets the ceiling on your influence. Being framed as the “technical conscience” boxes you into a narrow role. Instead, position yourself as someone who knows the industry, has seen implementations succeed and fail, and will proactively surface the risks the customer doesn’t yet know about—the things they don’t know they don’t know.
— SEs act as a “human API” between customers and product management—translating vague feature requests into actionable feedback and pushing back on requests that turn out to be aspirational rather than genuine buying signals. The right question is always, what outcome are they trying to achieve, and is this feature actually the best way to get there?
— POCs are high-cost investments—often two people for two to four weeks—and should never be offered just because it’s “the next step.” Success criteria must be defined upfront, and the SE should use the POC as a “gift and get”: offer time and resources in exchange for early involvement in security review, legal, or procurement so both sides avoid losing months at the finish line.
— The value conversation must anchor every interaction. If a customer can’t explain why they want to model processes beyond “so that we have modeled processes,” they aren’t ready to buy. Every conversation needs to come back to outcomes—regulatory compliance, operational change, and team efficiency—not features. And on the buying side, prospects who show up without a clear brief fall into the paradox of choice, get overwhelmed, and make worse decisions.
Max is also on LinkedIn—check out his profile here: https://www.linkedin.com/in/max-luepertz/.
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!Show More
Now Playing
Ep 110 – What's Your Baseline? in 2026
We teased it over the last couple of weeks when Roland posted about …
We teased it over the last couple of weeks when Roland posted about how to build products and when we started things like our Substack (an excellent article by Hanneke …is out this week—go take a look!).
But now it is the time to give you a look behind the scenes at how your favorite podcast turns the page from a hobby to a real business. And then there is also another welcoming change coming to you … that I guess most of you have missed over the last couple of episodes.
In this episode of the podcast, we talk about:
— The Return of J-M: J-M makes his highly anticipated return as co-host after a brief hiatus. The duo also gives a massive, heartfelt shoutout to the guest co-hosts who stepped up to the mic during his absence—Caspar, Matus, and Russell.
— From Hobby to Business: The episode focuses heavily on the future of the brand in 2026. They discuss transitioning the podcast from a fun passion project into a fully fledged, legal business entity registered in Virginia.
— Who This Is For: They reflect on their core target audience, which includes current practitioners and practice leaders. They also focus heavily on helping the next generation of professionals who need to learn foundational process knowledge.
— The Tech Stack Glow-Up: The hosts discuss their evolving technology and production stack. They detail their journey of moving from simple tools like iMovie to robust platforms like Riverside or Premiere Pro.
— Hitting the Road: Building relationships through live events remains a top priority. They highlight upcoming speaking engagements at the All About Process Management conference in Germany, as well as upcoming events with ABPMP and the PEX Network.
— Pillar 1—Packaged Knowledge: The first new business pillar focuses on “Packaged Knowledge.” This includes their published books, J.M.’s upcoming “explain-it-like-I’m-five” mini-series, and highly graphical visual reference guides.
— Pillar 2—Tools and Templates: The second pillar features “Tools and Templates.” These are specifically designed as gap-closers for software platforms, aiming to save clients from having to purchase expensive, bespoke consulting.
— Under the Hood with KNIME: As part of this tooling effort, Roland mentions he is building specific data models and workflows. For example, he is currently finalizing a KNIME workflow designed to process spreadsheet data into a more meaningful output.
— Pillar 3—Skills Building: The third pillar is entirely dedicated to “skills building.” We plan to offer online training courses that cover core concepts, tool mechanics, and contextual governance, all at accessible price points.
— Pillar 4—Consulting Services: For the fourth pillar, the guys will continue offering targeted “Consulting Services.” This ranges from traditional consulting engagements to tweaking their provided templates to fit a client’s specific regulatory or organizational needs.
— Media Services: A brand new “Media Services” offering will help aspiring creators get their voice out there. They plan to assist authors with publishing under their official imprint, help with end-to-end podcast production, and provide marketing support.
— Creator Spaces: Community building is expanding through dedicated “Creator Spaces.” They are utilizing platforms like Discord and Patreon to foster synchronous conversations and mutual support among process practitioners.
— What’s Dropping Next: In the coming weeks, audiences can expect an influx of short-form “TLDR” videos. They are also launching a brand new web shop with integrated learning management and will be sharing the results from their recent audience survey.
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.
Ep. 109 – Business Transformation: Meherban Faroogh
– – Business transformation programs rarely fail because of …
– – 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.
Meherban is the founder of PPS Partners in Toronto, who 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 almost never 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.
— Creating a psychologically safe environment during discovery workshops—through humor, deliberate pacing, and reframing pain-point conversations away from blame—is what gets the real issues on the table rather than the polished version.
— 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.
— Trust requires touch: building genuine alignment across an organization is extraordinarily difficult to do purely online, and the shift to remote-first working has made this one of the hardest and most underappreciated challenges in transformation today.
You can find Meherban on LinkedIn: linkedin.com/in/meherbanfarooq.
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.
Is quality management the most thankless job in the organization? In …
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!Show More
Now Playing
Ep. 107 — Business Architecture Explained: Breanne Casteel
Sometimes (always?) the problem that we see in organizations is not …
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.
One of the skills that I see an increasing demand for Business …
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.
PS: Please reach out to us by either sending an email to hello@whatsyourbaseline.com. And meanwhile, don’t forget to subscribe to the What’s Your Baseline? podcast on your favorite platform.
This podcast is hosted by Roland Woldt and J-M Erlendson, two experienced consultants with decades of experience in large consulting firms and tool vendors.
About Roland
Roland is the main author of this site and the podcast host.
He is a well-rounded executive with 25+ years of Business / Digital Transformation consulting and software development / system implementation experience, in addition to leadership positions within the German Armed Forces (11 years).
He has worked as a Team Lead, Engagement / Program Manager, and Enterprise / Solution Architect on many projects. Within these projects, he was responsible for the full project life cycle, from shaping a solution and selling it, to setting up a methodological approach through design, implementation, and testing, up to the roll-out of solutions.
J-M is the co-host of the podcast, and is a Business Process Architect, Methodology Specialist, Conference Speaker, and Transformation Engineering Lead with over 15 years of experience in Business Process Management (BPM), Enterprise Architecture, Supply Chain Management, and Project Management. He helps clients develop and implement business process frameworks, hone process-centric strategies, and execute process improvement and architecture modernization projects.
He is a leader in business, founding and running multiple highly successful independent arts companies and charities.
Here are the guest on our show so far. Click on an image to open the episode in a new tab.
Mike Idengren: Scaled Agile and Arch.
Julian Krumeich: Process Mining
José Pires: Get the most out of conferences, ...
Carlisle Gunn: EA strategy & capabilities
Zach Bennett: Strategic process consulting
Caspar Jans: Management of change
Jason Jovanis: Working with recruiters
Amar Modi: Interacting with analysts
James Dening: Process Mining
Jakub Dvořák: Consulting in Process Mining
Ansgar Bittermann: Selecting the right team
Kevin Scully: Task Mining & RPA
Ziv Ilan: Task Mining & RPA
Laurie Kelly: Communic. the Value of EA
Wings Liang: Quality Excellence
Avi Ghosh: Open Source
Rick Smith: Security Architecture
Josèphe Blondaut: Women in Process
Gabriela Galic: Women in Process
Mirko Kloppenburg: How to inspire people
Bernd Rücker: Process automation
Ron Baker: Lean and Six Sigma
Jeremy Voltz: WYB Shorts 9
Sebastian Kotulla: Lean and Process Mining
Dan Marquez: Strategy to Execution
Jehane Adam: Org. Change Management
Adi Klevit: Process Mgmt for Small Orgs
Walter Bril: Process Notations
Luca de Risi: Why CiOs need EA
Marc McGregor: Enterprise Mining
John Hill: Process Simulation
Anthony Gilbreath: Sustainability
James Toomey: Design-driven Transformation
Kevin Tan: Process Modeling
Christoph Piller: Subject-Oriented BPM
Moritz Berger: APQC
Gia Thi Nguyen: Center of Excellence
Peter Dern: Learning & Enablement
Adam Egger: Learning & Enablement
Ron Cohen: Learning & Enablement
Michael Schank: Process Inventory
Shoeb Javed: Operational Intelligence
Martin Holling: BPM Implementation
Lotte Vugs: Process Mining Data
Wiebke Apitzsch: Data Projects
Caspar Jans: BPM Adoption
Maximilian Neumaier: Low-Code/No-Code
Scott Armstrong: AI and BPM
Heather Wendt: Building Community
Breanne Casteel - Bus. Arch. Implementation
Peggy McCann - Retirement Challenge
Amy Levine - High-Performance Teams
Olaf Geyer: Process Mining Readiness
Mike DeCamp: Business Arch. For New Product
Russell Gomersall: EA/BPM Misconcept.
Caspar Jans: EA/BPM Misconceptions
Nick Reed: Mergers & Acquisitions
Luca de Risi: Mergers & Acquisitions
Michael Schank: GRC & Process Perspect.
Craig Overmars: Exec.-Aware Strategy
Dan Marquez: Execution-Aware Strategy
Hanneke Loefs-Mos: Process Community
Leslie Robinet: Unleashed EA
Ben Lamorte: OKRs
Matúš Mala: Process Mgmt Education
Tuhin Chakraborty: AI-Driven Task Mining
Zbigniew Misiak: BPM Trends
Kastin Deal: Legacy Modernization
Neelesh Harmalker: Effective Change
Steve Ponting: Emotional Intelligence
Maxwell Smith: AI Hype
Katharina Paulick: Green BPM
Vassiliki Spentzou: Integr. Mgmt System
Tony Phillips: Decisions, decisions ...
Daniel Matka: Episode 100!
Russell Gommersal: Episode 100!
Christoph Piller: Episode 100!
Caspar Jans: Episode 100!
Eetu Niemi: Lightweight Enterprise Arch.
Angelika Rinck: Data Governance
Dan Funk: Open-Source Automation
Daniel Matka: BPM Education
Michael Hill: PEX & BPM Publication
Rosaria Silipo: KNIME & Data Analytics
Breanne Casteel: Bus. Architecture Explained
Regina Haar: Quality Management
Meherban Faroogh: Bus. Transformation
Max Lüpertz: Successful Presales
What others say
Praveen Edwin
The What’s Your Baseline? podcast is a tool I keep in my back pocket to navigate the challenges in an ever-changing business technical ecosystem.
The podcast episodes cover topics that are relevant to business process management, process optimization and enterprise architecture domains.
The podcast gives me an immediate perspective on how, as an enterprise architect, I should look at these topics with a lens to see where and how it applies within my landscape.
Praveen Edwin
Reddy Ice
José Pires
Enterprise Architecture and Process Management nowadays are filled with technical jargon, which is an unnecessary obstacle for organizations and professionals who want to get started or stand up their own practices effectively and efficiently.
The What’s Your Baseline podcast demystifies these disciplines with clear information and targeted advice. In addition to architecture-relevant topics, the podcast includes culture, business, and digital transformation practical insights that will help you run your practice better.
Roland and J-M also have great chemistry, which makes listening to their show both valuable and entertaining.
José Pires
Excellence & Innovation
Dr. Helge Hess
In a business world deluged by so many buzzwords, clarity is power. That is exactly the value that the podcast ‘What’s your Baseline?’ delivers.
The two hosts Roland and J-M have decades of practical experience in the fields of Business Process Management and Enterprise Architecture and manage not only to explain theoretical concepts, but also to show the very concrete practical benefits for companies on their way to Operational Excellence.
A must-hear for all BPM/EA stakeholders!
Dr. Helge Hess
Software AG
Kevin Scully
Whats Your Baseline tackles the myths and facts of the multi-billion dollar Process Intelligence market; covering topics such as Task Mining, Process Discovery, Process Mining, Process Modeling and RPA.
Roland and J-M, with their guests, provide valuable insight into the nuances of each approach to better understand how to optimize business processes. Using a medical simile, process mining provides the “prognosis” and RPA provides the “medicine.”
It’s refreshing to hear from experts who have been in the trenches versus industry analysts who just review spreadsheets and hearsay.
Kevin Scully
Kryon
Nina Bourgeois
In a world where podcasts have become more and more popular, it is hard to find one that is informational, provides transparency, and has facts from experts in the field.
The “What’s Your Baseline?” podcast provides valuable insight into the Business Process Management and Enterprise Architecture world. It uncovers multitudes of questions one may have, and secrets to help one succeed in this space. It is the perfect on-the-go podcast for someone who is looking to learn more without having to get on a call with a sales person. J-M and Roland have 15-25 years of success in the field.
This is a must-listen to podcast for anyone looking for something relatable and to keep them hooked!
Nina Bourgeois
Zuora
Jakub Dvořák
Despite competing for every valuable minute of listeners’ time in an already crowded podcast scene, it’s always a pleasure to compliment a show of people who are as passionate about their work as you are.
And I can honestly say that it is precisely what I feel from Roland and his co-host J-M on the What’s Your Baseline podcast. It’s a great show about the fascinating world of BPM!
Jakub Dvořák
Process& - Host of the Mining Your Business podcast
Where to find us?
The What’s Your Baseline Podcast can be found on all major platforms. Click on an icon below or search in your favorite podcasting app.
