Successful Architecture Implementation — with Roland Woldt
#63 Get on this flight with Roland Woldt to learn more about Successful Architecture Implementation.
In this episode, I’m talking to Roland Woldt about his new book “Successful Architecture Implementation”. The book is a holistic guide on how to successfully run your Enterprise Architecture — or as I would call it — Business Process Management implementation project.
Today’s Guest:
Roland Woldt
Roland is a BPM, process mining, and transformation consultant, podcast host, and author.
Roland has an impressive track record of more than 25 years in the BPM space. He worked as a consultant and in management positions for Accenture, Software AG, KPMG and iGrafix.
Together with J-M Erlendson, Roland is hosting the What’s your baseline? podcast.
A few days ago, he published his first book to share all his experience with the BPM and Enterprise Architecture community.
Roland lives in northern Virginia, about an hour’s drive from Washington DC, together with his wife, two dogs, two cats, and seven chickens.
You’ll learn:
- What Roland’s new book is all about
- How this contributes to building a process-driven organization
- What Roland’s predictions for the future of BPM are
- Where to meet Roland in person in the near future if you are living in Europe
Resources
- Roland’s LinkedIn Profile
- Roland’s book: Successful Architecture Implementation
- Roland’s podcast: What’s your baseline?
Get notified about new episodes:
Transcript
Please note that the transcript was generated automatically and only slightly adjusted. It does not claim to be a perfect transcription.
Jingle (0:47)
Welcome to the New Process Podcast. Learn all the tools, methods and best practices, combined with people, emotions and a human-centric mindset, to rethink your process and push it to the next level. And here is your host, Mirko Kloppenburg.
Mirko (1:05)
Yeah, welcome to episode 63 of the New Process Podcast. Welcome to episode 63 of the New Process Podcast. Today we’re going on to a short flight with BPM process mining and transformation consultant, podcast host and soon-to-be New York Times bestseller author, Roland Woldt. Roland has an impressive track record of more than 25 years in the BPM space. He worked as a consultant and in management positions for Accenture, Software AG, KPMG and iGrafx. Together with J-M Erlendson, Roland is co-hosting the What’s Your Baseline Podcast and a few days ago he published his first book to share all his experience with the BPM and enterprise architecture community.
Mirko (1:53)
Roland lives in Northern Virginia, about an hour’s drive from Washington DC, together with his wife, two dogs, two cats and seven chickens. I really appreciate his experience and his view on BPM matters. I have already been a guest on his podcast and now I’m looking forward to talking to him in this format. So in the episode you will learn what his new book is all about, how this contributes to building a process-driven organization. We are also elaborating a bit on his predictions for the future of BPM and you will learn more about the chance to meet Roland in person in the near future if you are living in Europe. So enjoy the interview with Roland Woldt.
Jingle (2:41)
And now let’s start to rethink processes.
Mirko (2:45)
Yeah, welcome to New Process Podcast, Roland. Finally, we made it. It’s great to have you here, so welcome.
Roland (2:53)
Thanks for having me. I’m super confused if I should talk German to you or if we speak in English.
Mirko (3:00)
Actually the last episode I published twice. I recorded it twice, one in English and one in German language, so you could have been a guest for a double version as well, but let’s stay in the English world here today. That’s okay, I would say.
Roland (3:19)
I would have to remember what I said, you know, and then repeat it, which, at my advanced age, is not that easy.
Mirko (3:26)
Yeah, I can imagine. Yeah, but anyways. So let’s dive right into the check-in. So what do you prefer in an aircraft: aisle or window seat?
Roland (3:37)
Aisle.
Mirko (3:38)
Why?
Roland (3:39)
It’s just more convenient, you know. If you need to go to the restroom or if you need to get to your roller bag or whatever, you don’t have to ask other people.
Mirko (3:48)
Okay, and what is your favorite airport?
Roland (3:57)
Oh, that is a very good question. So the local airport — we have three airports in the DC area. So we have National in DC, which is the least favorite because of the traffic to get there. We have Baltimore-Washington International, which is a small airport but it’s clean, it’s convenient. You drive over the interstate to get there. But my local airport is Washington Dulles and it’s like a big bus station, you know. You just arrive and then it’s like — they have a little train that brings you to the gates or to the terminals and it feels like riding a bus. So that’s not fancy-favorite.
Roland (4:35)
I would love to see — I haven’t seen it — I would love to see the new airport in Portland, Oregon. As you know, I worked for a company that was based in Portland, so I’ve been there a couple of times. But they just reopened a new terminal and I saw videos about it. It’s super nice because obviously Portland, you know — timber and forest and whatnot — they played with that theme and it looks super awesome. So I’m looking forward to going back there and see how the airport looks. You know, the old one that I used was also not fancy.
Mirko (5:10)
Okay, anyway — Portland, Oregon. Cool. Okay, yeah. So that’s it for the check-in. Then I would say — that’s basically my favorite question I always ask — how would you describe your relationship to processes?
Roland (5:37)
Oh, they exist.
Mirko (5:38)
They exist, you as well?
Roland (5:39)
I think I’m biased. I’m doing that process and architecture thing for almost 30 years now and if you do it for so long — as they say, if you just have a hammer, everything is a nail — you have that professional deformation and you look at something and say, oh yeah, that’s a process error. You know, somebody dropped the ball, they could do better. Even though there might be other reasons — somebody has a heartbreak and is not on top of his game — whatever it is, not everything is a process issue.
Roland (6:17)
But to come back to that, the first time I really was exposed to it was after my military time. Even then I developed some processes for — if, whatever, something bad happens — and you want to have it planned, what you do. But the professional side was when I went in ’97 to Deutsche Bahn where they put up a customer service center on greenfield. After the decentralization and split of the Bahn into Fernverkehr, Nahverkehr, Cargo and so on — the different branches that they have — we built and designed a customer service center for DB Cargo somewhere greenfield, whatever. And they obviously need to know what are the processes, and they were using a very well-known tool for this, and my colleague said “Don’t touch it, you can break it.” And guess what the very mature 29-year-old does? You get your hands on it, you know, and that’s why I got exposed to it. And the rest is history, as they say.
Mirko (7:22)
Um, I introduced you as BPM process mining transformation consultant, as podcast host and now, since a week when we are recording this — so about two weeks when we are releasing this — you are the author of a soon-to-be New York Times bestseller. Congratulations on this.
Roland (7:46)
You know that I shared my royalties just in the prep call, just before this. I’m miles and miles away from it. Close to it, yeah.
Mirko (7:56)
So the book is called Successful Architecture Implementation and then a practical guide on how to implement your EA and BPM program. It is. That’s good. Before we dive into the book — why should I buy your book? Yeah, just sell it to me.
Roland (8:15)
Well, so first of all, you want me to be on the New York Times bestseller list, right? So that’s the means of getting me on that list. But no, in all seriousness, what I’ve seen in so many projects — and I worked for two software vendors in half of my career, the other was working in consulting organizations — and a lot of clients just think like, oh yeah, process, give me your damn tool, give me the niceties and let it go away. And then they start drawing some processes — whatever, they could have used a whiteboard for it, in all seriousness. And then they say, oh yeah, now the project is over, we don’t need this thing anymore. And they put it on their virtual shelf and it collects virtual dust. And at some point in time somebody says, “Why do we pay so much money for it? Why is nobody using it?” And then it just disappears.
Roland (9:08)
And I think that is a missed chance that organizations have. Because — maybe the second detour in my mind — there is no difference between BPM and EA. It’s the same thing. People just look at the same thing with different angles, okay? So an organization has one architecture, a structure, and it could be easily “organically grown” — your listeners see me doing air quotes here — or it could be planned. And of course I think the planned is the better way. And for that you have the tools. There’s various out there. I don’t want to name any one. On my podcast I always say we’re equal opportunity tool critics, so we don’t have a preference.
Roland (9:52)
But in the book I use the tool — so maybe shout out — I was using Software AG’s ARIS for this as an example. But the idea was, yeah, it’s a tiny little tool that exists for 30 years or so, but that was more because that’s the one that I was most familiar with, because that was the one that Deutsche Bahn had and I worked for the vendor, blah blah blah, and I had access to it. So that was the criteria. A lot of the stuff that I describe in the book is applicable to any tool — obviously not the specific configuration steps that I talk about — but all the other stuff.
Roland (10:26)
And I saw the need for the book because I’ve seen those initiatives fail because people just didn’t follow through. They collected dust and then they threw it out. And the reason for that is, at least in my mind, people don’t realize that this is an enterprise software that you implement, and with that there are certain processes that you should follow. And one of the main concepts in the book is the approach that I propose, which has four areas…
Roland (11:04)
The first one is strategy, right — so figuring out who do we want to be when we grow up. You know, who are our stakeholders, what are the objectives, what are the services that we want to provide. Oh, by the way, which gatekeepers do we need to stand up and how do we measure that we are successful? And then that also includes setting up a communication program — right, do good things and talk about it. It also includes creating visibility via dashboards and reports, because there’s that question: are we 5% done or are we 85% done? There’s a tiny difference in between.
Roland (11:42)
The second big thing is — and I say in the book you shouldn’t start with it, but then I start with it because it’s the easiest — is the technology part. Yes, you can do architecture without a tool, but having a tool and having a professional tool makes things so much easier because you can collaborate and you can version — whatever. All that nonsense that those tools do that a whiteboard or a butcher block paper doesn’t do, right? So I call that technical governance — that area. Buy a tool, bring it in, initial provisioning, configuration, scripting, automation, reporting, whatever.
Roland (12:36)
The third one is what I call process and organizational governance. So in my mind, you need to lay out very clearly what are the rules of engagement. So when I think about it: Mirko is the new guy on my project. His role is process modeler. What’s the first question he will ask? “What am I supposed to do?” Right? So you better have an answer for that.
Roland (12:59)
And then I typically like to draw processes for this — because it’s a process, you know? Yeah, love that. If you just have a hammer, everything is a nail, right? So you draw a process, but you derive roles from it that you then can use for permissions, that you then can use and derive your training program from it, because you know what people are supposed to do, you know which roles you have, you know what they’re — whatever, right? So you can do this. Or you can also identify — and I babble about this and I put in the government as an example — you identify your governance organizations, because you have people who do, people who make the rules and people who enforce the rules. So I’m giving the example of the ARB, the Architecture Review Board, which in most organizations is known as the Committee of No — N-O — because they always reject everything. But I want it to be the Committee of Know — K-N-O-W — because they can be helpful.
Roland (14:02)
And I tell the story of a client engagement that I had where we had a very light-touch implementation stand-up of an ARB at that client in an agile environment. So that’s the third one. And then, once you have everything — you have your idea where you want to go, you have your tool, you have rules of engagement defined — guess what? You want to bring in content. So I’m talking about, okay, what is the content import part? That could be twofold. That could be connectivities to other systems of truth, like an Archer for risks or a ServiceNow for apps. But it also could be the big pile of Visios, napkins, whiteboard photos and whatever you have that you need to bring into the tool to put it into your structure.
Roland (14:59)
And there’s a couple of ways how to do this. It starts with creating your catalog — what do I have? — and assessing: is it current? Do I really want to bring that in? Is that a stupid idea, or is it outdated?
Roland (15:10)
So those four areas — and I talk in the book about those, then in separate segments — after an introduction segment where I talk about the changing role of architects and what are the different frameworks and methods and notations and gobbledygook, right? When I also introduce then: which capabilities should you stand up? I’d be using a capability model that one could use for a maturity assessment as well — a capability model that has like five main capabilities, decomposed into 24, decomposed into 105-ish, 115, I forgot, I haven’t counted them lately. Maybe they populate.
Roland (15:58)
So doing this, and then I go into again those areas: strategy, technical governance, process governance and import. And then I round up the book in a last segment where I said, okay, now we’re talking about that stuff for hundreds of pages — let’s apply that to a use case. And I chose BPM as one architecture view, if you want to describe things.
Roland (16:11)
And then I have some real-life examples: well, how does it look like? How do I structure my database? Functional versus end-to-end view? What do I do with risks? I talk about how could an import — in this case into ARIS — look like? Scripting, how do I develop this? Oh, you need a dev and a test and a prod environment. Interesting — that’s extra cost.
Roland (16:35)
I walk people through with the example to say, okay, if I don’t know what to do — anything — in my mind architecture is on the… I don’t know, where does space begin? 100,000 feet? You know, somewhere on that level. You know, it’s relatively simple. You get your arms around something, you create a catalog if you will, and then you analyze your catalog and then you plan and do something — because if you don’t do anything with it, guess what? All the stuff upstream — your catalog and your analysis — is nonsense, right?
Roland (17:10)
And I thought in that last chapter — now we’ve created our functional end-to-end decomposition and we imported stuff — I have three chapters about analysis: like, where do I start if I don’t have anything? There’s one called base analysis, where you use things that the tool ships with — reports and all that stuff — to analyze it. What should you look for in process and work and risk and apps and whatnot?
Roland (17:34)
Then I have a chapter about simulation, which is a very interesting topic in my mind, especially when you think about digital twin and all those shenanigans. And then I have a very thin chapter talking about cross-intelligence, where I basically then put the different analysis methods on a Venn diagram — from human-oriented to data-driven. And if you have a Venn diagram, you can put all the other stuff on there like Lean and BI and all those things — and then it closes out.
Roland (18:10)
I have two more appendices that I talk about: what’s the BPMN and how do I do data modeling — because I referred to that in the previous chapters. And somebody might say “the rules of engagement: create a BPMN diagram” — if you don’t have a clue what BPMN is, you should tell them at least a little bit and not just say “read the 500 pages of the spec”, because nobody will.
Mirko (18:32)
So that’s, in a nutshell, the book. Yeah, cool. Thanks for this holistic overview. I think the content seems to be quite holistic. Whenever I want to introduce EA BPM, it sounds like it’s a good idea to have a closer look onto your book.
Roland (18:44)
I do agree.
Mirko (18:46)
What kind of person — just to verify that — did you have in mind when writing the book?
Roland (19:01)
So it’s… yeah, it’s a — and your listeners know that I run the What’s Your Baseline Podcast, so I’m officially a publisher now. So it’s a What’s Your Baseline publication — yay! It’s the same target. It’s people who work and run those practices — you know, practitioners. Right? So, like your job when you were at Lufthansa, right, where you had to deal with it every damn day and you struggled with the tool and all that type of stuff — you would be dead center in that audience for the book.
Mirko (19:37)
Cool. Yeah, I definitely have to read it. As I said, I haven’t read it up to now, but I’m curious, because that seems to be a quite good fit. You remember I did the survey end of last year, and the top BPM topic for 2025 was “How to build a process-driven organization”, and I think what you are covering in your book is something which is for the people who are going to build a process-driven organization — and that makes sense.
Roland (20:11)
And how it came to be was — obviously, I do that for a while now, right? And I always had the same question, right? And it’s not the client’s fault. Everybody’s new at some point in time. But then I thought, wouldn’t it be great if they just could read it and I could say, hey, it’s here — read it. And when you read it, we can talk. So I started back in 2021, I started writing articles on whatsyourbaseline.com. And that was good enough, right? I also created proposals…
Roland (20:43)
You know, where people ask me, oh, what’s the implementation schedule? I created a little — again — Gantt chart, you know. I said, oh, this, this, this, this. And then I put them in the footnotes and then said, oh, by the way, go to the website — okay, somewhere in the back that nobody reads anyways. But then last year — was it last year or in ’23? — I read that the average business book has 50,000 words. Okay. And I was just curious: how much did I write? And I thought, oh, maybe 20,000 words, I don’t know. So I copied all those articles, as is, right, in a Google Doc — 43,000 words. And I said, oh, 7,000 words, that’s half an afternoon.
Roland (21:30)
So at the end of the day I had to rework all the articles, because sometimes things don’t fly. You should say, oh, as we saw in last week’s article — that obviously doesn’t fly in a book, you know. But in some areas there’s also some thinking that has changed. I wrote those articles, and then on top of it I wrote another 35,000 words. Wow. So the whole thing is now 75,500 words.
Roland (21:50)
And I do have a couple of freebies that readers can download — like the slides and a worksheet for selecting the tool and a tracker in Notion for tracking your imports, that type of stuff. Little add-on bundles that I published as products for sale on the site. A couple of people bought it. So that was my little test pilot — is there an interest for it? And the answer was yes.
Roland (22:27)
And the readers of my book will get access to those for free. So it’s a twofer, as we like to say here — two for one.
Mirko (22:40)
Yeah, that’s super cool. And I would also like to have a look into the future. You were part of the survey and you already shared your predictions for 2025. As far as I remember, it was mostly about the market consolidation. I’m super curious. We’re now in April, so a few months into 2025 — what’s your update on this?
Roland (23:07)
Okay, so first of all, thanks to Hanneke, who was one of my beta readers, who after she read it, came back and said, “I read it, I was unsatisfied — where’s the outlook?” And of course, she was right. So I wrote a couple of pages. But I start with the words: A wise man once said, ‘Predictions are hard, especially about the future.’ So I will not try to look into my crystal ball and tell you what the future holds and pretend that I will be right. So we will see what my observations are there. So take it with a grain of salt.
Roland (23:41)
But I had four things — some of them I said in yours. So one is: architecture will continue to be a niche discipline, because we still struggle with communicating the value. There’s no shared metrics and whatnot. The second one — in opposite to everybody else who said it on your survey — there will be no AI revolution. No. Humans will still be needed. It’s just little helpers that are a little bit smarter than what we had before. The third one is what I said in my prediction: I see a consolidation in the market and I see an opportunity for new players, for an open source tool — which I’m a big fan of, but I don’t want to spoil it too much.
Roland (24:57)
And lastly, the benefits that you can get by doing architecture work and process work — they will be still there in the future, even if you just get started now. Yeah, start now. Right? Tune out the noise that you have and just get started. You will see benefits of doing it.
Mirko (25:03)
Absolutely, I fully agree. And I would also agree to this AI thing. Yeah, it’s a real buzz hype right now and I’m curious what the real use cases will be with regards to BPM. And we talked about that in the podcast where we talked about burnout prevention — maybe it was not in the podcast, it was in the live session afterwards — where Eugene said, oh, even if you apply AI, you may automate a process and get faster, but in the end you will still need someone to verify the results. And for that person to verify the results, it’s even harder because this person has just the end result to verify and does not know the process. How did the AI come up with this and that solution? So maybe we add some more work on the other side if we apply AI. Just one example.
Roland (26:03)
I agree. In our current episode of the podcast — which is the previous one when this show will air — we had a conversation with Matush Mala from the Process Academy. And Matush, he’s at a point in his life where he thinks, oh damn, we need to have some foundations to be laid. You might have seen my posts about, oh, how do we motivate young kids in college to join the profession, which we don’t do. And I like his approach with the nonprofit Process Academy to say, oh, we’re going to name that, because where I agree with him is: you see specialization in college. So, oh, people learn to script Python for process mining and whatnot, but they don’t understand what the bigger picture is. And I have the process lifecycle in my book, and I said, yeah, mining has its place in the landscape — measurement and analysis. That’s great. There’s other things to do — solution design and problem identification and whatnot. You need to have that bigger picture in mind to be able to assess what your current task is and how it fits in.
Roland (27:17)
And I definitely agree with Matush on this — there’s a gap in that foundational training, because we don’t… I get the impression we teach the students to pass a test, we don’t teach them the foundations. We don’t teach them curiosity. To say, oh, why is that? They don’t ask. Like Ted Lasso said, we have an attention span of a goldfish — 19 seconds — and everybody expects them to…
Roland (27:53)
I don’t know. I don’t know. I don’t know. I don’t know, man. I don’t know. Well, you tell me when you read my book, you know — three pages. Let’s see how many years you will need to do that. Let’s find out.
Mirko (28:06)
Absolutely. Oh, that’s super cool. But just to keep it on point here in this episode — what would you say overall? What is your key message to the listeners — not just based on the book, just overall? What should they keep in mind?
Roland (28:24)
That’s a good question. There is a place for BPM and architecture. I said a couple of minutes ago, there are definitely benefits in there. I would aim — if I would get started with it today — I would aim for a more holistic perspective on it. So that’s why I just mentioned the process lifecycle, solution lifecycle, right — to put it in. And I would not specialize too early. I would also not recommend to look at the old methods and say, oh, that’s old, nobody needs it — like what the Lean folks did. The concepts of value and waste — I’m a big fan. If I had no clue how to analyze a process, I would look for those seven types of waste — eight, whatever, yeah — so that limited number. And I would say, when I look at my process, do I find something? Can I make the case and do that type of stuff? So my recommendation for somebody who’s thinking going into this space is: have an open mind, keep your curiosity and don’t specialize too early.
Mirko (29:40)
Okay, that’s good. And read your book.
Roland (29:43)
Of course. Of course. Or the short summary that you will publish — the 19-second version on TikTok.
Mirko (29:50)
Great. So the readers can buy your book, they can listen to your podcast, they can go to your website. Is there any other hidden source we don’t know yet and you would like to share with our listeners? How can they get in contact if they want to know more?
Roland (30:07)
Oh, there’s a couple of things. So first of all — to have the plain advertisement — there’s three ways how you can get the book. Right? I define three bundles. One is: you can today go to Amazon, buy the book as a paperback or as an e-book on your Kindle. That is available now. Or you can read it on Kindle Unlimited — for those of you… I don’t know if they have that in Germany — but it’s a subscription service that they offer. The book will, in a few weeks, also appear on Apple Books and Google Play Books and whatever other things. Right now it’s just on Amazon.
Roland (30:56)
The second thing is, if you’re my target audience — run a BPM or EA practice — I’m happy to sell you a bundle of books. A discount if you buy five. You get a discount if you buy 10, 15, 20, whatever. So let’s talk — ping me. Happy to have that conversation.
Roland (31:14)
And the third one — which is actually aimed at the same target group — is: well, now you read my book. It’s 380 pages and I get the feeling I just scratched on the surface. I offer you, for $100, to get one copy of the book in the format you like and an hour of consultation with me, so that I can answer the questions and you get the color commentary. So three ways of getting it.
Roland (31:40)
Going forward, there will be a German version of it. I just need to have my friend ChatGPT translate it, and then I have to review it and translate the slides and all that type of stuff. And there will be an audiobook version in English that will come out sometime in Q2.
Roland (32:01)
Okay, if you haven’t heard — or if you haven’t had enough of me — obviously there’s the podcast. So we publish the podcast every other Monday. There’s my musings on the website — absolutely correct. And there will be another book this year.
Roland (32:14)
My second book will be called Successful Process Mining Projects, and I’ve developed a six-step process for doing these type of projects. And my idea is to provide a data set, and then you can use that and put it in your tools — simulation, modeling, data analysis, process mining, whatever — and I’m curious if you find the same improvement opportunities following that six-step methodology, if you will, in yours. And I’m super looking forward to this. And of course, you could package this then as a course or anything else to read.
Roland (32:52)
So that’s what I’m currently thinking of when I think about What’s Your Baseline. I’m still working with a couple of friends on a little side project that I don’t know if it ends next, so I don’t want to jinx it now, but there might be something coming in the digital world eventually — or not. So we’ll see. I don’t want to talk about this yet. But if we make the decision that we go with it, then obviously we’ll make a big stink.
Roland (33:27)
The outlet where you can find me is LinkedIn. Mirko, I guess you will put my LinkedIn URL in there.
Mirko (33:31)
Absolutely.
Roland (33:32)
Yeah, I’m absolutely looking forward to hearing from you — not only you, Mirko, but you, the audience. So if you like what we do in the podcast, if you like what I wrote, please reach out. I love having those conversations with people that I don’t know — that’s super cool.
Mirko (33:47)
Wow, thanks for the insights. I think that was quite good to get a quick overview on what the book is really about. And now our listeners can go to Amazon, buy it and get really deep into it. I’m not sure — this was a quite short flight. We already landed the aircraft. I’m not sure if you realize that — that we’re already on the ground.
Mirko (34:14)
Just one second last question — is there anything else you would like to share with our listeners? Did we miss anything?
Roland (34:23)
Wasn’t that enough? I think I was babbling for over 30 minutes now. So, no, no, no. There will be more to come. Right? Stay tuned. Follow, obviously, What’s Your Baseline on LinkedIn. Connect with me, connect with JM, my co-host. Oh yeah, well, he’s a nice guy. I don’t know about me, but he’s a very nice guy. So, anyways — right? So that would be my ask, because I think what we need to do is — it’s a very small community — and I think we all need to, you know, act more with each other, because then that will raise the overall boat, if you will.
Mirko (35:00)
Absolutely, cool. And final question: how would you describe your flight experience today in just three words?
Roland (35:06)
Oh, I didn’t notice that we landed — so, great. It’s good. Yeah, yeah. Flight should be uneventful. It should be like riding the bus, and nothing should happen and you should forget it immediately — which I hope people don’t forget this episode — but within the analogy, it was uneventful. Super soft landing. Yeah, well done.
Mirko (35:29)
Oh, that’s great to hear. Thanks for this feedback, Roland. It’s always great talking to you. So thank you for finally being my guest in the New Process Podcast. I’ve been in yours already, and I’m looking forward to more interactions with you. So thank you so much.
Roland (35:44)
Yeah, we might see each other in September. I will speak at a conference in Stuttgart. I don’t want to say too much, but I heard Hamburg is right around the corner. So you or Martin buy the beer, you know, and I stop by.
Mirko (35:58)
Yeah, maybe we can set up a Stammtisch for this, or we meet.
Roland (36:04)
Oh, Martin already offered that — so you’re too late. I said, yeah Martin, but then I want to have some little thing built out of toilet paper rolls — you know, a little trophy for the farthest commute?
Mirko (36:17)
Absolutely, yeah — and that’s quite fun. That’s cool. I’m really looking forward to that. So, Roland, thank you so much. Have a great day and bye-bye.
Roland (36:24)
You too. Bye.
Jingle (36:28)
Let’s recap today’s New Process inspiration.
Mirko (36:32)
Yeah, thank you for joining us on this short flight today. I hope this conversation helps you to take a decision if reading the book is a good investment for you. Roland is quite holistically covering all the four areas, like strategy, technology, process and organization governance, as well as how to get content into the BPM system. I think it’s certainly worth it for anyone who’s building a process-driven organization to learn more about these four areas.
Mirko (37:05)
I really like his offering of buying the book together with an hour of Roland’s time. So if you are interested in this, I can assure you that you will have an outstanding conversation with him. I’ll put all the links into the show notes — so just go to newprocesslab.com/episode63. And Roland will be visiting Germany in late summer. Isn’t that cool? We are already planning to meet at BPM Stammtisch in Hamburg, so this could also be a good option for you to meet Roland in person.
Mirko (37:42)
To not miss this event, just join the BPM Stammtisch space on New Process Pro. If you are not yet a member of New Process Pro, you can sign up for free by going to newprocesslab.com/stammtisch — this will lead you directly to the respective space and you’ll get an invitation as soon as the date for the next Stammtisch is set.
Mirko (38:02)
For the next episode, I’m planning to share more about the New Process BPM framework in a second bilingual episode — so another episode in English as well as German language is coming up. Just stay tuned. But for now, thank you very much for listening. Have a fantastic day. Bye-bye and auf Wiedersehen.
Jingle (38:24)
You’ve been listening to the New Process Podcast. Make sure to subscribe so you don’t miss the next episode — for more tools, methods and best practices to rethink your process and push it to the next level. Thank you for listening.
Mirko (38:39)
Before you leave — as you might know, I’m doing a lot of research on how to rethink processes and how to find out more about how to rethink your own process. You can download my free New Process checklist, which provides a lot of impulses on how to push your process to the next level. To download it, just go to newprocesslab.com/checklist. Thank you very much. Bye-bye.
