Digital Transformation • Culture

Chiseling out Culture for the Digital Age

Chiseling out Culture for the Digital Age

This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.

About this conversation

A CIO Talk Network conversation with Daren Hubbard (Wayne State University), Dr. Jonathan Reichental (City of Palo Alto), hosted by Sanjog Aul.

What the conversation established

The conversation established that culture, more than technology, is the main barrier to digital transformation, and that building it means removing risk aversion, silos, and old habits rather than only adding tools. Daren Hubbard of Wayne State University said digital work should extend what faculty and researchers already do, keep the vision simple around student success and faculty excellence, and favor continuous improvement over a fixed blueprint, since Moore’s Law keeps changing the tools. Dr. Jonathan Reichental of the City of Palo Alto said culture is the differentiator when organizations have equal access to technology, pointing to Kodak, which built the first digital camera but failed on culture, and to recruiting, where his team now draws 100 to 150 applicants per opening. He cited a 2013 Harvard Business Review survey in which 70% of people did not know their organization’s vision, and Zappos, where supported employees drove 400% better results, to argue for shared responsibility and permission to fail.

Host Sanjog Aul talks with Daren Hubbard, Chief Information Officer of Wayne State University, and Dr. Jonathan Reichental, Chief Information Officer of the City of Palo Alto, about chiseling out culture for the digital age. Both argue that culture, not technology, decides which organizations finish a digital transformation and which stall. Hubbard describes starting from what faculty and staff already know and favoring continuous improvement over a fixed blueprint. Reichental points to recruiting, vision, and permission to fail, citing Kodak, a 2013 Harvard Business Review survey, and Zappos.

Contributors

  • Daren Hubbard, Chief Information Officer, Wayne State University
  • Dr. Jonathan Reichental, Chief Information Officer, City of Palo Alto

Host: Sanjog Aul, Founder and Host, CIO Talk Network

On this page: Key takeaways · Chapters · Explore more · Transcript

Key takeaways

  • Daren Hubbard, Chief Information Officer of Wayne State University, says digital transformation should build on what people already know instead of changing their work wholesale. He explained that faculty and researchers bring knowledge and skills, and that new technology should help them spread and disseminate that knowledge on new platforms.
  • Dr. Jonathan Reichental, Chief Information Officer of the City of Palo Alto, argues that culture, not technology, is what differentiates organizations. He noted that two companies can have equal access to the same tools and skills, so behavior and environment decide who succeeds at digital transformation.
  • Dr. Jonathan Reichental, Chief Information Officer of the City of Palo Alto, frames Kodak as a failure of culture rather than technology. He pointed out that Kodak built the first digital camera but could not pivot its leadership, management, and people to a new way of doing business.
  • Dr. Jonathan Reichental, Chief Information Officer of the City of Palo Alto, ties culture to vision and recruiting. He cited a 2013 Harvard Business Review survey in which 70% of employees did not know their organization’s vision, and said his team now draws 100 to 150 applicants per opening because its culture creates meaning.
  • Daren Hubbard, Chief Information Officer of Wayne State University, favors continuous improvement over a fixed digital blueprint. He said the technology will always change under Moore’s Law, so the aim is the best technology experience built through a constant listening tour with campus stakeholders.
  • Daren Hubbard, Chief Information Officer of Wayne State University, says removing risk aversion is essential and points to Detroit’s auto industry. He warned that complacency about cars and reliance on trucks pushed the automakers toward bankruptcy, so leaders must take calculated risks and jettison what no longer serves the vision.

Chapters

  • 0:00 Introduction: chiseling out culture for the digital age
  • 2:16 Starting from what people already know
  • 4:32 Culture as the differentiator
  • 8:43 Why Kodak failed and recruiting for culture
  • 13:10 Continuous improvement over a fixed blueprint
  • 17:55 Vision and the Harvard data
  • 24:36 What culture looks like when things go wrong
  • 28:03 Mixing generations on the team
  • 33:39 Hiring slow and retaining the right people
  • 40:14 Shared responsibility and permission to fail
  • 47:23 Removing risk aversion, the Detroit lesson
  • 53:07 Deciding what to let go

Explore more

Transcript

Introduction: chiseling out culture for the digital age 0:00

Sanjog Aul [00:00:22]:
And the topic is Chiseling out Culture for the Digital Age, and I have Daren Hubbard, Chief Information Officer with Wayne State University. Hi, Daren. How are you?

Sanjog Aul [00:00:39]:
We have Dr. Jonathan Reichental, who’s the Chief Information Officer with City of Palo Alto. Hi, Jonathan. How are you?

