Customer Experience • Innovation • Leadership

Can IT Push Innovation Beyond All Customer Expectation?

Can IT Push Innovation Beyond All Customer Expectation?

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 Brian Siwak (District of Columbia), hosted by Sanjog Aul.

What the conversation established

The conversation established that Brian Siwak of District of Columbia treats true innovation as new ideas that carry a real chance of failure, separate from incremental fixes to products that already exist. Siwak said teams should accept risk when the cost of failure is low, citing his rule to fail fast and cheap, and should put rough prototypes and pilots in front of citizens and agencies within weeks rather than specifying large projects up front. He said the district’s Apps for Democracy competition produced a cost avoidance it put at $2,300,000, and that a public data catalog begun in 2005 opened a wave of government data availability. Siwak argued that public sector ROI can be a better or new service rather than only financial return, that design should start from customer experience, and that opening data, such as DMV queue times, lets enterprising citizens build applications the government did not have to fund.

Host Sanjog Aul talks with Brian Siwak, CTO of District of Columbia, about whether IT can push innovation past what customers expect. Siwak separates true innovation, which carries a real risk of failure, from incremental improvement of products that already exist, and he describes running short prototypes and pilots that citizens and agencies test before anything is built out. He points to D.C. work such as the Apps for Democracy competition and a public data catalog started in 2005, and he explains how public sector ROI can mean a better or new service rather than only financial return. He argues that teams should accept failure, design for customer experience first, and open government data so outside developers can build on it.

Contributors

  • Brian Siwak, CTO, District of Columbia

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

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

Key takeaways

  • Brian Siwak, CTO of District of Columbia, defines true innovation as brand new ideas that carry a real risk of failure, not incremental improvements to products that already exist. He said a research and development group in his agency should not be constrained by current customers’ wishes, or it will never break outside the box.
  • Brian Siwak of District of Columbia argues that innovating means accepting risk when the cost of failure is low. His rule is to fail fast and cheap, trying many things and learning quickly from what does not work rather than settling for the status quo.
  • Brian Siwak of District of Columbia builds rough prototypes and pilots and puts them in front of users within weeks to get feedback early. He said the district asks what can be developed in a month or six weeks instead of running multi year projects costing millions that may miss changing needs.
  • Brian Siwak of District of Columbia says public sector ROI is not only financial but can be a better or new service for citizens. He said the Apps for Democracy competition let the district point to a cost avoidance it put at $2,300,000 from launching that single program.
  • Brian Siwak of District of Columbia favors opening government data so outside developers can build on it. He cited plans to publish DMV queue data across the city so an enterprising citizen could create an application showing current wait times and warning a person before their ticket is called.
  • Brian Siwak of District of Columbia says teams should design for customer experience first and expect to keep innovating without end. He pointed to the iPhone released in 2007 as an example of simple, intuitive design, and said any organization that decides it is done innovating is not worth following.

Chapters

  • 0:00 Introduction: IT pushing innovation beyond customer expectation
  • 1:57 D.C. and the Apps for Democracy competition
  • 3:43 What counts as true innovation
  • 5:12 Research and development free of customer constraints
  • 7:26 Accepting risk and failing fast and cheap
  • 9:21 Prototypes, pilots, and agile delivery
  • 17:54 ROI for public versus private innovation
  • 26:14 Everyone and everything as an always on sensor
  • 31:14 Designing for customer experience first
  • 36:56 Opening DMV data to citizen developers
  • 50:20 Choosing innovative partners and suppliers

Explore more

Transcript

Introduction: IT pushing innovation beyond customer expectation 0:00

Sanjog Aul [00:00:48]:
Today’s topic is can IT push innovation beyond all customer expectation? And our guest for today’s show is Brian Siwak, who is the CTO of District of Columbia, that’s Washington, D.C. How’s work life and the weather?

Brian Siwak [00:01:19]:
For those of the listeners out there that are familiar with D.C., it’s been a pretty hot summer, both weather-wise and politically. So, it’s been interesting, but we’re having a great time and really doing some interesting things over here.

Sanjog Aul [00:01:33]:
So, in terms of the topic that we have picked up today, and of course, you’re on that hot seat where, yes, you are expected to keep the desktops running and everything, but I’m sure the expectations are far beyond that with everything getting changed in the government and the world around us. So how do you see the world changing in the last couple of years?

D.C. and the Apps for Democracy competition 1:57

