Latest / Ops Cast / Keeping the Lights On While Changing the Engine: Managing Transformation in Marketing Ops with Adele Kurki
Transcript
- 0:24Michael Hartmann: Hello everyone.
- 0:25Michael Hartmann: Welcome to another episode of Opscast, brought to you by MarketingOps.com and powered by all the MoPros out there.
- 0:31Michael Hartmann: I am your host, Michael Hartman.
- 0:32Michael Hartmann: Today I'll be talking with our guest about one of the most persistent challenges in marketing operations, how you can how you change the business while still running the business.
- 0:41Michael Hartmann: So to join to do that, joining me is our guest Adele Kirky, senior marketing operations lead at Avon.
- 0:48Michael Hartmann: Over the past several years, Adele has built and led global marketing ops functions through major change, including top-of-funnel redesigns, evolving go-to-market strategies, and large-scale transformations, all while keeping day-to-day execution running across distributed teams.
- 1:03Michael Hartmann: So this episode is going to be all about the reality of transformation inside marketing ops.
- 1:07Michael Hartmann: Hopefully, marketing is a little bit too, balancing BAU work with long-term initiatives, creating transparency across global teams, securing the leadership buy-in for technical change and figuring out when frameworks like Agile help and when they don't.
- 1:20Michael Hartmann: We'll have an interesting conversation about that, I expect.
- 1:22Michael Hartmann: So, uh Adele, welcome and thanks for joining so late since you're in Linway.
- 1:28Adele Kurki: Thank you.
- 1:29Adele Kurki: Thank you.
- 1:30Adele Kurki: It's 8 p.m.
- 1:31Adele Kurki: here in Helsinki, and it's definitely dark as we are recording this on February.
- 1:36Adele Kurki: Um, thank you for a warm introduction and invitation.
- 1:39Adele Kurki: I've been following your podcast uh for a while, and I must say I'm deeply grateful to share my perspective today.
- 1:45Adele Kurki: So um I serve as senior marketing operations lead, as you mentioned.
- 1:49Adele Kurki: Uh a significant recent change is already now.
- 1:52Adele Kurki: Uh, we, for instance, moved the marketing operation team to a revenue operations organization, which adds a little bit of a spice for today's conversation.
- 2:01Adele Kurki: Okay.
- 2:02Adele Kurki: Is that a new thing since we last talked?
- 2:04Adele Kurki: That is a new thing since we last talked.
- 2:07Adele Kurki: But, anyways, we're focusing definitely on marketing operations.
- 2:12Adele Kurki: Uh, more tech operations and analysts in how we are working with our stakeholders uh in in moment of transition as well as day to day.
- 2:22Michael Hartmann: Um, so why don't we start there, like talk through a little bit like in in so this is like a pullback the curtain moment a little bit.
- 2:30Michael Hartmann: So uh when I say Adele and I spoke before, it's um yeah, it varies from guest to guest how long ago that was.
- 2:38Michael Hartmann: Um, but I think we we are recording in early February of 2026, and I think we spoke in early October, if I remember right, something like that.
- 2:46Michael Hartmann: So it's a few months.
- 2:47Michael Hartmann: So um that's not that long, but it sounds like some change.
- 2:53Michael Hartmann: So like maybe walk us through your role.
- 2:55Michael Hartmann: Um and I'm I'm really curious um about the like the global nature of what you do.
- 3:03Michael Hartmann: So we we like I've had global teams managing them from the US, but people in other countries, and we've had a few people on who manage global teams from Europe and other places.
- 3:15Michael Hartmann: So I'd love to get your perspective on that as well.
- 3:18Adele Kurki: Absolutely.
- 3:19Adele Kurki: Actually, let's start first kind of like getting the scope and globe in place.
- 3:23Adele Kurki: Uh, indeed, we are a mighty team of marketing operations specialists uh serving our stakeholders across the US, uh APEC, and Europe.
- 3:35Adele Kurki: So practically we are serving our sales colleagues and supporting colleagues around the globe.
- 3:42Adele Kurki: Um, we are specifically in Europe and US, so that we are able to ensure these 360 uh view support uh every single day.
- 3:53Adele Kurki: Um, maybe kind of like opening a little bit of a like what does it mean?
- 3:57Adele Kurki: What is the scope and what is kind of like the team supporting with?
- 4:00Adele Kurki: Um we are practically ensuring that we have optimized customer journey.
- 4:06Adele Kurki: So practically we in improve sales and marketing alignment, uh, we lead initiatives that boost operational efficiency.
- 4:13Adele Kurki: Uh practically, the team kind of owns the funnel ink, like everything top of the funnel.
- 4:19Adele Kurki: Is it tracking, operations, tooling, marketing analysis uh and analytics is our team?
- 4:25Adele Kurki: Okay, we set the targets in the beginning of the fiscal years, we own AI workflows for marketing.
- 4:33Michael Hartmann: Targets for like leading marketing leads and things like that, funnel funnel metrics.
- 4:37Adele Kurki: Exactly.
- 4:38Adele Kurki: Okay, funnel metrics, setting the targets in the beginning of the fiscal year.
- 4:41Adele Kurki: Like, hey, if our sales target is here, how as marketing function are we able to support to kind of like get us there?
- 4:49Adele Kurki: Yeah.
- 4:49Adele Kurki: Right.
- 4:50Adele Kurki: Um indeed, and of course, there is this admin part, which is not always so cool, which is like the admin.
- 4:56Adele Kurki: Of course, we have always privacy, security.
- 4:59Adele Kurki: When we're thinking about a global business, there are Europe is very like strict with their data privacy, same like all the states might have slightly different elements.
- 5:08Adele Kurki: So all of that work is also monitored and controlled uh in our team.
- 5:13Adele Kurki: If you think about like, okay, we have this global element, we have that work element, what else there are there is there is a ton of stakeholders.
- 5:22Adele Kurki: Um we work day to day, obviously with marketing, it's part of the name as well, right?
- 5:27Adele Kurki: Uh but day-to-day with sales, is it kind of like a sales rep or sales leadership?
- 5:32Adele Kurki: There need to be day-to-day alignment so that we actually connect the businesses together.
- 5:37Adele Kurki: Um, we have sales uh motion, but we have also product motion.
- 5:41Adele Kurki: So we own part of the product motion.
- 5:43Adele Kurki: We work day to day with product teams to ensure that we are the same map, we are roadmap support each other.
- 5:49Adele Kurki: Um and also, of course, if they are end-of-the-life cycles, who owns the customer communications, we're raising our hand and supporting there as well.
- 5:58Adele Kurki: Then, as we have analytics, analytic engineering, all that planning.
- 6:02Adele Kurki: So it's really, really interesting uh core business that we're doing here in the in the marketing operations.
- 6:10Michael Hartmann: It's all because this is it just struck me as you were talking about, and now we're gonna talk more about the the tension between run the business, change the business kinds of things.
- 6:19Michael Hartmann: But also, I just was it sort of hit me as you were describing one of your roles is to help the business, um, whether it's efficiency, velocity, effectiveness of things that are going through the funnel, but also um, and I think about this as being an advocate for customers, right?
- 6:35Michael Hartmann: Whether it's privacy, compliance, doing kind of doing right by them.
- 6:39Michael Hartmann: And it does feel often like those are also intention.
- 6:42Michael Hartmann: Do you in and you got the global differences that make it more complicated?
- 6:45Michael Hartmann: You see, do you feel that too?
- 6:48Adele Kurki: Yeah, absolutely.
- 6:49Adele Kurki: And also something that's really sometimes you forget is like, okay, when you are in like an operations enough, actually, that backroom role is actually sometimes the most customer-facing, is especially if we think about like, for instance, AI workflows, which I mentioned here.
- 7:04Adele Kurki: It's like sometimes actually today you're creating in operations an AI that is actually for us to serve the whole customer flow until the closure.
- 7:14Michael Hartmann: Yeah.
- 7:15Adele Kurki: Which is quite interesting uh perspective as well.
- 7:17Adele Kurki: So then for that perspective, it's really, really good to be connected on those stakeholders that are there to actually monitor and like setting the standards.
- 7:28Michael Hartmann: It's interesting.
- 7:28Michael Hartmann: Sorry, I was kind of smiling because I just had a personal experience.
- 7:31Michael Hartmann: It was not a sales funnel thing, it was more of a support thing, which you know, it was a you know AI chatbot, whatever.
- 7:38Michael Hartmann: And I asked about two questions, didn't understand it, asked the second one, another one.
- 7:45Michael Hartmann: It told me kind of, oh, if you want this, ask this.
- 7:47Michael Hartmann: I put it in.
- 7:48Michael Hartmann: Like, I don't understand what you're saying.
- 7:50Michael Hartmann: I was like, I just put in what you just told me to do.
- 7:52Michael Hartmann: Yeah, and it would not it, I just got the same don't understand over and over and I was five.
- 7:58Adele Kurki: And honestly, those things you want to avoid, right?
- 8:01Adele Kurki: Because it's actually not helping the customer, it's just creating the frustration.
- 8:05Adele Kurki: Then you're like, I remember this brand, but not on the most positive way.
- 8:10Michael Hartmann: Yeah, and if I'm I can't remember what it was, but I think it was like a well insurance thing or something like that.
- 8:15Michael Hartmann: And I'd like no choice, right?
- 8:17Michael Hartmann: I'm like, so uh it's not like I could do anything about it.
- 8:20Michael Hartmann: Anyway, solely off topic, but um so when we talked before, you said that we you know, over the last few years you've led several major initiatives.
- 8:31Michael Hartmann: Um maybe walk us through what some of those are that you want to highlight.
- 8:35Michael Hartmann: Um and maybe go even a step back and like what kind of what was the the trigger or catalyst that led to like why we wanted to pursue those changes to the business.
- 8:47Adele Kurki: Yeah, absolutely.
- 8:48Adele Kurki: I could maybe share kind of like three key elements and then we look a little bit on like how to bring it to the to the board and what kind of like triggers those.
- 8:58Adele Kurki: Maybe if we think about what drives change from marketing operations side, like okay, if it's not like given change, which which sometimes happens.
- 9:08Adele Kurki: It's um after all, we are the architects, we are building the invisible bridges between the data points, we're bringing the actions, we're bringing the insights.
- 9:21Adele Kurki: Okay, from that perspective, often the change is that hey, we cannot bring, like we are missing some bricks from this invisible bridge.
- 9:31Adele Kurki: And that is what at least uh in our case have been triggering a couple of um cool work projects where one, for instance, is that hey, we need to find a good way to automate and build marketing attribution, as simple as that.
- 9:49Michael Hartmann: Okay.
- 9:49Adele Kurki: Do you have the the bricks in place so that you can tell the story to your leadership that, hey, okay, this is what sourced, this is what tipped, this is what influenced, and you know, this is the storyline of the deal.
- 10:02Adele Kurki: And these is these are the ways where we should invest.
- 10:05Adele Kurki: And if you want to make a change, this might be the way where you're leading towards too.
- 10:10Adele Kurki: Another project is from pretty much the same elements.
- 10:16Adele Kurki: It we started quite early within AI marketing flows.
- 10:20Adele Kurki: Okay.
- 10:20Adele Kurki: Of course, they've been kind of like quite along in the business, but it wasn't kind of like that mainstream to bring them uh, let's say four years ago or so.
- 10:29Adele Kurki: And there the conversation started, like, okay, we have again this invisible bridge, and we see their gaps.
- 10:37Adele Kurki: How can we fill it when we don't have resourcing in place?
- 10:42Adele Kurki: Okay, how do you replace basically additional human partners?
- 10:47Adele Kurki: Are there gaps that we can do?
- 10:48Adele Kurki: And we started building actually proactively, like, hey, actually, let's let's do a POC.
- 10:54Adele Kurki: Let's try so that we can sell later for leadership that okay, actually, if we are investing in this, we can provide X times return on investment.
- 11:05Michael Hartmann: Okay.
- 11:06Adele Kurki: And then a third big one, which was actually a quite recent one, is that um sometimes in marketing and especially in marketing operations, we tend to think and simplify that hey, our customers are living only one life cycle.
- 11:23Adele Kurki: So we are looking like, okay, they entered the system, they did this, and then they either closed or did not.
- 11:28Adele Kurki: And um we wanted to solve it.
- 11:31Adele Kurki: Like, hey, okay, how do we create more transparency on if our uh like um prospects are going through with different life cycles?
- 11:41Adele Kurki: Okay, they might not enter to the opportunity process this time, okay.
- 11:45Adele Kurki: Let's end like enrich, engage, blah blah blah, and then they come again and again.
- 11:51Adele Kurki: Yeah, and we created a process on how to bring that transparency to the table.
- 11:56Adele Kurki: Now you can already hear, like, okay, so how did you explain it to your level because it sounds already quite technical and complex?
- 12:04Michael Hartmann: Well, that one is that's another one that's like it's hard to explain because everyone's so used to there's already a linear funnel model, right?
- 12:11Michael Hartmann: Which it it's an easy framework to get, but there that's not the reality.
- 12:14Michael Hartmann: Think of how people research actually behave.
- 12:20Adele Kurki: Yeah.
- 12:20Adele Kurki: And especially if you have product that you can try for free, or you can kind of like bring your colleagues into, or you change businesses.
- 12:30Adele Kurki: Uh, and it's a missed opportunity if you somehow lose the ends after the first life cycle, as we wish.
- 12:36Adele Kurki: So uh and honestly, with this project, I had a lot of difficulties to figure out like, okay, how can I like this this is so important, this is so cool, this is high impact.
- 12:47Adele Kurki: But if you go to your leadership, like, ah, there is this life cycle and these objects and you know blah blah blah blah blah.
- 12:52Adele Kurki: So elements to bring to the table to kind of like create this invisible bridge first, communications and preparations.
- 13:03Adele Kurki: Yeah, find the annex, like find what is important in the in the leadership level, what like what matters, and then try to model some sort of an uh impact.
- 13:14Adele Kurki: It doesn't have to be perfectly fine, like after all, we're not looking at like okay, was it like the stuff?
- 13:20Michael Hartmann: Nothing like accounting data and financial data, right?
- 13:22Adele Kurki: So but kind of like an estimate, like okay, you can all, for instance, in this life cycle side or this AIF law, you can see where the gap is.
- 13:30Michael Hartmann: Something reasonable that you could defend as a benefit, right?
- 13:33Adele Kurki: Even if Yeah, and and get the attention, because then the conversation starts when you are able to get into that table with that first pitch that hey, this is actually relevant, and we want to solve it because it has a dollar value, and dollar values are important for you to make it through this fiscal.
- 13:49Michael Hartmann: Absolutely.
- 13:50Adele Kurki: So that's kind of like how we how we started the conversation.
- 13:53Adele Kurki: Then the other thing uh with some of these projects is that it's really important that you build authority inside the company so that you have a certain level of trust within the leaderships, which means that okay, you do your day-to-day like within your team in a in a good level, you keep the constant transparency, you are visible.
- 14:13Adele Kurki: But for sometimes it is a good thing to do like an official audit or bring an external to support you into this con conversation.
- 14:28Adele Kurki: It is something that I learned a little bit like in an uncomfortable way, because I think I'm like, ah, but I know my business, I've been here.
- 14:35Adele Kurki: Um I know what they're going to say.
- 14:38Adele Kurki: But um we brought a great um consultancy CS2, not advertised, but they did a really good work with us.
- 14:48Adele Kurki: Uh, we brought them to the table and said, like, hey guys, um, we have this problem.
- 14:53Adele Kurki: We really think that this is important.
- 14:55Adele Kurki: We already calculated how much this would be bring bringing us value.
- 14:59Adele Kurki: Um can you kind of like jump into with our leadership and let's have a chat like with additional authority to make it through?
- 15:07Adele Kurki: Yeah, yeah, it's a validation.
- 15:09Adele Kurki: Yeah, sometimes validation.
- 15:11Adele Kurki: And and it was amazing.
- 15:12Adele Kurki: We did like a proper audit, the validation went through, the leadership worked, workshopped with us, like, okay, how does the good look like?
- 15:20Adele Kurki: And we were able to start this process as we planned.
- 15:25Michael Hartmann: Yeah.
- 15:26Adele Kurki: So that's kind of like an additional element which I didn't maybe realize earlier that hey, actually, this is an asset.
- 15:32Michael Hartmann: Um can I just go ahead and finish, and then I have I want to follow up on a couple of threads there.
- 15:39Adele Kurki: Yeah, yeah, absolutely.
- 15:40Adele Kurki: There are so many things that we could discuss.
- 15:42Adele Kurki: Um, but maybe I want to also touch base, which we will discuss also later, is that it's really important that you have data trade trust in the team that is uh is in the team and you bring constant visibility for everyone in the team.
- 15:57Adele Kurki: It is so, so easy, in especially with marketing operations, to just like do the admin, you know, close the fires, please collect the closest stakeholders, but it's really hard to bring the success cases to the organization or these development projects or the actual impact.
- 16:17Adele Kurki: But that's really important if you are willing to bring these big, big projects into the table and want to have that uh first conversation.
- 16:24Michael Hartmann: Yeah.
- 16:25Michael Hartmann: So a couple of things just I want to see if uh this sounds right.
- 16:29Michael Hartmann: So a couple of takeaways for me.
- 16:31Michael Hartmann: One, it's important to speak the language of the stakeholders who have the control of the first strings, right?
- 16:37Michael Hartmann: Who can say yes or no on your your ideas, and I think that's a critical one, and people should spend time understanding what that language is.
- 16:43Michael Hartmann: That's I think it's important.
- 16:45Michael Hartmann: Thank you.
- 16:46Michael Hartmann: Um there's an element of what I would call doing the BAU work well earns you the right to go and trust to go do other things that may be over.
- 16:57Michael Hartmann: Right.
- 16:59Michael Hartmann: Um and sometimes it means also including the right to bring in a uh an expert authority on something to help you prove prove the case.
- 17:08Michael Hartmann: But um the the um I think it's really important here.
- 17:15Michael Hartmann: Yeah I'm I'm a little torn here on the the last point you made about uh trust in data.
- 17:21Michael Hartmann: And I think part of that is what I find a lot of people do with marketing and sales data is they try to treat it when they get grilled as if it should be um right, accurate, whatever word you want to choose, as if it was something that has high levels of control, accounting, finance, you know, operational data, if you were like say manufacturers, like that, which it doesn't like and I think there's a level, like there's a part of this is like, yes, you want to build trust.
- 17:52Michael Hartmann: To me, part of that is setting expectations that like what is right, what is like is not going to be the same level.
- 17:59Michael Hartmann: And also being honest, like like and I think we've all probably I was talking to somebody earlier today about these weird anomalies I would see inside uh, in this case, Salesforce data, that would lead me to go down paths, go like, why am I seeing this?
- 18:15Michael Hartmann: Right, and it turns out there are ways the sales teams were operating, which I don't really like.
- 18:21Michael Hartmann: I have a opinion about whether or not that was the right thing to do, but it was doesn't really matter, right?
- 18:27Michael Hartmann: That was what how they operated and the data led to that.
- 18:30Michael Hartmann: Yeah.
- 18:30Michael Hartmann: And so being able to go, like, hey, we we can or we can't do this, we can get close, we can get directionally correct, right?
- 18:37Michael Hartmann: Right.
- 18:37Michael Hartmann: And I think that's setting that expectation there and being honest about the quality and and completeness and accuracy of the code.
- 18:43Michael Hartmann: Oh, absolutely.
- 18:43Michael Hartmann: Yeah, okay.
- 18:44Adele Kurki: Absolutely.
- 18:45Adele Kurki: And and I think like something that's really good to understand from uh what makes like marketing analytics, for instance, quite specific is that we have uh the top of the funnel which where you cannot measure everything, even if you'd like to, it's always directional.
- 19:01Michael Hartmann: Yeah.
- 19:02Adele Kurki: And then there is this uh additional element, is like what from what angle are you watching the data, or what angle are you reporting the data?
- 19:11Adele Kurki: The sourced, for instance, like if you're looking for hey, let's see um how marketing builds pipeline.
- 19:18Adele Kurki: Yeah, you can look at from so many angles.
- 19:23Adele Kurki: Um there can be as many manual adjustments, opinions, even sometimes, that it's always directional.
- 19:31Adele Kurki: Yeah, and you have to be very specific.
- 19:35Adele Kurki: For instance, when I'm providing numbers, let's say to the Bordek or something, need to be quite open and honest, like, hey, the data you're looking today describes that XYZ.
- 19:49Adele Kurki: And you can like again speak the language, but also be honest.
- 19:54Adele Kurki: Okay, it means if it's sourced, they can the system XYZ can be two years ago, three years ago.
- 20:02Adele Kurki: Now, if they convert it, there might have been actions X, Y, Z happening in between.
- 20:08Adele Kurki: On this other bill, like other window when we are looking at, okay, it was tipped over, or can like, hey, the opportunities process started from this marketing action.
- 20:17Adele Kurki: It it tells a very different story if it was like that.
- 20:20Adele Kurki: Three years sourced, can be from marketing, tipped by sales, or hey, sourced by sales, tipped by marketing.
- 20:26Adele Kurki: Which one do you want to have?
- 20:28Michael Hartmann: Yeah, so I think uh we could we could spend all and we probably have before spent a whole conversation on just that kind of topic.
- 20:35Michael Hartmann: And it's just I think it's I like to reinforce that because I think I still think there's a lot of people who um are are being held accountable to a level of quality on data that is, I think, unreasonable for most marketing and sales teams.
- 20:52Michael Hartmann: Even the ones who have a focus on data quality.
- 20:56Michael Hartmann: It's just it's just the nature of it.
- 20:59Adele Kurki: Yeah, and I think in in any ways, like you aim to keep it as clean as possible.
- 21:04Adele Kurki: Um, especially in the times of like automation at AI.
- 21:08Adele Kurki: You want to be as directional, as good as possible.
- 21:11Adele Kurki: You want to provide those different visibilities or different life cycles.
- 21:15Adele Kurki: But it's good to be realistic.
- 21:17Michael Hartmann: Yeah.
- 21:18Michael Hartmann: Well, and the other part that I always tell people like when I coach people are gonna be, whether they've been on my team or I do, you know, independent coaching, who are being asked to do reporting, right?
- 21:29Michael Hartmann: If you uh if you see something, like you should be keenly aware to look for things that don't match a pattern.
- 21:36Michael Hartmann: Because I guarantee you someone will ask the question if you just throw these numbers or charts up.
- 21:41Michael Hartmann: And you need to be prepared to answer the question of why does it say that?
- 21:44Michael Hartmann: It doesn't mean you have to have like it doesn't mean it has to you change it or fix it, right?
- 21:50Michael Hartmann: But you go for me, like hey, I give you an example, right?
- 21:55Michael Hartmann: Uh started seeing we first launched Marketo, but we started tracking attribution and we started seeing influence on opportunities that were created well before we launched.
- 22:05Michael Hartmann: And I'm like, I don't know what's going on here.
- 22:07Michael Hartmann: Like, so I had to go figure out why, because even though I don't that didn't make any sense, right?
- 22:12Michael Hartmann: Yeah, there's a logical reason why I was able to explain it, but I think that like that's the other part, right?
- 22:18Michael Hartmann: So don't just go like, oh well, the data just can't be good.
- 22:22Michael Hartmann: You should yes, you should try to.
- 22:23Michael Hartmann: Make it as good as possible for automation, AI, all those things.
- 22:26Michael Hartmann: And also be prepared to answer when things aren't correct or don't look correct, right?
- 22:33Michael Hartmann: Because for the people who aren't familiar with it, they won't get it.
- 22:35Michael Hartmann: All right, I'll get off my eye horse there.
- 22:38Michael Hartmann: Um okay, so let's get into this the topic of you got these big projects, but you like said, like we still have to keep the machine running, right, if you will.
- 24:02Michael Hartmann: Um how do you think about balancing those two, like run the business, like we keep referring to it, run the business, change the business in a practical day-to-day sense.
- 24:13Michael Hartmann: Like, what do you how do you think about that?
- 24:17Adele Kurki: Well, honestly, when we have well, first of all, I believe in something called like 80-20 or 70-30 type of a modeling that you have constantly elements that are like supporting short, mid, and long-term growth.
- 24:38Adele Kurki: And practically that means that okay, you have this day-to-day, so we keep the business running, fine.
- 24:44Adele Kurki: But we have always development projects on the side that support like mid and long-term, longer term um elements.
- 24:51Adele Kurki: Now, there is of course different sizes of fires.
- 24:55Adele Kurki: Let's say that we have um decided that okay, one of these growth uh projects will take place, let's say this lifecycle um project.
- 25:03Adele Kurki: We plan.
- 25:05Adele Kurki: We plan so that we have uh that in our roadmaps uh from the very start.
- 25:11Adele Kurki: And we plan it in a timeline that makes well always is ambitious, but it's still making sense, so that we have the capacity to run um the day-to-day.
- 25:23Adele Kurki: Obviously, if you and all the operation teams have always a huge backlog, you need to be just able to prioritize.
- 25:32Adele Kurki: This is always there, and then from the fires, you have, for instance, 70% or 50% of your week, depending a little bit, dedicated for those.
- 25:42Adele Kurki: You do the prioritization inside that time that you have available.
- 25:45Adele Kurki: Yeah.
- 25:46Adele Kurki: So you have just like different buckets of time that are dedicated for different swim lanes, and you prioritize inside those what makes sense.
- 25:55Adele Kurki: Um in these projects, the good and easy thing is that you have you have to provide already to the top, like to the top level or to the leadership, some sort of roadmap, and you want to proactively update uh the organization about changes or expectation setting that hey, again, you have to over-communicate.
- 26:15Adele Kurki: First of April, the change will be there, the change will like mean this and this, and then you can like track from there like what needs to happen at what deadline, and that's like already set, it's predictable.
- 26:28Adele Kurki: It's in your operational roadmap, so your team knows exactly what's happened, so they can focus only on uh on that.
- 26:34Adele Kurki: The challenge, I think the real challenge is that when something else happens on top of that.
- 26:41Michael Hartmann: Something unexpected.
- 26:42Adele Kurki: So something unexpected.
- 26:44Adele Kurki: Let's say we changed a sales motion, which actually happened.
- 26:49Adele Kurki: Uh, or we change a team, or we change, you know, a structure, or something like that.
- 26:56Michael Hartmann: Which creates an integration that you can, you know, yeah.
- 27:01Adele Kurki: Something something random, which um which requires some time somewhere.
- 27:07Michael Hartmann: Yeah.
- 27:08Adele Kurki: And um then it's really good to go back to a team, like, hey, okay, this is still our roadmap, and we still want to ensure that we don't just drop everything and fix something as urgent, but have that long-term vision at the same time.
- 27:27Adele Kurki: Yeah.
- 27:27Adele Kurki: Which is kind of like a little bit sometimes like, oh, but but but this is like really urgent, like we need to fix this fire.
- 27:33Adele Kurki: But if we fix every single fire immediately, we'll never stop firefighting.
- 27:40Adele Kurki: And this function needs to look like longer term to the horizon, like, okay, what this business needs tomorrow.
- 27:49Adele Kurki: And for that reason, we kept even we had this organizational change, for instance, we kept this long-term process.
- 27:55Adele Kurki: We keep, we make sure that this swim lane is not touched.
- 27:59Adele Kurki: Then we have all the operational tasks or admin stuff.
- 28:04Adele Kurki: Okay, what can we change there to ensure that this urgent fire, for instance, is fixed.
- 28:09Adele Kurki: In our case, it was actually um we had to change, or we moved out of one sales sales team, which happened to be the sales team we were handing over our leads.
- 28:22Adele Kurki: So we need to figure out like, oh, okay, well, let's figure out like um a new way of routing and figuring out when and how we do handover leads, and what do we kind of like hand over for marketing, for instance.
- 28:33Adele Kurki: Um, so that's that's a little bit of a fire, but anyways, it's something that we can solve, like peace of mind, let's focus on figuring it out.
- 28:42Adele Kurki: SAP, let's say we have three days, and the team or the resources or the hours that we are focusing on building this long term, they continue.
- 28:51Adele Kurki: We need it still tomorrow.
- 28:53Michael Hartmann: Yeah.
- 28:53Michael Hartmann: So we have a deadline.
- 28:55Michael Hartmann: So in my so when I've led teams, I'm with you, right?
- 28:59Michael Hartmann: And and sometimes it's I'm not sure early in my career I would have had the enough breadth of knowledge and experience to be able to, in the moment on the fly, evaluate is this something that really needs to be addressed now, or you know, you know, can we solve an immediate problem and then the bigger long longer term fix?
- 29:19Michael Hartmann: How how do you because the reason I bring this up is I I've also had teams come to me where I go, something's come in unexpected, we all have to jump, and then um they get frustrated over one of two, sometimes both things, right?
- 29:33Michael Hartmann: One is, you know, why is this all like how does this keep happening, right?
- 29:38Michael Hartmann: Why are we getting these fire drills?
- 29:41Michael Hartmann: How can we stop that?
- 29:42Michael Hartmann: The other is I've committed to a longer-term project, and now this is impacting my ability to execute.
- 29:47Michael Hartmann: How do I, you know, what's good because then it becomes a reflection on them.
- 29:51Michael Hartmann: It may have an impact on their compensation, but how do how do you I I I guess I've kind of I don't even know that I've written it down.
- 29:58Michael Hartmann: I guess I have a little bit of a mental model about how I think about the prioritization and that kind of stuff happens and how to evaluate it, but what's your take?
- 30:07Adele Kurki: Well, of course, it comes back to then what is the like what is the fire?
- 30:13Adele Kurki: Um I always go back in my chair because always when you are like everything is urgent, everything's fire, it actually means that you need to calm down.
- 30:23Adele Kurki: Yeah.
- 30:23Adele Kurki: Um what is the actual business impact?
- 30:27Adele Kurki: Uh, who is driving it?
- 30:29Adele Kurki: Is this urgency for a person, for a certain team, or is it actually like a business-wide impact?
- 30:37Adele Kurki: And if you were to create or solve the problem from the scratch, sometimes you don't have you to are given like, oh, this is urgent, you need to do this.
- 30:47Adele Kurki: I always challenge my team to really think like, okay, what is the problem we solve?
- 30:52Adele Kurki: Okay, if we decide that this is, you know, this has actually quite a big business impact, what is the best way to solve it?
- 31:00Adele Kurki: Okay.
- 31:00Adele Kurki: Uh what is the sufficient way?
- 31:02Adele Kurki: It doesn't have to be perfect, especially if it's like uh a short term, like, okay, hey, actually, we need to just like preach it through how much time we dedicate for it compared to the other things that are on our table.
- 31:16Michael Hartmann: Yeah.
- 31:17Adele Kurki: So that's that's where we are coming um usually.
- 31:21Michael Hartmann: Yeah, I think I I think about it.
- 31:24Michael Hartmann: We'll take a like a system down kind of issue or a break-in integration, something like that.
- 31:32Michael Hartmann: I think what what gets mixed together sometimes is uh not only we've got to immediately fix that, and at the same time we have to figure out why it happened.
- 31:41Michael Hartmann: And one of the simple things I try to do is like separate that.
- 31:44Michael Hartmann: Let's solve the immediate problem, then let's go fix separately in a in a less you know urgent thing.
- 31:52Michael Hartmann: Let's go try to understand how that happened and how can we minimize the chance it happens again.
- 31:56Adele Kurki: Yeah.
- 31:56Michael Hartmann: Right.
- 31:57Adele Kurki: Absolutely.
- 31:57Adele Kurki: Uh, of course, in in all these roles, it's really important to understand the root cause, because otherwise it it can be it can be sometimes actually wider, like oops, uh, luckily the like result was this small fire, because it could have been massive something else.
- 32:12Adele Kurki: Um so definitely that's that's really important.
- 32:16Adele Kurki: And that's actually something that we expect quite proactively, also.
- 32:20Adele Kurki: If you know it's something it's really good to check if it's if it doesn't require too much to just like deep dive or like check what is the root cause, even if we wouldn't fix that fire immediately.
- 32:32Michael Hartmann: Yeah, so another um I think we've hinted at this a little bit.
- 32:35Michael Hartmann: There's this idea of, I think you even used the word transparency at one point.
- 32:39Michael Hartmann: Like how um and communication, like how important is it, do you think, for marketing apps teams to be both transparent about the capacity, what's on the roadmap, and communicating that well, um, as opposed to um kind of holding back and just focus like I mean it's it becomes easy to be discounted and focus just focus on the the urgent things that are right in front of you.
- 33:08Adele Kurki: Well, honestly, honestly, and what we're trying to do here is that you as a marketing operations leader and you as a marketing operations team want to be a strategic partner instead of you know help desk or ticket mastering function.
- 33:31Adele Kurki: And the first thing in order to change that, especially if you are in the situation that you figure out, like, ah, oops, you're listening to this and you're like, ah, well, my Jira is full and it's actually like everyday fire only.
- 33:44Michael Hartmann: Yeah.
- 33:45Adele Kurki: How you start doing the change is to bring this transparency.
- 33:48Adele Kurki: What is the function doing?
- 33:49Adele Kurki: Honestly, it seems to be very cryptic sometimes and really hard to understand.
- 33:55Adele Kurki: But bringing it visible is really important.
- 33:59Adele Kurki: And how do you do it is to first bring, like, okay, this is my roadmap.
- 34:04Adele Kurki: This is kind of like the first level of expectations.
- 34:07Adele Kurki: I think these are expected to happen.
- 34:09Adele Kurki: I am committing to these things, and my team is committed to these things, and also sometimes this is why we are not able to deliver everything that you're bringing to our backlog.
- 34:19Adele Kurki: And we have to practice no.
- 34:21Adele Kurki: Um, when we are thinking about the transparency, it's these communication elements, this human to human, which need to happen in like manager to manager, manager to organization, team to organization.
- 34:36Adele Kurki: Your team has to understand also the roadmap.
- 34:40Adele Kurki: Why did we choose these elements?
- 34:41Adele Kurki: Why are they important?
- 34:43Adele Kurki: You are okay to say no if things are not part of the roadmap.
- 34:49Adele Kurki: And also, this roadmap lives.
- 34:51Adele Kurki: Yeah.
- 34:51Adele Kurki: Like if we have these uh fires, like we are all all okay to drop also something as long as we communicate to the stakeholders and the organization what's happening.
- 35:03Adele Kurki: Um, another interesting thing which I find more like more and more important, especially for roles that are working in very like operative level, where it is sometimes hard.
- 35:16Adele Kurki: Like, hey, I'm actually doing only admin work.
- 35:18Adele Kurki: Like my job is to ensure that you know everything goes fine and it's invisible.
- 35:23Adele Kurki: Um, is to plan together how can we bring this visibility to those roles.
- 35:29Adele Kurki: Um, is it then kind of like bringing them to the kind of like function meetings or like find the cross partners, but also technical transparency.
- 35:38Adele Kurki: Ensure that everything that is done is hey, this is visible to sales, yeah.
- 35:43Adele Kurki: This is visible to the product.
- 35:45Adele Kurki: We are actually connecting the dots.
- 35:47Adele Kurki: Um that is really, really important that it's not only about these humans and the text and their being in the meetings, it's also they're visible in the technical execution.
- 35:56Adele Kurki: Who did what?
- 35:57Adele Kurki: Everything is transparent.
- 35:59Michael Hartmann: I I love that you brought up the idea of being transparent if you're a leader, being transparent with your team.
- 36:03Michael Hartmann: Because I think it's a mistake I made probably early in my career as a as a people leader, and I see others do, is they try to in the in the name of trying to shield their team from the politics or whatever, they they don't address the questions the team will have, like if things start shifting, you know, we've got this roadmap, but we're getting into you know, we're in getting like how like it's really important for me at least.
- 36:33Michael Hartmann: I want a culture where I'm like I'm gonna share as much as I can, right?
- 36:37Michael Hartmann: And I you know, be honest when I can't about stuff.
- 36:40Michael Hartmann: Yeah, because I think it's um that if if you don't do that, people start to ask questions about why did direction go this way or that way, what's my role, right?
- 36:54Michael Hartmann: Am I able to push back all those kinds of things?
- 36:57Michael Hartmann: Um, because what I've had I've had to do literally at times is like do I just sort of describe those situations, right?
- 37:03Michael Hartmann: We had a roadmap, big project stuff we're working on, and something came up and it sidetracked us for a longer time than we had hoped, and it was gonna impact that timeline for the the big project.
- 37:14Michael Hartmann: And I've had to say, like, this is why, especially if it was me, like I made the decision that we had to do that.
- 37:22Michael Hartmann: Like, I will be like, I'm gonna own that, right?
- 37:25Michael Hartmann: I'm not gonna hold you accountable for change, right?
- 37:29Michael Hartmann: As long as you were doing things as appropriate.
- 37:32Michael Hartmann: But I think I I I would be as transparent as I could about the why.
- 37:38Adele Kurki: Absolutely.
- 37:39Adele Kurki: And especially if you want your team to be also a proactive problem solver, if you want them to, you know, feel comfortable on bringing like, hey, I know it is anonymous, like something off, or you want them to solve independently and grow and keep the curiosity and something.
- 37:57Adele Kurki: In order for them to solve the business problems, they need to understand what's happening in the business.
- 38:03Adele Kurki: It's uh being the transparent on what's happening, yeah, why things are happening, why things are not happening.
- 38:10Adele Kurki: Um, and then also building that business acumen constantly.
- 38:15Adele Kurki: Like this is the way the business works in our industry, in our car, like, you know, type of a business, um, so that they can work independently, especially when you're working in global companies, because then there is this time zone things and different stakeholders you want that your team is speaking the same language because nothing is more uncomfortable that everybody are a little bit confused.
- 38:39Michael Hartmann: Yes.
- 38:40Michael Hartmann: Yeah.
- 38:41Adele Kurki: And and you are then kind of like the operational center which is supposed to tell the truth.
- 38:45Adele Kurki: Yeah.
- 38:45Michael Hartmann: Well, and worse, no, everyone thinks they're on the same page, but they're actually not.
- 38:50Adele Kurki: Oh, yeah.
- 38:50Adele Kurki: And that's that's the worst.
- 38:52Adele Kurki: And that's why uh these kind of like frameworks, especially in global environments, works well.
- 38:56Adele Kurki: Like, okay, roadmap, always up to date.
- 38:59Adele Kurki: Better if it's living somewhere, um, also as some kind of like living element such as Jira.
- 39:04Michael Hartmann: Yeah.
- 39:05Adele Kurki: In Epics, you can put epic, like epics for development projects.
- 39:09Adele Kurki: Here we go.
- 39:12Adele Kurki: But it actually kind of like creates some sort of transparency and living elements in a way, which helps also stakeholders then to go independently, let's say in Apex time zone to review, like, okay, hey, how was my project?
- 39:25Adele Kurki: Or I think I did drop a ball.
- 39:27Adele Kurki: What is the status of it?
- 39:29Michael Hartmann: Right, yeah, yeah.
- 39:30Adele Kurki: Type of a thing.
- 39:31Michael Hartmann: Yeah, so you hinted at agile stuff, and I feel like we have I'm trying to remember, like, this is the downside of not having talked to you in so long, but uh I think maybe we had a slightly different uh opinion or point of view about where agile fits in and where it doesn't.
- 39:47Michael Hartmann: Because I to me it feels like it works really well, generally speaking, for like the the regular recurring repeatable stuff, tickets, if you will, and maybe on some projects stuff.
- 40:01Michael Hartmann: Oh, there feels like there I also like personally I think there's work that doesn't really match that.
- 40:06Michael Hartmann: Like, which how do you do you guys use agile for what you do?
- 40:10Michael Hartmann: Is it like universal?
- 40:11Michael Hartmann: What do you like?
- 40:12Michael Hartmann: How do you think about it?
- 40:14Adele Kurki: Well, I think we don't like use the official agile uh framework that's it.
- 40:19Adele Kurki: But we have like agile elements.
- 40:22Adele Kurki: Right.
- 40:23Adele Kurki: Um, I do like frameworks.
- 40:24Adele Kurki: I think it's kind of like for every operational person at some moment of time, you have to certain level of control freakness.
- 40:32Adele Kurki: Um, but we, for instance, work on on targets and uh roadmaps and Jiraports to ensure that we have a certain level of execution and technical um transparency, meaning now technical with not in the systems, but in this kind of like ticketing system to have um documented communications and stakeholder management and then this global visibility.
- 40:54Adele Kurki: Um we loop that back to our kind of like living roadmap.
- 40:58Adele Kurki: So we have you know the classic um document that you can showcase in different environments and share, but then we also try to keep it livable and actionable in Jira uh in visual manner so that we can also track hey, are our sprints actually supporting us to finish our goals?
- 41:19Adele Kurki: Do we see blockers?
- 41:20Adele Kurki: Should we re-adjust?
- 41:21Adele Kurki: Were we too ambitious or too like less ambitious that we wanted?
- 41:26Adele Kurki: Um so for that, the agile works.
- 41:28Adele Kurki: Maybe the other, like that's maybe the less agile part as such.
- 41:33Adele Kurki: Um, but it is a tool that helps us to monitor and understand in two weeks' prints if we're going to the right direction, and that we are like all controlling our deliveries.
- 41:47Adele Kurki: Yeah.
- 41:47Adele Kurki: Um, I said it is really easy to go to the firefighting mode.
- 41:51Adele Kurki: Uh, the other thing that we already touch based is this um percentage like, okay, in moments of crisis, you might have 50-50 development firefighting, 70-30.
- 42:02Adele Kurki: You know, have this percentage conversation, like, hey, this week, where are you focusing today?
- 42:08Adele Kurki: What are your key priorities in these swim lanes?
- 42:10Adele Kurki: Okay, we have a special week coming ahead.
- 42:13Adele Kurki: Yeah, we might need to change a little bit.
- 42:15Adele Kurki: Yeah, yeah.
- 42:16Michael Hartmann: Well, and that gets, I mean, I I think that's a really good, like I want I want people listening or watching to miss this, right?
- 42:23Michael Hartmann: This idea, like the goal is 80-20, 70-30, split between run the business, change the business, or whatever that number is.
- 42:31Michael Hartmann: But that's a goal, like any given week, right?
- 42:34Michael Hartmann: You may have to adjust because you've got a time-sensitive campaign or event, or someone's gonna be on vacation, right?
- 42:44Michael Hartmann: And so that you have to be something breaks adaptable to shift, right?
- 42:48Michael Hartmann: Yeah, something breaks.
- 42:50Michael Hartmann: Um, so it's interesting because as I was thinking about you talking about agile, um, because I like so total transparency.
- 42:58Michael Hartmann: I'm I'm I've used lots of different methodologies, I've built methodologies, and I understand conceptually, I like the idea of agile.
- 43:07Michael Hartmann: Um, but I find with almost all methodologies is that people are super hard at core advocates.
- 43:13Michael Hartmann: Generally, there's a lot of them who use it as a very rigid structure as opposed to a tool to help them, right?
- 43:19Michael Hartmann: And taking advantage of the things that make sense and don't make sense for a given thing.
- 43:23Michael Hartmann: That's probably my biggest, but also I just I was it just hit me as you were just talking about because you brought up Jira.
- 43:28Michael Hartmann: And I think I what I try in the really hard to separate the tool that you're using for it from the methodology.
- 43:36Michael Hartmann: And I think I've used Jira, I've used several other project management tools, and I am a believer in having that, right?
- 43:43Michael Hartmann: Because I think to your point, like one of the things it helps you uncover if you don't already have a way of doing is the the two important things to understand what you can actually deliver, which is how much work is coming at you or you have on your team's plate, and how much capacity do you actually have that still allows for maybe a little bit of development time, time off, whether it's sick, vacation, holiday, whatever.
- 44:09Michael Hartmann: Um, and if you if you don't have a way of doing that, you're gonna be you're gonna get yourself in a lot of trouble because you just take especially if you're not comfortable pushing back, go like you're just gonna say keep saying yes, because I think a lot of people in ops um want to want to help.
- 44:29Michael Hartmann: You know, absolutely, and it's hard to say no.
- 44:35Adele Kurki: And something that you want to be mindful, like I think there are two additional elements why I like keeping this kind of ticketing system, whatever it is, like asana van de blah blah.
- 44:45Adele Kurki: Um first is actually you get really good data on enablement needs.
- 44:50Adele Kurki: There are a ton of tickets that come like actually these guys that just don't know how to do their work.
- 44:56Adele Kurki: Like, this is not a bob's task.
- 44:58Adele Kurki: Or hey, we actually see a pattern that we for some reason none of the team or we didn't have a flagging system, there is a buck somewhere.
- 45:08Adele Kurki: This is actually something that shows that there is a buck.
- 45:12Michael Hartmann: Yeah, yeah, yeah.
- 45:14Adele Kurki: Um the other thing that helps is that yeah, the other thing is that if you have a global team, you and also like the bigger the team, um at some moment of time when you have all these stakeholders all around the world, it might be really hard to understand what is actually.
- 45:34Adele Kurki: Actually, the workloads that come to the team.
- 45:37Adele Kurki: And especially if you have a lot of ambitious junior roles, as you mentioned about this kind of like people pleasing, if I translate it that way.
- 45:47Adele Kurki: Yeah.
- 45:48Adele Kurki: It you don't want to burn them out.
- 45:51Adele Kurki: You want to ensure that the curiosity is there, the coachability is there, the mind is sharp.
- 45:58Adele Kurki: And you're providing the growth by walking through, for instance, time to time, these conversations on like, not only on the sprints, but for instance, in your one-to-one, like, hey, actually, like we saw these tickets coming, like, ignore.
- 46:13Adele Kurki: We'll solve them.
- 46:14Adele Kurki: Or we kind of like, or hey, your workload has increased uh 25%.
- 46:21Adele Kurki: Let's open it up.
- 46:22Adele Kurki: What is kind of like making it busy?
- 46:24Adele Kurki: Okay, is it hindering your development targets?
- 46:27Adele Kurki: Um you know, or there's the hidden cue.
- 46:34Michael Hartmann: Yeah.
- 46:37Adele Kurki: Yeah, exactly.
- 46:38Adele Kurki: So it it it works kind of like it works really well as a tool um also for these kind of purposes.
- 46:46Michael Hartmann: Yeah, so like you're hinting at maybe this is where we can wrap up, is you're hinting at using that as a tool to help with um development and growth for teams, right?
- 46:57Michael Hartmann: Absolutely.
- 46:58Michael Hartmann: So do you like how do you think about that?
- 47:02Michael Hartmann: Like, how important is that to you?
- 47:05Adele Kurki: Um well, the the growth in general, if we if we jump to that direction, um all operational roles are quite high demanding.
- 47:15Adele Kurki: Like it's not that easy any like anymore to enter to the roles because it's not like I'm afraid, right?
- 47:23Adele Kurki: Exactly.
- 47:24Adele Kurki: Uh and it can be very overwhelming because all like you have a bunch of stakeholders, especially when coming into these international companies, like you have all the stakeholders, they're demanding hundreds of millions of stuff, they don't even know what they're demanding.
- 47:37Adele Kurki: And uh you then try to figure out, first of all, like run and understand what are the new ways of doing things, what is the smartest way of doing things?
- 47:51Adele Kurki: Okay, there are no benchmarks.
- 47:53Adele Kurki: How can I be smart at solving this problem in scale?
- 47:57Adele Kurki: And for that reason, you need to be able to keep that curiosity, that kind of like space for thinking straight, um, and actually solve the problem the stakeholder couldn't even ask.
- 48:09Adele Kurki: And better if you are able to solve it before.
- 48:12Adele Kurki: So, for that reason, I really, really, really want to invest in growing, mentoring, supporting uh the team members, both expanding their, you know, technical ability and keeps the space to learn, but especially keep their you know headspace healthy.
- 48:32Adele Kurki: Yeah, and it's so easy.
- 48:33Adele Kurki: Whenever it is in my powers, of course.
- 48:35Michael Hartmann: Yeah, right, right.
- 48:36Michael Hartmann: Well, and also, I mean, the the one thing I would add if I was in your sh to your statement is at some point that's the person's responsibility to take advantage of it.
- 48:47Michael Hartmann: Like you can create you can create the space and time, but you can't make them do it, and if they choose not to, that's on them.
- 48:56Adele Kurki: Yeah, absolutely.
- 48:57Adele Kurki: But I think it's it's really important to be able to build that space and protect the space.
- 49:03Adele Kurki: Is it then transparency, the systems, the roadmaps, yeah, especially in moments of change when it is overwhelming in multiple fronts, um and especially if you're in in more junior roles?
- 49:18Michael Hartmann: Yeah.
- 49:18Michael Hartmann: I mean, I I I've had people on teams who I remember one who was pursuing an MBA, and I just we just we we were very honest and direct with each other, you know, about how that would look, you know, and what commitments we still had to make um on the occasion when that person needed to leave early or you know, do a tr, you know, some sort of project or whatever.
- 49:44Michael Hartmann: We just we worked it out.
- 49:45Michael Hartmann: And but I think it ultimately um it benefited that person and it benefited the organization for that person.
- 49:55Michael Hartmann: Like so giving them the ability, they became more loyal, they were like willing to put in extra work and um all these things, so and did was good at what uh at the work.
- 50:07Michael Hartmann: So anyway, um we've covered a lot of ground here, Adele.
- 50:12Adele Kurki: Yeah, absolutely.
- 50:13Adele Kurki: Thank you for a great conversation.
- 50:15Michael Hartmann: That's great.
- 50:16Michael Hartmann: Um, so if people want to continue maybe one of these threads or something, or follow what you're you're doing, what's the best way for them to do that?
- 50:24Adele Kurki: Well, I'm in LinkedIn.
- 50:25Adele Kurki: Uh, so you can find with me, you can find me with my name, so Adele Kurki.
- 50:31Adele Kurki: Um, feel free to reach out.
- 50:33Adele Kurki: I'm super, super happy to continue the conversation on any of these topics we cover it today, these calls.
- 50:39Michael Hartmann: Yeah, we've we we did cover a lot of ground.
- 50:41Michael Hartmann: We hoped hopscotched a bit.
- 50:43Michael Hartmann: Well, Adele, thank you so much for joining, especially late.
- 50:46Michael Hartmann: I do know I it's not easy.
- 50:48Michael Hartmann: I appreciate that.
- 50:48Michael Hartmann: So thank you.
- 50:50Michael Hartmann: Uh thanks to our uh listeners and supporters and audience out there.
- 50:54Michael Hartmann: We always appreciate that.
- 50:56Michael Hartmann: Um, if you have ideas for topics or guests, or want to be a guest, do like Adele did and reach out, and we'd be happy to get the ball rolling.
- 51:03Michael Hartmann: Till next time.
- 51:04Michael Hartmann: Bye, everybody.
- 51:05Michael Hartmann: Bye.