Sanjog Aul [00:00:50]:
So it’s a beautiful morning, and we also wanted to talk about some creativity that Michelangelo, the famous sculptor, he used when he saw an image in a block of marble and then focused on chiseling it out and that he did by removing the extra. So the premise of this topic is in the digital age, we know we need to have culture in place and that’s actually been reported as the top barrier to proper digital transformation and the culture is not about just bringing something new but in fact identifying what we need to remove. Also, so that you’re in a way chiseling out the culture which will help prevent the risk aversion, the lack of customer centricity, and the siloed mindsets that you see in the organization which hold them back. So to that, Daren, I’ll start with you as the first question. We know everyone wants to think digital and is going digital, and there’s a lot of talk and action related to technologies, the people, the processes, the whole performance infrastructure. We also talk culture, but then that culture is still to be defined and what would that look like compared to what you have today. So could you give your view of what that culture looks like?

Starting from what people already know 2:16

Daren Hubbard [00:02:16]:
So I think when you talk about culture, it’s important to state and really affirm the fact that folks come into an organization, into any type of situation with some preconceived notions and ideas about what they need to do to be successful in that organization. And when you’re talking about trying to move that total organization to more of a digital culture, you have to really first deal with where people are coming from. And so with that, we’ve tried here at Wayne State, for example, to really embrace and affirm that folks have knowledge, they have skills, they have ideas, and really trying to support those as they are applied to digital environments. And so if you are one in an institution of higher learning, you got a lot of faculty, you’ll have a lot of researchers, folks who are knowledgeable about a lot of different topics. And in a lot of ways, digital, or not, does not change any of that knowledge that they have. Really, the digital and the use of the new technologies really then help to spread out their knowledge a little bit further or help them to disseminate it further. So we really like to work with them to not change the way that they do their work wholesale, but to really try to leverage what they are already doing more effectively, more efficiently through using this new technology. And so really trying to go digital is about adapting what’s positive, what works for them already, and helping them to extend what they are already doing to new mediums, on new platforms with new tools.

Sanjog Aul [00:03:55]:
So very well said, Daren. And now, Jonathan, when we look at digital, it’s to me and to many that I speak with, digital is, of course, about technology. But more than that, it’s about rethinking the very experience that we offer, as a result of whatever we do, whether we take care of what the customer wants or how we run things internally. And that is to be looked at besides just technology. There may be some other dimensions we have to think or rethink. What would those be?

Culture as the differentiator 4:32

Dr. Jonathan Reichental [00:04:32]:
I think culture is more important today than ever before. And what we’re seeing today is a world in which 2 companies, 2 organizations can have access to the same raw materials, a lot of times to equal amounts of skill. So what differentiates 2 companies? And it’s gonna come down to culture. And culture then is gonna influence the way in which an organization can embrace their digital transformation. And I’ve been sort of thinking about and been involved in digital transformations in some form for many years now. We think about it in terms of technology. But in reality, because we all have access to the same tech again, it’s gonna be much more about how the organization approaches it, the behaviors, all the characteristics of culture. So I think, more than ever, if your organization has started or is in the middle of your so called digital transformation, you better be really looking at, do you have the culture to enable that? Have you created an environment where people’s ideas are embraced? Where people are having fun. Where people feel that they can take risks. Where if they fail, they’ll be supported to try the next idea. So, fundamentally, to me, you gotta super focus on this topic today, on the culture piece if you’re gonna make digital transformation work.

Sanjog Aul [00:06:08]:
And to that end, Daren, when you look at the word culture, it is very fluid or rather very subjective for many. And it is rightfully so because each organization may have something different happening. The different customers, the different internal workflows, etcetera. So when you are looking at culture, are there any common denominators that you would say are critical that we at least get that foundation built in? Of course, then you tweak or do that custom layer for yourself, for your organization.

Daren Hubbard [00:06:41]:
I think there are some common themes that you can really get people around and get people to agree upon. And again, I’ve always worked in higher education and, for us, I think that culture around student success and sort of faculty excellence are things that we can embrace and really try to mold the culture around. And so doing things, whether it be administrative tasks or things that support higher learning or research endeavors, if they are focused around those two base items of student success and faculty excellence, I think things can grow from there, and things also can shape and reform themselves to better support those ideals. But you really do have to start, I think, at a common point because, again, folks have different perspectives and different focus areas inside the organization. But if we can agree on those two main things, to really get our culture to wrap around and serve each other, I think we have a better chance of success in that way.