Brian Siwak [00:01:57]:
I think D.C. has been at the forefront of many of these changes that we’re seeing, especially in the public sector, over the last few years. I think a lot of it started with some of the work that we did around leveraging citizen input for helping connect citizens to their government and to the data that we publish. You might remember, a couple of years ago, we launched the first Apps for Democracy competition, which, I think, really, for the first time, leveraged citizen engagement, and got people involved in the process of leveraging information that we put out there to create applications that were interesting for themselves and their fellow citizens. And that really launched what I think is a huge revolution. If you look at the whole Apps for X idea, it’s being used in many, many different places, governments, both here in the United States and abroad, as well as places like the Army. The Army just completed an Apps for the Army competition, which evidently generated a whole host of really interesting and innovative solutions that were actually generated by folks within the Army themselves. So we really have, I think, pushed the envelope quite a bit, and we continue to do so every day.

Sanjog Aul [00:03:18]:
Now with respect to the word innovation, and I would not say it’s cliched, it is the hot thing that people are talking about, and in fact they’re saying that’s the only way we could survive in the rapidly changing world. How much, besides the enthusiasm that we have, do you think the people know what this innovation term means and how to make the best use of it?

What counts as true innovation 3:43

Brian Siwak [00:03:43]:
I think it’s something that we feel our way through, and with any term, there are any number of different definitions that would apply given different situations. So innovation in and of itself is hard to define. I think we need to look at the different things that we’re talking about and try to understand exactly what constitutes innovation in that context. So, for example, if we are trying to build a better mousetrap, right? We’re trying to take a product or service that we currently provide and make it better. Is that true innovation? Or is that just something that we are responding to our customers’ feedback and saying, okay, well, we can tweak this and tweak that? I tend to look at innovation really as truly new concepts that have never been explored before, things that actually have the risk of failure associated with them, but also have the risk of potentially breaking new ground and trying to really create some new ideas that we can put out there in the world.

Sanjog Aul [00:04:51]:
With respect to innovation, that’s another thing people do is, yes, they have this great idea and of course they would try to go through the due diligence process. How much of that is truly vetted with the actual customer? Because what people say is that we should not produce something and then try to sell it, we should only produce it.

Research and development free of customer constraints 5:12

Brian Siwak [00:05:12]:
I think that holds true for things that are post innovation. We have a group of people within my agency here in the District Government that are focused on what we call innovative ideas, or research and development, if you will. And the idea is that these guys should not be constrained by the desires and the wishes of the customers that we currently have. If they have those constraints, they’re never going to be able to break outside of that box and try to do something new and something different. I do believe that when we look at the products and services that we do create, those things absolutely should be what people want. Otherwise, there’s not really much point in building that. But when we think about innovating, and we think about delivering and developing new ideas and new concepts, we really need to take a step forward and say, okay, well, nobody really knows what they want right now, but here’s an idea, and here’s something that we want to try. Let’s see if it sticks. Great example of that would be the data catalog that we built in D.C. starting in 2005. I don’t think there was really any concept back then of making data public. A few people in the community might have been asking for that, but it wasn’t really a huge desire. But we built it, and we did it, and that kicked off a huge process of transparency and data availability and government. So I think, if you think about innovation, you really need to be very forward thinking and not be constrained by the wishes of the customers that you currently have.

Sanjog Aul [00:06:57]:
One is to, of course, what you just rightly mentioned that we are not waiting for those people to sell in order for us to move ahead. At the same time, what do you think is the value of us doing something which we feel is right, but perhaps that could be like a binary 50-50 probability of that being a success because it may or may not be adopted by the customer. And since we have not truly gone to the customer to see, if I try to do something like this, would it fly? What’s your gut feel? At least we check that gut out.

Accepting risk and failing fast and cheap 7:26

Brian Siwak [00:07:26]:
Risk is going to be a part of every innovative idea and concept that we try to explore. If we want something truly risk free, we’re gonna end up with the status quo, and we’re not gonna ever get anywhere. In order to innovate, you have to accept some risk. And actually, I don’t mind accepting a lot of risk as long as that risk is associated with a low cost of failure, if it does fail. One of my favorite expressions is, fail fast and cheap. But what that implies is that you try lots of stuff. I think there’s a stigma around risk and around failure in the public sector, especially. These are the things that we’re trying to change. We can try new things. We can experiment. We can really push the envelope in any number of different ways, but we also have to recognize that these things might not work. When they don’t work, we need to say, okay, hey, that didn’t work. Let’s learn from that and move on and try the next thing. Maybe make it better the next time. But it’s a great point. I think there’s a huge amount of risk associated with some of these things we do. It’s just how we limit that and the educated decisions that we make around that, that really make us successful.

