Share this article:

Podcast | Chief Human Experience Officer, Workhuman: How employees are shaping AI adoption

KeyAnna Schmiedl, chief human experience officer at Workhuman

Workhuman’s approach to AI has given employees room to experiment, learn and develop solutions to the problems they encounter every day, from handling customer calls to managing executive travel.

Through hackathons and access to training, the company has encouraged people across the business to help design new tools. KeyAnna Schmiedl, Chief Human Experience Officer at Workhuman, shares how that approach has produced AI agents that bring customer information together before a call, support preparation for speaking engagements and help reuse flight credits, while giving employees a voice in how their work changes.

She also explores balancing shared values with local customs across US and European teams, using employee recognition to uncover contributions and potential workload pressures, and creating career opportunities that extend beyond promotion. Throughout the conversation, Schmiedl explains why people leaders need to remain curious and seek ideas from across the organization.

Host: Hello, everyone, and welcome back to another episode of the HR Grapevine US podcast. I'm your host, Benedict Evans, community engagement manager here at HR Grapevine, and I'm really pleased to be joined today by KeyAnna Schmiedl, Chief Human Experience Officer at Workhuman. KeyAnna looks after the people strategy. At Workhuman. So that's everything from talent and total rewards to learning and development culture, employee experience. Uh, before joining Workhuman, she was VP of Social and Environmental Impact at Mozilla and Global Head of Culture and Inclusion at Wayfair. So she's seen the people function from a lot of different angles. Today, we're going to be diving into what it really looks like to lead a people team across a business of more than a thousand people, with teams spread across the US and Europe. And I think that's something a lot of our listeners will be able to relate to as expectations around work can look pretty different from one side of the Atlantic to the other. AI, of course, is changing the way that we all do our jobs, and plenty of employees across the board are saying that work maybe just doesn't feel quite like it used to. So we'll be chatting about how you can successfully build one culture spread across different countries, how you integrate AI into the business without losing trust, how you keep a real sense of how people are feeling, and how you make sure everyone has a voice, whether they're in an office, on the frontline or working on the other side of the world. KeyAnna, a really warm welcome to the podcast and thank you so much for joining us.

Guest: Thank you so much for having me. I'm excited for the conversation.

Host: Absolutely. I'll dive straight into it. It really is big topic or the main point that I wanted to hit with you was how do you run a people function across, you know, two continents? What do you standardize globally and what do you leave local and how do you strike that balance?

Guest: Yeah, I think listen for us, there are some what's that are non-negotiable. Like the way that people get treated. The shared values across our company. The idea of what good leadership looks like, what good people management looks like, what good colleagueship looks like, right? Like you want to have the sense of no matter where you're at in the world, if you walk into a space that is supposed to be curated by Workhuman, that you know exactly where you are, while at the same time saying, and then there may be some house, right? Some house around local customs that make it feel slightly different, but also in that way authentic to exactly where you're experiencing Workhuman. So that's the big thing for us is to try not to over script too much, try to have a ton of trust, and to just agree on some of the simple basics and then to say, and if you find something else that works, great, but then share that back, right? So we also don't want it to feel like one culture dominates the other that all of the ways that the US works gets exported to, say, Ireland or the UK or anything like that, we want to make sure that there's a good mix of what are the things that we're learning in real time and sharing back to create more of that holistic global culture. And what are the things that we're okay with saying? Yes, that is absolutely a custom there. And that's great. It's not a custom here, and that works as well.

Host: I'd be really interested to know if you've had any, for lack of a better term, culture clashes in how you've dealt with those.

Guest: I think one of the examples I'll give you is maybe a bit counterintuitive. However, I think it has a lot of benefit and that is the culture around holidays in Europe is very different than the vacation culture here in the US. And so, you know, for people who are first experiencing that and going, well, you're taking two weeks off. Like we have this project. I actually think it's been a really good example of importing a culture to the US, or exporting a culture from Europe that normalizes. No, I've got time. I'm taking it off. I'm letting you know ahead of time that I'll be away and I plan to be offline unless it is truly an emergency. I think there are some things about us kind of hustle culture that has wormed its way into the way. The best way to do great work is to be on all the time, and that is completely unhealthy. And so being able to see our European colleagues take time unapologetically has helped us to say over here, look, if you're off, be off, and we should be able to respect that. And if we can't, then we need to understand what it is about the way that we do things around here that is impeding on your ability to be away.