Sanjog Aul [00:07:46]:
So when we make our effort, Jonathan, we know that one part of us is saying, okay. Let’s see if we can get people within the organizations to behave in a certain manner, which could, in some cases, be fruitful, but in many other cases, could also be a risk because this could be a superficial output or something that you’re seeing. But essentially, a culture is developed when a person is doing the right things or things conducive to the digital when no one is looking. That means you’re talking mindset. Is there, I would say, an advanced level of effort that needs to go in which will allow you to traverse from just shifting the mindset, which is conducive, to digital, to actually a mindset where then these people turn out as catalyst versus a bunch of sheep that you are trying to be a shepherd for.

Why Kodak failed and recruiting for culture 8:43

Dr. Jonathan Reichental [00:08:43]:
Well, one thing that organizations have to recognize is that you don’t shift culture in a 2 month initiative. This is for the long term, and it requires a significant commitment from leadership, first of all. They have to make that choice. And then it’s working with the organization for a long time to make the shift. Some companies never make the change. I was thinking about the famous story of Kodak. People say Kodak failed because they didn’t see digital cameras. They didn’t see the digital phenomena happen. And that’s actually wrong. The reality is Kodak created the first digital camera. They were actually ahead of the game. And so why did they fail? It was really a failure of culture. They thought that they could continue to market their existing business and sort of overcome the other major trend that was happening in the marketplace. And their environment, their leadership, their management, their people, were not in a position where they could quickly pivot to a completely new mindset, start thinking about a different way of doing business that eventually they would have to radically change in how they approach what they were doing to be able to compete and be successful. And they didn’t, and the rest is history. So I think that’s part of it. I think it has to come at sort of from the very beginning of recruitment, right through to all the different aspects of the experience an individual has at a business. When I look at the City of Palo Alto and particularly my team, I always talk about what’s it like today recruiting versus what it was like when we started our transformation 5 years ago? When we would have an opening at my team, we’d be lucky if we got maybe 5 to 10 people applying. And today, when we have an opening, we get 100 people, maybe 150 people. And I’m very proud of that number because we’re competing with Facebook and Google and LinkedIn, all the other folks around in my neighborhood. And the reason is, I ask people when they come to the interview, why are you applying? Because we’ve been successful in communicating that we have a culture that creates meaning, that is a culture that’s fun, where people come to work, they have a purpose. That’s where culture starts, with recruiting. In terms of how you can make a change every single day, is how you recruit. And that’s an area also to focus on.

Daren Hubbard [00:11:33]:
I’d like to piggyback on what he said really quick if we could. I think a lot of what Jonathan just mentioned is around empowering folks when they first get in the door. That if you’ve got a culture established in your organization and you empower your team members as they come on board, that this is a place that embraces new technology, that embraces the ability for folks to add positively to the organization, then cultural shifts or mindset shifts are things that you don’t necessarily have to continue to build or try to start. They are in place from the very beginning, and you just leverage them continually and promote and really affirm that folks have that power to really embrace things and to make change from their own personal level.

Sanjog Aul [00:12:24]:
And so to that, Daren, when we look at going digital and then trying to become a conducive culture for it, we, on one hand, would like to know what are we pursuing. But at the other hand, digital is not something a destination. It’s gonna be a journey because today you are pursuing one set of capabilities or what your organization or what your customer wants. But the customer is gonna be fickle. The environment is gonna be changing fast. It could be another. So are we not better off saying no to that holy grail definition or blueprinting and just focus on becoming better internally for us to serve the best externally?

Continuous improvement over a fixed blueprint 13:10

Daren Hubbard [00:13:10]:
Yeah. I would say the latter is probably true. It’s definitely true for me and my organization. We focus on continuous improvement. And I like to tell folks, even though we’re a technology organization, it’s not about the technology. It’s about our ability to support individuals, our partners on our campus, in our environment, to do better the things that they need to do to move the whole organization forward. And so if we sit back and design some blueprint to future technology success, we are gonna miss the mark. The technology deal is always gonna change. It’s always gonna be renewed. We still have Moore’s Law in effect, and that trickles down to everything that we do around technology. And so we have to focus on adding the value and really having a culture that supports us being able to work side by side in partnership with our business areas and then our main customers inside our organization. But then also with each other as technologists to embrace what’s new and not be so wedded to our particular religion around our technology choices, but really to focus on how can we use all these tools that we may have at our disposal to move the whole organization forward.