Sanjog Aul [00:08:36]:
So if you were to say, the customer, and the reason we are looking at it from a customer standpoint, that how much could we innovate so that the customer loves it and they participate and in fact they drive innovation versus we saying, okay, let’s try to wow the customer. So if you had to do that, one of the basic characteristics of a customer that you would look at is how fickle are they, how quickly could they change their mind, because frankly, it’s not their skin in the game. They could change their mind tomorrow and you invest it and then suddenly, they would say, this is not something I want or perhaps this is old fashioned, it’s passe, so let’s move on. And here you go, you left high and dry.

Prototypes, pilots, and agile delivery 9:21

Brian Siwak [00:09:21]:
All of that is possible. I think customers can be both predictable and fickle depending on the situation. In the current crop of customers I have, are basically all of the different agencies of the District Government as well as the citizens and residents of the District of Columbia. And the things that they look for on a day to day basis actually change depending on demographics, depending on what’s going on at any given moment, things like that. So we have to understand that we will see both sets of perspectives and that some things that we try will take off like wildfire and some things that we try will wither and die on the vine, with not much success. But that really shouldn’t stop us from trying different things. We try to engage individuals and organizations in new ideas early on in the process. So what we’ll do when we’re developing something new is actually build a prototype, build a pilot, do something that we can get up very quickly that might not have the ideal user interface or even have a remotely complete set of features. But we’ll put it out there and say, hey, give us your feedback. Are we going on the right track here? Or do we need to shift gears and re-steer this thing into something that works better in a different scenario? And from that, we get a lot of different feedback that is useful in order for us to make some of those changes. I think, really, a lot of it has to do with an agile methodology that we use here as well. We don’t try to build things that take years and months to construct and millions of dollars. What we try to do is, any project that we enter into, whether it’s a standard implementation of something or whether it’s something completely innovative, we really look at it from a very short term perspective. What can we develop in a month? What can we develop in six weeks that has some defined inputs and outputs or some defined actions that we can then test and put out there to the community of users, whoever they happen to be, and say, hey, is this useful? The sooner we can do that and the more effectively we can do that, the better off we’ll be in terms of really making sure that we do the right thing.

Sanjog Aul [00:11:38]:
When was the last time the customers came knocking on the door saying, you know what, we want this, this, this, this, and since you exceeded our expectations, there are 5 other things?

Brian Siwak [00:11:50]:
It happens all the time. We do some development here, for citizens and for other agencies in the government. We tend to do a pretty good job. When we promise something, we tend to over deliver on what they’re looking for, which obviously is good. What everybody needs to realize is that this is something, I think, that once it’s moved out of the innovation stage and more into the productized phase, we have to think about. We really need to look at how we communicate to our customers that there are a series of processes that we go through in order to make sure that the things that we do put out there are robust and that they are repeatable, and that they can be supported, rather than just throwing lots of features into something without really vetting whether or not those features are a good thing or a bad thing. Whether it’s in the process or not, it has to take the right amount of time to percolate and be defined before we can actually put it out there for real.

Sanjog Aul [00:12:54]:
If you were to go out and try to get the input from the customer, how much are they truly willing to participate in the innovation process versus saying, okay, you go into your own sandbox, create something. When you’ve created something, bring me a prototype and then I’ll give you feedback. How proactive is the customer willing to be?

Brian Siwak [00:13:15]:
When it comes to government, very proactive. I think it might be a little different when it comes to a private sector organization. But people expect a lot, I think, out of the government that their taxpayer dollars fund. And for the most part, I would be willing to bet that just about everybody out there has their own issue or issues that they believe pretty strongly in, and that technology can actually be leveraged to help do something interesting along the path of that issue. And so if you ask anybody out there, what could we do? What’s something brand new that you’ve never seen before? I would be willing to bet that most people not only have ideas, but are also very willing to share them. When it comes to a for profit company, I would suspect it’s a little different simply because the motivation behind developing a new product is a little different. It’s a for profit enterprise, and the person who’s sharing that idea is not necessarily going to see any of those profits. So I think there’s probably a bit of a difference there.

Sanjog Aul [00:14:19]:
Get into a little more detail about how customer centric innovation can actually be brought about. What is the basis of us going into the customer centric innovation? And can we truly expect tangible ROI?

Sanjog Aul [00:17:32]:
I’d love to use this three letter acronym which people are mostly afraid of is ROI. And when it comes to the innovation and especially customer centric innovation, would we actually be doing number crunching versus trying to get that earth shattering innovation going?