Host: I would also like to ask you a little bit about sort of pulling back slightly from a more international perspective, a governance perspective as well, and ask about the challenges that come in handling things like the EU Pay transparency directive. And there's also there's a, you know, there's a sort of patchwork statewide of US rules. How what's your approach for that? How are you, how are you handling the, the emergence of these, you know, not necessarily punitive legislations, but very firm legislations, you know, as a sort of international organization.

Guest: Well, I think in a couple of different ways. The first is that, you know, where there is the most detail necessary. So in the instance of the EU pay directive, then that becomes our new baseline, right? So in the US there's the gender pay gap, but it's not as specific as the EU pay directive. One of the things that we do is we say, okay, then we're going to meet the baseline of the EU pay directive and we're going to try to do that globally, right? So everywhere that we're located and not just say we're only going to do it in the EU, and then we're not going to pay attention to the same level of requirement in the US. I think the challenge is in how this work is understood and how to translate what actually what good looks like and what is actually a negative. So one of the, the challenges that have always existed, even here in the US is this idea of reporting the gender pay gap, like it's a pay equity gap. So pay equity says, are you being paid appropriately for the skills that you have and doing the same job? The gender pay gap says regardless of your gender, are you being paid the same for doing the same work? And so in conflating those two things, it can lead to a lot of confusion around, well, are you saying that then women are not fairly paid? No, that's not what we're saying. But also when you report out in the aggregate, it could be that, you know, for instance, most of our engineering resources are located in Ireland. And so for us, the challenge is, well, like many other tech organizations, the majority of the people who make up the tick population happen to be men. And so in that way, it's yes, women that are in that space, they are paid equally to the men who are doing the same work. But because there are fewer of them, it creates this illusion that we have a pay gap. And that's not exactly right. So I think what what has happened for us is learning the importance of helping people to understand what do these numbers actually mean? What is the story that it's telling? And not in a way to try to make us look better if we have some gaps that we need to fill, but in a way to then be able to say, so here's what we're doing to proactively address these things, and here are some of the challenges that are going to be more long term. So for instance, you know, more women in engineering, especially when you're competing with larger tech organizations, well, that means that, you know, maybe we need to invest more heavily in entry level talent and internships and things like that. So it's how can you get creative to solve some of these challenges that are not unique to our business? But then on the flip side, when you look at the US, it's so many of the leaders in the US of key departments are women. And so from a global perspective, we balance out quite nicely. But individual jurisdictions, it might tell a slightly different story.

Host: It's interesting. It seems that there's a sort of a slight patchwork. You maybe have to take a slight patchwork approach in terms of communicating that. And I would I would like to know how, what you see as sort of best practice in helping people figure, figure it out almost for themselves with a, with a, with a gentle push, as it were. Like, what's your approach to that?

Guest: I think it's every year restating what are the definitions of these things? Right. Again, pay equality and pay equity are not the same thing. The gender pay gap focuses on pay equality. I'm paying the same for the same work, regardless of gender. Whereas pay equity says based on your skill and your level, you're paid fairly. So every year, just reiterating that to help folks to understand and then being as transparent as humanly possible about the information that we have and about where we have work to do, but also the places where we're actually really proud of the numbers and making sure that that's a globally understood story and then locally saying, okay, so now these are the projects, the tasks, the opportunities that we have based on what it looks like here and what the experience is in this locale. So to your point around the patchwork, yes, you eventually want to be able to talk locally, but you want to make sure that globally baseline information is understood in exactly the same way.

Host: I'm going to go off on a slight tangent here in terms of the questioning, but okay. What kind of leader do you think yourself to be, and do you. Would you position yourself, perhaps as part of a. Like a new generation of HR leadership in approaching the role?

