iPhone vs. Purpose-Built Android in Healthcare | Will Mobley (BradyIPS) | Frontline Mobility Edge

WEBVTT
00:00:04.000 --> 00:00:10.880
I'm Brett Cooper and this is the Frontline Mobility Edge, where we discuss the latest in mobile device technologies and how they're shaping the frontline landscape business.
00:00:11.039 --> 00:00:12.000
Thank you for joining us.
00:00:12.080 --> 00:00:13.279
Let's get started.
00:00:13.759 --> 00:00:17.440
Hello, welcome to another episode of the Blue Fletch Enterprise Mobility Roundup Podcast.
00:00:17.519 --> 00:00:23.039
I'm Brett Cooper joined today by Will Mobley from Brady IPS.
00:00:23.120 --> 00:00:23.760
Did I get it right?
00:00:23.920 --> 00:00:24.239
Correct.
00:00:24.320 --> 00:00:24.719
Spot on.
00:00:24.879 --> 00:00:25.039
Awesome.
00:00:25.199 --> 00:00:25.440
Awesome.
00:00:25.519 --> 00:00:26.719
Can you like just hop into it?
00:00:26.800 --> 00:00:28.399
Can you give us like the background?
00:00:28.559 --> 00:00:36.640
So for those that don't know, Honeywell P PSS was bought by Brady and is now a division of Brady Technologies.
00:00:36.719 --> 00:00:41.280
Maybe is that can you give us an overview of what Brady does and what you guys do within Brady?
00:00:42.000 --> 00:00:42.399
Absolutely.
00:01:00.479 --> 00:01:01.759
And that's uh that includes us.
00:01:01.920 --> 00:01:07.359
So now our division uh is called Brady Intelligent Productivity Solutions.
00:01:07.439 --> 00:01:15.439
So it's taking our traditional uh barcode, RFID, scanning, printing, and mobile computing arm of solutions in the AIDC space.
00:01:15.599 --> 00:01:18.239
And now we're a separate division of uh Brady Corp.
00:01:18.480 --> 00:01:26.319
Uh so now we've got our space along with Brady's uh traditional identification uh area, and together we form uh Brady Corp.
00:01:26.400 --> 00:01:30.799
So it's uh it's exciting and a lot of a lot of new things happening, but all positive.
00:01:31.439 --> 00:01:32.400
A lot of moving parts there.
00:01:32.480 --> 00:01:35.280
And and you're you talk about your role within within Brady.
00:01:35.439 --> 00:01:37.120
I I know you do just for the folks listening.
00:01:37.280 --> 00:01:38.480
What's uh what do you focus on?
00:01:38.640 --> 00:01:42.239
What areas you're mainly uh doing day-to-day, week to week?
00:01:42.640 --> 00:01:46.719
Yeah, I'm uh so I'm our on our strategic healthcare team on the IPS side.
00:01:46.879 --> 00:01:50.319
So I focus uh with our strategic health systems in the Northeast.
00:01:50.400 --> 00:01:56.879
So from from Maine to South Carolina, working with uh our larger health systems around uh technology for data collection.
00:01:56.959 --> 00:02:24.960
So a lot of uh that scanning, printing, and mobile computing around, whether it's inside the clinical space or inside the four walls of a hospital, could be outside the four walls or even in the supply chain and all facets of a health system, and just helping them uh with their technology, with uh data collection, uh patient safety, uh, as well along with data accuracy that's we're helping them uh keep their operations smooth and running, but also their their clinicians uh operate on a full full pace with productivity uh at the at the primary focus.
00:02:25.280 --> 00:02:26.560
So that's your day-to-day.
00:02:26.639 --> 00:02:29.919
And then uh I know you have a side gig, which I'm gonna throw us out there.
00:02:30.000 --> 00:02:38.560
So you uh on LinkedIn, if you follow follow Will, he's got some funny videos out there, but um, I believe it's beyond the labels, you're sort of like the the area we're focused on.
00:02:38.719 --> 00:02:43.280
Um my favorite was the uh I think you got a soccer player to kick a device.
00:02:43.439 --> 00:02:44.080
Is that correct?
00:02:44.400 --> 00:02:45.439
That that's true.
00:02:46.159 --> 00:02:48.479
So it's been a been a fun uh side gig.
00:02:48.719 --> 00:02:49.520
What's the origin of that?
00:02:49.759 --> 00:02:55.039
I I guess what you're just like this is all this uh these rugged device videos are boring.
00:02:55.120 --> 00:02:56.400
I'm gonna do something interesting myself.
00:02:56.479 --> 00:02:58.719
Is that the itchy decide to scratch there?
00:02:59.039 --> 00:03:00.240
I was bored, right?
00:03:01.039 --> 00:03:02.400
Didn't have enough to do.
00:03:02.639 --> 00:03:28.400
Uh no, it we wanted to do something different and give people uh a behind-the-scenes look at at our division uh of Brady, but uh also lend insights to the the experts we have on hand, but also show in a fun way uh our solutions, doing extreme product testing in maybe environments that you wouldn't normally put a device uh on the hockey rink, uh in a baseball field, a soccer field, dropping them from three stories up, you name it.
00:03:28.560 --> 00:03:39.120
But uh the goal was to provide insights, uh demonstrate our devices' durability and and how they can uh fix or survive in any environment you put them in, but also add some humor too.
00:03:39.280 --> 00:03:42.479
So it's been uh been a fun video series, uh for sure.
00:03:42.719 --> 00:03:46.879
Yeah, so definitely check it out if you're if you're on LinkedIn scrolling, it it's a good follow.
00:03:47.039 --> 00:03:49.120
I one uh one other just note on that.
00:03:49.199 --> 00:03:57.439
I know the the sports theme piece, you are formerly you are a football kicker um for multiple years in college.
00:03:57.680 --> 00:04:01.120
Um do you still uh are you still to kick a ball?
00:04:01.680 --> 00:04:02.960
I think I can still kick it.
00:04:03.039 --> 00:04:07.840
I I have not for many years, but it's been a few, but I think I can still kick it.
00:04:08.080 --> 00:04:10.479
Yeah, it is uh it looks a lot easier on TV.
00:04:10.560 --> 00:04:14.159
I've tried it before, and uh kicking a football through the uprights is incredibly difficult.
00:04:14.319 --> 00:04:14.639
Yeah.
00:04:15.039 --> 00:04:15.919
It is it is funny.
00:04:16.000 --> 00:04:23.920
And now you see it with the college game day guys, the with the kids uh training to get the scholarships with Pat McAfee and and those guys on Saturdays.
00:04:24.000 --> 00:04:30.079
It's it's fun to fun to see people have an interest in kicking, but they realize it's it's more to it than just swinging your leg.
00:04:30.399 --> 00:04:34.000
It is uh yeah, I was it's I was definitely humbled when I gave it a try.
00:04:36.240 --> 00:04:36.800
I'll give it a try.
00:04:37.439 --> 00:04:38.160
Nope.
00:04:38.959 --> 00:04:40.079
Not gonna happen.
00:04:40.399 --> 00:04:40.720
Awesome.
00:04:40.959 --> 00:04:58.720
All right, so so today's discussion um from a topic standpoint, I'm gonna it's a it's a long topic, but really just focused on the frontline workers' experience and how that leads to the success or failure of these initiatives in large enterprises.
00:04:58.800 --> 00:05:02.959
And we'll focus on healthcare, and we'll we'll dive into that here as one of the subtopics.
00:05:03.040 --> 00:05:10.720
But as a background, from a standpoint of, I think there was a McKinsey report talked about um large enterprise transformation projects.
00:05:10.959 --> 00:05:29.040
And I think about put it pegged it at around 20, 25% of those are successful, uh, 20% of them are complete failures, and there's some room in between, which is more than half of them are, you know, in this sort of a valley of despair uh where they're just not working.
00:05:29.279 --> 00:05:38.399
And I always think about the experience I've had with a couple clients where you know you talk to the CIO or somebody at the C-suite, and they're like, we want to get a new device that's 20% faster.
00:05:38.480 --> 00:05:41.759
You know, if all of our stuff is 20% faster, our ROI is gonna go up 20%.
00:05:42.079 --> 00:05:44.959
So I feel like that's the the boardroom conversation.
00:05:45.120 --> 00:05:53.199
And then there's all these people on the front line that are you know day-to-day using these things that they have no input into that decision or those types of decisions.
00:05:53.360 --> 00:06:06.639
So um I think the the first thing I think about is like the spec sheet of it's faster or it has you know this drop spec, whatever this is, is not always the nexus for what makes a program successful.
00:06:06.879 --> 00:06:19.600
Like outside of like the specs, what do you think about what are the areas that you talk about when you talk with clients around thinking about that experience, that that frontline user or that person who's gonna be actually using the device for eight to ten hours a day?
00:06:19.920 --> 00:06:28.079
Yeah, I think that's a great, great question because uh speeds and feeds specs are all great on paper, but when you bring it to life, it sometimes things are different.
00:06:28.319 --> 00:06:34.560
And so our our focus is really how do we have a discussion around the people, the process, and the technology.
00:06:34.720 --> 00:06:43.199
And so it's focusing first on the users, especially in the healthcare space where the clinicians are are the primary focus and they're already busy.
00:06:43.279 --> 00:06:51.120
And so adding more complexity to their day is is really not ideal, not for just for time and money is at stake, but lives are too.
00:06:51.279 --> 00:06:56.560
And so we're focused on how can we improve their experience, uh, then really it's also look at the workflow.
00:06:56.720 --> 00:07:10.800
And that's what we're talking about a lot is uh how can we impact the people in a positive manner, but also uh look at the workflow and ensure that is that the most productive or best use of the technology you're using, or the best way uh to do what you're currently doing, whatever that may be.
00:07:10.959 --> 00:07:13.759
And then we can look at what's the best technology fit is.
00:07:13.920 --> 00:07:22.079
But really, I don't like to talk about this scanner can scan 30 feet, and that's further or less further than than this other competitor or this other product.
00:07:22.160 --> 00:07:38.560
Uh for us, it's focused on on all the things that take place inside a customer's environment, and then we can look at the right technology, and then we from there we can determine what specs might be fit best, but really it's ensuring that we're prioritizing the people, their process, and then we can look at the technology for us.
00:07:38.959 --> 00:07:46.319
When you think about that that total cost of sticker price, somebody will look at it and say, hey, an iPhone costs 900 bucks.
00:07:46.560 --> 00:07:52.319
This Brady device is twice as expensive and it's 30% slower according to the CPU spec.
00:07:52.480 --> 00:07:54.480
How do you combat that when you're having those discussions?
00:07:54.560 --> 00:08:05.920
Like what is the what are the things you do to get people from this is the iPhone everybody loves to this is a device that's actually gonna make that difference for your employees?
00:08:06.480 --> 00:08:09.920
I think it it's it's a great point because we get that a lot.
00:08:10.079 --> 00:08:14.720
And it it sort of depends on who you're talking with, what the the best approach might be.
00:08:14.879 --> 00:08:19.920
But but oftentimes when you look at the total cost of something, we're looking at the full life cycle.
00:08:20.160 --> 00:08:34.399
So because our devices, our our technology and our solutions are all built for the enterprise, they're they're rugged, they can survive drops, thousands of them, whether it's a guy punning it or a hockey stick, you name it, uh, but we can survive that.
00:08:34.559 --> 00:08:37.759
But we're also we're built uh built to last, really.
00:08:37.919 --> 00:08:44.720
And so our devices are typically lasting seven, eight, nine, ten years in some cases, depending on what you're doing with it.
00:08:44.879 --> 00:08:52.480
Whereas an iPhone, you look at an iPhone or consumer grade device of similar types, are lasting just a couple years, two or three, especially in healthcare.
00:08:52.559 --> 00:08:54.879
They're typically replaced every two or three years.
00:08:55.039 --> 00:09:02.240
And so, although the initial sticker price might be higher, you're not having to buy as much as many accessories.
00:09:02.480 --> 00:09:09.039
Device lasts longer, and it's it's built uh to survive different environments, so it's not gonna break as often.
00:09:09.200 --> 00:09:20.080
When you look at a consumer grade device, uh in a single lifetime of one of my devices, it's you're gonna have to have two or three or sometimes four different versions of a consumer grade iPhone.
00:09:20.320 --> 00:09:30.480
You're gonna have to purchase typically accessories that'll be adding to your expense that are outside the traditional uh need of just a device itself, and and they break more often.
00:09:30.559 --> 00:09:41.039
If I how often are you gonna drop your iPhone or your personal phone on purpose or by accident, whatever it may be, from a six-foot stand, and uh it's gonna survive and you're not gonna be scared that it's gonna crack.
00:09:41.200 --> 00:09:44.720
I don't have that concern with our solutions, but with a personal device, it does.
00:09:44.799 --> 00:09:50.320
And with nurses, I think the only people that can break devices more than a group of 12-year-old boys are nurses.
00:09:50.399 --> 00:09:53.600
They just seem to find a way to break things.
00:09:53.759 --> 00:10:08.159
And so having devices that don't just solve what you're doing, but also can last longer than just one drop or one day on the job, that's uh that tells a big story, especially when it comes to solutions like ours, which are purpose-built for those environments.
00:10:08.879 --> 00:10:11.919
So a follow-on question on the healthcare piece.
00:10:12.000 --> 00:10:14.960
Um, and this goes to my, I'm gonna call my gross back.
00:10:15.039 --> 00:10:15.919
So you mentioned 12-year-olds.
00:10:16.000 --> 00:10:17.840
I have a 12-year-old who has an iPhone.
00:10:18.159 --> 00:10:19.919
I look at it and it is gross.
00:10:20.000 --> 00:10:25.039
Like he's got grubby hands, he's like playing sport ball, whatever, and it's like got mud on there and food, whatever.
00:10:25.120 --> 00:10:27.039
He's eating while he's looking at his phone.
00:10:27.200 --> 00:10:34.159
Um, the ability to clean devices is something that I think about this a lot, which is a really big thing in healthcare.
00:10:34.240 --> 00:10:43.679
You took talk about what healthcare organizations have to do or required to do for cleaning devices and how that might differ than a consumer Android or iPhone device.
00:10:44.320 --> 00:10:51.440
It's that's a great point because infections control or just uh cleanliness as a whole is critical in a healthcare space.
00:10:51.600 --> 00:10:58.080
There's not just uh germs that we pick up on a daily basis, but other germs that are just inside the hospital in general.
00:10:58.320 --> 00:11:02.240
And uh you drop it on the floor or whatever it may be, it can pick up a lot from it.
00:11:02.320 --> 00:11:08.080
And so with an iPhone or something, uh typically there's there's a case, but it's maybe not that protective.
00:11:08.240 --> 00:11:21.840
Uh and it even if iPhones as a whole, you start to get uh hydrogen peroxide or purple wipes, or some of these other detergents or chemicals that are used to clean them, that'll wear away fast, especially on a on a personal device.
00:11:21.919 --> 00:11:23.600
That's gonna wear it down quickly.
00:11:23.759 --> 00:11:37.519
But if I take one of our devices, which are disinfectant ready, so they can withstand uh those hydrogen peroxides or purple wipes, you can wipe them hundreds of times a day, and it's not gonna deteriorate the plastics uh as in the same way that it would an iPhone.
00:11:37.600 --> 00:11:48.159
And so that, again, to your point, it not only keeps them clean, but it also protects the device long term so that you're using that device, not having to replace it because you're simply doing your job for it.
00:11:48.320 --> 00:11:51.519
Uh just by cleaning it, that's part of your role as a nurse.
00:11:51.600 --> 00:11:57.279
And so if you're not able to do that, then you're not effectively using the technology or being able to do your role properly.
00:11:57.679 --> 00:12:01.600
Um the other follow-on question for that is ergonomics.
00:12:01.679 --> 00:12:09.919
I last year had a customer, the healthcare customer, that um they chose specifically to go with the Honeywell device.
00:12:10.080 --> 00:12:16.639
You know, I can't remember the exact quote, I'll paraphrase it, but he's like, he's like, yeah, the Honeywell device fit in our nurses' hands better.
00:12:16.720 --> 00:12:30.240
Um, you know, we have 90% women on staff, and the device is just well designed to hold your hand all day, whereas the other device they looked at was larger, heavier, and he's like, they've they had zero interest in that device when we started piloting.
00:12:30.480 --> 00:12:34.240
Can you talk about ergonomics when you think about that, the healthcare space?
00:12:35.039 --> 00:12:48.799
I give absolutely I give credit to our design team uh as we come out with new solutions, whether it's a mobile device or a scanner, printer, whatever it is, they're they're in the fields talking directly with users and end customers to get that feedback.
00:12:48.960 --> 00:12:56.240
And I think you you hit the point that we recognize that's that's part of our story when we talk about a device that's built for the enterprise.
00:12:56.399 --> 00:13:05.279
It's not just the directedness, it's not just the durability, but it's also a device that's built to last and also fit and be used 24-7, really.
00:13:05.440 --> 00:13:17.600
And so an iPhone is great, uh, it looks good, it feels good, but it's not really conducive to be being held or used all day for your shifts for a nurse who's using it for a 12-hour shift or whoever it may be.
00:13:17.759 --> 00:13:20.960
And so we really take uh a deep expertise in that.
00:13:21.120 --> 00:13:39.200
And so whether it's the curved edges to make it easier to put your hand around and shape to it, or uh the ledges that are designed to rest your fingers on so it's easy to type and text or call, or even just the way uh areas where the scan engines are positioned, just to make it easier so you're not having to twist your arms in different directions.
00:13:39.279 --> 00:13:47.200
It seems such like a simple thing, but just where it's placed, now it's just a simple uh six-inch move versus now adjusting your whole entire arm and shoulder.
00:13:47.360 --> 00:13:59.200
And some of those things they they seem so basic, but when you start to add it up over the hundreds of scans that happen a day for a nurse or or whoever it may be, that adds up quick and can drastically change the experience.
00:13:59.360 --> 00:14:10.000
And so that comfort, that that familiarity, if I could say that word properly, uh, and part of that goes back to that experience of the clinicians or the people that we talked about earlier.
00:14:10.320 --> 00:14:15.440
That's a major focus of us that's built into what we do and how we design our products.
00:14:16.080 --> 00:14:24.559
When you when you're doing like pilots and rollouts, I think one of the things I always look for is the make or break factors and the adoption.
00:14:24.639 --> 00:14:36.639
So that those users in the field, like when you walk the floor of a hospital or a clinical unit or a private practice during one of these, how do you know whether it's working?
00:14:36.720 --> 00:14:42.399
What are the things you're looking for when you're like, you know, is it people using the devices, is people leaving the devices, wherever?
00:14:42.480 --> 00:14:46.480
Like, well, how do you know that people like it and it's actually going to be successful?
00:14:46.879 --> 00:14:47.120
Yeah.
00:14:47.440 --> 00:14:52.639
I think the first thing is are they using it for the the the purpose, what it was built for?
00:14:52.799 --> 00:14:58.000
Like, for example, a lot of people bought Pelotons during COVID, but now they're just used as close racks, right?
00:14:58.159 --> 00:15:02.559
So they're using them, sure, but it's not for the designed purpose in a way.
00:15:02.720 --> 00:15:06.960
And so I think that's the first thing is uh let's take uh a mobile device, for example.
00:15:07.120 --> 00:15:09.039
Are you are you using it for what it's designed for?
00:15:09.120 --> 00:15:10.720
It's not just something that's in your pocket.
00:15:10.879 --> 00:15:27.919
Uh, but then also what excites me actually is now when we start to walk the floor, for example, and communicate uh and see what those nurses or those clinicians, those frontline workers, what they're doing and how they're using devices, what excites me is when they start to find ways that they can use devices for other workflows.
00:15:28.080 --> 00:15:34.000
So yeah, I'm using it for bedside clinical nursing, but then they start to get excited and say, well, what if we used it for this?
00:15:34.080 --> 00:15:35.360
Or what if we used it for that?
00:15:35.519 --> 00:15:40.799
And now you're starting to see uh people that are not just using technology, but they're embracing it.
00:15:40.960 --> 00:15:52.240
And that's that's real exciting for us on the Brady side of things to people pe to see people enjoying our devices, but also seeing them leverage it to now connect their entire health system.
00:15:52.399 --> 00:16:02.799
Now we're not just talking about one workflow, but now we're talking about how we can connect different departments and different workflows together so that everybody's communicating, everybody's on the same page, leveraging the technology uh at hand.
00:16:02.879 --> 00:16:09.840
And that that's a big differentiator than just somebody who simply uh is using it just to get by or just has it in their pocket because they have to.
00:16:10.159 --> 00:16:11.200
Yeah, it's a good point.
00:16:11.279 --> 00:16:19.039
I I always think about uh I have this persona in my head when I'm helping with deployments, and um there's there's the persona, and I've named him, his name is Carl.
00:16:19.200 --> 00:16:24.320
And Carl Carl works in receiving, and Carl hates all new technology that corporate has ever given him.
00:16:24.480 --> 00:16:38.799
Um how do you leverage those Carls out there, the people that are the the native sayers, when you're doing a deployment or helping a client or partner get stuff out the door, how do you actually leverage that person to make the experience better?
00:16:39.279 --> 00:16:45.840
Yeah, I I think it's to us, obviously we can't talk to everybody, but uh beforehand, although although we want to.
00:16:46.000 --> 00:16:50.960
But I think it's really uh in your your preparation is key for any deployment.
00:16:51.120 --> 00:16:56.480
And I think uh for that it's talking to users at the user level, understanding their experience.
00:16:56.639 --> 00:17:05.839
But it's not just to me, it's not just listening to answer to say, oh, how can I take what you say and then plug my solution in as the answer, but also listening to understand.
00:17:05.920 --> 00:17:08.480
That's what it's more we primarily focus around.
00:17:08.640 --> 00:17:10.319
Yes, we want our technology to be deployed.
00:17:10.480 --> 00:17:18.559
Yes, we want Carl in this case to use our technology, but how can we really understand what Carl is thinking and why maybe he's hesitant to change?
00:17:18.720 --> 00:17:22.559
And I think that's the big thing you mentioned is is change, change management.
00:17:22.640 --> 00:17:25.599
And what does that look like for us?
00:17:25.680 --> 00:17:26.559
How do we help with that?
00:17:26.640 --> 00:17:28.319
But also how's an organization do that?
00:17:28.640 --> 00:17:35.920
And one of the key components is preparation uh for it, but also uh for us is a key group that I call superusers.
00:17:36.000 --> 00:17:44.960
And this is where I've really seen success with some of our deployments and things as we introduce new technology is having people who work the floor.
00:17:45.039 --> 00:17:50.160
So they're they're clinicians, they're frontline workers, they're in the supply chain, wherever it may be, that we're deploying technology.
00:17:50.319 --> 00:18:00.640
And we we work with them to get specialized training, so they're more familiar with our projects, our products, uh, they understand what's happening, uh, but also they're able to convey the why behind why we're doing it.
00:18:00.799 --> 00:18:04.960
And it's not just here's a new device, but here's a device and here's why we're doing it, Carl.
00:18:05.200 --> 00:18:12.240
Because here's the value it can enhance your experience, and this is what the change will look like and improved with your with the technology.
00:18:12.400 --> 00:18:27.920
But then the superusers can also express to Carl in his language, because they're I'm not their day-to-day 24-7, but they can express uh in Carl's language uh why it matters or what the solution is that needs to be fixed, or where the value is uh from our solutions as well.
00:18:28.079 --> 00:18:43.200
So uh being able to integrate, being able to talk to people, listen to them carefully, but then also having uh uh teammates, if you will, on hand for those deployments who are in the facility working, uh that's that's a value, especially when you're doing a rollout that requires a big change for people.
00:18:43.599 --> 00:18:45.440
Well, I like how you called out change management there.
00:18:45.519 --> 00:18:58.319
It made me think of the one of the other questions I had for you is around you know, when you put a new piece of technology into an environment, how do you deal with the existing processes that suck?
00:18:58.480 --> 00:19:10.960
And uh the the kind of example of this, let's say you're a a um healthcare organization, you have to fill out five sheets of paper for this one procedure, and then they move that, they're like, well, let's put some mobile devices because that'll make it better.
00:19:11.039 --> 00:19:24.559
And they they still have the user has to go to five different apps to go do things for a procedure, and it's like it's the same uh subpar process with new technology, and it just it it just makes users more frustrated.
00:19:24.640 --> 00:19:29.839
But how do you navigate that or how do you guide people on thinking about that change management around the process side?
00:19:30.240 --> 00:19:32.319
Yeah, it's a great, a great uh question.
00:19:32.400 --> 00:19:36.480
And there's a couple, I guess as a whole, ways we can look at it.
00:19:36.640 --> 00:19:39.839
One of them is actually our part of our experience team, our user experience team.
00:19:40.000 --> 00:20:07.279
So we can cut their uh black belt, lean six sigma trained, and they can actually come and if whether it's a manual process or you mentioned a virtual process, we can come on site and do a site walkthrough and identify what are you currently doing today, what's your current process, and what would it look like if you had a different technology in place, or if we're talking a mobility device, what would it look like to have a mobile device in here and how can we maybe eliminate some of those extra steps?
00:20:07.440 --> 00:20:14.640
Or uh you mentioned paperwork, for example, but how can we eliminate extra things that might take up more time and make you more efficient, more productive?
00:20:14.799 --> 00:20:28.640
So that's that's one approach we would take uh just to level the ground and uh fully free, but being able to get on site and uh see what are you experiencing today and what would it look like if it could be improved through that process.
00:20:28.880 --> 00:20:34.079
But then it's it's also I think you change the biggest thing, nobody wants to change unless they ask for it.
00:20:34.160 --> 00:20:37.119
And so I think understanding that why is critical.
00:20:37.279 --> 00:20:39.359
Uh, here's why we're doing it.
00:20:39.599 --> 00:20:53.440
Okay, today, if we take your app example, uh today we're going through five apps, but by leveraging this change of technology using a mobile device, we're gonna be able to now work with those app companies or find a new solution that doesn't require you to go to five different apps.
00:20:53.519 --> 00:20:56.799
And so this is the first step in making your life easier.
00:20:56.960 --> 00:21:08.160
So I think explaining that, the why behind what you're doing from a big picture and then bringing it down into the the users' levels and where their role is in that why process, that transformation process is critical.
00:21:08.319 --> 00:21:21.759
And so, okay, today there still might be a couple steps according to your example, but we're using this as a platform to get to the next step in our journey, which will help eliminate all five of those apps or or whatever that may be for what the example is for the customer.
00:21:22.400 --> 00:21:23.759
Make the process better.
00:21:24.079 --> 00:21:24.400
Yeah.
00:21:24.559 --> 00:21:24.799
Yeah.
00:21:24.960 --> 00:21:35.039
Um, last topic I had for you, so you you touched on this just healthcare and why it's one of the hardest industries to operate in from a technology perspective.
00:21:35.279 --> 00:21:53.119
Like if you had to summarize, and I think you touched on this a little bit before, like when you think about how difficult healthcare is, especially in North America, it's difficult everywhere, but North America in particular, like what are the things that make it really, really hard to put new technology into healthcare that does all these improvements that you articulated earlier?
00:21:53.599 --> 00:21:54.720
How long do we have?
00:21:55.039 --> 00:21:56.799
Uh you got four minutes, go.
00:21:57.119 --> 00:21:57.920
Yeah, really.
00:21:58.319 --> 00:22:08.799
Uh Um, I think a few things are are uh a challenge, and it's partially because there's a lot of different stakeholders in healthcare.
00:22:08.880 --> 00:22:15.200
Uh if I go to a supply chain or a warehouse customer, maybe it's IT, it's operations, it's purchasing.
00:22:15.279 --> 00:22:22.480
Uh, but for for healthcare, you still have all three of those departments, but then you have nursing informatics, you have clinical informatics, the frontline workers.
00:22:22.640 --> 00:22:27.279
And so there's more, I think, stakeholders in the game, which is which is not a bad thing.
00:22:27.440 --> 00:22:34.000
I mean, you want that when you're deploying technology that will impact patient safety and patient lives when they're at stake.
00:22:34.160 --> 00:22:39.519
But uh it just adds sometimes extra complexity and and layers to that decision-making process.
00:22:39.680 --> 00:22:42.400
They're also looking at from a security standpoint, right?
00:22:42.480 --> 00:22:52.319
The uh in healthcare, we have access to to patients' health history, their payment, their insurance information, their social security numbers, et cetera, all at someone's fingertips 24-7.
00:22:52.799 --> 00:23:05.599
And so being ensuring that devices are secure, uh HIPAA-approved, they make they uh validated by the EMR or the EHR, and they're prepared to withhold all that information is critical.
00:23:05.759 --> 00:23:14.480
And that's part of the reason why health systems uh are attacked more than any other uh vertical for data breaches or for attempts at malicious malware.
00:23:14.559 --> 00:23:21.599
And it's also more than twice as expensive too to recover from that because you have such critical information at someone's fingertips.
00:23:21.680 --> 00:23:27.920
Uh and so having devices that are required and able to be more secure is critical and to go through that process ahead of time.
00:23:28.160 --> 00:23:41.519
And then you mentioned uh earlier to the infectious control side of things, uh devices that can withstand a clinical environment, that can withstand not just a durability of dropping device or however that may be, but then also being able to be wiped down and cleaned, et cetera.
00:23:41.680 --> 00:23:42.960
So there's there's different levels.
00:23:43.039 --> 00:23:49.920
And I think the the fourth one for me is part of that stakeholders, but but uh nurses and clinicians, they're they're also highly educated.
00:23:50.079 --> 00:24:02.640
And so it's not just uh we can't necessarily, or a health system can't just give them a device and run and say, hey, this is what we're gonna do, as you could to maybe a teenager at a grocery store uh who's just doing that for the high school job, for example.
00:24:02.799 --> 00:24:12.000
Uh, but they they require devices and technology that that makes sense, is explained to them, but also can help and uh enable and improve their process.
00:24:12.319 --> 00:24:15.119
Because a lot of them, this is what works for me, this is what I'm gonna do.
00:24:15.200 --> 00:24:19.680
And so if you just throw technology at them, it's gonna become that Peloton that just has clothes hanging from it.
00:24:19.759 --> 00:24:21.279
It's just it's not gonna be used.
00:24:21.440 --> 00:24:26.480
And so deploying properly and effectively, but also with the clinician in mind, is critical.
00:24:26.559 --> 00:24:31.920
And sometimes that can be more challenging than just uh giving a device to a store and and letting them use it.
00:24:32.079 --> 00:24:33.680
Uh, but it's a lot more steps to it.
00:24:34.000 --> 00:24:35.759
Yeah, it's a lot a lot of pieces there.
00:24:36.000 --> 00:24:46.079
The one of those fall-ins I have from that, it's I I feel like iPhones have been very prevalent in healthcare over the last 10 years.
00:24:46.240 --> 00:25:01.279
Um, I'm not sure if it's driven by just Epic and their early support of it with a lot of EHR supporting iPhones or from doctors, like you just mentioned, are typically um highly compensated individuals, which the iPhones use more um in that demographic.
00:25:02.000 --> 00:25:06.240
What is your theory around you know why iPhone is so prevalent in healthcare?
00:25:06.319 --> 00:25:15.680
And then also just some of your thoughts on why health organizations rethink that about going towards the Android uh you know designed operating systems like you guys sell.
00:25:16.319 --> 00:25:20.319
I think iPhone uh there's a few reasons why it's it's so uh prevalent.
00:25:20.400 --> 00:25:27.119
Uh is part of it is some of the major EMARs, so Epic, for example, and others, that's what they they build off on first.
00:25:27.279 --> 00:25:36.240
So they're the building, their first step uh of is each implementation or each new build they have of their software is designed on iOS and for iOS.
00:25:36.400 --> 00:25:41.599
And so sometimes Android's view is viewed as the secondary option or lagging behind.
00:25:41.759 --> 00:25:42.480
That's changing.
00:25:42.559 --> 00:25:45.599
I'll say that's changing, but that's historically part of the reason why.
00:25:45.759 --> 00:26:05.599
I think another reason is um because nurses, because they are highly educated, there's been challenges in the nursing uh field for nursing shortages and health systems don't want to put anything at risk that could uh or do anything that could put them at risk to lose their nurses or new lose their employees, they don't want to upset the Apple cart.
00:26:05.680 --> 00:26:06.559
That's literally.
00:26:06.799 --> 00:26:13.920
And so nurses, because they're highly educated, uh, they're important, they're valuable team members, but they also they want to use devices that they want to use.
00:26:14.079 --> 00:26:23.519
And so because they use an iPhone on a daily basis, that's what they're comfortable with, that's what they prefer to use uh as their daily roles instead of having to learn something new.
00:26:23.599 --> 00:26:24.960
And I don't really fault them for that.
00:26:25.119 --> 00:26:26.720
I'd like to keep it simple too.
00:26:26.880 --> 00:26:36.000
And so because uh health systems don't want to upset their employee or their nursing base when especially when there's a shortage out there, they just roll with what the nurses want and desire.
00:26:36.160 --> 00:26:45.920
So I think those are a couple of reasons that have have have been relevant and that we've seen a lot as we talk to different health systems, is that it's driven by the EMR, but also from the nurses.
00:26:46.079 --> 00:26:54.240
But we're starting to see a shift, I'd say, in in uh, especially from an IT perspective, but even from clinicians too, be more open to other options.
00:26:54.400 --> 00:26:58.640
And I think it's primarily revolving around the idea of doing more with less.
00:26:59.119 --> 00:27:01.279
We're all being asked to do more right now.
00:27:01.359 --> 00:27:07.440
Uh you and I, whether it's a nurse in the in in a clinical environment, whatever it may be, we're all being asked to do more.
00:27:07.519 --> 00:27:09.440
And health systems are feeling that effect too.
00:27:09.680 --> 00:27:18.720
Do more, serve more people, offer more services, but do it with less funding, less support, less resources, uh, sometimes less people, and sometimes less technology as well.
00:27:18.880 --> 00:27:28.559
So the health systems today are looking for people they can partner with, but also technology they can provide that can enable them to do more with less.
00:27:28.720 --> 00:27:44.559
And I think a great example of that, if not the greatest example, is our mobile devices that allow you to take two, three, four, sometimes five devices, a scanner, a pager, uh a computer in some cases, and take that all into a single device.
00:27:44.720 --> 00:27:46.880
And now I can have all of that at my fingertips.
00:27:47.039 --> 00:27:57.359
And now my clinicians can be mobile, they can chart on the go, we can leverage ambient listening, we can scan, we can talk, we can uh take pictures, we can communicate all from a single device.
00:27:57.519 --> 00:27:59.359
And that enables them to do more with less.
00:27:59.440 --> 00:28:05.759
And by the way, that device also lasts longer and is more comfortable for them to use long term throughout their shift.
00:28:05.920 --> 00:28:21.519
So I think uh we're seeing a big change, we're starting to see a change, especially as healthcare prioritizes mobility in terms of where they're giving care, but also what they're giving in terms of technology, but also seeing that shift uh in an interest in Android and purpose-built solutions like ours.
00:28:22.640 --> 00:28:23.119
Good answer.
00:28:23.200 --> 00:28:23.519
Thank you.
00:28:23.599 --> 00:28:25.039
Um, we're we're at time.
00:28:25.119 --> 00:28:28.720
I'm gonna summarize this key things we we we talked about or that I took away from this.
00:28:28.960 --> 00:28:37.359
First one is um the cost of a device is not just the the street price, it's what it costs over four or five years.
00:28:37.440 --> 00:28:38.559
I think you articulated that.
00:28:38.799 --> 00:28:40.880
Things like cleaning is incredibly critical.
00:28:41.039 --> 00:28:44.880
A lot of the um long-term support, drop specs is important.
00:28:45.039 --> 00:28:47.599
Um you know, focus on the end users.
00:28:47.680 --> 00:28:52.960
I as you look at deployments, you know, that example I gave around if fits in their hand better, it just feels better.
00:28:53.119 --> 00:28:56.480
Those types of things are really important as you're testing things in the field.
00:28:56.720 --> 00:29:06.400
Um the process, uh, you know, you you you talked about if you have a new device of technology going out there, make sure you're looking at your processes, updating those.
00:29:06.559 --> 00:29:08.960
You have a team of people that people can leverage for this.
00:29:09.119 --> 00:29:15.839
Um, and then the last one, I think just the yeah, the the shifting landscape of going from iOS to some of these newer devices.
00:29:15.920 --> 00:29:17.920
So it's it's a lot to uh to think about.
00:29:18.079 --> 00:29:27.039
Um just to close out with a will, if people are interested in learning more about your team, your solutions, Brady, what you guys can offer, where would they reach out to you at?
00:29:27.680 --> 00:29:29.759
You can connect with me on LinkedIn if you'd like.
00:29:29.839 --> 00:29:32.640
That's probably an easy, easy access point to it.
00:29:32.799 --> 00:29:39.039
But uh our our whole team is is available, ready to support from a healthcare dedicated focus, even outside the healthcare space.
00:29:39.119 --> 00:29:41.759
We've got uh resources available and ready.
00:29:41.920 --> 00:29:46.960
But uh, you can learn more on our on our website, BradyCorp uh there, or reach out to me on LinkedIn.
00:29:47.039 --> 00:29:48.319
I'd be happy to talk further.
00:29:48.559 --> 00:29:48.880
Awesome.
00:29:48.960 --> 00:29:51.839
And then conferences you'll be at in the next four to six months?
00:29:52.160 --> 00:29:52.400
Yes.
00:29:52.559 --> 00:30:01.119
Uh uh we'll we'll be at uh Vartech as an organization, VarTech, NRF, uh I think it's ProMat this year, or whichever one manufacturer.
00:30:01.920 --> 00:30:02.480
Yes in Chicago, yeah.
00:30:02.880 --> 00:30:05.680
ProMats this year, and then HIMS, of course, as well, Vive too.
00:30:05.759 --> 00:30:10.960
So the the key and major industry conferences we'll we'll have teams at, and then our team myself will be present too.
00:30:11.039 --> 00:30:13.279
So happy to support and talk with you further.
00:30:13.519 --> 00:30:13.759
Excellent.
00:30:13.839 --> 00:30:14.880
Will, thanks for being on today.
00:30:14.960 --> 00:30:16.799
And if anybody has questions on this, feel free to reach out to him.
00:30:16.960 --> 00:30:20.000
Will Mobley, M-O-B-L-E-Y on LinkedIn.
00:30:20.160 --> 00:30:22.000
Uh appreciate it and have a good one.
00:30:22.240 --> 00:30:22.720
Excellent.
00:30:22.880 --> 00:30:23.759
Thanks, Brett.
00:30:24.000 --> 00:30:26.559
Thank you for tuning in to the Frontline Mobility Edge.
00:30:26.720 --> 00:30:30.319
If you enjoyed this episode, make sure to subscribe for more content every month.
00:30:30.480 --> 00:30:35.119
If you'd like to learn more about Blue Fletch, check out the link in the description or visit us at bluefletch.com.
00:30:35.279 --> 00:30:36.480
See you next time.