ROI for public versus private innovation 17:54

Brian Siwak [00:17:54]:
I think ROI is an interesting concept, especially when it comes to innovation, because I think by definition, there’s not necessarily a tangible ROI associated with something that’s a quick and dirty test or a pilot of a new idea. And I think there’s another difference here as well between the public and private sectors. In the private sector, everything really has to lead back to profits or company expansion, when all is said and done. And if a private sector innovation program doesn’t really have a tie in to the rest of the organization, or a process that innovative ideas can be captured and leveraged, then there’s not really much of a point to having this program. In the public sector, it’s similar, but we’re not actually necessarily tied to a financial ROI. We can look at a more efficient provision of services or a new way of providing services that actually generates a better ROI for us or generates a different form of ROI, I should say. Sometimes, however, it is very tangible in terms of financials. If we have a new innovative way of doing something that breaks down a current process and reassembles it in fewer steps or fewer pieces and provides a better service to the citizen, then we’re actually going to save a ton of money there. So we do look at ROI, on one hand. On another hand, it’s not necessarily just a financial thing for us.

Sanjog Aul [00:19:40]:
So, of course, people would talk about the numbers at the time of investing. Would they not come back to you and ask for the returns when you’re doing anything? I know you’re talking about the government sector and you’ve been in the private sector yourself, right? Would you say that you are enjoying the bliss here being in government that you’re not challenged as much on the numbers?

Brian Siwak [00:20:04]:
That’s not necessarily true. We’re challenged by numbers, to a great extent, actually, especially these days with declining tax revenues and budget cuts across all levels of government. And I can look at my innovation program and look at the things that we’ve done over the past, say, 5 years, and I could put a number to that. So if you look at the Apps for Democracy competition, the district government has floated the number of, I think, savings of $2,300,000 or cost avoidance of $2,300,000 simply by launching this program. So there are ways to put numbers to many of the things that we do. And I think at the end of the day, if we look at all of our innovation activities, we do have to have some kind of positive return on the investment that we put in there. What I’m saying though is that positive return is partially numbers based. We have to show some financial return, i.e., savings or cost avoidance or even revenue generation. But we also can point to a much better provision of services or new services that the government can provide for its citizens as positive ROI for that particular innovation.

Sanjog Aul [00:21:17]:
Let me back up. When a customer is actually trying to participate in this, are they more likely to buy your product again, or buy more?

Brian Siwak [00:21:41]:
I think so. It’s an interesting point, and I think one of the things to think about is what actually motivates people in general. If people feel a sense of ownership, in terms of something new that’s been developed or feel like they have taken part in a process that produces something that they can take advantage of, then, yes, absolutely, the loyalty will be there. I think companies and organizations, private and public sector, that recognize this and that take advantage of those individuals that are dedicated enough to make suggestions and become a part of the process are really going to benefit from that at the end.

Sanjog Aul [00:22:22]:
So would you think that the customers are essentially going to become loyal when you keep giving them more and more, or after some time you’ll say, you know what, you’ve already given me a Mercedes. What’s the point in you keep spending? So at what time would you think you would want to stop the innovation for that customer growth?

Brian Siwak [00:22:45]:
I don’t think ever. I can’t think of a single thing, especially in the area of technology that’s done, that has been finished. And I think that’s evidenced by the rate of change, the fact that the rate of change in nearly every sector in this industry has been increasing dramatically for years and years and years now. Just a simple example, look at the number of different smartphones that are being released on a monthly basis. Every month, you have the next new thing and the next best thing. And all of these things are sometimes variations on a theme, but sometimes they really break new ground. Obviously, the iPhone, when it was released in 2007, broke new ground, caused a huge shift in the smartphone market, which a lot of people have since followed. But there are incremental improvements on that, and there are major improvements on that. And I think, as time goes on, these things will never stop. They just continue. Any organization that says, okay, we’re done, we don’t need to innovate anymore, is probably an organization that’s not worth really following much anymore.

Sanjog Aul [00:23:59]:
Now, while we say very coolly that we could involve customers in this situation, one is, as you mentioned, you go and build up and show it to them, another is in the very conceptualization. How practical does it become when you are going about doing your thing and customers going about living their life? Are you going to pester them by knocking on their door every second day to say, hey, this is this new cool thing that we’re working on? How willing are they to participate? And if at all they are, what is that communication mechanism that could be put in place? You could put a discussion board, you can put things like that, but that’s again dependent on a customer to come and log something on it.