Guest: I think just by nature of the generation that I fall into. My default answer is yes, but also I think what I have learned over the years is, I mean, it's even in my email signature, I'm a creative pragmatist, right? So I am excited by new ideas, by a person who has a better answer than I could have ever come up with on my own. And at the same time, to be able to say, okay, what is the best way for us to get that done? And do we actually have to break it into pieces and say, this year, this is what we want to accomplish on the way to this ultimate end goal? And I think in that way, what makes maybe me in this new generation that you're talking about unique, is that we do not expect that we will be the ones with all of the answers, or even in some cases, the best answers, but rather I see myself as the person who should know who is going to be the right person, or the right people in the right roles to get us to that best answer. And how do I make sure that they are able to share their collective wisdom in a way that it gets heard and that we are able to? I don't want to say take advantage, but we're able to appreciate that and put it into practice. Right. So even if it doesn't come from me personally, if it comes from members of my team, I want to make sure that they get the credit for it. But also it is my responsibility to then bring that up to my peer set in in the C-suite. Right. And so I think it's just in the sense of remaining curious, being thoughtful, not careful. And so what that means is really focusing on that sounds like a great idea. Let's try it and see what we learn and then iterate and improve from there as opposed to, yep, we need to make sure that this is the best idea. And then we implement this as if our life depends on it, and if it fails, then we're all screwed. Like that's not the mindset that I have. Um, and I think that can't be the mindset, especially in the time that we're in right now, because everything changes so rapidly. There's a new innovation. It feels like every three months. And then it's like, okay, well then how do we implement that thing into the thing that we were already changing? And so I think there's a bit of like change resiliency to and the, and not having the expectation that everything has a clear black and white solution, or that everything can be simply solved once and then never has to be solved again.

Host: It's really interesting that you point out that really it's not about necessarily having the answers. It's really knowing where to look and how to look. And that brings me on quite nicely to one of the things that I did want to ask you was listening at scale and bringing that creative pragmatist approach that you've mentioned. How do you keep a genuine read on sentiment across such a large organization. And what is what are the steps that you take to decide what really is worth, you know, following, even if it's even if it's feedback that can be quite hard to hear sometimes.

Guest: Sure. I think, um, a couple of things. Right. Look, for years there's been this back and forth of, ah, employee sentiment surveys worth it. Or do they actually send you down the wrong path? Are you amplifying the right voices to get at the nuance? All of those things. And I think for me, it's like, put that aside. What we notice is that the most rich data set for us comes from recognition moments. Those are the instances where you learn about a project that maybe you didn't know about, or a member of your team who was really critical in getting something done, yet that's not part of their day job, and that therefore, you wouldn't have even been talking about it in a one on one. And so you get a real sense of not only who's doing the work, but the type of impact that they're having. But then you can also notice things like, I'm seeing a lot more award messages around, you know, things for jumping in at a time where I just was at my limit. And so then that can give you a sense of, huh, are we starting to see a little bit of burnout and might that begin to proliferate because the same people keep jumping in to help? How might we want to address that? So that's one way. I think the other way is having conversations with people. I will tell you that when I first started, my team size was was larger and I met with every single person one on one. And the idea there was, I want to hear from you. How is your experience going here? What are the challenges that you see? What are the things that get in the way of you doing great work? And when are the times that you feel best about the team, your colleagues, what we're working on, how you're delivering all of those things. And I don't think you should ever stop that, especially as a leader in this role. Right. So some people call it chief people officer or chief human resource officer. We call it the chief human experience officer. Whenever I'm traveling, I'm talking to the team at all levels. I'm not just spending time with my peer set. I'm making sure that regardless of whether it's members of my team or it's members of the broader community that I'm checking in, that if we're in the canteen together, I'm asking folks, how's it going? What are you working on right now? I'm trying to get an understanding of what the experience is from places that I might be less likely to hear it from directly, but also embedding in my team the expectation that my leaders are doing the same thing, and that if there is a challenge, that they're talking about it with each other. And if there seems to be a theme around this challenge that they're bringing it up in our leadership team meetings so that we can make sure that we're doing what we need to to address the challenges that we see, or to give information where it seems like there's an information gap, and also to be mindful of those times where the answer might not be something that people like, but that you're being honest with them about what the answer is. Why that's the answer. And what, if any, alternative there is. And so we do that. Like I mentioned on my team, we have work, human leader meetings where it's everybody who's director plus in the company globally attends these meetings where we ask for, you know, pre-event surveys, what's going on. We give updates, of course, but then also, you know, we have folks checking in after the meeting. How did that go? What are the things that you're hearing? Oh, they didn't really like that. This felt more talk at okay, so then let's change the format a bit and make it more time for Q&A or to survey for topics ahead of time. So it's more about how can you kind of real time make sure that everybody feels encouraged to keep a pulse on what's going on. And that also then gives you a sense of where is this like a universally shared thing, which we should bubble up and create a solution for, or at least address in some way, versus where is that a pocket instance? And maybe for that business partner that's supporting that area of the team, they might want to spend some time on that with the leader of that team. So it's a balance of the recognition moments and being proactive and trying to understand the sentiment, not just what the moment says, and simultaneously getting out there and having conversations and encouraging people to share back with you the things that are working, the things that aren't working.

