WEBVTT
00:00:13.534 -->
00:00:15.737Hello everybody and welcome to Adjusted.
00:00:15.737 -->
00:00:22.721I'm your host, greg Hamlin, coming at you from Sweet Home, Alabama, and Berkeley Industrial Comp.
00:00:22.721 -->
00:00:26.532And I'm excited to share with you this rebroadcast.
00:00:26.532 -->
00:01:05.191One of the hot topics in the industry has been technology and how technology is transforming the insurance industry, especially on the claim side, and in this episode we had the opportunity to talk to Sam Neer, and Sam has a lot of experience when it comes to the claim side and technology, as he manages quite a bit of this as a project manager for us, and so I really enjoyed this dialogue as we talked about how we go through that process, what transformation looks like, what opportunities could still be ahead of us and what companies are doing to leverage that on the claim side.
00:01:05.191 -->
00:01:07.522So I hope you enjoy this episode.
00:01:07.983 -->
00:01:24.025As always, I encourage you to like, share and follow the podcast, as well as to leave a five-star review so we have an opportunity to help others find this podcast and enjoy the content we've created.
00:01:24.025 -->
00:01:30.305And, as always, I remind you to do right, think differently and don't forget to care.
00:01:30.305 -->
00:01:31.246Enjoy.
00:01:31.246 -->
00:01:33.391Welcome to Adjusted.
00:01:33.391 -->
00:01:39.340I'm your host, greg Hamlin, coming at you from beautiful Birmingham, alabama and Berkeley Industrial Comp.
00:01:39.340 -->
00:01:42.265And with me is my co-host for the day, matt Yelling.
00:01:42.846 -->
00:01:43.507Hello everyone.
00:01:43.507 -->
00:01:48.536This is Matthew Yelling, coming from St Louis, Missouri, along the banks of the mighty Mississippi.
00:01:49.581 -->
00:01:51.203So glad to have Matt with us.
00:01:51.203 -->
00:01:51.685Today.
00:01:51.685 -->
00:01:54.170We actually have a special guest with us.
00:01:54.170 -->
00:01:56.153That is with Berkeley.
00:01:56.153 -->
00:02:02.013Actually, it goes by the acronym BAM Tech, but Berkeley Alternative Markets Technology.
00:02:02.013 -->
00:02:08.973Our special guest for the day is Sam Neer, who is our group product manager at Berkeley Alternative Markets Tech.
00:02:08.973 -->
00:02:11.127So, sam, could you say hello to everybody.
00:02:11.580 -->
00:02:13.585Hey everybody, Very excited to be here.
00:02:13.585 -->
00:02:20.881Greg and Matt, and again I'm based out of Raleigh, North Carolina, where it's a little bit warmer not as warm as Birmingham, Alabama right now, but still there.
00:02:20.881 -->
00:02:29.481And I will say, no one wants to say Berkeley Alternative Markets Technology over and over, so we might just call it BAM Tech just for all of our sanity, if that's okay.
00:02:30.002 -->
00:02:31.025I think that's wise.
00:02:31.025 -->
00:02:32.368I think that's wise.
00:02:32.368 -->
00:02:44.293So the topic today this is something we've never really tackled in the nearly three years that I've been doing adjusted is claims and technology and the role that it plays in helping us do our jobs.
00:02:44.293 -->
00:02:54.944So I wanted to bring Sam in today to talk to us a little bit about that, since he is part of the Berkeley company that manages our technology to help us be successful.
00:02:54.944 -->
00:03:05.165Before we dive deep into the topic, Sam, I wanted to ask you a little bit about yourself, so I'm sure that you knew you were going to be in workers' compensation, right?
00:03:05.819 -->
00:03:07.002Greg, you knew it it's like.
00:03:07.002 -->
00:03:27.987And coming up as a small boy I would say to my dad with a glint in my eye one day, dad, I can do work in workers' compensation and a quippy line I'll have is either the way I ended up in the industry is either I found my way into making great technology products with great organizations and really affecting change, or I follow the goal of becoming the most stable, uninteresting version of myself.
00:03:27.987 -->
00:03:30.484One of the two, and again maybe it's a little bit of column.
00:03:30.625 -->
00:03:41.050A, maybe it's a little bit of column B hey there is a lot of stability in workers' compensation insurance, so that's the one positive right, it's something to be accounted for.
00:03:41.150 -->
00:03:58.152So, with the 30-second background again, I've been working in digital technology for the last 12 years in product management, Started off in PR and analytics, then moved to telehealth right at the height of the pandemic Would not recommend trying to jump into telehealth at that time and I've only been in the insurance industry for a couple years now.
00:03:58.152 -->
00:04:08.671But at the same time I've really just had a baptism by fire but learned a lot and I think insurance is a great area in SureTech that's having a lot of new frontier, a lot of old legacy systems upgrading.
00:04:08.671 -->
00:04:10.334So it's a great time to be alive.
00:04:10.334 -->
00:04:12.056And again, my specialization is claims.
00:04:12.056 -->
00:04:20.975I'm beginning to dabble a little more on the policy and underwriting side, but the trends are out there that are impacting all of us and really excited to talk those through.
00:04:21.720 -->
00:04:22.221That's awesome.
00:04:22.221 -->
00:04:23.985Well, I know the headlines right now.
00:04:23.985 -->
00:04:32.002When you hear about technology, you hear about the mass layoffs of companies like Twitter and Facebook and everybody else Google.
00:04:32.002 -->
00:04:36.255So there really is something to what you as you were joking.
00:04:36.255 -->
00:04:39.850There is some stability that comes with insurance and workers compensation.
00:04:39.850 -->
00:04:46.389It might not be as glamorous, that's definitely not the Silicon Valley dream, right but there's definitely opportunities for stability.
00:04:46.670 -->
00:04:54.644And glamour is in the eyes of a beholder, right, and I will say that the impact and the scale of which we're being able to operate here at Berkeley is enormous, right, and so that's what I do.
00:04:54.644 -->
00:05:01.687Enjoy that, and you getting to build technology that powers really a lot of what happens in the workplace is really awesome, so I'm thrilled.
00:05:01.687 -->
00:05:06.095Okay, I tell my wife I'm the coolest guy ever, and she doesn't believe me yet, but she'll get there soon.
00:05:08.161 -->
00:05:15.322So when we talk about technology and claims claims have been around for a while what do we mean?
00:05:15.322 -->
00:05:18.632What's the role of technology in claims?
00:05:19.574 -->
00:05:20.718I think that's a great question.
00:05:20.718 -->
00:05:26.831Again, I'm going to start off with a buzzword, because everyone needs a cool buzzword to begin, but I'm going to say the technology in claims.
00:05:26.831 -->
00:05:29.202The word of the day is augmentation, right?
00:05:29.202 -->
00:05:33.021So with this is you know, the claimant experience is a very human one, right?
00:05:33.021 -->
00:05:35.011You're in the moment, you're in the accident.
00:05:35.011 -->
00:05:37.781How are you basically getting through that process?
00:05:37.781 -->
00:05:51.283And that's why, at least how I'm viewing this is how can technology assist in that process to augment the adjuster and the humans who are very much interacting with that claimant at that moment and that experience, and also with the policyholders and also with agents.
00:05:51.283 -->
00:05:52.889Again, there's a whole spectrum right here.
00:05:53.529 -->
00:05:56.427But with that is, some people just try to say can we automate it?
00:05:56.427 -->
00:05:57.430Can you just talk to a computer?
00:05:57.430 -->
00:05:58.302Can you never interact?
00:05:58.302 -->
00:06:01.211And yes, there's going to be the small paper cuts or the report.
00:06:01.211 -->
00:06:10.865Only there's going to be some subset that can be automated.
00:06:10.865 -->
00:06:14.437But the way that I've been viewing it, at least my time here at Berkeley, is how can we use the best of technology to augment the best of humans to really attack these problems?
00:06:14.437 -->
00:06:19.672So that's where I believe that most places will say just throw a computer or machine learning model at it.
00:06:19.672 -->
00:06:26.093But in reality, how can we leverage technology to leverage humans is the way that at least I've been trying to approach it.
00:06:26.939 -->
00:06:34.293Can you give an example a recent example maybe of how you're using technology to augment something in the claims industry?
00:06:35.122 -->
00:06:35.887Way too many, matt.
00:06:35.887 -->
00:06:37.819And again, this is what keeps me on my toes, right.
00:06:37.819 -->
00:06:43.673So with that, for instance, sometimes again we will use machine learning or what some people call AI.
00:06:43.673 -->
00:06:50.247So ML is the buzzword, machine learning which is sometimes people call it AI, it's all these different cool terms, right?
00:06:50.247 -->
00:06:54.692Just saying hey, the Skynet is doing something in the background.
00:06:55.319 -->
00:07:01.822So from there we, at least some of our Berkeley time will say hey, when a new claim comes in, based off the first report of injury.
00:07:02.343 -->
00:07:08.613How do we get some of these early details to identify whether it's going to be a large-scale claim or just the paper cut right.
00:07:08.613 -->
00:07:14.600And again, when it's the smaller ones, we're saying hey, an adjuster doesn't need to do 17 of the normal steps.
00:07:14.600 -->
00:07:22.749Again, all the regulatory and must-have requirements we're always doing to meet the laws of the land, but some of the steps of the process, all the follow-ups.
00:07:22.749 -->
00:07:32.663We can reduce some of that on that, when the machine learning or AI or Skynet identifies saying hey, you don't need to do everything on this one, right, and we don't get it 100%, but directly.
00:07:32.663 -->
00:07:33.687That saves some time.
00:07:33.687 -->
00:07:38.826So we just do the human steps, the augmentation where they need to plug in and reduce some of that early.
00:07:38.826 -->
00:07:42.687So that's a good example where we're saying, hey, technology will identify some things.
00:07:42.687 -->
00:07:48.939Example where we're saying, hey, technology will identify some things that reduce some of those steps, but we still have the human doing the must-have steps in that process.
00:07:49.300 -->
00:08:02.464I think it's really key one of the things you're highlighting there and that we're not in a state where we're looking for technology to replace human beings, but if we could redeploy some of those efforts so we have time to do the things humans are really good at.
00:08:02.464 -->
00:08:09.834That's one of the things that can make us special if we allow computers to help us and technology to help us improve the processes.
00:08:09.834 -->
00:08:16.341Sam, what are some of the misconceptions you see when you start to hear about how technology can improve claim processes?
00:08:16.341 -->
00:08:30.163You're dealing with a lot of claims people who probably don't all have high levels of technology background, and so what are some of those misconceptions you sometimes hear, where there's some, you know, maybe they don't align with what's actually, what actually can be done.
00:08:30.202 -->
00:08:33.601Well, yeah, I think that's a great question, greg, and, but I will say it's.
00:08:33.601 -->
00:08:36.429There's two ends of that spectrum, of those misconceptions, right.
00:08:36.429 -->
00:08:41.326One is that technology, hey, anything that I don't like doing right now, technology can solve.
00:08:41.326 -->
00:08:43.649It can solve world hunger just with a single flitch.
00:08:43.649 -->
00:08:45.774Sam, here's an idea.
00:08:45.774 -->
00:08:56.600Just go make it happen, wave your magic technology wand and it's just like my parents, when I go home for Christmas, think that I, because I work in technology, can solve all of their router problems and printer problems.
00:08:56.740 -->
00:09:11.681Some people think that, hey, technology can solve anything you want there, just like the printers, the TV's broken, can you fix the Roku it you want there, just like the printers, the TV's broken, can you fix the Roku it's like I can't do everything, folks.
00:09:11.681 -->
00:09:26.162So that's one end of the spectrum and the other one is that misconceptions is that technology can't do some of the cool things that humans historically could do, and some of those which, when you actually talk about it, makes sense Like, hey, we want technology to catch mistakes or errors, right, oh yeah, of course I would like that.
00:09:26.162 -->
00:09:29.110Or could it reduce mundane, repeatable tasks?
00:09:29.110 -->
00:09:32.947So you're doing like think, work and not just click, work, right.
00:09:32.947 -->
00:09:36.423But the two ends of those spectrums are always fun, and especially insurance.
00:09:36.504 -->
00:09:41.101Some it tends to gravitate towards oh, technology isn't going to be able to do anything.
00:09:41.101 -->
00:09:44.928So that's the fun conversation, and I'll actually flip the question back to you.
00:09:44.928 -->
00:09:52.892How have you all seen, like what are some of the misconceptions you've found, or working in this industry longer than I have that you know that come up a lot as well.
00:09:52.892 -->
00:09:55.365Is there any different ones besides from those two extremes?
00:09:56.568 -->
00:10:12.312All right, Well, I was just going to say the one I've seen the most in my experience has been that often technology can do things, but what's not being calculated is the amount of time and effort and resources that would have to be deployed to get there.
00:10:12.312 -->
00:10:25.032And so often I feel like adjusters, managers, supervisors have the want list, and the want list might save them five minutes, but it might take 10 years to accomplish it today.
00:10:25.032 -->
00:10:28.208So then the prioritization becomes the issue.
00:10:28.208 -->
00:10:30.798It's not always that it can't happen.
00:10:30.798 -->
00:10:35.496It probably could, but is it really worth having that happen, for what it's going to cost?
00:10:36.880 -->
00:10:45.835Yeah, my example would be the first notice of loss and automation of that and triggering, maybe, keywords.
00:10:45.835 -->
00:11:09.995You gave the example of highlighting a more serious claim, so you trigger it on words like amputation, traumatic brain injury and those go to a more experienced, high-level claims person, versus you have something where it's like contusion, laceration, and those things get assigned to a newer person or somebody maybe with less experience.
00:11:09.995 -->
00:11:17.684So I mean, I've seen some examples of that through automation and augmentation I guess you know the word we're using.
00:11:17.684 -->
00:11:27.335So that would be an example I've seen of where it's been applied in the industry versus having it go basically across the spectrum.
00:11:27.335 -->
00:11:33.153A new claim comes in and always goes to Sandra because Sandra reviews every new claim.
00:11:33.153 -->
00:11:49.955It's like, well, if we can identify those things and you might identify 80 percent of the stuff and then Sandra just gets 20% and then that time that Sandra's freed up is now able to go and do some other tasks, versus all she's doing is reviewing new losses coming in.
00:11:49.955 -->
00:11:52.287So that's a recent example I've seen.
00:11:53.139 -->
00:11:58.592I love that example, man, because I will say it's like it's a combination of routing rules saying hey, and we're picking out words.
00:11:58.592 -->
00:12:07.471But this is where technology, like we say, can assist is sometimes when you have to write the exact if-then rules and then you forgot a derivation right.
00:12:07.471 -->
00:12:08.429Some people call things very similarly.
00:12:08.429 -->
00:12:21.355There's also this idea in technology called stemming, where you know you do plurals or ING or things like that, right, and that's where you can say, hey, technology with natural language processing, called NLP, come up with all variations of this type of word or even recommend words.
00:12:21.355 -->
00:12:23.067And that's what it's getting crazy right now.
00:12:23.067 -->
00:12:25.288It's saying here I'll just recommend these 20 other words.
00:12:25.640 -->
00:12:31.126Should these route to this type of adjuster who's going to handle this type of catastrophic claim, for instance, or this cat claim?
00:12:31.126 -->
00:12:34.788So that's where it can use the combination of an if-then rule set.
00:12:34.788 -->
00:12:37.081That's kind of basic but it's good in technology.
00:12:37.081 -->
00:12:42.753But then can technology figure out a few more examples around that to help escalate that.
00:12:42.753 -->
00:12:46.850I love that example and again, it's one we're even looking to utilize here to some degree.
00:12:46.850 -->
00:12:48.967And how can we expand and enhance that as well?
00:12:49.899 -->
00:12:52.769And it's small things, and then you can continue to build on them too.
00:12:52.769 -->
00:12:57.850Right, it's nice to have the home run, but a lot of times it's the little singles.
00:12:57.850 -->
00:13:00.277And how do you gain little efficiencies, the 1%?
00:13:00.277 -->
00:13:05.630You know better improvement, and then you know that becomes exponential improvement over time, right?
00:13:05.879 -->
00:13:11.013So Sandra now has you know, 80% of her time freed up to do more meaningful other tasks.
00:13:11.013 -->
00:13:14.249You know, we're not trying to eliminate her role.
00:13:14.249 -->
00:13:22.033We're trying to elevate her role into like okay, let's, you know, you're better utilized in this capacity versus you know reading.
00:13:22.033 -->
00:13:23.625Yeah, I mean, that's another example.
00:13:23.625 -->
00:13:26.773I mean and the difficulty I work with a lot of attorneys and nurses.
00:13:26.773 -->
00:13:35.460You know the difficulty I get a little pushback from them is I'm in the show me state, I'm in St Louis, I'm in Missouri, they want to see everything.
00:13:35.460 -->
00:13:38.602So that's some of the difficulties I experience.
00:13:38.602 -->
00:13:42.746On the kind of the reverse end, like no, let me review the document, give me the document.
00:13:43.287 -->
00:13:47.650And one of the fun things about the changes in technology is sometimes under the hood.
00:13:47.650 -->
00:13:59.442It is not easy to decouple with machine learning and AI and insert buzzwords I mean, I joke Skynet from the Terminator back in the day, right, but to that end is, it can't always show you that way.
00:13:59.442 -->
00:14:06.575So that's where, sometimes, again, the idea of again buzzword, back again augmentation, where you could say the computer or ML or AI recommended this.
00:14:06.575 -->
00:14:08.524Do you want to take action on it?
00:14:08.524 -->
00:14:16.140So it's not basically making the choice all the way, but it's allowing those to say hey, oh, I want to double look at the document, the show me side, I want to.
00:14:16.140 -->
00:14:18.466Okay, let me just double check to make sure the computer got it right.
00:14:18.466 -->
00:14:23.164And if it does that 100 out of 100 times or 99 out of 100, maybe you start trusting it.
00:14:23.700 -->
00:14:24.302So that's the idea.
00:14:24.302 -->
00:14:25.785Is you don't, like you said, we all want to.
00:14:25.785 -->
00:14:32.052Using a bad sports analogy, we all like seeing the long pass bomb to Randy Moss at the end, you know, with a touchdown.
00:14:32.052 -->
00:14:38.211I don't know why I'm going to the Vikings in the 90s, but in reality the teams that just chunk it Chunk it forward like five yards at a time.
00:14:38.211 -->
00:14:38.990Five yards at a time.
00:14:38.990 -->
00:14:46.503The small incremental gains can eventually really get you there, and it's not as glamorous as the star play, but that's really what's going to move the needle in the long run.
00:14:48.109 -->
00:14:53.451Okay, so one of the questions I had, sam, is what is technology good at in the claim space?
00:14:54.393 -->
00:14:59.792Yeah, and that's where I think the unglamorous side sometimes of technology is the piping right.
00:14:59.792 -->
00:15:07.437Technology is a good thoroughfare of information, connecting different systems, facilitating seamless and easy communication interactions.
00:15:07.437 -->
00:15:15.851A couple of ideas that come to mind that, especially in the claims space, especially as we as adjusters need to be more easily contactable, or basically reaching out to claimants.
00:15:15.851 -->
00:15:20.990Things like digital payments Don't go say my old school checked my grandma like my grandma did.
00:15:20.990 -->
00:15:22.384Can I get something in?
00:15:22.384 -->
00:15:22.821You know?
00:15:22.821 -->
00:15:23.283Venmo?
00:15:23.283 -->
00:15:24.226Right, we've heard that.
00:15:24.226 -->
00:15:29.110Or texting, right, like which kid under the age of 25 wants to have a phone call?
00:15:29.110 -->
00:15:29.652They dread it.
00:15:29.652 -->
00:15:31.166That's like is that a punishment, right?
00:15:31.166 -->
00:15:33.489Am I being grounded because I have to answer the phone?
00:15:33.489 -->
00:15:41.669So, everything from the piping to also thinking about where you can identify patterns, right, technology could say I'm seeing a lot of this problem.
00:15:41.669 -->
00:15:44.393Let me just say this is a problem.
00:15:44.393 -->
00:15:45.375What should we do with it?
00:15:45.375 -->
00:15:47.182So we can't always say the what to do with it.
00:15:47.182 -->
00:15:48.666That's the million-dollar question.
00:15:48.666 -->
00:15:56.260For instance, one of our partners at a similar company, midwestern Employers Casualties, have this idea of identifying problematic claim notes.
00:15:56.260 -->
00:15:57.804Hey, we've seen a bunch of these claim notes.
00:15:57.804 -->
00:15:59.571This one is flagged for attention.
00:15:59.571 -->
00:16:07.366Or another operating unit at Berkeley is also saying we've seen claims like this.
00:16:07.366 -->
00:16:08.552You might want to go check those out.
00:16:08.552 -->
00:16:15.429So these are the ways that technology can find those patterns, to then surface it, and then at that point the adjuster or the human can take it there.
00:16:16.051 -->
00:16:20.788And so, again, the reticence is sometimes that technology is not as good as humans in everything it's like.
00:16:20.788 -->
00:16:22.293Well, that's majority clue.
00:16:22.293 -->
00:16:34.128True, we have a brain, we have the ability to think, but it can also look at 10 million claim notes and come up with some groupings of problems and say, hey, I've seen similar ones that a human would never be able to do.
00:16:34.128 -->
00:16:37.985And then data validation and anything that we said earlier.
00:16:37.985 -->
00:16:42.533It's not think time, it's just checking a box, because computers, they do make errors.
00:16:42.533 -->
00:16:48.970Trust me, I've got a backlog full of bugs to try to tackle, but at the same time it's much more consistent than humans at that part.
00:16:48.970 -->
00:16:54.029But trying to ask your computer, or even the newfangled chat GPT, I tried.
00:16:54.029 -->
00:16:55.693You know that's the buzzword nowadays.
00:16:55.693 -->
00:16:59.668I tried to ask it to write a haiku about claims adjustment and it failed miserably.
00:16:59.889 -->
00:17:04.492So anything that wants perspective, but it did actually have a good song to claims.
00:17:04.492 -->
00:17:05.818This is one aside about claims.
00:17:05.818 -->
00:17:10.009I asked it to do a song about claims adjustments to the tune of Baby Got Back and it did.
00:17:10.009 -->
00:17:13.491Says I like small claims and I cannot lie and it actually went there.
00:17:13.491 -->
00:17:14.355So it started.
00:17:14.355 -->
00:17:18.426It's getting closer, but the huge nuance is not.
00:17:18.426 -->
00:17:19.549There is where it needs to be.
00:17:20.171 -->
00:17:23.163Great points huge nuance you know is not.
00:17:23.163 -->
00:17:23.765There is where it needs to be.
00:17:23.765 -->
00:17:24.126Great points, yeah.
00:17:24.126 -->
00:17:44.913So when you're working with, obviously you know individual adjusters, you're working with injured employees, you're working with different components, what are some of the challenges in managing those expectations of the claim staff when it comes to technology and when it comes to, you know, enhancements and things like you know Greg alluded to earlier, like, and you alluded to when you're like fix all my stuff.
00:17:44.913 -->
00:17:47.972Like, what are some of the?
00:17:47.972 -->
00:17:49.279What are those expectations?
00:17:49.279 -->
00:17:51.086Like, how do you, how do you normalize?
00:17:51.125 -->
00:17:51.386those.
00:17:51.386 -->
00:17:52.589That's great, man.
00:17:52.589 -->
00:17:56.780It's like it's the idea of I want it all and I want it now Right.
00:17:56.780 -->
00:18:01.630Like that's the problem that we're dealing with right here is like there's so much that we want to fix.
00:18:01.630 -->
00:18:05.404Greg, you made a great point earlier saying, hey, we don't always necessarily know the size.
00:18:05.404 -->
00:18:08.845This will save me five minutes, but it's going to take Sam six months to build Right.
00:18:09.446 -->
00:18:16.443So some of the misconceptions that I want to when thinking about this question it's a really good question is that one?
00:18:16.443 -->
00:18:17.726You hear about it elsewhere.
00:18:17.726 -->
00:18:18.768Well, we can do it right away.
00:18:18.768 -->
00:18:21.551Hey, I've heard about my friend who works at a similar insurance company.
00:18:21.551 -->
00:18:25.865They have this cool button that brews some coffee and does X, y, z for my claim process.
00:18:25.865 -->
00:18:26.851Why can't I do that?
00:18:26.990 -->
00:18:32.731So the misconception is people don't forget all the piping, all the underlying architecture that goes up to make that.
00:18:32.731 -->
00:18:35.740Another is the response times.
00:18:35.740 -->
00:18:40.348We think that everything and every system is supposed to be blistering fast, which should be.
00:18:40.348 -->
00:18:41.971Like my iPhone starts up in a second.
00:18:41.971 -->
00:18:42.993I can't wait a second.
00:18:42.993 -->
00:18:45.435Something pauses, even briefly.
00:18:45.435 -->
00:18:46.457We're like what's happening.
00:18:47.079 -->
00:18:53.830So the challenge is again these are misconceptions that are out there, so the challenge is trying to not just address them, but then overcome them.
00:18:53.830 -->
00:18:56.768And that's where again product management comes in.
00:18:56.768 -->
00:19:03.313My entire profession is to say, hey, we understand that your iPhone can boot up in a second and we understand that your friend can do X, y, z at this other carrier.
00:19:03.313 -->
00:19:04.513Here's how we're different.
00:19:04.513 -->
00:19:08.857Let's work within our sandbox and let's create amazing things within there.
00:19:09.579 -->
00:19:15.481So it's really us trying to overcome those by doing the quick explanation, because you can't just say no, we can't do it.
00:19:15.481 -->
00:19:24.577Then you just feel like either you're being talked down to, but at the same time, our role is in product management and even within technology is to explain what we can do.
00:19:24.577 -->
00:19:30.652And then we partner with again great claims groups who are coming up with amazing ideas to figure out what we can do.
00:19:30.652 -->
00:19:42.462I'll actually turn this question back to you two and saying you've seen a lot more of these mismanaged expectations over time and I know, greg, you said earlier, there's a mismanaged expectation of sizing.
00:19:42.462 -->
00:19:43.285What do you think on technology?
00:19:43.285 -->
00:19:46.780Technology teams can do better to help in that conversation Like what?
00:19:46.780 -->
00:19:51.601As we, as technologists, what do we need to learn when actually engaging in that back and forth?
00:19:52.343 -->
00:19:53.425It's a great question.
00:19:53.425 -->
00:20:11.189I think on our end sometimes we don't understand how hard certain things are, not maybe how difficult, but how many hours would be needed to accomplish something, and so that wish list we've talked about can get really long, because we can all think of things that would make things easier.
00:20:11.189 -->
00:20:14.587Well, if I just clicked here, then I wouldn't have to do these five other things.
00:20:14.587 -->
00:20:52.772So I think, sometimes understanding also what other things are being worked on that are competing for that same time so we could spend five weeks adding a new button to the screen, or we could do this other thing that would allow us to automate small claims and so understanding the impact, I think on both sides, sometimes maybe the technology side might not understand the lift that would come from something, and then that's our job to make sure we're speaking up to explain that, and then, on the other end, I think, understanding how long it takes so that we're prioritizing the right things.
00:20:52.772 -->
00:20:54.006I don't know what your thoughts are, matt.
00:20:55.319 -->
00:20:56.422Yeah, it's something similar.
00:20:56.422 -->
00:21:10.856I think spending enough time with the people doing the job is a lot of times the difficulty in making sure, like when I say I want this, like that five button example, or like I have to click on these eight things to have this happen.
00:21:10.856 -->
00:21:15.971Instead of these eight things, like would it make sense to click on it once, and then it jumps to eight.
00:21:15.971 -->
00:21:19.569What is steps two, three, four, five, six, seven doing?
00:21:19.569 -->
00:21:21.161Are they doing anything like?
00:21:21.161 -->
00:21:22.142Just you know?
00:21:22.142 -->
00:21:23.763Sometimes maybe it's the you know three, four, five, six, seven, doing?
00:21:23.763 -->
00:21:24.785Are they doing anything like and just you know?
00:21:24.785 -->
00:21:29.730Sometimes maybe it's the you know the data architect or maybe it's the person that's actually, you know, the business analyst.
00:21:30.271 -->
00:21:31.373Do they understand?
00:21:31.373 -->
00:21:34.836And then sometimes it claims people really don't understand.
00:21:34.836 -->
00:21:42.334Well, the reasons you have to click on steps three, seven are this like that triggers this, you know piping triggers this, you know piping.
00:21:42.334 -->
00:21:47.855Like you know that, like sam was saying, like so I think there's definitely roles on both sides.
00:21:47.855 -->
00:21:56.246Like the reason yeah, the phrase that everybody hates is like well, the reason we do it that way, sometimes there is a reason why it's done that way.
00:21:56.246 -->
00:22:02.529Right, yeah, yeah, because an actuarial will come over and hey, you just cut out this process.
00:22:04.161 -->
00:22:05.064We love those phone calls.
00:22:05.064 -->
00:22:21.292We love those phone calls and I'll actually add something out there I think it's great to say is we, as technologists, I think need to get better at actually going and sitting down next to the person saying walk me through, instead of just saying I want X, y, z at the eighth step, like skipping steps two through seven, let me see why you don't need those.
00:22:21.292 -->
00:22:25.290And then again, that's where the dialogue can occur right, hey, step number three.
00:22:25.339 -->
00:22:28.509And I need to give a shout out to my amazing team who thinks through all these things.
00:22:28.509 -->
00:22:31.448So again, we have a team called Claim to Fame where we really focus on claims.
00:22:31.448 -->
00:22:36.622Shout out to that group where they'll say, hey, you forgot about regulatory reporting here or you forgot about NCCI.
00:22:36.622 -->
00:22:39.022We'll have these different plugins of different steps.
00:22:39.022 -->
00:22:41.023We may need it, but that doesn't mean we can't.
00:22:41.023 -->
00:22:45.386We may need steps now, one and two, but we may not need three, four, five and six.
00:22:45.386 -->
00:22:51.049So I think it's a good back and forth to be able to explain, but too many times we just hear I want to go jump from one to eight.
00:22:51.049 -->
00:22:57.452We write it off as technologists says, can't do it, and then it dies and you lose that potential savings over time.
00:22:57.452 -->
00:23:01.075So rolling up the sleeves and getting in the trenches is important.
00:23:01.075 -->
00:23:02.615It just takes time, right.
00:23:03.195 -->
00:23:04.576So how would you so?
00:23:04.576 -->
00:23:15.784Greg and I are both in claims management and we manage the claims adjusters and claims analysts and examiners, etc.
00:23:15.784 -->
00:23:17.506So we have prioritizations that are important to us.
00:23:17.506 -->
00:23:23.214You guys obviously have prioritizations that are important to IT and to technology.
00:23:23.214 -->
00:23:29.276What's the best way to manage those prioritizations and the limited resources?
00:23:29.276 -->
00:23:30.643Because, like the example.
00:23:30.663 -->
00:23:31.586Greg gave earlier.
00:23:31.586 -->
00:23:39.307How do we manage something when there's only a limited resource, it resources and technology resources?
00:23:39.307 -->
00:23:42.623Unfortunately, you know, we mentioned, you know, google earlier.
00:23:42.623 -->
00:23:46.724Like we don't have Google money, we're not going to throw like all this at everything.
00:23:46.724 -->
00:23:48.971You know how do we manage those prioritizations?
00:23:49.661 -->
00:23:52.529These are the questions that make us happy that we're asking these questions, right?
00:23:52.529 -->
00:23:53.842Well, there's a simple answer.
00:23:53.842 -->
00:23:55.203Actually, matt and Greg, I will tell you.
00:23:55.203 -->
00:23:59.592The way we prioritize is liquor and guessing Joking okay, I wish it was that easy.
00:23:59.592 -->
00:24:00.432Or just a dartboard.
00:24:00.432 -->
00:24:06.666It's like close your eyes and that's no, I completely joke, but I think a better way of for lack of a letter buzz phrase.
00:24:06.666 -->
00:24:11.209It's basically like it's the voice of the tactical combined with the insight of the strategic right.
00:24:11.680 -->
00:24:16.242So with that is, we need to anytime you ignore sort of the people who are living this day in the day-to-day.
00:24:16.242 -->
00:24:26.855On the flip side, if all you're focusing on is the details and the weeds, you will miss the bigger strategic opportunities out there.
00:24:26.855 -->
00:24:47.913So the first thing we need to do in order to prioritize the chaos that is a huge backlog and seems like 15 new things have popped up in the last 30 minutes since we've been talking is combining those two, get those two inputs and then after that, you need to basically then narrow it down quickly, because there's always way too much that you want to do, just like my wife has 15,000 home projects she wants me to do.
00:24:47.913 -->
00:24:51.464We can't talk about 15,000 projects, we need to talk about five, right?
00:24:51.464 -->
00:24:54.251So first is, get the inputs, do your homework.
00:24:54.251 -->
00:24:59.873Again, with targeted homework, you can't boil the ocean, narrow it down and then pick a direction and go.
00:25:01.920 -->
00:25:05.008I think it's sort of the idea that a lot of places have analysis, paralysis.
00:25:05.008 -->
00:25:18.422And again, there's a show called Prison Branko, maybe years ago, where the guy Wentworth Miller who played one of the characters there she said there's only four rules you need to remember Make a plan, execute the plan, expect the plan to go off the rails, throw away the plan.
00:25:18.422 -->
00:25:20.884So even with that, things will go wrong at times.
00:25:20.884 -->
00:25:21.266It's not.
00:25:21.266 -->
00:25:25.391Any plan is not perfect, but you need to make it and you need to start executing it Right.
00:25:25.391 -->
00:25:29.056So, take those inputs, lower it down and then go.
00:25:29.056 -->
00:25:36.364But in reality, if you're not thinking about the strategic, then you're missing out.
00:25:36.364 -->
00:25:42.280And, greg, I'll actually ask you as basically as a claims leader, what's important when we on the technology side should be thinking about the strategic.
00:25:42.280 -->
00:25:44.047Should we be coming to you with the ideas?
00:25:44.047 -->
00:25:49.512Should you be coming to us, or is there some better forum for us to make sure we're not missing that voice of the strategic?
00:25:50.755 -->
00:25:53.196Yeah, I feel like that conversation has to go both ways.
00:25:53.196 -->
00:25:54.258But I do think you're right.
00:25:54.258 -->
00:25:55.218It's really important.
00:25:55.218 -->
00:26:03.943You don't want to have your technology department so focused on just better, and our competition is going to be looking for those ways to do it better.
00:26:03.943 -->
00:26:20.000We're all trying.
00:26:20.000 -->
00:26:26.883So if all our attention is just trying to make sure that the car runs, that's great, but we're going to miss out on some really important things.
00:26:26.883 -->
00:26:38.220So I think talking back and forth and creating that dialogue of what's possible versus what can be dreamed up is, to me, I think, some of the first steps to really coming up with that.
00:26:38.220 -->
00:26:40.546That's what I would say anyway, matt, thoughts on your end.
00:26:40.546 -->
00:26:42.096Yeah, I like how.
00:26:42.597 -->
00:26:43.358Sam put it.
00:26:43.358 -->
00:26:55.645I'm a big James Clear fan, where you just have to start something about you know, ultimately, like you know, it's great to have the plan, but sometimes you have to start and finish something.
00:26:56.295 -->
00:27:04.719You can't keep worrying about that being perfect, because then you'll never get anything started and you'll never finish anything.
00:27:04.719 -->
00:27:10.936If it's always got to be 100% accurate, there's going to be little glitches, like you said.
00:27:10.936 -->
00:27:12.162There's going to be little bugs.
00:27:12.162 -->
00:27:20.558Having people understand that we're going to do that, and then Greg hit on it too, like we can't create something.
00:27:20.558 -->
00:27:24.107That is also so bad, though that it's creating all this maintenance, right.
00:27:25.615 -->
00:27:29.205It people and technology people want to work on new things, right.
00:27:29.205 -->
00:27:32.664Unfortunately, like claims, a lot of times it's like we're a legacy.
00:27:32.664 -->
00:27:34.923There's a lot of legacy stuff.
00:27:34.923 -->
00:27:36.999There's years and years.
00:27:36.999 -->
00:27:46.077There's there's legal components in this component and you know reporting upward components, so there's all that that needs to be factored in and sometimes that's you know, you know the minutiae.
00:27:46.077 -->
00:27:49.267That's not glamorous and you know nobody wants to work on that stuff.
00:27:49.267 -->
00:27:51.378You know it's all the fun new.
00:27:51.378 -->
00:27:51.960You know.
00:27:51.960 -->
00:27:53.784Things that everyone wants to work on right.
00:27:53.784 -->
00:27:55.827Yes, very much so.
00:27:56.976 -->
00:27:59.785I've heard it said that objects in motion tend to stay in motion.
00:27:59.785 -->
00:28:03.025So I think there is something to getting started and just getting moving.
00:28:03.025 -->
00:28:10.079Sam, I know on our end our claims people we're pretty good at understanding a lot of medical terminology.
00:28:10.079 -->
00:28:12.642Now we're also pretty good at learning a lot of legal because we spend a lot of time in both of those worlds.
00:28:12.642 -->
00:28:15.912We're also pretty good at learning a lot of legal because we spend a lot of time in both of those worlds.
00:28:15.912 -->
00:28:22.542But when we start to get in the technical side, I think maybe I'm the only one, but I do think sometimes we struggle a little bit.
00:28:22.542 -->
00:28:35.167So what are some of the challenges or what do you do from your perspective to break down some of these concepts and help the folks and claims understand what it is you're trying to accomplish?
00:28:36.015 -->
00:28:50.218Yeah, I think that's a great question, greg, because, just as a technologist coming into insurance, it's sometimes you're like it's actually going both ways, because insurance is not the easiest and most straightforward at times, right, and I had alphabet soup for my first, like when I first joined I was like, oh my gosh, let's play this game.
00:28:50.218 -->
00:28:51.460Which acronym is this?
00:28:51.460 -->
00:28:52.981Is this the insurance company's acronym?
00:28:52.981 -->
00:28:53.804Berkeley acronym?
00:28:53.804 -->
00:28:55.685Is this the state acronym?
00:28:55.685 -->
00:28:57.509There's two acronyms for the same thing.
00:28:57.509 -->
00:28:58.730How do I survive it?
00:28:59.055 -->
00:29:05.739But I think that idea is like, hopefully, things like this podcast where you're explaining things like in metaphors or analogies.
00:29:05.739 -->
00:29:10.616This is like XYZ, or even my bad analogy of my wife giving me the honey-do list.
00:29:10.616 -->
00:29:20.766How do we break this down into a shared understanding that we all have a chuckle as well, but try to talk a similar language and that's what product management does, usually trying to take stakeholders and then developers.
00:29:20.766 -->
00:29:37.740So first of all, talk something out and if it makes no sense, try it again and then say explain it like you were explaining it to a five-year-old and everyone seems to kind of like roll their eyes, like no, okay, I can try to explain that, but in reality it makes you to simplify it and then get to a way that you understand it.
00:29:37.759 -->
00:29:46.695Another thing that we do in our team a lot is basically diagram, diagram, diagram big boxes, like you're going to a whiteboard, and again we use a digital tool called Miro.
00:29:46.695 -->
00:29:54.469There's other versions out there, but how do we just like there's a box here and it goes to this box and let me get this process to this box right?
00:29:54.469 -->
00:30:01.826So that's how sometimes we explain the intricacies of APIs and batch jobs and all buzzword soup.
00:30:01.826 -->
00:30:05.663When you hear again I'm sure when people hear our technologists talk, they're like their eyes are rolling.
00:30:05.663 -->
00:30:07.181What are they talking about?
00:30:07.201 -->
00:30:07.481right.
00:30:08.296 -->
00:30:20.148And so this is why at least one of our goals is to explain what we're doing and why is I say let's make it stupid, come up with bullet points, not long paragraphs, and explain to it in a common language.
00:30:20.148 -->
00:30:33.604And then, if there's follow-up questions and Neville is like, well, I actually care about, there's that one person in the room who's like I want to ask the detailed question, to be the teacher's pet, right At that point, then you say let's sidebar this and let's go to the huge deep dive.
00:30:33.604 -->
00:30:35.727The same idea as, I think, on both ends.
00:30:35.727 -->
00:30:47.965Also, when adjusters like you said earlier, matt is like they may just say I just wanted to do this, but need to break it down that way, I think both sides need to say explain it simply and then have the follow-up questions after that.
00:30:48.674 -->
00:30:51.980Matt Levin, it's really easy to forget all of the things we just assume we know.
00:30:51.980 -->
00:31:03.457And I could say well, we denied the TTD because of the IME, but we need to keep in mind CMS and somebody who's outside is like what in the world did he just say?
00:31:03.457 -->
00:31:09.258And somebody in claims understands every word I just said, and I do think it goes both ways.
00:31:09.799 -->
00:31:15.200I love that, greg, and I think especially because, again, a lot of developers sometimes are not even having that interaction.
00:31:15.200 -->
00:31:20.337So, again, if you ever get a developer on a call, you'll rattle that off and they'll just be completely like.
00:31:20.337 -->
00:31:23.096They're like, I understand none of it, so I'm not even engaged, right.
00:31:23.096 -->
00:31:28.217So I think the goal is is saying, just like you know, I've seen great on this podcast people will explain what you know.
00:31:28.217 -->
00:31:28.999What are these terms?
00:31:28.999 -->
00:31:30.340Let me explain the context.
00:31:30.340 -->
00:31:33.665Even if it's baseline, or most insurance adjusters or people will know.
00:31:33.665 -->
00:31:36.769How do we here's, do we all understand what we're talking about?
00:31:36.769 -->
00:31:38.923Yes, yes, yes or no?
00:31:38.923 -->
00:31:40.920Okay, let's explain 30 seconds.
00:31:40.920 -->
00:31:41.623There we go.
00:31:41.623 -->
00:31:42.444Now let's move on.
00:31:42.444 -->
00:31:46.020And I actually finally understood like it took me a while, but I actually understood exactly what you said.
00:31:46.020 -->
00:31:47.910So that's where us, as technologists, we're getting there.
00:31:47.971 -->
00:31:48.454We're getting there.
00:31:48.454 -->
00:31:57.903There's hope, right, credit cards.
00:31:57.903 -->
00:32:02.028So periodically the credit card system would go down.
00:32:02.028 -->
00:32:17.203We still had the whole the old, you know, swiper probably too young to even have seen any of those but greg and I aren't, you know but no one knew how to use it.
00:32:17.203 -->
00:32:22.942And then there's, occasionally credit cards don't even have those raised ridges anymore, so then you have to write it down and people are like what do you mean anyway?
00:32:22.942 -->
00:32:27.982What happens when, when technology goes down and it's all hands on deck for you?
00:32:28.022 -->
00:32:29.787guys, you just, you just panic.
00:32:29.787 -->
00:32:31.337That's what you do.
00:32:31.337 -->
00:32:38.082You just panic, you know, just like I don't know, no, it's like then everyone it claims home exactly, just like it's a shutter down for the day.
00:32:38.102 -->
00:32:40.657I guess no one else is doing any more work, right, like those are.
00:32:40.657 -->
00:32:42.703Those are the good old days of like snow days or something.
00:32:42.703 -->
00:32:43.636It looks like it's gonna snow.
00:32:43.636 -->
00:32:50.461I guess we just shut it down right, but uh, unfortunately we're not in middle school anymore, right, and I'll have to ask at the end, matt, how you survive those fun.
00:32:50.461 -->
00:32:55.490Probably the, the cha-chings and people like you know, customers I'm sure love that and love taking time right.
00:32:55.490 -->
00:33:04.218What I will say is, like anything, like any types, you've got an emergency on claims, whether it's technology, people forget that the techniques that you use, whether in you know either on the claim side.
00:33:04.238 -->
00:33:09.878When there's a fire, whether it's at home, when there's a fire, whether anything, is you just one, shut out the noise and focus right.
00:33:09.898 -->
00:33:13.544The problem is with technology is sometimes it's very hard to diagnose the problem.
00:33:13.544 -->
00:33:18.569But you'll hear, hey, the system's slow or something like that or something's not working right.
00:33:18.569 -->
00:33:23.415And then of course everyone trying to be helpful is like, oh, and this other thing isn't working and this thing.
00:33:23.415 -->
00:33:26.724And then we have to like, okay, there's a lot of noise, how do we focus it?
00:33:26.724 -->
00:33:31.259You start decoupling these things, breaking it down, and you hear, oh yeah, that thing's been broken for the last two years.
00:33:31.259 -->
00:33:32.961Thank you for that help.
00:33:32.961 -->
00:33:36.766It's not helping right now in the panic or the fire.
00:33:36.826 -->
00:33:52.099But I think communication is also key because when something breaks, just like you had there, the difference is if you put up a sign saying, hey, our credit card machine is broken, it's going to take us a little longer to process payments, people are like, oh, okay, they know, they understand, at least I'm going into it.
00:33:52.099 -->
00:33:55.107You see those sometimes like a big fast food addict.
00:33:55.107 -->
00:33:59.125When I go in, someone puts a sign I'm saying we're understaffed today, please be patient.
00:33:59.125 -->
00:34:02.122I'm like, oh, okay, this is why the line's taking so long.
00:34:02.122 -->
00:34:13.740So communication is also a way, during those panic moments, to try to communicate it there, right, and finally send consistent messaging and then at the end give a wrap-up or summary.
00:34:13.820 -->
00:34:23.182We had technology called a buzzword retrospective, where we get in a room and again, most people have retrospectives but we get in a room and say why did everything go so badly right?
00:34:23.182 -->
00:34:24.822And it's never a fun conversation.
00:34:24.822 -->
00:34:33.922You don't want to be having these, but you really need to have the tactical discipline and say here's everything that went wrong, summarize it and then send it out to your stakeholders for accountability.
00:34:33.922 -->
00:34:45.822I've had to send Greg a couple of those emails last year and they're not fun to send, but I'm hoping that it gives the visibility saying hey, we're taking ownership for what did break and here's what we're doing to solve it in the future.
00:34:45.822 -->
00:34:54.543Right, greg, when you get those emails from me, you're not happy to see them, but I'm hoping you're at least liking that we're taking ownership that we broke something, right?
00:34:55.144 -->
00:34:57.289Absolutely, and I think some of the things you know.
00:34:57.289 -->
00:35:04.496We don't have these types of problems very often, but when they have happened, what I really appreciate one is just the regular communication, knowing.
00:35:04.496 -->
00:35:07.208You know, sometimes it's every half hour hour.
00:35:07.208 -->
00:35:10.498This is where we're at, this is what we're working on, this is what we're doing to fix it.
00:35:10.498 -->
00:35:21.403Updates are going to follow, and then at the end that updates are going to follow, and then at the end, talking about, this is what we found out, this is what we learned, this is how it happened and this is what we're going to do so it doesn't happen again.
00:35:21.403 -->
00:35:26.242I think that's a big part of it, and luckily we have a company culture where we can accept ownership and there's not a lot of finger pointing.
00:35:26.242 -->
00:35:28.027That allows us to get better.
00:35:28.027 -->
00:35:32.746So kudos to Berkeley for developing that, but that's a big part of the success.
00:35:33.608 -->
00:35:43.702This is what I love working about this organization and why I think we are the leader in our respective insurance areas is the fact that we've got a great product and again, like you said, it doesn't happen often, but no company is perfect.
00:35:43.702 -->
00:35:48.744It's how the company responds and we take ownership and then we say how do we not make sure this doesn't happen again?
00:35:48.744 -->
00:35:56.315A lot of places that I've worked, even past, companies try to sweep it under the rug, saying companies try to sweep it under the rug saying hey, there was no problem, or let's just cross our fingers and toes and hope it doesn't happen again.
00:35:56.315 -->
00:36:04.201We actually take the methodical time to really not just figure out what went wrong but enhance so it doesn't happen in the future, and that's why we're always pushing forward, which is appreciated.
00:36:04.521 -->
00:36:06.467So that's awesome.
00:36:06.467 -->
00:36:09.083I mean, how many problems bubble down to communication.
00:36:09.083 -->
00:36:11.956Right, when it's like hey, like you, you gave the example.
00:36:11.956 -->
00:36:18.521Like you gave the example, like put up the sign telling people you know we're moving slower today because we're understaffed, we know this is down.
00:36:18.521 -->
00:36:25.286Hey, we know emails responding slowly or we're not able to get outgoing things or ingoing things or whatever.
00:36:25.286 -->
00:36:26.467So just that communication.
00:36:26.467 -->
00:36:31.750I think you know it's critical and hopefully this never happens at our industry.
00:36:31.929 -->
00:36:45.887But that's why I had to give the restaurant analogy, right, yeah, when those problems go down we have the after action review, or whatever you want to call them, and we're able to improve the process right.
00:36:45.887 -->
00:36:46.307Very much so.
00:36:46.914 -->
00:36:53.922So, sam, this is the exciting part, I think, is where do you see technology going to improve claims outcomes in the future?
00:36:53.922 -->
00:36:58.965So we've talked about some of the things we're doing now, but where do you think this goes in the next five years?
00:36:59.775 -->
00:37:01.561Yeah, and I think that's a really great question, greg.
00:37:01.561 -->
00:37:02.615And that's what again exciting.
00:37:02.615 -->
00:37:04.983We don't always just want to be fixing the bad things.
00:37:04.983 -->
00:37:11.340We also want to be improving and really enhancing and making more fun for everyone involved the technologists, the adjusters, policyholders.
00:37:11.340 -->
00:37:20.070There's a lot that technology can do to really enhance and so, for instance, the research firm McKinsey recently had a report, and again they call it what was called human in the loop.
00:37:20.489 -->
00:37:38.967We've talked a little bit about this earlier, where technology can take some of the mundane heavy lifting but then keep the human apprised of the steps and, if they need to stop or double click or click in or, as you said earlier, find the documents, read the document, show me they can, but the human is at least tangential to that process, right?
00:37:38.967 -->
00:37:40.172So they don't have to do everything, but they're in the loop.
00:37:40.172 -->
00:37:48.492Another one is again the buzzword that was really big years ago, but you still hear it a lot is cloud computing, and most people don't even know what that means or like how does that impact me?
00:37:48.492 -->
00:37:53.106But the better way to think about it is the Daft Punk song from years ago harder, better, faster, stronger.
00:37:53.106 -->
00:38:01.070So cloud computing can make systems faster, more reliable, have better uptime, just overall better experience.
00:38:01.070 -->
00:38:07.860And so that's another shift to saying hey, let's get away from the thing that's been in the closet, the server in the closet for the last 50 years Don't unplug.
00:38:07.860 -->
00:38:09.885You see those signs like don't ever unplug this.
00:38:11.036 -->
00:38:16.117More like we don't have to worry about someone tripping and just like, oh gosh, the system's down right.
00:38:16.117 -->
00:38:18.545Another one is the idea of buying versus building.
00:38:18.545 -->
00:38:25.682Some larger organizations like ours historically have been like we got to build everything ourselves, we got to do everything ourselves and manage everything ourselves.
00:38:25.682 -->
00:38:46.242But really the great thing about Berkeley, while we're leading sort of this insurance industry, is we're thinking about what are we great at and let's execute that and let's augment with other organizations that do their best at, and then we make an ecosystem the best right, we at Berkeley are plugging in the piping, but we don't have to build everything from scratch, Sort of like, again, you're making your recipe.
00:38:46.242 -->
00:38:49.925You don't have to do it the way grandma did, where you make every single ingredient from there.
00:38:49.925 -->
00:39:00.708I can get the best ingredient from here, the best ingredient here, best ingredient from here, and still make that delicious dessert.
00:39:00.708 -->
00:39:02.034Man, I'm making myself hungry at this point.
00:39:03.815 -->
00:39:06.621And then the last word is we talked about machine learning and AI, Again sort of with the idea of human in the loop.
00:39:06.621 -->
00:39:10.036But where can we leverage those technology areas to really solve problems that we didn't even think about?
00:39:10.036 -->
00:39:27.003Right, Like one of the exciting things that we in the technology side saying go to the basic question, the job to be done of what are we trying to do here and where can technology assist so we're able to ask bigger and bigger questions, it seems like every year, but then again we then have to go back to the drawing board.
00:39:27.003 -->
00:39:27.885Can it actually do it?
00:39:28.315 -->
00:39:29.742Is it regulations.
00:39:29.742 -->
00:39:34.862But it's exciting to happen to be an insurance tech, so it gets me up in the morning.
00:39:35.204 -->
00:39:38.635I agree, but it's exciting to happen to be an insurance tech, so, like I, you know, gets me up in the morning, I agree.
00:39:38.635 -->
00:39:47.204And when I think back on, when I started my career, you know, maybe four or five years in some of the data analytics was starting to, you know, really start to get into insurance and everything was about filling out a field, right.
00:39:47.204 -->
00:39:49.442There's a new box every five minutes.
00:39:49.442 -->
00:40:03.494Here's a new box, here's a new box right, because we have to capture the data and so, as a frontline adjuster, it was a nightmare because it was like well, now I've got to make sure I find the 900 boxes and all the data goes in the right boxes, right.
00:40:03.916 -->
00:40:23.826But I look at where we are now and some of the advances in analytics and being able to just cognitively not only read notes but start to make inferences about what those things mean, that will allow us to do things, that, instead of having to fill 900 boxes out, we can actually get to that same place without having to do that, which is exciting to me.
00:40:23.826 -->
00:40:31.233To think about where that goes next, I don't even know what that looks like 10 years from now, but it's very interesting to see.
00:40:31.233 -->
00:40:34.742Very much so, sam, overall, I've really enjoyed having you on here.
00:40:34.742 -->
00:40:38.041I can't end the episode without joking.
00:40:38.041 -->
00:40:47.699Our audience will never hear it, but in the middle of this technology episode, my computer had a blue screen of death and we had to stop the entire podcast because everything locked up and shut down.
00:40:47.699 -->
00:40:52.740So even in those moments this stuff can happen, but the show must go on.
00:40:52.740 -->
00:40:53.965The show must go on.
00:40:53.965 -->
00:40:54.717That's right.
00:40:54.717 -->
00:40:59.043Luckily, we have a great editor that will make this sound amazing at the end.
00:40:59.565 -->
00:41:05.347But I wanted to end this season by asking each of our guests to tell us something that they're grateful for.
00:41:05.347 -->
00:41:08.918I'm really a big proponent of putting good vibes in the universe.
00:41:08.918 -->
00:41:17.518I feel like there's plenty of people doing the opposite, so my small contribution to the world is to make sure I put something good in every time I could think of it.
00:41:17.518 -->
00:41:20.907So for you today, sam, what's something you're grateful for?
00:41:21.635 -->
00:41:24.985I love this question, by the way, and again listening to other amazing adjusted podcasts.
00:41:24.985 -->
00:41:31.619Shout out please go back to the library, where there's a ton of great episodes on Spotify or your streaming platform of choice.
00:41:32.260 -->
00:41:33.222Great content there.
00:41:33.222 -->
00:41:35.447But I have one professional and one personal.
00:41:35.447 -->
00:41:39.867So the professional thing I'm grateful for is an amazing claims product and analyst and dev team.
00:41:39.867 -->
00:41:42.722So again, I get to come on this podcast and tell everyone about it.
00:41:42.722 -->
00:41:48.476But we've got a lot of great people who have been working for decades, who really get all the credit for supporting Berkeley Industrial Comp.
00:41:48.476 -->
00:41:51.800And again, our alternative markets are BAMTEC.
00:41:51.800 -->
00:41:57.027It's too much of a mouthful even for me to say, and on a personal level, I'll call it the five Fs, right.
00:41:57.027 -->
00:42:01.798So my faith, my family, football film and finally, fast food.
00:42:01.798 -->
00:42:06.797Okay, so those five really get me up in the morning and make me excited.
00:42:06.797 -->
00:42:14.409So I'm grateful for all of those things and again, grateful for this podcast and the best co-host group product manager could ask for.
00:42:14.489 -->
00:42:17.099So, thank you all for a great conversation.
00:42:17.719 -->
00:42:27.757Thanks, Sam, Really appreciate having you as a guest today, and with that we will wrap up this episode and hope you'll follow us in future episodes releasing every two weeks on Monday.
00:42:27.757 -->
00:42:30.882You can also catch our blog on the off weeks.
00:42:30.882 -->
00:42:35.902So again, remind everybody to do right, think differently and don't forget to care.
00:42:35.902 -->
00:42:36.835And that's it, guys.
00:42:36.835 -->
00:42:37.114You.