Brian Siwak [00:24:44]:
I don’t think you can force anybody to do anything. I think you really have to look at the different users and customers that you have, and that group will naturally self select to those that are interested in helping with the process and those that are not. The organizations that are, I think, forward thinking and willing to use customer input and feedback to help guide their processes are the ones that are going to use technology to connect in a more frequent way with their customers. And those that are interested in it will respond and will become a part of it, again, partly due to, I think, wanting to see certain developments made and thinking that if they have a voice in that, maybe their desire will get fulfilled. Also, I think it’s a pride of ownership thing. People love to be able to say, hey, that was my idea. I helped to create that. And I think that you need to take advantage of those people when they’re out there.

Sanjog Aul [00:25:43]:
Now, if you were going to use IT and you’re going to push the envelope, what are the truly next frontiers? You’ve already put CRM, you’ve already put your social networking related technologies, and you are trying to get things from them or inputs from them. What is the next cool thing that IT could do, which will take your interaction and input that you can get timely from the customer to the next level?

Everyone and everything as an always on sensor 26:14

Brian Siwak [00:26:14]:
I love that question, and it’s actually something that we’ve been experimenting with a little bit here. These days, many, many people carry devices with them all the time that are always on and always communicating with the network in some way, shape, or form. And we’re moving very quickly to a world where everyone and everything is an always on sensor of something. I think that the next place this goes is to really activate those interested parties, your customers, the people that want to take advantage of new products and services and say, listen, load this application up on your iPhone and leave it running in the background or on your Android phone and leave it running in the background. And let us measure where you go every day. We’ll anonymize the data, but we want to see what your traffic patterns are in the city. Or maybe we look at how long it takes you to go various places at different times a day, and we aggregate all that information to get a great map of where congestion happens at what point in the day, on what day of the week, and at what time. So it’s really this concept of anyone and everything is a sensor that’s always on, and the data is constantly being aggregated on a back end system that can then be analyzed and leveraged to help inform some new development that we’re working on. Now, one is to give somebody a customer experience. Another is to get business outcomes. Are the two aligned all along? I think they have to be.

Sanjog Aul [00:30:53]:
So we were just about to start talking about the alignment or the gap, in fact, which exists between what we offer people as customer experience and what is the intended business outcome. Are they always aligned? Or sometimes you take the leap of faith that let me give the customer experience and business outcome is something that we will receive?

Designing for customer experience first 31:14

Brian Siwak [00:31:14]:
I would always focus on customer experience, frankly. I think, if you design a product or service that’s going to resonate in a good way with a customer base, whoever that happens to be, and that actually, by the way, needs to be defined very carefully, because customer experiences and successful customer experiences will definitely differ depending on the customer and the user. If you focus on that and do something that really does speak to the way that people want to use that product or service, you’re going to have the attendant business outcome that’s going to solve the problem. I think if you focus on business outcome and pay less attention to user experience, then you’re actually going to have a harder row to hoe to actually cover and hit that particular business outcome.

Sanjog Aul [00:32:11]:
Don’t you think that we have a natural temptation to listen to people who are most vocal? As part of people saying innovation, go talk to your customers and take some of those lead customers who are the most vocal and take their input and get going. How would we be as this?

Brian Siwak [00:32:28]:
And I think one of the ways that smart and forward thinking organizations deal with that is by really looking at design, whether it’s product design or a new idea that they’re trying to flesh out, and do it based on the various personas or categories of users that they’re either trying to reach or the ones that currently do use their products and services. If you leave out any piece of that demographic, you’re necessarily going to be excluding them from the design process. Now it’s tricky because sometimes those things are a bit incongruous. And I keep going back to the iPhone mainly because it’s sitting here on my desk and I’m staring at it, but I think it’s a great example. The phone itself is very simplistic, and the interactions that you can have with it are really not that complex. Now, I’m a self professed geek. I love getting into the guts of something and tweaking it and tuning it and trying to do different things, and that’s one of the things that drives me crazy a little bit about the iPhone. But at the same time, it is simple. It is easy to use. It is intuitive. And that actually does make it a pleasure to use on another level. So it’s really important to look at the different user communities and try to come up with something that’s not necessarily a hybrid, because hybrids, I think, probably won’t appeal to individuals in any group. But really focus on what is the baseline that you can put in place that will make everybody happy? And then how do you incrementally go from there to keep that basic feel and still develop things that will appeal to all of your different constituents?