Host: Talking of sentiment as well, if I if I have done my research even partially correctly, I believe work has done some research that sort of found that a significant portion of employees feel work was better in this sort of, you know, in the past, in this kind find a golden era of work. What's your what's your take on that? Like what? What do you think that what keeps cropping up is what might have been lost? And, and is there anything that you're, you're doing to allay those fears or address it in some way?

Guest: Well, I certainly hope there's nothing we're doing to stoke those fears. Uh, at the same time, what I would say is you hit something very important. It's the sense of you feel like. Like it used to be better because you feel you lost something. I think in the past, what there was, was there was a ton of clarity on, you know, for the most part, day in, day out, what is my role? What are my contributions, how do I move up the ladder, etc.? And I would tell you that, you know, maybe since Covid, maybe slightly before that, slightly after, depending on who you're talking to, we got more into this career Rockwell situation. Also, we're in a unique point in time for technology companies, especially SaaS organizations where there we're not in this, you know, growth at all cost kind of momentum that we had in the last ten, fifteen years. And so that is a shift to be able to say, okay, so we're not trying to hire as many people as humanly possible, which then therefore means we're not promoting people as quickly as perhaps we were in the past. But that shouldn't mean that you still don't have the opportunity to learn and grow. It just means what those opportunities look like may be less structured than how you historically would have thought about them. That works for some people. It doesn't work for others. And so for us, it's, you know, we've spent the, the last year or so really working on skills based job architecture. How can we ensure that everybody understands what's their requirement for their role? What's the requirement for the role above or below them? But also, what about other roles that they might be interested in. If you have a skill set here and we don't know about it, you might be a great candidate for an internal move or to cover a mat leave position where it gets you to explore a different skill set, explore a different part of the business, learn a little bit more, and then maybe that sets you on a different path for your career than what you initially thought. So in that flexibility, still trying to give people a little bit of a compass around the map, right? So that they can then say, okay, I want to head north, or actually I want to go slightly northwest or I'm, I'm heading south. I don't mean that in a bad way. Um, but whatever, whatever that orientation needs to be. I also think that some of the things that maybe feel like they were lost, people are romanticizing them a bit. You know, there's the sense of, oh, it was simpler back in the day. Yeah, maybe, maybe that's true. At the same time, there was a lot more discrimination back in the day, there was a lot less flexibility around how work gets done when it gets done, where it gets done. There was a lot less opportunity spread equitably across the board. And so it's, you know, I don't want people to just have on the rose colored glasses or, you know, whatever that metaphor is about the past, but really try to be able to articulate what is it that they feel like they're missing now that makes work harder? And then how can we try to address those things?

Host:  It does seem in the current climate that whichever direction the compass points, usually there's AI.

Guest: Yeah.

Host: And that's something I did want, I did want to touch on is your thoughts on bringing in AI without, without losing employee trust or, you know, at the very gaining trust actually in how you implement it? Stacked on to that. I would also like to get your opinion on something about hackathons as well. Is that is that within your remit as well? Because that's really interesting as well. So could you could you talk to me about those two sort of conjoined points?

