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.116 — Opportunities for the Future: Michael Rosemann

One thing that process and architecture folks are good at is analyzing the as-is and then optimize it.

But why? What would happen if we wouldn’t do “As-Is” and rather start …with a fresh perspective when designing new processes?

Scary?

I think it is scarier what our next guest, Dr. Michael Rosemann, pointed out — that you can only optimize so far until nothing is left for you to do. And then what?

Michael is the author/editor of twelve books available in five languages and the author of more than 400 refereed papers. He is globally known for his work in areas such as BPM maturity models, context-aware BPM, process innovation, rapid process redesign, affective process design and process modelling quality. Michael has presented his work at all major global BPM conferences and delivered keynotes in more than 30 countries. His research projects received funding from industry partners such as Accenture, Cisco, Infosys, PwC, Rio Tinto, SAP, and Woolworths.

In this episode of the podcast, we talk about:

– From efficiency to opportunity. After decades of classic BPM work (maturity models, rapid redesign, reference models), Michael pivoted away from pure cost-cutting toward “crafting desirable futures” — a shift sparked partly by his father asking if making companies more efficient was really the legacy he wanted to leave.

– Three reasons change happens: urgency (a burning platform), curiosity (wanting to test the unknown), or ambition (a clear, desired destination). Leaders who fall into none of these tend to stay “big, fat and happy” — and stuck.

– Root cause analysis of success, not failure. Instead of diagnosing what’s broken, Michael’s team studies “positive deviants” — top performers — and replicates their hidden practices across the organization, using process mining to find and scale what’s already working.

– The seven types of opportunity (a counterpart to Lean’s seven wastes), including concepts like “first data advantage” — looking at what data your process starts with and asking who else might value it (e.g., an airline offering pet-sitting because it already knows who’s traveling with pets).

– Process expansion, attention, and generalization — three of the seven opportunity types, illustrated through Domino’s “pizza tracker” (monetizing attention), and Uber’s expansion from people to pizza, patients, and produce.

– “Lot size of one.” The goal isn’t catching up to best practice — it’s building processes so unique that no competitor, and no amount of design thinking, could replicate them (e.g., QUT’s concept of an “upgradeable degree”).

– Opportunity appetite statements. Just as organizations have risk appetite statements, Michael argues they need the opposite — a deliberate, structured statement of what opportunities they’re willing to pursue, modeled in part on NASA’s approach to balancing risk and ambition.

– Make the future tangible. Examples include a six-minute video imagining a trauma patient’s full recovery journey in 2033, used to rally internal and external stakeholders around a shared vision rather than incremental process fixes.

– RX, EX, TX — Revenue Design, Emotional Experience, and Trust Experience. A framework for evaluating opportunities beyond pure transactions, including the idea of “transactional benevolence” (e.g., Netflix pausing billing for inactive subscribers, or a retailer refunding a price drop you didn’t even know about).

– Reframing the business case. To get leadership buy-in for trust- or future-focused initiatives, Michael suggests shifting the conversation from short-term cost to long-term opportunity cost — the price of not acting.

– AI as a thinking partner, not just a tool. Michael previews a prototype built with SAP Signavio that uses AI to proactively surface opportunities from an uploaded process model — “reverse prompting,” where the tool greets you with an idea instead of waiting for a problem.

– The Future’s Triangle. A simple framework for understanding organizational inertia: the weight of the past, the distraction of the present, and the pull of the future — and why most companies only operate on the first two.

Michael can be found on LinkedIn here: https://www.linkedin.com/in/michaelrosemann/

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

Ep.116 — Opportunities for the Future: Michael Rosemann

One thing that process and architecture folks are good at is analyzing …

Ep. 115 — Startups: Vidar Hokstad

When should you start with process and architecture in a startup? That …

When should you start with process and architecture in a startup?

