TRANSCRIPT 🔗
WEBVTT
00:00:04.320 --> 00:00:05.759
Hello and welcome to today's show.
00:00:05.839 --> 00:00:09.199
I'm Jacqueline Stockwell, CEO and founder at Leadership Through Data.
00:00:09.279 --> 00:00:12.560
I inspire and motivate information leaders across the world.
00:00:12.720 --> 00:00:14.160
I'm here with Jenny Lynn.
00:00:14.400 --> 00:00:19.760
She is an experienced civil servant with a specialist background in information management.
00:00:19.920 --> 00:00:27.920
She currently serves as the Digital Workplace Program Information and Records Manager Lead within the Department of Finance in Belfast.
00:00:28.239 --> 00:00:41.039
With a demonstrated history of working across data protection, records management and information access rights, Jenny is now working at the front of the digital transformation for the Northern Ireland Civil Service.
00:00:41.280 --> 00:00:50.320
She is an active member of the professional community for the Information and Records Management Society, known as the IRMS.
00:00:50.560 --> 00:01:05.439
Jenny is developing the information architecture for in-place records management in Microsoft 365 for the NICS, making it easier for staff to work collaboratively and do records management without even knowing.
00:01:05.680 --> 00:01:11.040
And I'm thrilled to have you, Jenny, because we've been known each other for quite a long time now.
00:01:11.200 --> 00:01:13.840
So it's exciting to have you on today's show.
00:01:14.000 --> 00:01:15.840
We're not it's one that changes all the time.
00:01:16.000 --> 00:01:18.159
I mean, this is a fairly new rule to me.
00:01:18.480 --> 00:01:20.719
Jackie only started in December.
00:01:20.879 --> 00:01:43.920
And I've gone from being a sort of a hands-on information manager, data protection officer, very operational, reacting all the time to queries, questions, issues, um, you know, very fast pace to a more kind of proactive and kind of more laid back, not laid back, but certainly more time to sort of think about the way forward.
00:01:44.079 --> 00:01:51.439
So this program is really to um bring in place records management in 365 and retire or old EDRMS.
00:01:51.599 --> 00:01:53.359
So it's it's a really exciting place to be.
00:01:53.439 --> 00:01:56.719
I'm really enjoying what I'm doing, um, but it's just a different way of working.
00:01:56.879 --> 00:02:02.239
So yeah, just um follow me on the journey as we go, uh is all I say, because we're just very, very new to this.
00:02:02.400 --> 00:02:12.719
Well, the program director had involved me from the very early stage of the programme setup to kind of just sort of hear me out on um where he thought the the program could go just based on my experience.
00:02:12.800 --> 00:02:16.319
And as we went through the programme, it became very obvious that there was a dedicated role there.
00:02:16.479 --> 00:02:24.319
Um, I was very keen to do that role, but civil service being the way, you know, rightfully so, there's processes to follow, and we followed those processes to do it.
00:02:24.479 --> 00:02:33.199
So, you know, it was it was it was a natural transition for me, but also quite a big change up to I'm just going from, as I say, that really reactive thing into the this providable way.
00:02:33.439 --> 00:02:39.759
But it's well, the the main thing is with what you don't get with a lot with these kind of programs and projects, the right people are in the right job.
00:02:39.919 --> 00:02:53.520
So experience, um, understanding, innovation, forward looking is how I would describe the way we're going with this and getting the right people in to do that and recognizing those talents is is is really important for anybody who's looking to involve themselves in these kinds of products.
00:02:53.840 --> 00:02:57.039
So tell me about your old role.
00:02:57.280 --> 00:03:09.599
This is something that comes up a lot, especially in the Department of Finance, because not only is it um you know what quite outward facing, um, we do a lot of policy work um and others outward facing around land and property and and statistics and so on.
00:03:09.759 --> 00:03:13.680
There's also the HR department for the whole of the civil service that's within the Department of Finance.
00:03:13.759 --> 00:03:20.159
So there's a huge amount of um uh FOI and subject access that goes on in our department.
00:03:20.319 --> 00:03:21.599
A lot of them overlapping as well.
00:03:21.680 --> 00:03:27.599
So you would have got requests that took in a lot wide range of of both FOI and SAR.
00:03:27.919 --> 00:03:38.479
So the main thing we found was to make sure that there were dedicated people for each, that the same people weren't doing the same job, although, of course, there is a shared column of knowledge and a shared experience.
00:03:38.800 --> 00:03:47.280
Siphoning and siloing what is an FOI and what is SAR is really important because if you if you start to mix the two together, it gets very confusing for people.
00:03:47.439 --> 00:03:54.639
And I think as well, being quite clear about how we educate our staff on each thing, that we don't have a one size fits all.
00:03:54.800 --> 00:03:58.240
This is this is information access um course.
00:03:58.319 --> 00:04:03.599
There's there's specifically awareness around data protection and awareness around freedom of information.
00:04:03.680 --> 00:04:04.960
So it's important for that.
00:04:05.280 --> 00:04:07.039
They're linked but they're not the same.
00:04:07.199 --> 00:04:12.000
Yeah, it it is it is uh I think starting with the staff, it's really important to to define that.
00:04:12.159 --> 00:04:21.199
The other thing as well is you know, when you're talking about things like where we are mixing personal information in with FOI, that's where you look to your exemptions.
00:04:21.279 --> 00:04:41.839
You know, you're talking about looking at your section 40 brackets two, looking at your section 40 brackets one in some cases when it comes to HR, and you
Load full transcript
know, not just telling individuals we're not going to give you this, it's your personal data or it's somebody else's personal data, allowing them to understand that actually if they're looking for an element of their own personal data, we'll flip that for you proactively into a subject access request.
00:04:41.920 --> 00:04:45.759
And I know that's ICO guidance, but sometimes it's quite difficult to do in reality.
00:04:45.920 --> 00:04:53.360
So it is about ensuring that the customers serve right from start to finish, and we're explaining very, very clearly to them the difference between the two things.
00:04:53.519 --> 00:05:09.360
It's difficult, it doesn't always work because sometimes people have bring their own issues into the situation, but you have to do what you can do to try and make sure it's clear because there's if those things do get mixed up and they go, say, for example, the ICO with a compar concern or complaint, it can get very confusing.
00:05:10.399 --> 00:05:15.439
My main thing is keep them separate, keep the teams separate, but linked in terms of knowledge.
00:05:15.680 --> 00:05:16.160
Amazing.
00:05:16.240 --> 00:05:16.720
Thank you for that.
00:05:16.800 --> 00:05:17.680
It's a great piece of advice.
00:05:17.839 --> 00:05:24.240
So in the civil service, information isn't just data, it's the historical record of government decisions.
00:05:24.399 --> 00:05:30.639
How has the shift to digital first government changed the way we preserve the why behind policy decisions?
00:05:30.879 --> 00:05:39.279
I think it's made it much easier to capture decisions and because it makes it easier to capture decision making if teams are using the tools properly.
00:05:39.519 --> 00:05:51.600
You know, email, um, all our collaborative spaces we have now, even you know, the version histories we can create, they all create quite a rich record that isn't then confined to an A4 page, so it comes in different f looks and feels.
00:05:51.759 --> 00:05:58.720
But however, the the sort of flip side of that is that you know everything's a bit more dispersed now, everything's a bit wider spread.
00:05:58.800 --> 00:06:05.120
So it's um so it's about making that forming that official record, ensuring it's stored in the right place and making it easy to do the right thing.
00:06:05.439 --> 00:06:12.959
How do you implement modern records management in an environment where it's deep set in legacy processes?
00:06:13.120 --> 00:06:14.720
This is the way we've always done it.
00:06:14.879 --> 00:06:16.639
Like what's your suggestions?
00:06:16.879 --> 00:06:20.480
Yeah, I think you have to start by meeting people kind of where they are.
00:06:20.639 --> 00:06:25.360
Legacy processes exist because they solve a problem for people, even if it's inefficiently.
00:06:25.439 --> 00:06:34.079
So it's first looking at what process they're trying to achieve, what problem they're trying to solve, and then introducing small, manageable changes that will reduce that friction.
00:06:34.240 --> 00:06:40.160
In the civil service, building alliances or or relationships with operational teams is really crucial.
00:06:40.399 --> 00:06:48.319
So when people see that better workers' management saves time, reduces risk, they're much more willing to move away from the familiar old ways of working.
00:06:48.480 --> 00:06:52.240
And having champions and ongoing managed services too is really important.
00:06:52.480 --> 00:06:58.319
People who can continue to advocate for maintain digital workplace when you're no longer embedded in that part of the project.
00:06:58.399 --> 00:07:07.199
So having those people built in into those areas, those people that will champion what you're trying to do, even when you've stepped away from that area, is vital for that ongoing there.
00:07:07.519 --> 00:07:14.399
Yeah, and I think that you 100% it's the relationships that you have with the people and feed into those.
00:07:14.480 --> 00:07:18.639
So um we can't know the business, we can't understand the processes.
00:07:18.720 --> 00:07:22.879
So if we go in and say we're gonna do this to you, the back's gonna go up straight away.
00:07:22.959 --> 00:07:31.199
It's about bringing them on the journey and explaining how it'll help and allowing them to bring their expertise back to you and say, actually, we do this because X, Y, and Z legislation says why?
00:07:31.360 --> 00:07:32.000
Right, okay.
00:07:32.079 --> 00:07:34.720
This isn't necessarily gonna work, but something over here will work.
00:07:34.879 --> 00:07:36.399
It's that two-way engagement for sure.
00:07:36.879 --> 00:07:43.439
So you hold a PG diploma from the University of Dundee, which is renowned for its archives and records management program.
00:07:43.920 --> 00:07:50.560
What is one theoretical principle from your studies that you find yourself applying most in the real world of civil service?
00:07:50.800 --> 00:07:52.319
Jackie, we're going back quite a few years now.
00:07:52.720 --> 00:07:54.079
I know that I don't know.
00:07:54.720 --> 00:08:00.720
To be fair, you know, there are things in that theory that I still think about, you know, and use in the day-to-day practice.
00:08:00.879 --> 00:08:03.279
The main one being that records are evidence.
00:08:03.519 --> 00:08:08.079
A record is something that is valuable and it's it's it's not just because it exists.
00:08:08.319 --> 00:08:15.680
So because you created it doesn't mean it has to be kept as a record, despite what you know, your your panic mindset thinks.
00:08:15.839 --> 00:08:26.720
So it's really about cutting through the noise of we must keep everything just in case, and thinking about well, if it's evidentiary and it gives you know the evidence of a decision, that's when we keep it.
00:08:26.800 --> 00:08:31.120
That's the record, not all the conversation, not all the conversation around that decision.
00:08:31.199 --> 00:08:34.000
So, and I think the ICO indeed would agree with that as well.
00:08:34.080 --> 00:08:39.279
They're not interested in you keeping every single minute shy piece of conversation that comes to decision, they're interested in the decision.
00:08:39.440 --> 00:08:45.519
So keeping that record as evidence sort of theory works in practice for your entire life cycle.
00:08:45.919 --> 00:08:52.639
What made you get that pro practitioner's certificate and what was the outcome in your job role because of it?
00:08:52.879 --> 00:09:02.240
Yeah, I mean, like a post-graduate diploma is great if it's for you because it is academic, it is theoretical, um, it gives you that theoretical practice behind how you apply it.
00:09:02.320 --> 00:09:05.440
And the the certificate helps you actually apply that in the real world.
00:09:05.519 --> 00:09:08.559
So it gives you real-world case studies, real world examples to work from.
00:09:08.720 --> 00:09:15.759
So I think that you know, it shows you how to structure that legislative knowledge into an understandable and meaningful way for people.
00:09:16.080 --> 00:09:22.960
You can use it to you know learn how to weigh risks and design mitigations that are practical rather than kind of paper theory.
00:09:23.039 --> 00:09:37.279
Um, and it really helped with understanding like spotting some patterns quickly, um, you know, processing, you know, looking at um so understanding data flows is something that you know you can only really learn in in practical aware, you know, awareness and training.
00:09:37.440 --> 00:09:42.000
So it's it's kind of the pr the practical sense to the theoretical background.
00:09:42.320 --> 00:09:44.879
I just want to approbe a ri around life cycles.
00:09:45.039 --> 00:09:47.039
Yeah, the life cycle of a record.
00:09:47.200 --> 00:09:52.159
So many people think that records management is just don't delete things, delete things.
00:09:52.480 --> 00:09:57.919
From your experience, what is the most high risk stage of the information life cycle in a government context?
00:09:58.240 --> 00:10:12.720
Yeah, I think most stages of the life cycle are risky in a way, but what we are really focusing on in the programme and what has become apparent is you know, creation is really something we need to take a better focus on.
00:10:12.799 --> 00:10:21.360
I don't think it's about necessarily about fully about risk, but certainly about making better decisions right from the outset, which will cause a lot of less pain down the line.
00:10:21.440 --> 00:10:24.720
So it's maybe that you know, good foundations build a good house.
00:10:24.799 --> 00:10:27.360
And I think that you know, creation is something that we just take for granted.
00:10:27.440 --> 00:10:30.240
It's created there, it's created here, it's in in the civil service.
00:10:30.320 --> 00:10:41.279
We create right into our EDRMS, which is actually an ERMS, the way we treat it, and it makes everything very structured and very much like a record right from the outset, which isn't necessarily the right thing.
00:10:41.360 --> 00:10:50.799
And what we're trying to do is flip that narrative on the head to say that not everything you create is a record, you know, and it's going back to that, you know, it's ev what's it what's evidence, what's your decision making?
00:10:50.960 --> 00:11:05.919
And treating things, and it's a term we're we're starting to use now, is a managed document and talk about things in MS365, those tools that allow you to manage things in a very structured way with good managed metadata, um, but not making it a record, not making it immutable until it really needs to be so.
00:11:06.159 --> 00:11:21.600
So I think it's that creation stage, we're making those early decisions around, or you know, we're storing things in in various places, but when it comes to capturing it, um, that it becomes, you know, it's it's a managed document and it's managed nicely, but it's still usable for people.
00:11:21.759 --> 00:11:33.200
And I think that if you have a good start, then when you come to retention disposal, a lot of those issues around we've got so much stuff that we don't even know where to start with retention disposal, or we're scared, it's been so long, we can't we're scared to let go of it.
00:11:33.360 --> 00:11:35.759
Um, you know, a lot of those decisions have been made early on.
00:11:35.919 --> 00:11:41.919
So you've you've got your disposal policies in place that will get rid of the rot right before so it doesn't become a problem towards the end.
00:11:42.080 --> 00:11:46.799
So then yeah, starting out, you know, the creation is is where it all should really begin, ironically.
00:11:46.960 --> 00:11:47.440
Not ironic.
00:11:47.600 --> 00:11:49.759
Wait, but then you put AI in there, don't you?
00:11:49.840 --> 00:11:52.240
And then creation becomes even bigger and more.
00:11:52.559 --> 00:11:54.720
It's only taking you five minutes to mention the AI word, Jackie.
00:11:54.799 --> 00:11:57.120
That's I try and keep the dirty word out of here, but it is.
00:11:59.440 --> 00:12:00.240
Yeah, no.
00:12:01.519 --> 00:12:03.440
Um, okay, so let's talk about SARS.
00:12:03.679 --> 00:12:07.120
So they're becoming increasingly more complex and far more frequent.
00:12:07.759 --> 00:12:11.519
Public sectors and government organizations are getting more and more.
00:12:11.759 --> 00:12:20.080
What is your strategy for managing vectatious um or massive SARS without sort of paralyzing the daily operations of the department?
00:12:20.559 --> 00:12:28.720
It's really difficult, Taki as you know, because it's always been, you know, our first finding foundation around SARS is give the people what they need, you know, what they want.
00:12:28.879 --> 00:12:33.120
We we should we try as hard as possible not to restrict a subject asset request.
00:12:33.279 --> 00:12:39.759
And it's always been quite um very, very, very rare that would you would step back and say, look, we can we can't service this anymore.
00:12:39.840 --> 00:12:49.840
Um and not necessarily through volume, but certainly through, you know, um the the the measures of manifest the unreasonable, you know, rather than volume, because I don't think that's a really good way.
00:12:50.000 --> 00:12:59.200
We we do, you know, in Department of Finance, before I moved on as a DPO, we receive a hundreds and hundreds of subject access requests because there is EHR in there.
00:12:59.440 --> 00:13:12.639
And I think that, you know, the issues we've had with volumes will change hopefully going forward, because I think the most important thing is to be more proactively transparent with your data around, especially around HR processes.
00:13:12.720 --> 00:13:16.799
So there's systems being created that allow you more access to your own personal data.
00:13:16.960 --> 00:13:19.440
And I think as well, a big thing is around trust.
00:13:19.600 --> 00:13:25.840
So people don't trust processes in HR, they don't trust that people are telling them the truth, they don't trust if it's not transparent enough.
00:13:26.000 --> 00:13:35.360
So by changing that, um, you know, that transparency around the actual HR process will hopefully look to reduce the night of people putting in subject access requests.
00:13:35.519 --> 00:13:45.840
Um, I think there are still, you know, issues around, you know, with the new um Data Use and Access Act, you know, we're moving towards that sort of FOI definition of fictitiousness.
00:13:45.919 --> 00:13:53.600
Um, but I think that genuinely we still need to be quite cautious about doing that when people are genuinely looking for their own personal information for the purposes.
00:13:53.759 --> 00:14:06.080
So, you know, I think I think what what would cut the volumes and cut the kind of tension in there is to be more transparent from the outside about people, about HR particularly, or about their processes and allow them to access their data easier themselves.
00:14:06.399 --> 00:14:10.159
They're not getting caught in this entrenchment between their issues and SAR.
00:14:10.480 --> 00:14:20.000
But I want to talk about sort of um data protection by design and you're working with teams, project management managers, I assume, um, to deliver what you need to deliver.
00:14:20.159 --> 00:14:28.080
So, how do you get project managers to think about data protection at the start of this project that you're doing rather than treating it right at the end?
00:14:28.240 --> 00:14:37.120
Well, this is why I was so excited that you got this job, Jenny, because it's kind of where you where you can think about it as well, rather than a checkbox exercise at the end.
00:14:37.279 --> 00:14:39.279
See, it's the eternal question, Jackie, isn't it?
00:14:39.360 --> 00:14:43.679
It's always about when do we do data protection during a project?
00:14:43.759 --> 00:14:51.120
And there's a lot of projects in the civil service, a lot of big, you know, outward-facing ones, a lot of internal ones, changing systems and IT, for example.
00:14:51.279 --> 00:14:55.039
And I think it all starts with data protection by design and default.
00:14:55.200 --> 00:14:58.000
You know, it is from that very, very outset of the program.
00:14:58.399 --> 00:15:08.799
And I think the main thing I've done is put the DPO out there as a put them in your boardroom, put them in your project board, put them in your project team as a consultation.
00:15:08.960 --> 00:15:14.000
Um, it's it's it's talking about that right from the outset because what we're talking about here is cost saving.
00:15:14.080 --> 00:15:15.840
You know, that's what you're selling is cost saving.
00:15:16.080 --> 00:15:24.639
You design an IT system and you talk to me at the end, I'll point out the things that you cannot build in, retention disposal, for example, that's gonna cost you down the line.
00:15:24.879 --> 00:15:31.200
So, you know, I've focused on those kind of more um project incentives around I'm gonna save you time and money if you talk to me from the outset.
00:15:31.360 --> 00:15:40.559
And they respond well to anything that talks about reducing risk later on, improving stakeholder competence, um, you know, preventing the need for the last-minute redesigns, as they say.
00:15:40.639 --> 00:15:45.039
So it's talking about data protection as a project enabler rather than a blocker is really important.
00:15:45.120 --> 00:15:49.919
So we're gonna enable you for your project to be successful, for your system to be successful, for your outcome to be successful.
00:15:50.080 --> 00:16:12.000
And I think as well, you know, we have worked very closely, or I had worked very closely with our procurement um teams, our finance teams, our IT colleagues as well to say if you have are approached by somebody who's looking to do a new tender or a new system, mention my name, bring me into the room, um, and put those DPIA checkpoints into the governance paperwork as you go along with your project managers.
00:16:12.399 --> 00:16:16.000
And that just becomes part of that, just that part of the process.
00:16:16.080 --> 00:16:17.600
It just becomes natural that way.
00:16:17.919 --> 00:16:22.879
How do you build the culture of compliance where you see staff as enablers rather than barriers?
00:16:23.039 --> 00:16:29.600
Um I think it's about positioning data protection and indeed information management as something that helps people do their jobs.
00:16:29.759 --> 00:16:40.559
I think we go back to the last question there, you know, it's about improving how you're doing things, how improving how your project goes, improving how your piece of work goes, and making make your jobs easier and more safe.
00:16:40.720 --> 00:16:58.240
So my priorities were always simple practical guidance, quick wins, being really approachable to people and quite collaborative and explaining why things exist, not just what the you know, why it, you know, so for example, the legislation, explaining why a rule in legislation exists, not just what that rule
is.
00:16:58.399 --> 00:17:02.639
It's not just computer says no, it's because, you know, why, you know, well, it depends.
00:17:02.720 --> 00:17:04.000
You know, let's look at this this way.
00:17:04.160 --> 00:17:05.599
This is why we're doing it this way.
00:17:05.759 --> 00:17:12.000
So I think that, you know, that's really important to have that sort of balanced engagement with and collaborative with people.
00:17:12.160 --> 00:17:20.000
And whenever they feel supported that way rather than judged, they're far more likely to go along with you on the journey and adopt that good practice.
00:17:20.240 --> 00:17:28.240
So, you know, it's it's just about being, you know, I'm not, you know, here nobody wants to be scared of the person with the you know, the big gavel who's going to cut down on them.
00:17:28.480 --> 00:17:29.279
It's collaborative.
00:17:29.359 --> 00:17:31.599
You have to be personable and bring people along on the journey.
00:17:31.680 --> 00:17:34.079
And I think a bit of humor also helps too.
00:17:34.240 --> 00:17:42.480
The first thing, you know, if there was a data incident and somebody came to me and said, I have a staff member who's made an who's made an error, um, they've lost a night's sleep over this.
00:17:42.640 --> 00:17:43.920
I am straight on the phone.
00:17:44.079 --> 00:17:45.200
Do just don't.
00:17:45.440 --> 00:17:47.119
Do not ever do that to yourself.
00:17:47.200 --> 00:17:48.319
It is not worth it.
00:17:48.559 --> 00:17:50.079
Please do not feel bad.
00:17:50.319 --> 00:17:51.519
Mistakes happen.
00:17:51.599 --> 00:17:55.359
You know, I've never encountered a malicious person, thankfully, but mistakes happen.
00:17:55.440 --> 00:17:56.720
We'll we'll work through this together.
00:17:56.799 --> 00:17:58.480
I'm not in the culture of blame here.
00:17:58.640 --> 00:18:02.559
We'll just work to make fix the issue and change our cultures to make it better.
00:18:02.720 --> 00:18:10.000
And I think that's so important because that's your that's your influence, that's your approach, that's how you deal with the people, and that's how you build those relationships.
00:18:10.079 --> 00:18:20.000
And I think that is a huge part of an information leader's job role to have those relationships so they will be included in things without being shut out of them.
00:18:20.160 --> 00:18:23.039
So I think that's uh an amazing piece of advice there.
00:18:23.119 --> 00:18:23.440
Thank you.
00:18:23.599 --> 00:18:25.119
So last question from me.
00:18:25.359 --> 00:18:31.039
If you could automate one part of the FOI SARS process tomorrow, what would it be?
00:18:31.359 --> 00:18:32.400
Automate it?
00:18:32.640 --> 00:18:34.880
Maybe dealing with the ICO, who knows?
00:18:35.119 --> 00:18:37.039
I don't I do know what I'm gonna say.
00:18:37.119 --> 00:18:50.960
I wouldn't automate anything, anything that involves the staff, the FOI staff, because the involvement they have in terms of knowing the legislation, knowing the systems, knowing the people, it's really, really important.
00:18:51.039 --> 00:18:54.000
I mean, you can throw AI on the data and it'll bring you back an answer.
00:18:54.160 --> 00:19:05.200
Having that, the same as what I'm doing in terms of information leadership, is that converse that that conversation, that collaboration with staff who have to do a lot of work to you know to put information in the FOY.
00:19:05.519 --> 00:19:10.160
Having the team there with that skill and knowledge to support them on that journey, you can't automate that.
00:19:10.480 --> 00:19:17.039
You know, you just can't, because that is just human interaction between you know, civil servants and colleagues to bring people on the journey.
00:19:17.200 --> 00:19:25.519
And as well as that, whenever you know a conflict does come up, you're able to, you know, you've built those relationships to get you through that without being scared or you know, people falling out.
00:19:25.759 --> 00:19:32.000
So it it is really, really vital that we don't automate the human interactions to get the results that we need.
00:19:32.240 --> 00:19:32.799
Yeah, 100%.
00:19:33.039 --> 00:19:36.319
So there's still a human behind the job at the end of the day going forward.
00:19:36.480 --> 00:19:39.359
So it's been absolutely sensational to have you on the show today.
00:19:39.440 --> 00:19:44.960
Uh Jenny, how can listeners reach out to you if they want to know more about your old job or your new job?
00:19:45.119 --> 00:19:50.000
Um, as you know, Jackie, I'm not great on LinkedIn, but I am on there, so please um follow me on LinkedIn.
00:19:50.160 --> 00:19:53.119
Um, and if you DM me, I'll I'll eventually get back to you.
00:19:53.440 --> 00:19:58.880
Thank you for listening to the journals of the Information Entrepreneur with me, Jacqueline Stockwell.
00:19:59.039 --> 00:20:04.799
I hope you found this episode inspiring and helpful and have some takeaway tips that can be useful to you.
00:20:05.039 --> 00:20:09.039
If you liked this episode, please like, review, and share it with your friends.
00:20:09.200 --> 00:20:14.720
Your support helps us reach more information leaders to stay inspired and listen to great content.
00:20:14.960 --> 00:20:19.359
Want to test out your strengths and weaknesses and measure it against our Empower framework?
00:20:19.519 --> 00:20:21.119
Please complete the scorecard.
00:20:21.200 --> 00:20:24.079
It's a great way to improve and evaluate your skills.
00:20:24.319 --> 00:20:28.079
You can find the scorecard at the end of the description of this podcast.
00:20:28.319 --> 00:20:35.839
Stay tuned for a new podcast every Thursday and remember to be bold, be brave, and be beautiful.