Guest: Yeah. So listen, I would tell you that hackathons have become a shared ownership model across the leadership team, but also across people who are interested. And that's very exciting because it means you don't necessarily have to be the one in Ajax or in technology to coordinate the whole thing, to know that people are interested in generating new ideas and working differently. That being said, at the start, it was really a tech focused thing. Then it became a hybrid tech plus Ajax thing, and then it became a well, actually, we in the exec space, we need to do our own hackathon. We need to understand not only what we're asking people to do, but what are the challenges that we would like to solve with this new technology, and then take that back to our teams and then run a hackathon for our own department. So it sort of evolved over time. What has remained the same are sourcing the ideas that then you will put resourcing behind to explore and generate an MVP or, you know, a prototype or whatever it is that you're trying to create based on what people are saying would help them at work to either get work done more efficiently, to remove some bureaucracy, to simplify things, whatever the case may be, that they feel like is important. And also saying regardless, like, if we stay with that compass metaphor, I would tell you that in some ways AI has become the magnet that then reorients the compass a bit. And so what we've tried to do is kind of decrease a bit of that magnetism to say, we want to be mindful of AI, and we want to be using it as smartly as possible. At the same time, we need to ensure that there's a human in the loop. So where does it make the most sense to have the human in the loop? And if it's its multiple instances. Okay, well then what do those responsibilities look like? And then ultimately what do these roles become? So not just simply, you know, starting at you need to use AI and then giving you a litany of here's exactly how you should use AI. We spent the last, I want to say eighteen months just experimenting, just giving everybody a license and saying, go out there, experiment, having different levels of courses that people could take all the way up to like fully full certificate programs, creating AI ambassadorships. And now at the point of having AI business partners or sourcing AI business partners. And for us, the biggest thing that we've learned is if you let people in on the design, they will get excited about it. If you let people tell you what they believe the right solution could be, then they will adopt it. I could not tell you in the call center that from our first hackathon, the place where they should have been spending their time was creating an agent that could similarly tell. Sentiment analysis, but also pulling the logistics of what is this phone number? That likely means they're calling from what organization? If you have the employee ID because they're redeeming points, well, then that can tell you, hey, this is their most recent orders. And actually there's a problem with one of their orders. And here's where it stands right now. So that by the time they were picking up the phone call, they already had all of the information at their fingertips that then like would de-escalate a conversation. Because if you can imagine calling customer service, you typically not calling them to say, hey, I just wanted to let you know everything went swimmingly and thank you so much. Right. And, and the more you have to be put on hold, the more frustrated you get. Well, that's also a high turnover role because you constantly have people yelling at you, even though it's not your problem or your fault, I should say. And so them coming up with their own solution, that solution has actually won external awards, and it made us think differently about who needs to be part of the solution and the design around implementation with some of these tools. I don't need to know what the answer is. I don't need to go to, you know, the head of our call center and tell them, here's what you should be doing, because there people know what would work better for them and for our customers. So bring them into the design, bring them into the fold, and you get a lot better. Not only adoption, but also smarter solutions than if it was just the exec team sitting in a room dictating what needs to happen. Now we're at the point where we have a culture of experimentation. We have implemented some things, and now we're saying, okay, what are those across the organization, business processes that we really need to look at, you know, from a shared ownership model and then redesign collectively. That's a place where we can absolutely play a role by saying, you know, who from our team should be a part of those conversations? What are the resources that we will give them, and how will we help to support coming up with the right solution, with as little ego in the process as possible? And that feels like the right evolution, right? Because we started with what are people identifying? And then we move to, so where are the places where people are identifying similar challenges, or people are identifying their individual part in a shared process that touches a number of departments in the organization.

Host: I mean, it's a really good point about the use cases of AI. I mean, actually an interesting point that you said you spent the last eighteen months experimenting. It seems to me that there is there's a conversation to be had around almost, you know, as you say, exec or board level about how you position it in terms of future value creation. But do you have any other instances from, From. From your sort of AI experimentation across Workhuman that have either surprised you or pleased you, as it were, in terms of, um, in terms of like value, you know, generating business value that maybe that wasn't obvious to from a top down perspective.

