Episode 25: (Data Bites) The Easy Road to Digital Transformation

From our interview with Tony Saldanha, on Monday, we learned that Digital Transformation is something that cannot be avoided.

Instead of spending time on getting the newest and best technologies, it behooves industries and employees alike to focus more on creating an atmosphere and culture that accepts and loves change. By instilling a critical thinking and creative mindset, digital transformation will follow!

To keep up with the podcast be sure to visit our website at datacouture.org, follow us on twitter @datacouturepod, and on instagram @datacouturepodcast. And, if you’d like to help support future episodes, then consider becoming a patron at patreon.com/datacouture!

Music for the show: Foolish Game / God Don’t Work On Commission by spinmeister (c) copyright 2014 Licensed under a Creative Commons Attribution (3.0) license. http://dig.ccmixter.org/files/spinmeister/46822 Ft: Snowflake

Show Notes:

Welcome to data couture, the podcast about data culture at work at home, and on the go. I’m your host, Jordan Bohall. If you like what you hear, be sure to subscribe lows, get the latest episodes wherever you get podcasts. And if you’d like to stay up to date on everything data couture, be sure to follow us on Twitter at data couture pod. Finally, if you’d like to help support this in future episodes, consider becoming a patron of the podcast through our
Patreon page@patreon.com. forward slash data couture. Now on to the show.

Welcome to data couture, I’m your host Jordan. And on today’s data bites, we’re going to be talking about outcome based design. So following up from the interview with Tony on Monday case you missed it, Tony. So Donna was our special guest. And he spoke quite a bit about digital transformation and part of that digital transformation piece is focusing not so much on the technology itself, but rather on the outcomes that they produce. And so all of these new technologies all for example, ai or machine learning or predictive analytics or robotic process, automation, any of these they are purely

In the background, at the end of the day, they’re going to be like the furniture of our businesses, they’re going to be thought of as more or less just those pieces that we need those necessary pieces that we need to operate our business. So, in effect, to perform a digital transformation, instead of focusing on the digital pieces, the data pieces, the new bits of technology, what we should be focusing on, is, or are the outcomes of whatever processes we’re trying to digitally transform. What does this mean? This means that instead of looking at the newest and best bit of technology that has just come out from whichever vendor, we should, instead be focusing on what we’re trying to solve.

And so this gives a lot of credence towards, say the financial services industry where there’s a lot of legacy technology but at the end of the day, what we care most about is We can fund alone, for example, or we can open a checking account or we can help our members or our customers along their financial journey. And so that really is the outcome we’re searching for. We’re searching for that outcome where our members, our customers are able to achieve whatever financial goals they have, of course, along with their financial planners, and the people that are helping them plan their financial journeys, but the members, the customers, they don’t care about the technology just in case it blends in smoothly with their particular life.

And so when we’re thinking about digital transformation, we should stop thinking so much about, well, this technology or will this platform or will this SAS the software as a service? will this help us do this better? No. Instead, we should think of it as a holistic project, what’s our end goal? We want to make sure that our customers can open up a new checking account that they
can access that checking account on every single platform on every single system or every single channel through which they interact with us, they can have that same experience across the whole organization.

What does that mean technology, you better believe it means technology, it means quite a bit of automation, it means quite a bit of connecting various systems together, it means quite a bit about knowing who our customers are members are. However, if we just focus on the technology, we we look at the trees instead of the force, we don’t see the whole picture, we just see little bits and pieces that can fix this problem or that problem. We can connect this bit of data to that bit of data. Instead of thinking about the member side of things, we want to help our members we want to help our customers in this example. And so I think Tony suggestion, which is have the design thinking have the end goal orientation.

to come up with a solution, and then the technology will fall into place, whether or not you’re using legacy technology or whether or not you use some new bit of tech, it’s a relevance. And so I find this an interesting notion of digital transformation. Because when we think of digital transformation, we usually think of employing the latest and greatest bits of technology in order to solve these problems that we think we have. Instead, what Tony saying is, no, we already have a technology, we have so many things in place. Instead, we should be thinking about the outcome because the tech will fall into place. And so what does that mean on a practical application? What does that mean for your actual business?

Well, it means perhaps, and I hate to use this analogy, but don’t go chasing waterfalls, TLC to date myself. Nevertheless, what it means is we have lots of smart people working in our organization. And we don’t need to go looking for the newest and best tech that hasn’t proven itself, all we have to do is think critically and think creatively about how this tech can actually achieve this end goal. So what does that mean? Well, to hearken back to previous episodes and the previous week, we need to have lots of people with strong capabilities in digital literacy. Why is that important? Because to have digital literacy means to, and again, I know that there are hundreds and hundreds of different definitions. And there’s so many different certifications and pads towards becoming digitally literate. But what I’m trying to say here is we have these people who are experts in their bit of technology, we need to gather them together, we need to get
I don’t know what to call it, maybe we can call it a scrum team. If you want an agile team, call it a lean team or waterfall team.

Whatever management style floats your boat. But nevertheless, we need to have a group of experts sitting together, seeing this in solution that we’re trying to solve, in my pet case, my pet example, having a member, be able to open up a checking account and having a good experience with that, and having that available in every single channel in which that customer interacts with your bank or your institution. And try to determine how the technology that already exists and the technology that’s already in place and stood up and most importantly, that’s already paid for. How can that solve the problem?

And that’s, that’s a beautiful thing. That’s That’s a beautiful definition of digital transformation. Why? Because it makes it so much more accessible than the kind of opaque black box the version of digital transformation or the notion of digital transformation that we’re all used to here. And used to saying but not actually acting upon. So with Tony’s version of digital transformation, it really just means thinking critically, it just means being problem solvers. I really, I really like that. That means that every one of us every one of our companies can truly achieve a digital transformation without really investing too much more and brand new technologies or never, or maybe not new technologies but not investing in something that they don’t know anything about.

I’d love to hear your comments, your suggestions, your thoughts, be sure to leave them down below in the comments section and I will talk to you next time.
That’s it for the show. Thank you for listening. And if you liked what you’ve heard, then consider leaving a comment or like down below. Stay up to date on everything data couture, be sure to follow us on Twitter at data couture pod, consider becoming a patron@patreon.com forward slash data couture.
Music for the podcast. It’s called foolish game. God don’t work on commission by the artist spin Meister used under a Creative Commons Attribution 3.0 license, writing, editing and production of the podcast is by your host, Jordan Bohall.

Liked it? Take a second to support Data Couture on Patreon!

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.