Sanjog Aul [00:14:32]:
And, Jonathan, I might throw a curveball at you on this one where a leadership is defined where someone allows other people to follow a vision. That means you define a vision, and then other people follow it. But guess in the digital age, we just discussed and, at least, Daren, you had endorsed the fact that you can truly not be just preparing for tomorrow. And if you don’t prepare for tomorrow or the day after, that means it’s tough to really put a blueprint or a vision in place. And when you don’t have a vision in place, what is the basis of someone following a leader?

Sanjog Aul [00:17:10]:
So, Jonathan, here is an interesting twist where digital age means everything could change tomorrow. When you bring people in, as you mentioned, when people come to you and competing with Googles and Facebooks of the world, you promise them a journey and a good journey. But without a good enough vision, you cannot really have them follow a certain path, and without that, they might get confused. That’s the risk at least. So especially in digital age, without having a clear or not having a vision, how would you lead the troops, and how will you in fact even build a culture without having an end goal in mind?

Vision and the Harvard data 17:55

Dr. Jonathan Reichental [00:17:55]:
Well, you’re at a disadvantage if you don’t have a vision. But here’s some interesting data on this topic. There’s a Harvard Business Review survey done in 2013. People were asked in their organizations whether they know their organization’s vision. And the answer was sobering. 70% didn’t know their organization’s vision. That all translates into 70% of people who come to work don’t know what they’re working for. They don’t know what they’re doing. I mean, you think they’re doing tasks. And this is something, when I get in front of a lot of the tech audiences I speak to, I tell them when you go back to the office, talk to your teams about your vision. Have that discussion because you gotta come into work and actually know what the higher purpose is. I mean, that’s what people want. So in my team, when I first got here, we created this pretty high level vision to build and enable leading digital city. And that’s a pretty lofty goal. And I think to your point earlier, when we were talking on flying there, Sanjog, it can’t be written such that it means nothing. And I agree with that. So we have to have discussions that are at all our meetings, in our division meetings, in our all hands meetings about what does it mean to us. What does that look like in terms of actions? And on a weekly basis, things are gonna shift. There’s gonna be new tech. It’s gonna be a new cool thing or a new project. But fundamentally, we’re all marching towards what we aspire to be, and that’s that vision to be now a leading, smart and digital city. So the feedback I’ve received is people have a good understanding of the big picture. They might not know, on any given week, where we’re at in terms of the journey or whether we’re headed in the right direction. But they know what the overall goal is, and it has created the right context for the right discussions. And ultimately, we can always go back to, this is where we are headed. We made some twists and turns, but we know what the destination is.

Sanjog Aul [00:20:08]:
And to that end, Daren, when you look at an organization and you are trying to create that vision and subsequently the culture, it truly cannot be done in the ivory tower or the corner office. And if you are looking to get people to provide you a view of what they would like to see, you could get, I mean, you talk thousand people, you’ll get thousand inputs. Who do you keep happy? How do you come up with a gross aggregate, if you will, aggregate view, which you then convert into a vision and especially when you’re dealing with everything being influx. Because today, they may say, I want this type of not a culture, but this is the type of work that I would like to do, which is which I’ll find meaningful. Tomorrow something changes, they may say, my needs, my aspirations, my desires have changed. So do you keep playing this moving target vision exercise?

Daren Hubbard [00:21:06]:
Actually, no. I kinda keep the vision of the organization relatively simple and straightforward. I think much like Jonathan stated for the City of Palo Alto to be this great digital and smart city, from Wayne State University in terms of technology. Our goal is to provide the best technology experience, whatever that may be. And so with that, we take our show on the road, so to speak, to go and interface and build partnerships with all the key campus stakeholders and community members. And take from that, literally that listening tour that’s always underway. Take from that specific things that need to be adjusted or focused on in route to that excellent technology experience. And so I think as we work with our teams, as we really try to communicate what that overall vision is, we just have to be consistent around. We’re trying to be the best. We’re trying to do things in a way that promotes the overall goals of the university, and we’re trying to bring the best technology to bear on that experience. And again, having a vision like that, that’s easy to communicate to your teams, easy to communicate to the people who you support. It’s easy then to take in that information and then apply the best technology that you have access to at that particular time to get you down the road further to closer to that goal. We understand too that those goals and visions are meant to be a little bit lofty so that you’re always driving to them because no one wants to work in an organization that’s stagnant or felt like they’ve accomplished something and now we just have to play defense. Folks really like environments to work in that are pushing forward, that are always out there trying to find the better way, the better how to build the better mousetrap, so to speak. And there’s a great book by Jim Collins called Good to Great. He talks a lot about developing what he called the hedgehog principle. Sort of this simple principle or idea or concept that can keep your organization fresh on its feet and really moving towards sort of higher and better articulated goals and visions for success. And so we try to take that principle and foster it in a way that we can all work around it and work toward it. And so, in terms of a vision, we try to keep it simple and communicate and get information back to help build on it.