Sanjog Aul [00:34:10]:
Now as the different varieties of customers that you could have consuming the same offering that you have, they could be either seeking novelty, they could be discoverers, they may have different types of social orientation. They may have different ways that they make decisions. And what triggers them? There are so many different factors that we are looking at. Do you think we have a crystal ball across the whole strata and be able to get the right level and amount of input for us to really say, yes, we polled our customer to get this customer centric innovation going?

Brian Siwak [00:34:52]:
I think there’s a lot of diminishing returns in effect there. There’s a certain level of information gathering and polling that you can do to try to get all of the information that you need. And I think it depends also based on what it is that you’re actually trying to do. So if I’m sitting here in the government, let’s say I want to build a real simple application that leverages real time bus arrival data and allows me to give my constituents a web application and a smartphone application that lets them use their location to find out when the next bus is going to come and maybe how full it is and what’s its average speed and all of that kind of stuff. I can do an initial poll of the community to find out exactly what kind of features and functionality would be interesting for that type of application. But what I would rather do is get a baseline of what’s interesting, build something quickly, put it out there, and then iterate from there. Rapid releases, new versions with enhancements and fixes that come out very quickly, I think are a much better way of developing something rather than trying to get all of the requirements and all of the details upfront, and then building a massive project that at the end of the day isn’t really going to meet the needs, whether because those needs have changed or because you actually didn’t capture the requirements in the right way in the first place.

Sanjog Aul [00:36:23]:
When you talk software, when you talk IT, yes, you’re the top guy and you would call the shots and you would be accountable. Would you want to own innovation when it comes to, suppose in your particular scenario, a regular person who belongs to, say, the D.C. government who belongs to the Washington, D.C. area. Aren’t they the one responsible for innovation and you’re enabling them?

Opening DMV data to citizen developers 36:56

Brian Siwak [00:36:56]:
In a sense, potentially. And we’ve leveraged citizen input in a number of different areas. But you’ve got to keep in mind that the taxpayer dollars that are funding the government’s operations, this is one of the places that we choose to invest those dollars in order to try to stay cutting edge and try to develop things that will really help maximize the efficiency of the operations here or provide some of these new services and products that we’re talking about. Simple stuff like take the DMV, for example. Nobody wants to go stand in line in the DMV. And frankly, the DMV doesn’t want you to come and stand in line in the DMV because it’s more expensive for them to serve you and much, much less efficient. So when we look at putting products and services of the DMV online or e-enabling them, we try to figure out what’s the low hanging fruit there? What are the easy things that we can do? And then we incrementally go from there. But, by the way, I would welcome citizen engagement there as well. If we put data out there and a citizen develops an application, here’s a great example. So the DMV has a queuing system where when you walk into the DMV, the standard system, when you take a number, it flashes up on the screen when it’s your time to go to the window and you take care of whatever business it is. We’re actually looking at taking the data that that system generates at all of the DMV locations across the city and making that public, just putting that into our data catalog. Now we could take that data and do interesting things with it, but I guarantee you there’s an enterprising citizen out there who would take that information and put it into an application that could show you at any moment in time, maybe not only what the wait times are at any given DMV, so if you came in right this second and got a ticket, you would wait 37 minutes to get seen. But maybe you could even type your ticket number in, and the application itself would give you a 10 minute warning when you were about to be called. So you could go away and do some other stuff before you had to go back to sit in line. So it’s just one example. But I think there’s a lot of interesting ideas out there in the community, and we just need to take advantage of those however we can.

Sanjog Aul [00:39:08]:
Now what you just mentioned is a good idea. Now when, I suppose, an idea works or does not work, either the DMV is going to get the blame or the praise. And that’s where the interaction is happening with the customer. And some wise people say that the best IT is supposed to be invisible. So if that’s the case, then the touch point at DMV should be with the DMV office bearers and let them come back to us, and along with the interaction that they’ll have with people who are going to the DMV, come back to IT and then let them tell us we want this, this, this and this, and let IT go ahead and develop those features or functionality or the core features that you can offer and let them get more praises versus blame. Is that how you are running your innovation engine? And if you are, then how are you having that push the envelope of let people ask more? How are you making sure that more people come for more features?