Guest: So one is popping into my mind and I think there's another one in there. So let me start with the first one. The first one is have an EA on my team that supports myself, the head of finance, the head of legal, and she's a quieter type person, but absolutely excellent at her job, yet has a broader skill set than you might think when you think of somebody who's an executive assistant. Well, I was not aware of all of the time she was spending learning about AI and, and tinkering with it. I was aware when she would say, hey, I would love to take this course. It's three hours on this day. And I'd say absolutely, of course, go ahead. But, you know, I was thinking, oh, okay, I see you're trying to find better ways for us to generate the notes after the meeting or things like that. What she came up with was multiple agents that do so many different things. Like for me, she said, you know, I notice you have a lot of speaking engagements and a lot of travel. And so this agent is going to proactively tell you, here's what you have coming up. Here's maybe some things that you have talked about before that might make sense here. Here's what you should be thinking about so that I'm ready to be thoughtful and engaged, as opposed to, I just got out of this meeting and now what am I supposed to be talking about? I would never have told somebody, create this agent for me. And as we, you know, kind of looked across the business, we also had another EA who said, I'm noticing that we do a lot of last minute flight changes in these sorts of things. I think there's an opportunity for us to work with our travel partners and create a better system for us to be able to take advantage of. Oh, if you cancel the flight over here, we can reuse these credits over here and not have to track them manually in Excel. And so also created an agent to do that. And then all of a sudden we're like, we're saving all this money on travel because we're being thoughtful about where do we have opportunities as opposed to which airline do you want to fly tomorrow? Right. And then there have been places in the business where for our go to market operations team, where they were able to create an agent that would ingest customer pitch calls or, you know, customer consulting calls and would tell them like, hey, here's an opportunity that you missed where you may want to go back and dig into this. It seemed like this person was very interested in this topic, but that you will only glazed over it to help really fine tune the way that we show up in conversations as opposed to having our own agendas of what we feel like we need to get to. Really balancing that against, well, what is it that this customer is telling us that they need or that they want to be spending time on and ensuring that we're having those conversations? So those are just a few examples. And what's been interesting is as you use cloud, as you use ChatGPT, you then find that some of these examples become universal solutions that they offer, like, you know, financial reporting, quarterly reports, things like that, where it's like, oh yeah, we created our own agent. Yeah, sure. Maybe they did this better. But what we gained in creating our own is the muscle around why this matters, who should be using it, the ways in which we like how it works and the ways in which we don't like how it works. So that when you use the cloud model or the ChatGPT model, you're a bit more savvy in, what does it actually need to do to be successful for you, and what are the things that would get in the way of that success?

Host: It seems a, um, an always changing mixture of serendipity and skill.

Guest: And just trying to encourage enough experimentation that the serendipity happens more often than not.

Host: Yeah. Yeah. The, the better you are, the luckier you get. Right.

Guest: Right. Right.

Host:  I've got one final question for you, KeyAnna, which is it's quite nebulous. It's quite sort of if blue sky thinking, if you will, but from your perspective in your role, what do you see as the single biggest challenge that you face and what is the biggest opportunity that lies ahead for you?

Guest: I think the biggest challenge is acknowledging the fact that org structures, not only have they not been working for us for a long time, but they can't work in the future of work. And so what I mean by that is, you know, post-industrial revolution, like we still have departments set up in ways that they were set up for, you know, World War Two factories, right? Like you hand this from operations to the product team to then the engineering team. And it's like that work has not worked like that for a very long time. Work has been much more, to use a word that you just used. Nebulous, right? It's been much more. What is the project that we're working on? Okay. Who do we need to pull? Oh, crap. We found this thing. Actually, we're going to need somebody from this team. And so I think the biggest challenge is reorienting literally everybody in the organization, including myself, to what are the ways in which work gets done. And then how do you set up the organization to ensure that it's easier to do work in those best ways, while at the same time trying to meet the needs of people who are going, well, how do I reach that next step? How do I grow and develop and are kind of still, you know, holding on to that traditional model in their heads and wanting a rubric for do these three things plus these two things, and then you wind up with VIP status. And so I think for me, that's, that's kind of the piece that keeps me up at night is how can you satisfy the need for clarity around what does success mean here? And how can I continue to grow and develop without people thinking that grow and develop means promotion only, while also balancing the needs of the business and the needs for people to think outside of their departments, their role structures, etc. and more geared towards. Here are the big meaty challenges that we're trying to solve. Who has interest? Who has the right skill set? Who has the right capabilities to help us solve for that? Those are the people that we want on that team. And then for this problem, it's a different mix of people. And so that's what I'm also most excited about is, you know, really cementing this idea of project based work and then deciding, are there any consistently routine things that still need to get done that should still be done by humans, as opposed to the AI outside of, you know, keeping the humans in the loop to make sure that the process is well run. I think that's our biggest opportunity and our biggest challenge.

Host: Yeah. Well, I mean, it does sound like, as is often the case, the biggest challenge is also the biggest opportunity. Correct. KeyAnna. It's been a fascinating conversation. It's a pleasure to speak with you. And thank you so much for speaking to me on the podcast.

Guest:Thank you for having me. I love the conversation and hopefully everything I said made sense. But if it does, you know, let me know.

Host: I absolutely will. Thank you so much again.

Be the first to comment.

Sign up for a FREE myGrapevine account to have your say.

Share this article:

You are currently previewing this article.Create account

This is the last preview available to you for the next 30 days.

To receive our daily newsletter and access HR features & insights, create a free account today.