Sanjog Aul [00:23:40]:
So getting real, Jonathan, when we look at these visions. So Daren mentioned that he likes to, as part of the vision, bring the best technology, and you mentioned about helping City become the best digital city. All of that is good, but then when a person is getting buried with 20 different projects, you introduce agile approach where a person literally doesn’t get a chance to breathe. The happiness, the fun, bringing, having parties or bringing your dog to the office, all of those cool things to some, it goes to a certain extent, but then it may not really lead you to build that culture that you want when people are getting burnt out. So can you realistically have a culture which is conducive to the digital age, allow the organization to move fast enough, and not burn the very people who constitute the culture?

What culture looks like when things go wrong 24:36

Dr. Jonathan Reichental [00:24:36]:
Well, this happens all the time. And it does take an enlightened and engaged organization to identify those symptoms and do something about it. I always say, it’s really easy when things are going good, to say you got a great culture. You can have celebrations. Things are smooth. I think what defines the culture is how the organization behaves when things are not going so well. In the example you paint there where perhaps the organization needs to quickly shift to upgrade a product or develop a new solution and it’s all hands on deck and things get dicey, how does the culture then operate? Do people help each other? What happens when there’s tension or people are frustrated? Is there an outlet for that? Is there a respect for people when they demonstrate in all sorts of ways a high degree of frustration? Those are telling. We’re in the IT business, and if you got a good IT organization, everyday things just run and you do your projects and you run your data center. But from time to time, we have some exciting moments where there’s a DDoS attack or there’s a major system that’s down and you can’t put your finger on it. Very quickly things get difficult. I kinda always like to stop the team and say, now is our time to shine. This is where we’re gonna show what we’re about. It’s how we behave over the next few days. It won’t be about if we start hating on each other and stopping people from expressing points of view or bracing ideas or supporting each other in those difficult moments, those are gonna be indicators that we may not have the culture we think we have. So those are things to look for. I think leadership really needs to step up when things are tough. And that’s probably the best answer I can give you for your question.

Sanjog Aul [00:27:03]:
So Daren, speed and excitement is not same as meaningful for all generations that you will have to deal with. Talk about digital, things move fast. Speed is expected. Excitement is desired by the leaders that, okay, if I’m building a good culture, everyone is excited. You take different generations. Somebody’s close to retirement. They may have a different view of what they wanted for the time when they’re awake to someone who is a Gen x who wants work life balance to the Gen y’s and millennials who want excitement. How do you create a hybrid culture, if you will, where everyone gets what they want so that they are able to contribute while thinking what is being done in the organization as a whole is meaningful for the whole organization because if someone who’s a different generation may not find speed and excitement to be great, but they are also expected to take a part in it. How do you tackle this?

Mixing generations on the team 28:03

Daren Hubbard [00:28:03]:
I think it comes down to really trying to get to know your teams and trying to constructively and intentionally build teams that do have a mix of personalities and generations if you can because you’re always gonna need folks to play particular roles. When you’re kicking off a project, sometimes you need those folks who really crave the excitement in the new to really step up and really get people pumped up about coming along on this new journey. However, when you get to the tail end of something where you’ve already deployed it, everything’s moving into production, there’s gonna be some folks who want that stability and that base level consistency of maintenance. And so, again, having the different generations present on your team at the same time is great because in an IT organization, you gotta do all that stuff. You gotta bring the excitement. You gotta bring the new, but you also have to maintain and stay up and stay current with the things that you’ve been providing for your organization. And so trying to find that balance and really offering opportunity for folks to move around. Because just because you may be at the end of your career heading towards retirement, you may still want to do something new. You may have gotten into technology in the first place because you were excited about new initiatives, new digital opportunities to change the way people do business or run their lives. And so you have to be open to allow for folks to participate at different levels and different projects where you have different roles and needs. But then you also have to try to be intentional about making sure that you provide opportunities for folks to keep them engaged at places where they can do their best. Because if you try to put the person completely fish out of water in something that they are really not feeling and not really engaged in, you’re gonna risk the overall success of a project. So it’s a balancing act, but it is one that I think most IT organizations really do have to learn how to do and try to do well in order to be successful.