Brian Siwak [00:40:13]:
A few things there. First of all, I don’t really understand that statement that the best IT is invisible. While there’s lots of technology underpinning many of the different things, it’s an impossibility in today’s world to not be confronted with technology every second of the day. And I don’t think that’s a bad thing. I think technology for technology’s sake is not necessarily a good thing, but technology with a purpose is a great thing. To the question of where the responsibility for innovation lies, I think the thing that we all (and this goes back to something I said earlier) have to accept is that with any new innovative idea, there’s going to be an element of risk in terms of that idea potentially not having the level of success that we want it to. My immediate response to that, and my very vocal response to that, is that that’s great. That’s fantastic. In fact, I would much rather try something and have it not work and know about that very quickly, not just that it didn’t work, but why it didn’t work, and go from there, than have an idea that I don’t really know anything about and won’t find out about for months and months and months. This is something that the public sector, I think, forever really has been very wary of because the public sector lives its life in the public eye. And it’s much easier to guarantee that you’re going to keep your job and stay doing what you’re doing if you take no chances and you don’t put your neck out and try new things. But if we don’t do that, we’re never going to get anywhere. We’re never going to get anywhere past the status quo. We have to accept that some of the things that we try won’t work, and we actually have to embrace that and enjoy it, appreciate it, and say, how do we take these things that didn’t work and make interesting things happen?

Sanjog Aul [00:42:14]:
Do you think whenever a customer claims or phrases or provides input verbally or in writing, is that truly what they want? Is there something beneath that which has to be recognized so that we are not going on to a journey or join a bandwagon and start riding it very fast but in the wrong direction?

Brian Siwak [00:42:35]:
I think we do have to recognize that everybody’s got their agenda, first of all. And secondly, people have bad days sometimes. Sometimes they just need to complain about something, and maybe they get aggravated about something one day that they don’t really mean to get aggravated about. So we have to be careful not to react too quickly to a statement of something going horribly wrong. Actually, a really fantastic example of that is some of the stuff that happened with the edited video recently that came out with the speech, I think it was the Department of Agriculture. That was a very fast reaction to something where not all the facts were known. Once all the facts were known, then the right response was slightly different than what actually happened. But I think we just have to look at this and be cognizant that things are going to change over time, people’s immediate reactions might be an immediate reaction as opposed to a more thoughtful, considered response. And we have to balance our desires to please everybody as quickly as possible with our ability to do the right thing.

Sanjog Aul [00:43:49]:
And look at the environment today. Almost every company has IT and pretty mature IT for the most part, whether government or private organization. And I’m sure many of them have folks like Brian who are very smart, proactive, and they are willing to take IT and the business to the next level. Then why the innovation, which is also customer centric and taking customer input and really taking it to the next level and pushing the envelope is not happening in many organizations? Is that ignorance or is it some profound reason because of which this is not happening?

Sanjog Aul [00:47:22]:
So luckily, most of us have IT, and in many cases, we do have smart people like Brian in our respective organizations. And we do talk about innovation. But then are all of us or at least most of us in a position where we are pushing the envelope with respect to innovation and getting the customer to come back, knock on our door 20 times a day to say, I want this, this and this and I will love you for it. So there is something missing between one organization to another which is causing this. Do you have a finger on that?

Brian Siwak [00:47:58]:
Part of it, and I’m just thinking back to some private sector organizations that I’ve been involved with in the past. I think a lot of it sometimes has to do with available resources and the perceived need to allocate them onto things that are not necessarily following an innovative path, but really making incremental improvements to something that already exists. So many enterprise software companies out there of smaller size don’t have the resources that they feel that they can necessarily put towards an innovative set of applications. They need to have all of their resources, all hands on deck, working on the current thing, whatever that thing is, and fixing problems, making it incrementally better, responding to customers and that kind of thing. We talked earlier about customer involvement in an innovation process. And one idea there that I mentioned was that you can’t really be constrained by what the wishes of the customer are, in terms of really trying to develop something new. And I think this is a great example of it. If an organization listens to what the customers say they want 20 times a day, then great, they’ll get incremental improvements and sometimes they’ll get that one idea that really blows it out of the water. But I would much rather say to my folks that are doing innovation, hey, don’t feel like you have any constraints here. Think about interesting and new ideas that could potentially be productized at some point, but really push the envelope and see where we get.

Sanjog Aul [00:49:49]:
Now, we also have an ecosystem that we live in, of course, whether it’s government or private. That is, we have suppliers and partners and stakeholders. Do you think we can pull this off alone? Do we not have to get them involved? And if we do have to get them involved, do you think they will be equally enthusiastic, at least at the same level as we are as an organization, to push the envelope for customer innovation? And if they aren’t as enthusiastic, are we going to suffer from the weakest link issue?

Choosing innovative partners and suppliers 50:20