That was the question that we’ve asked ourselves (as if there is a real-life example currently happening 🙂 and then …we thought, “Why not ask someone who is living in this space?”

And lo and behold, we found that person in Vidar Hokstad and had a very interesting conversation about life in startups and what it takes to even pull it off—not even thinking of our original question.

Vidar co-founded his first tech startup at 19, because he didn’t know enough to know how hard it would be. 30 years on, he has gone mostly from startup to startup, usually as the first technical hire, or a co-founder. He has both bootstrapped and raised VC capital, and recently spent 3 years working at a VC fund. He now runs a tech consultancy focusing on the intersection of DevOps and AI while working on his next big thing.

In this episode of the podcast, we talk about:

A startup is defined by pre-revenue or pre-profit status combined with rapid growth ambition — a chip shop is operational from day one, not a startup. Once you’re profitable and growing modestly, you’re a lifestyle business.

Early-stage capital is the most expensive capital you’ll ever spend, because you’re paying in equity. The earlier you are, the larger the slice of the company you trade away for the same dollar amount.

VC investors expect most of their portfolio to fail and are only looking for the 10x–100x outlier. If you can’t raise your next round within about 18 months, their interest moves on — so failing fast and validating quickly is the entire game.

AI has dramatically lowered the barrier to building a working prototype, letting founders show investors something tangible and compelling much faster than ever before.

But the industry is swinging back hard toward upfront specs and documentation, because AI coding agents can’t infer your unique business context. Writing a truly good spec turns out to be one of the hardest parts of the entire software development process — and most teams have been skimping on it for 25 years.

Your truly proprietary assets are your ideas, processes, use cases, and customer segments. The generated code is a commodity — everyone building on the same AI tools has access to the same output.

Lightweight processes pay off quickly once a startup begins to scale. The absence of basic QA, project management, and clearly written tickets is almost always what causes delivery to break down first — not the process itself.

A common and costly mistake is over-engineering: developers building for 10 million users when the total addressable market is 10,000. This happens when engineering teams are never told what the product actually is or who it’s actually for.

Process and architecture function as a communication layer — aligning engineering, sales, and leadership around a shared vision, the customer they’re serving, and the strategy connecting the two. It builds buy-in, and buy-in produces better work than a paycheck alone.

Vision must be communicated continuously from the hiring process onward, not just stated once and assumed to stick. Developers detach from the “why” quickly when daily work becomes purely tactical.

Both one-on-one check-ins and group meetings are essential to a healthy team. People rarely surface real blockers, interpersonal tensions, or technical concerns in group settings — individual conversations build the trust that makes those things visible before they become crises.

Vidar can be reached on LinkedIn here and also has a website: hockstadconsultng.com.

Reach out by emailing ⁠⁠hello@whatsyourbaseline.com⁠⁠ or subscribe to our newsletter and articles on Substack at whatsyourbaseline.substack.com.Show More

Ep. 114 — BPM Operating System

Roland and J-M go solo to pull back the curtain on something that’s …

Roland and J-M go solo to pull back the curtain on something that’s been years in the making: ⁠BPM OS⁠, a purpose-built, local-first tool stack designed to help small, talented …process and architecture teams stand up a real BPM practice — without the vendor dependency, IT overhead, or 12-month procurement nightmare.

In this episode of the ⁠podcast⁠ we talk about:
— Most BPM programs fail not because of bad content, but because organizations treat it as a pure IT exercise — buy a platform, check the box, and wonder why nothing sticks.
— The three pillars every BPM capability needs are content, governance, and adoption — yet most organizations only address the first one.
— Knowledge rented from consultants or SaaS vendors disappears the moment you stop paying; BPM OS is built on the principle that you own it outright, forever.BPM OS targets three groups: small internal teams doing more with less, consulting organizations that want baked-in methodology for client delivery, and vendors looking to bundle a white-labeled practice layer with their platforms.
— Groundwork is the brainstorming and planning app — dump ideas onto a canvas, sort them into zones, and shift into structured planning mode with priorities and rough timelines.
— Playbook is a lightweight wiki for capturing structured knowledge, course profiles, stakeholder analyses, and methodology documentation — with templates so you never start from a blank page.
— Atlas generates visual subway maps of your learning curriculum or capability landscape, complete with time-sensitive station states, deprecation indicators, and links back to Playbook pages.
— Outline lets you define the detailed content structure of a course or deliverable in a hierarchical, mind-map-style view — moving from “What do we need to teach?” to “Exactly what are the chapters and items?”
— Course Flow is a Kanban-based project management tool for developing and iterating on courses, complete with a built-in feedback form, an inbox for triage, and a status dashboard across all active projects.
— Cadence is a personal (and optionally team) task planner organized by day and category — with recurring daily items, carry-forward of incomplete tasks, and a simple velocity metric to spot overload before it becomes a crisis.
— The entire stack runs on Node.js, saves files as Markdown and JSON (no database required), plays nicely with Google Drive or OneDrive for backup, and optionally connects to GitHub or GitLab for full version history.
— Apps interoperate through lightweight linking and import/export — cards from Groundwork flow into Atlas, tasks from CourseFlow export into Cadence, and every Playbook page carries a permanent link that works anywhere in the stack.

Find out more and download your free personal copy of Cadence at ⁠whatsyourbaseline.com/bpm-os⁠—and check the episode show notes for a PDF overview of all six apps.

Reach out by emailing ⁠⁠hello@whatsyourbaseline.com⁠⁠ or subscribe to our newsletter and articles on Substack at whatsyourbaseline.substack.com.Show More

Ep. 113 — Customer Success Excellence: Chad Stephen

Once you’ve sold the licenses you are done. Right? Well, not so fast, …

Once you’ve sold the licenses you are done. Right? Well, not so fast, young Jedi.
While the salesperson happily will turn around and go hunting elsewhere, the customer has high expectations …about the treatment that he gets after the sale.

And even today I see organizations who see Customer Success teams as an afterthought and then wonder why they see churn or nastygrams from their customers. But it doesn’t have to be this way. We are discussing this interesting topic and organizational setup with Chad Stephen.
Chad has led cross-functional teams of 65, scaled the Customer Success org through 4x ARR growth, cut renewal process complexity by two thirds, and reduced time-to-value by 50%. More than once, at different companies. He has done it multiple times, at companies ranging from early-stage to scaled SaaS, across industries from FinTech to HealthTech to Restaurant & Hospitality.

In this episode of the ⁠podcast,⁠ we talk about:
— What is customer success, really? — Customer success means different things to different people, but the most important definition centers on one thing: driving value for clients. Renewals, onboarding, and account management are elements of CS, not the definition of it.
— The buyer vs. the end user — The person who signs the contract is rarely the one logging into the platform every day. A good CS function speaks to both audiences and translates the value proposition into something meaningful for each one.CS as a function, not just a job title — In any project or transformation, customer success is a function that can be owned by a team, a role, or — dangerously — “everyone,” which usually means no one. The discipline matters regardless of what you call it.
— The QBR trap — Quarterly business reviews that run 80 slides and double as sales pitches miss the point entirely. The best QBRs are about the customer’s problems, not the vendor’s product roadmap.
— Proactive vs. reactive CS—Waiting for a customer to come to you with a problem is reactive. True proactive CS means monitoring usage metrics, NPS surveys, and engagement signals before a crisis happens — not just crossing your fingers.
— The relay race handoff — The baton cannot hit the floor between sales, professional services, and customer success. There must always be a clear, singular point of contact for the client at every stage of the journey.
— When to involve CS in the sales cycle — CS should never be absent from a deal entirely, but timing matters. Bringing them in too early creates confusion; bringing them in at the right moment builds the bridge between “excited to sign” and “ready to succeed.”
— The hunter vs. farmer problem — When account executives are compensated only for net-new deals, they make poor customer success managers. Misaligned incentive plans produce misaligned behavior — something always falls through the cracks.
— Compensation drives behavior — If you want your CS team to own renewals and upsells, you have to pay them for renewals and upsells. Comp plans and job expectations must be in alignment, or you get animosity and dropped balls.
— Start CS early — even at Series A — Smaller organizations often default to the AE managing the account post-sale. The sooner a dedicated CS function exists, the better. Stickiness in SaaS is decreasing, which makes the long-term relationship even more critical.
— Onboarding is the most critical phase — Getting a customer up and running quickly and with a clear understanding of the value they bought, sets the tone for the entire relationship. A poor start is rarely fully recovered.
— Keep it simple — Over-engineered CS motions with 12 segmentation layers and elaborate playbooks often collapse under their own weight. The question to always ask: How does this actually drive more value for the customer?

You can find Chad on LinkedIn here: ⁠https://www.linkedin.com/in/chadstephen/⁠. And, of course, he has a website—https:⁠//www.doublewindconsulting.com/⁠.

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

Ep. 112 — Why Compliance Is Your Friend: Christof Layher

Everyone says they hate compliance. But what they actually hate is …

Everyone says they hate compliance. But what they actually hate is being told the truth at the worst possible moment.
The problem is not the regulation, though. It is the moment …you involve the people who understand it. Too late, under pressure, with no room to course-correct.

And then look at the fact that 65 to 95% of digitization projects fail. The answer is not to run them faster. It is to slow down enough to get them right — and that starts with bringing the right people in before the damage is done. So we brought in an expert in that topic: Christof Layher.

Christof is a digitalization and compliance specialist with over 20 years of hands-on experience in the pharmaceutical and biotech industries, having worked with organizations including BioNTech and mid-sized pharma and biotech companies. He operates at the intersection of IT, quality assurance, and business operations — precisely where those functions most often work against each other rather than together. His focus is on bringing structure, decision-making clarity, and clean execution to highly regulated environments where the consequences of getting it wrong are real. No slide-deck transformations, no tool evangelism — just repeatable, field-tested approaches built for GxP realities that hold up both in daily operations and under audit.

Christof’s methodology follows a clear sequence: establish order first, then drive targeted change, and build organizations that don’t collapse every time something shifts. He describes himself not as an outside consultant but as someone who works shoulder-to-shoulder with teams as a structural partner. He also hosts the ChaosHacker podcast, where he speaks openly about what actually goes wrong in digital transformation — and why common sense frequently outperforms any framework. His goal is straightforward: to set up digital initiatives so that people can make calm, confident decisions even when things get turbulent.

In this episode of the podcast, we talk about:

— Compliance is the messenger, not the cause. Like a doctor pointing out a broken leg you’ve been walking on, compliance teams surface uncomfortable truths that organizations already sense but choose not to address.
— Non-compliance is rarely intentional. In roughly 95% of cases, organizations fail compliance not by design but through blind spots, ingrained habits, and the bias that “it’s been working fine.”
— The “superhero fixer” problem masks systemic risk. When individuals compensate for broken processes to keep things running, the underlying issue becomes invisible — until it isn’t. Resilience can be a crutch.
— Compliance is sometimes weaponized to block change. People who don’t know how to handle new initiatives — or simply don’t want to — hide behind regulatory language rather than engaging honestly.
— Gold-plating regulations create the real slowdown. Rules often require one signature; companies implement ten. The organizational waste comes from over-interpretation, not the regulation itself.
— Shift left — bring compliance in early. The cost to fix issues compounds with every project milestone. Involving compliance at the requirements stage costs far less than presenting them a finished product that fails the checklist.
— Compliance is a competitive advantage, not just a checkpoint. Used as an indicator of where your processes diverge from reality, it becomes a continuous improvement engine — improving service delivery, reliability, and customer experience.
— Slow is smooth, and smooth is fast. With 65–95% of digitization projects failing (per McKinsey), the answer is not more failed projects delivered faster. Taking time upfront — including for compliance — produces better outcomes.
— Process owners must own compliance — not just the compliance team. Pharmaceutical law frames it clearly: the person who operates a process is responsible for running it compliantly. That shift in ownership changes everything about how people engage with the rules.
— Trust must be given before it can be earned. Leaders who model psychological safety — where failure is a shared learning, not a personal liability — unlock the early, honest conversations that prevent compliance crises.
— One bad actor spoils the basket. Building a culture of integrity requires leaders to live it visibly — and to remove those who exploit openness — regardless of their level in the organization.

Check out Christof’s LinkedIn and podcast!

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

Ep. 111 — Successful Presales: Max Lü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

1 of 24

Go to podcast archive

Meet your hosts

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.

Meet our interview guests

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
Christof Layher: Compliance
Chad Stephen: Customer Success
Vidar Hokstad: Startups
Michael Rosemann: Future

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!