Sanjog Aul [00:30:23]:
Jonathan, what if you have 2 or 3 different flavors or 2 or 3 different generations or mindset or personalities who may have all the skills that you need, but they bring a different mindset which would be the best they would like to keep in order for them to join you. So you mentioned about hiring people. So you may have a point of entry at the time when you mention something to these people and create excitement and that’s why they would get attracted to you. Another is to retain them. And now you’re talking not just the youngsters who are looking for the Google Facebook kind of culture, but also the other people within your organization. So I’m not repeating the same question I asked Daren, but here, would you give a different flavor of what your culture is to different people at the time of entry or for retention depending on who they are? And if you do, how do you stay consistent with what that culture, that one culture you’re trying to develop when you’re giving different things, like different strokes for different folks.

Sanjog Aul [00:33:17]:
So, Jonathan, different generations, different mindsets, different personalities, at the point of hiring them or retaining them, you have to tell what would mean well and stay consistent with that one vision, one culture you’re trying to develop. That doesn’t look like a straightforward exercise. So how do you tackle this?

Hiring slow and retaining the right people 33:39

Dr. Jonathan Reichental [00:33:39]:
You’re right about that. When you’re interviewing a person for an opportunity, the person should be interviewing you too. Particularly in the tech field today, we are very fortunate that there are lots of opportunities. The marketplace is pretty good right now. So prospective employees have options. So you need to really look deeply at the organization you’re joining. Does it reflect your values? Is it a domain that you’re interested and excited about? So in a way, the marketplace is filtering folks. They come, finally, the person decided that they’re interested in working for my organization and the city. They come, go through the panels. They’re finally in front of me. We’re having that conversation. And I really do hope there’s an interview going both ways. What I’m looking for are some sort of core behaviors. I’m looking for great communicators. I’m looking for people who are excited about public service, about a higher mission. And if the person is using words or is kinda talking about the work in a way that perhaps, ultimately, I believe that they don’t fully understand what they’re going to do or that they have a different expectation, we’ll discuss that. And so the recruitment process, it shouldn’t be long. It’s hire slow, fire fast. So that’s the mantra. Take your time where you can. You don’t lose a great candidate, of course. And try to vet people out. Now let’s continue that sort of thought. The person comes on board. You think everything’s great. And then, after a few months that person is having doubts. Did they make the right decision? I think there’s an ongoing conversation. I would recommend to leaders that they have regular check ins with not only the people who directly report to them, but every level of their organization. It’s a great way to find out what’s going on. Although mostly people won’t share the full truth with you. But if you can figure out, are you happy? Is it working out? Is it what you expected? What can we do? And so there is an ongoing monitoring piece to this that’s valuable. But there is another part which is more sobering, which is it might have been a bad hire. The person might not be a good fit. They might not align with your vision. And we shouldn’t shy away from that. We should confront it, have that conversation. The best case scenario is that a person recognizes that and just voluntarily leaves. If they try to fight it, despite what they feel, that’s just gonna create uncomfortable circumstances. So you’re trying to ensure that you’ve hired the right people and you’re retaining the right people.

Sanjog Aul [00:36:50]:
So Daren, when you look at the policies and governance and command and control structure which we used to be using for our technology management or even our business management, all of that cannot really be sustainable when you talk about the digital age, which means you have to start looking at creating a culture which will allow experimentation. Not again, reckless experimentation, but just about enough dose of open sandboxing that it will allow the new ideas to come and also then the collaboration. What’s the key to you allowing that while staying true to the culture that you are developing for digital?

Daren Hubbard [00:37:36]:
So I think one of the keys is you have to get people, particularly the folks that report to you who have responsibility for initiatives or certain segments of your infrastructure, empower them to sort of push the envelope and try things in a manner that is conducive to the needs of your organization overall. And so, you’re right. Sometimes our governance structures really do lag behind both the needs of the organization and the technology that’s available. And so in that, sometimes you have to let people push a little bit ahead and then try to clear the path for them, kind of retrospectively, where you can so that they can go out and really try to make things better. And it always helps when your team is working directly with customers to meet the needs that they’re seeing pretty much on the front lines, even if sometimes that gets out ahead of where your governance structure may be able to respond to it. Because if you’re dealing with issues right there as they occur, really working in partnership, those things will be communicated to governance, and you would likely get approval to go forward anyway. And so it’s one of those areas where you really do have to create a culture of empowerment around really helping to solve problems as opposed to just following guidelines and rule sets. Those are important for some things, and you can’t completely ignore them. But you do have to give folks a little bit of leeway to keep things moving forward as best we can, given the pace of technology and the pace of changes that need to occur.