Brian Siwak [00:50:20]:
I personally, here in the public sector, I prefer to rely on those partners and suppliers that are innovative, that are going to bring new ideas to the table, that are going to give me something new that I can try, that’s going to make a big difference in the way that I do something. And from that perspective, for me it’s somewhat Darwinian. The organizations, the partners and suppliers that are going to help me by innovating on their own, they’re going to naturally rise to the top. And the market in that sense will naturally self select. I think one of the critical things for me is evaluating those partners and suppliers along that axis. So looking at, what is the roadmap of your company? What is your innovation program like? What’s come out of it recently? What do you see happening 5, 10 years in the future? How can I leverage some of that starting now? And these are the things that I look at when I’m evaluating a company or a partner or a technology.

Sanjog Aul [00:51:26]:
So are these partners, truly, while they’re bringing the cool ideas, do you take them on face value and run with them? Or would you see this coming from suppliers and partners, they might have an agenda and thus it may not always be in the best interest of the customer? What’s your vetting process of the idea that’s thrown in?

Brian Siwak [00:51:44]:
You got to take everything with a grain of salt. And I’m not going to spend taxpayer dollars unless there’s a clear ROI associated with it. And again, that ROI could be financial or it could be providing a better service or product or it could be a combination of the two. And I have a responsibility there that I think is really important to the people that actually pay my salary and that pay for a lot of these developments to happen. We can’t take that responsibility lightly. But again, I don’t know how much of that I would consider true innovation. I would consider that incremental development or leveraging things that already exist to do something new and interesting. True innovation, I think, is, as I said in the very beginning, something that really is this spark and this creative idea that comes out of nowhere, that’s a brand new thought, that’s really something that has never been in existence before. So I think there’s a difference between those two things.

Sanjog Aul [00:52:43]:
Do you think there may be any specific trigger that we could be looking for, which would make the customer crave for even more?

Brian Siwak [00:52:51]:
If we do our jobs the right way, and this is the interesting thing about government, we talked earlier about technology being invisible or IT being invisible. I actually think that in a strange sense, government should be invisible if it’s serving its purpose. It should be there when you need it, not there when you don’t, doing its job behind the scenes to make everyday life work better for everybody. And so in a strange way, if we’re doing our job well, the craving should just be satisfied without anybody having to request something. Now obviously, nobody is in that position. And I think we can all do ourselves favors if we market the innovations that we do, and the services that we put out there, in a very, very interesting way, get people involved, get them aware and then get their input in terms of what’s next and the things that we’re working on that might or might not work.

Sanjog Aul [00:53:52]:
You’re saying that we are still doing catch up with whatever things people demanded, and we still are working towards fulfilling them. It’s like, try to learn how to crawl before you start running.

Brian Siwak [00:54:04]:
I can’t think of a single person that I know that thinks that the government has solved all of its problems and that it’s ready to go. I challenge you to find the one person on the planet actually who fits that mold. But we’re definitely, I think, ahead of the pack. I talk to a lot of my colleagues in other cities and we’ve done a lot of things here that I think causes some envy just in terms of our ability to execute rather rapidly, our ability to get things done on a limited budget. The quality of the individuals that we have participating in the process here is fantastic. And I think all of these things are pretty progressive for a government and for the way that we’re doing things. But there’s always going to be more to do, and that’s an important point that I think we have to recognize. This job is never done. That’s part of what makes it fun. There’s always something new to think about or something new to try. And because technology really pervades almost everything we do as a city in terms of the services we provide, there’s so many different areas that we can take a look at in order to try to really help make things more efficient and deliver new products and services to the people that need them the most.

Sanjog Aul [00:55:20]:
This was a very, very good discussion around how organizations, including government and private sector, can push the innovation. But then one very, very important point that you mentioned is that get the job done and perhaps customers will ask for more. Don’t try to build a Star Trek version of your innovation engine. Get the basics done, feed them with the right type of services and offerings, which satisfy them and they’ll come from all.

Contributors

Bryan Sivak

Bryan Sivak, CTO, District of Columbia (Washington, D.C.)

Bryan Sivak was appointed by Mayor Adrian M. Fenty on October 13, 2009 to the Cabinet post of Chief Technology Officer (CTO) for the District of Columbia. As CTO, Sivak leads the Office of the Chief Technology Officer (OCTO), an organizatio... More   View all posts
Add Comment
Click here to post a comment

Advertisement

FWS - AWSMarketplaceFreshservice MPU 300X224
Bryan Sivak