Sanjog Aul [00:39:26]:
Jonathan, when you are looking at this scenario of digital, fully cooked. You do not know what’s coming down the pike. Of course, there is learning for you. And when you yourself are learning and, basically, your neck is on the line, how the organization changes direction and what kind of culture you develop and how do you move forward. That means you’re tempted to take a closer look at everything that’s going on. And if you start doing it, that could stifle the very experimentation and the collaboration because people feel less enthused about collaboration and experimentation when they see somebody’s closely watching. How do you resist that temptation and look the other way so people can play?

Shared responsibility and permission to fail 40:14

Dr. Jonathan Reichental [00:40:14]:
Big question there. One of the things I just wanted to challenge a little bit was, you said potentially if a person is doing something risky or their neck is on the line, I think right there you got a problem. If you are pointing to one person and saying if they do this and it fails, they’re in trouble, you got a problematic culture right there. There’s shared responsibility today. We all have to have a bit of skin in this, and we all have to agree to it. And we have to give people the confidence and permission to do the things they’re doing with full support. Otherwise, you won’t see innovation in your organization. If people feel like they’re gonna be punished for failing or not getting the result that’s expected, they’re not gonna do it. And they’re gonna be quiet. And you can see that in organizations that are more conservative or just don’t have the success in the marketplace that they would like. Tony Hsieh, who founded Zappos and captured in his book Delivering Happiness, talks about happy supported employees create organizations that have 400% better results in the marketplace. And that’s a real number. So, I think we have to be deliberate and communicate clearly the permission we’re giving to people and how we’ll operate when an experiment or an innovation doesn’t go right, how the individual will be supported by everybody. That’s the approach. It’s not about looking the other way and sort of having a person go off and do their thing. It’s about a shared responsibility to innovation, to taking risks, and then being highly supportive when things don’t go so well.

Sanjog Aul [00:42:22]:
So you want to still stay attached, and I am asking for a situation where you would purposely want to look away. Because you are involved, you may be undermining what otherwise could have been experimented and or innovated. You always need to be that. I mean, how do you resist that temptation that I have to stay involved? How about a little bit of a hands off?

Dr. Jonathan Reichental [00:42:49]:
I think that’s right too. People that are being watched behave differently. We know about that. And so, I think probably at the core of your question is the question of trust. Do you, as a leader, trust the people you’re empowering to do something to be able to walk away and say, you know what? Report back to me in 6 months. I don’t need to know what you’re doing every day. That’s probably a measure of trust and really difficult to do. We shouldn’t trivialize this. It’s really difficult to do that. Because as managers, we feel ourselves accountable. We want to be involved because we want it to go right. And so it takes a high degree of trust. It also goes back to one of the core points I said earlier, which is providing sufficient buffer that when that team or that individual is having problems or the effort is failing that there’s that buffer to support them so they’re not in trouble. So I think if you combine those two, you give people the space to innovate and you turn away your full trust in their ability to at least give everything a good shot. And then if it doesn’t go so well, they have your support at that point.

Sanjog Aul [00:44:11]:
We’ll continue this conversation of how the leader themselves and, Daren, this is gonna be for you. Is one is to be able to trust as Jonathan mentioned so people can experiment. Another is to actually start fostering a culture where whether you’re talking to the people above you, which is executive management, or the people below you, to start basically stop a recursion, risk aversion. Because if there is a mentality that, okay, things are going well and I know I’m going to do whatever I’m gonna do for digital, but let me do it with minimized risk. If we continue with that word risk as top of mind, then maybe we are not doing some of those daredevil things we ought to be doing for us to charge ahead and make a difference. How do we remove risk aversion from the organization in order to build a good conducive culture for the digital age? In short, that’s the question.

Sanjog Aul [00:47:00]:
So risk aversion is key, which is actually, in many cases, paralyzing organizations from top to bottom, even though you provide them immunity or you say I’m gonna allow you to experiment. But people simply would not want to bring ideas to you because they feel it’s not worth it. What do you do about that, Daren?

Removing risk aversion, the Detroit lesson 47:23

Daren Hubbard [00:47:23]:
I think you do have to have a culture of really being open to opportunity and really letting both the people on your team who report to you, and then also educating the folks that you report to that in order to improve things, in order to drive continuous improvement in an organization, sometimes you gotta take a chance. You gotta try and push yourself a little bit beyond where you feel comfortable to get that great benefit at the other side. And so, just like in investing, sometimes the things that have high reward generally come with a little bit greater risk. And for organizations, if it was really simple and easy to do these transformations, everybody would do them. And that’s what kind of separates out organizations who have a level of inertia, and they just sort of stay put, and they don’t try anything new. And you find over time that those organizations start to atrophy and decline. I’m here in the city of Detroit, and we all know with our auto industry, they had a certain level of complacency around the cars that they were making and the reliance on trucks that when a change in the marketplace happened, that inertia led them almost all of them to bankruptcy. And so, again, learning from those types of examples, you have to try to push. You have to take a risk, try something new, go a little bit further out of your comfort zone to really be able to take advantage of the greater rewards that could be on the other side.

Sanjog Aul [00:48:59]:
And, coming to you, Jonathan, when you are looking at the internal processes and you got the overall customer journeys, you got a lot of different departments thinking their own way. So while you may be sitting there trying to build a conducive culture and try to have that sentiment across the board, but people are undermining the overall potential of digital because they’re thinking in silos because they feel that’s how they’re supposed to behave. So is that, say, your job or somebody’s job, that one person’s job to build one family, one village, if you will?

Dr. Jonathan Reichental [00:49:37]:
I would make the case that this is probably the most prolific and visible challenge that organizations are having today. It is the poor distribution of belief in a common vision and how to execute it. Particularly now since so many organizations are either about to jump on or are in the process of a digital transformation. I would bet that everyone listening and the three of us experience in our organizations that this phenomena every single day, that you might say, hey, we’re on board. We get it. We’re going forward. But you’re gonna confront colleagues who are in a different place, for a variety of reasons, whether it’s incentives, or different agendas. They may not yet be on board or may not believe in it. And it actually ultimately can be the reason why many cultural shifts and strategies ultimately fail is that the influential folks and the leaders who needed to be part of it did not buy in. So what differentiates then those kind of companies from the companies that perform well is that they created an environment where in the private sector there are incentives that suggest that if you’re not on board, you may not be in the right place. Or it becomes potentially a performance challenge. If you have a strong leader who is trying to bring the organization in a particular direction, ultimately, if you don’t agree with it, you’re not on board, let’s have the conversation, are you in the right place? That’s a little bit more cutthroat, and one hopes you don’t get to that extreme. So part of your question was, whose job is it? And you asked if it was my job. I have a role, but I don’t know this is my job to make sure everybody’s on the same page. I think what we can do as CIOs is paint a compelling vision, demonstrate good behaviors that are the kind of behaviors you wanna model for the organization. Really be clear about advantages and why somebody should get on board and what’s in it for them and their organization. And hopefully, you start to see the needle move forward. But keeping in mind that this is one of the hardest things to do.

Sanjog Aul [00:52:37]:
And to that end, Daren, this is one of our last questions. If you had to make an impact on hacking away or chiseling away the additional slack that we’ve been carrying or the baggage, how do you actually start? How do you rationalize what to hack away so that your digital image or digital sculpture that you’re trying to build in terms of culture start shaping up?

Deciding what to let go 53:07

Daren Hubbard [00:53:07]:
It takes a lot of time and listening to really understand where it is that the organization really wants to go. I think in the public sector, we have and are working in organizations that have existed a long time. Cities and universities are not like startup companies that can change their culture on a dime or have the flexibility to just say, we’re just not gonna do this anymore. We’re gonna do something different. Your ability to pivot is limited. And so with that, you really have to be sure about whether or not the leadership, the collective leadership that you both report to and are in charge of really is on the same page around where it is you’re trying to go, what the overall vision of that organization is. And then make some calculated and really introspective looks at what things do you need to jettison in order to stay true to that end goal or that higher vision that the organization wants. And you gotta get as much buy-in as you can, but sometimes, in your role, you have to take calculated risk to say, this thing we should let go. We have been doing this for 10, 20 years. It may be time to let it go. And I think in IT in particular, we’re always faced with things that while they may still be working, a new technology comes in and allows you to do things better. And you have to be open and accessible to letting things go and trying something new.

Contributors

Daren Hubbard

Daren Hubbard, Chief Information Officer, Wayne State University

Daren Hubbard is currently Chief Information Officer and Associate Vice President for computing and information technology at Wayne State University in Detroit, Michigan. Wayne State University is a large urban research university with the... More   View all posts
Dr. Jonathan Reichental

Dr. Jonathan Reichental, Chief Information Officer, City of Palo Alto

For over 25 years, Dr. Jonathan Reichental has been successfully helping organizations leverage the value of information and communications technology to solve business problems, increase effectiveness, and support revenue growth. He has ex... More   View all posts
Add Comment
Click here to post a comment

Advertisement

TECHM - DNA - MPU01 - 300x250
Daren Hubbard