Skip to content
Episode 13: ERM Book – Beyond the Basics episode artwork

Mar 18, 2020 28 min

Episode 13: ERM Book – Beyond the Basics

from AFERM Risk Chats Hosted by Association for Federal Enterprise Risk Management

Today we speak with authors of the new book about Federal ERM entitled Public Sector Enterprise Risk Management: Advancing Beyond the Basics. Join us as we speak with Cynthia Vitters, Sean Vineyard and Ken Fletcher about the book, their chapters and chapters contributed by other authors in our Federal ERM community!

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Episode 13: ERM Book – Beyond the Basics

0:00 28:05
of matches

Transcript Auto-generated, may contain errors

Hello and welcome to Risk Chats with AFIRM. I'm your host, Paul Marshall. Today we're speaking with three guests about a brand new book that is coming out in the AFIRM ERM world called Public Sector Enterprise Risk Management Moving Beyond the Basics. We'll be speaking with Cynthia Bitters, Sean Vineyard, and Ken Fletcher.

So let's start the show. Hello and welcome to the podcast. So today we're discussing a new book that's coming out in the ERM world and we have three of our folks in the community that helped put this together in our AFIRM community. So let's start by introducing everybody.

So we have Sean Vineyard here. Hi, thank you. I'm Sean Vineyard. Do you want us to...

Yeah, give a little background. Go for it. Yes, my name is Sean Vineyard. I'm the director for Home and Hour Service and we are in public sector practice.

Okay. Ken? Hi, Ken Fletcher. I'm heading my own consulting company, focusing on public sector ERM, federal government clients, having retired from federal service as the chief risk officer at the Transportation Security Administration.

Great. And we have Cynthia Bitters, too. Hi, my name's Cynthia Bitters. I currently serve as managing director for Deloitte, where I lead the enterprise risk management practice for GPS.

Okay. Well, so let's start off. How about Ken, why don't you give us a little bit of the basic information, the name of the book, you know, when it's coming out, some of the key pieces about that. So the book is titled Public Sector Enterprise Risk Management Advancing Beyond the Basics and the title is somewhat descriptive of what we were trying to accomplish.

Most organizations are, many organizations are at the point where they've got the basics down, you know, the artifacts as I would call them, they have a policy document, they've got a maturity model, things from the ERM playbook. But organizations, particularly government organizations, are inherently resistive to change and adopting new approaches. And so our focus of this book is really some ideas and theories about how federal and other public sector entities can overcome those organizational cultural barriers that really impede ERM from reaching a mature level. Where it starts adding value to the organization rather than an investment of time, people, and other resources to stand it up before it can really get to the point where it's adding both tactical and strategic value.

Right. And so why did you all think this was a good time to write this book? The idea actually came up as we were having lunch at the 2017 or 2016 Affirm Summit. Tom Stanton, who's a co-editor with me on the book, we're chatting.

And Tom had written an earlier book with Doug Webster that came out a number of years ago that was really focused on the basics, introducing ERM concepts to both risk practitioners within government, but more importantly, policymakers and folks that weren't necessarily associated and familiar with ERM. And so chatting with Tom during lunch and reflecting on many of the breakout sessions and some of the primary speakers, he said, you know, I think there's an appetite to refresh and move beyond where we had left the last book. Would you be interested in going in on that project with me? And so I'd never gone down the let's write and edit a book road before.

So I said, sure, not knowing what I was getting into. And it really built the theme of the book on culture, really built off of that theme that was kind of woven through many of the presentations and breakout sessions at the 2017 Summit. Right. There's quite a few authors involved, right?

It's not just the three of us in the room here. Right. Yeah, we have most of the chapters are co-written by several individuals. We have a series of case studies in the beginning of the book and then following on with a number of select special topics of keen interest to, I think, the federal and public sector ERM community.

So Frank Vetrano and Jason Stajanovich wrote a chapter on their experience in establishing and overcoming some of the cultural challenges at the federal housing administration. Ken Fahley and Kerry Weber from Treasury contributed a chapter on their experiences and how they were able to embed ERM as part of Treasury's internal culture. And Jennifer Hills and Sean Cantanasi from King County, Washington contributed a chapter on their experiences in implementing ERM, what motivated them to move forward with ERM in King County, and why the county government and county council were accepting of taking this step to introduce something that, quite frankly, wasn't very common amongst any level of governmental organizations. So special cases, and then we have a number of select special topics that we can talk about those later.

Well, we actually had Jennifer on the podcast, so go back and look for that one. It's a really interesting case study in King County. So yeah, why don't we do that? Why don't we dive into some chapters?

Who wants to go first? So really, the chapter that I supported is enhancing capabilities and culture through effective coordination, enterprise risk management, and internal control. So about as long as the title can get. But really, the driving force behind this chapter came from one of the first instances was when a firm set up the Ask the Experts panel, which I've supported, I think, since two years or so now.

When we first opened that up, we got a flood of questions. And I would say, not exaggerating, 60% of them were in some way or some form related to what's the difference between ERM and internal control? If my ERM program is coming from the CFO community, how do I make sure that they're unique and distinct? So a lot of questions concerning sort of just how the two work together.

So what we did last year is through our efforts with the firm summit is we actually had a dedicated session. We were thankful enough to have not a lot of people from NIST lead that session to kind of sort of spearhead some initial detailed discussion on how NIST specifically addressed that integration and coordination of ERM and internal control. So it was really well attended. People loved it.

I think we were kind of already on the path to this book. But I think we got so many inquiries afterwards and thoughts on how much they enjoyed that and how much people would love some more detail. But I think it kind of fueled the fire for the need for this chapter. And so when Ken had approached me about the book and we had discussed the topic, I was thrilled that we had this avenue to provide that detail to both the ERM and internal control community.

And this is a real pain point amongst the federal community. A123 in the playbook talked to the integration of ERM and internal controls. But there was absolutely no practical guidance on or even a real explanation as to what does it mean to integrate. And the diagram in the playbook, the little circle diagram kind of reflects internal controls as a subset of the ERM program.

And that's the way many people think about it. So this chapter, I think, really helps answer that question in a way that hasn't been answered before. What does it mean? And what are some of the pitfalls that you should be mindful of as you're going down that integration road?

Right. And I think that point that Ken makes, that was one of the driving factors is, you know, and it's no fault to policymakers or anyone. I mean, OMB was not having any sort of concrete legislation that supported the ERM. And we still are lacking that today.

Right. You know, they released it through OMB, Circular A123, which was what they had to do to get to STEM. In fact, I think it's out there. So no one's faulting them.

But I think because of that, that sort of began the STEM for what's causing some of the confusion because that's inherently a CFO organization's guidance. Right. Right. So that, I think, has led to some of the confusion.

It's there now. We're working to coordinate and kind of collaborate so people can create those unique programs. And so, again, when Ken approached me and said, okay, well, I think this would be a great topic and we also need to discuss the impacts on organizational culture and performance. You know, I immediately thought of a good friend of mine, Quibi Hazer, who leads KPMG's People in Change Practice.

And she's just a brilliant person when it comes to organizational culture. And so when her and I first started talking, it was, I was actually shocked to figure out how it was, how important the integration and coordination of the two programs were in improving organizational culture and performance. And so the goal of this chapter is really focusing on sort of the practical applications to effectively coordinate and especially integrate if you choose to do so, ERM internal control activity. And so the goal of the chapter is really to provide readers with a way to simplify sort of a complex undertaking in order to improve overall capabilities, outcomes, organizational culture.

And so it does that by kind of breaking it down, or breaking down the purpose of ERM internal control, really trying to clarify what is unique and what's not. Going into really a more comparison of sort of the critical elements of each of those programs so people can better understand where there's overlap and where there's some of that uniqueness. Understanding some of the role that integration and coordination plays in the advancement of organizational culture and actually providing some coordination techniques. How can you get started as an organization to actually coordinate or integrate these two programs?

And then, like Ken was mentioning, you know, we do present some considerations for people to take some of the market falls, but just things to make sure you're aware of these things prior to getting into this effort. Just anecdotally, you know, I'm curious, do you guys see out there the agencies that start their year-round programs with the CFO maybe do a better job at this than ones that don't because they just, you know, they own the internal auditor, the A123 review team, you know? I don't know, just anecdotally, just throwing it out there, but what have you guys seen? I think I've seen a mixed bag for the most part.

It honestly depends on your shit. It depends on so many actors because I've supported large organizations that it's in the CFO community and it's very well integrated and then inversely I've surprised on that it's not. I think what's interesting, I would agree with you, Sean, it is a complete mixed bag, but it comes down to a lot of the cultural pieces of the organization that existed. And, I mean, I've seen the same thing, but oftentimes when there's a strong culture of risk or understanding of risk, it helps that alignment happen.

I'm sure your chapter talks about that, but it is kind of that baseline. But there's really kind of two schools of thought. One is integration can happen and it can be beneficial to both ERM and internal controls. And there's another school of thought that there should be no integration, that even if the two programs report up to the same agency executive, that there needs to be a Chinese firewall placed between, there shouldn't be any sharing and transfer of information across that artificial boundary because it will contaminate either the internal controls view or the ERM view.

And I finally, quite frankly, I don't understand the rationale behind creating that separation because it breeds competition that's not healthy and it breeds inefficiency within the organization rather than sharing approaches and thoughts. Keeping them separate doesn't make any sense to me. So I think A123 has it right when it says you need to integrate. Now it's been reinforced by Appendix A that talks very specifically about the need for integration.

But you have to be careful about what you do. ERM can't become an internal controls program and internal controls shouldn't become an ERM program. They need to remain in their separate lanes, but there's huge opportunities for synergy between them. And I think actually in writing this chapter, I was consulting actually with Tom Brandt.

And I think he said that's what's been some of the confusion that he's seen as well is that integration people are taking that sometimes almost too literal, right? Saying by integrating, these have to be one and the same, which is not the case. So it's funny because actually the title was initially focused on integrating ERM internal controls and we actually shifted to coordinating ERM internal control because of that confusion, right? So I think that was something that was important to stress is the interpretation of integration does not necessarily mean this has to be one and the same program because they are unique.

Okay, well, Cynthia, why don't we talk a little bit about your chapter? Great, thank you, Paul. So title of my chapter, our chapter on cultivating and measuring culture risk to achieve forward momentum on ERM. So another mouthful.

And just, I mean, I guess backing it up a little bit of background with the book itself and the topic of the book. And I know I remember, I remember that lunch, Ken, that we were all sitting at the round table. And I remember thinking, just going back to my days at Federal Student Aid, I mean, I was helping support and implement and, you know, lead that program for a duration of what was 12 years, which is actually a really long time to be in one agency kind of watching what was going on. And, you know, I just remember thinking that, you know, culture is such an important component.

And when I thought about the things that I saw over a period of 12 years of time around, one, seeing the change in culture that occurred over that time as it related to supporting enterprise risk, but also just in the very beginning thinking about the topic. And it was kind of like, you know, we talked about ERM as a change management initiative and people would be like, what are you talking about? And they just had no idea. And I think that as we get to where we're at today, there's so much learning from that.

But also, you know, even that culture has changed where people now do understand how much of a change management initiative it is. So I just remember being really excited about, you know, the topic and the book and how it applied to that whole setting. And so just kind of the backstage. But then when we talked about, you know, what would make sense as far as a contribution of a chapter, we talked about, you know, thinking about it from a more formalized approach.

And are there ways that we can really look at how we measure that? And so, you know, a lot of the, you know, the gist of our chapter is around measurement. But, you know, just a little bit of the flavor. We start off just talking about what is culture risk.

So, and I think that's great because every time we talk about ERM, everyone has a different idea of what it is. And I'm sure as we read the chapter, we might see different themes of what people define as culture risk. I don't know, we'll see how it'll come to that. And then, you know, we talk a little bit about why is it important.

And that gets into, you know, some of the things I've talked about, even though chapter isn't a case study. It's just, you know, why is it so critically important that we think about this when we think about risk management programs? And, you know, there's always been thought about how much it's like a core component of the base of it. But I think even today, it's a core component of the base, but we went off and did all these things.

And now we're coming back and reflecting and saying it's so important to make things work. And then we get into how we manage and measure culture risk. And we do put forth kind of an organized approach around how one might do that. And, you know, just to give you a preview, I mean, it is a culture risk framework.

So just like there's an enterprise risk management framework that is out there, we also put forth an idea of, you know, if you want to really get into the measurement and kind of get in the weeds of this, you can put forth and, you know, use a framework to look at it. And then we talk a little bit about just where we go from here. And so, you know, I mean, that's kind of the gist of what the chapter is about. Great.

So. Well, I'm sorry. So I think you mentioned there's the culture, cultural risk and risk culture. That's two different things.

Is that right? Yeah. And you will see a little bit of that discussion in the chapter. Yeah.

Which is, yeah. We'll do that as a suspenseful item. That could be the suspense. Okay.

Well, why don't we wrap it up with Ken. Give us a little about your chapter and then maybe hit on, you know, any other chapters that we didn't talk about. So you're right about what you know, right? So my case study was on how we got to enterprise risk management at the Transportation Security Administration.

And unlike many organizations where it came from the internal controls financial services world, GSA came from our core operational passenger and baggage screening function. And I was fortunate to be a part of the group that. that moved the agency from one-size-fits-all to risk-based security, you know, TSA PreCheck, as most people think about that today. And the lessons that we learned, I mean, that was a huge transition for not just the agency but for the transportation industry and for federal government.

There was so much of what had been, you know, of that one-size-fits-all philosophy that was embedded in the national strategy for transportation security, national strategy for counterterrorism, combating terrorism travel, all of these documents and approaches for more than a decade were based on anybody can go bad and therefore everybody needs to be treated essentially the same way. And so the lessons that we learned and many of the approaches that we took to change the culture of the operational component of the agency for passenger screening, we imported over to our efforts for standing up the ERM program. And so it was really success in TSA PreCheck that led the agency leadership at the time to say, how do we take this risk philosophy and expand that to everything that the agency does, both on the mission operations as well as the business operations side of the house? And ERM was a great framework to work with in order to be able to do that.

And so the focus of the chapter, beyond a little bit of the history, is the elements of change that we developed and used for TSA PreCheck and how we were able to leverage those approaches as we began to implement the enterprise risk management program. And so what's interesting in most of the chapters, and mine included, and Sean talked about it, as well as did Cynthia, the book is an interesting mix between real-world practical experience and thought leadership on some of these topics, and theory. You know, here are real-world, the culture change or risk culture model. Sean has embedded the Burke-Litwin change management model.

You know, I introduced, you know, kind of a four-quadrant approach to addressing the elements of change in my chapter. So every chapter has a really good, interesting mix of theory as well as practical experience and practical application. I think that's what people want to see. You know, it's a nice theory, but how does this work?

Can you show me how this works? Yeah, it's awesome. Well, did you want to touch a little bit on the chapter from Bob Westbrook? Yes, so Bob Westbrook is the Inspector General for Pension Benefit Guarantee Corporation.

And the relationship between the external audit and inspections community and the ERM program is a hot topic. It was certainly a hot topic. When we were talking about the book, I don't think that that's changed much in the last several years. Agencies are really hesitant to give their risk registers and their, you know, beyond whatever they're going to submit to O&B as their formal risk profile, but they're not to bolt behind that.

They don't want to give that to the IG or the GAO because that presents the shopping list for the upcoming fiscal year of, you know, here's my pain points, come in and help inflict pain on me in these areas. So how do we begin to change that relationship from adversarial to collaborative? And Bob was really a leader in that thought process within the IG community. And so we asked him to write a chapter that he calls Working with the IG and GAO, Creating a Win-Win Relationship.

And this is some really interesting thoughts about how the two organizations can work collaboratively together to improve the risk management environment of the organization and their ability to achieve their goals and objectives while remaining independent and respectful of the independence that the IG and the GAO community have. So I think it really provides some great food for thought about how to move beyond. IG can be a great resource for a CRO who's having difficulty in overcoming some of the internal cultural barriers. The IG community can be a great resource to a CRO and a CFO on how effective the RN program and the internal controls program are independently, but as importantly, how effective is the integration of those two programs.

So I don't think CROs and risk functional managers in government typically look to the IG and the GAO as an ally and a resource, but they can be. And Bob presents a way to kind of flip the switch in how to think about that relationship. Okay, well, you guys definitely gave us a great overview of the book. Really, there's a couple questions left.

I mean, you know, I think I'll be answering this one. It's everybody listening right now. But who's the intended audience, would you say, for this book? Who gets the best benefit here?

Well, we wrote it with the federal ERM community primarily in mind because most of the contributing authors came from that community. But we included the county chapter, King County, Washington chapter, because not only does it provide good, interesting insight for the federal ERM community, but it makes the book directly applicable beyond the federal government to county, local, and state governments. And they're all resource-constrained. And in fact, they can't run deficits like the federal government.

I think governors have to balance their budgets every year, right? So how do you focus those limited resources on the areas that are most important and ERM can help? And then as we were talking to our publisher, Rutledge, the part of the conversation came around to, well, this is the content in the book. Because of the mix of theory and application, it really makes a potential good tax tour in academic course in risk management or enterprise risk management.

And so we think there's multiple audiences, academia, the federal government, and then the state-local and county government practitioners. Great. Well, I mean, really, I just want to know now, when is this book coming out? Where can we find it?

So the preliminary is already out. The advance notice, the book will be published in May. I'm told early to mid-May it will be out. It should be available on Amazon at that time.

Awesome. In both hard copy and soft copy form. Oh, yeah. Oh, yeah, but then, right?

Well, yeah, thanks, everybody, for joining us. Sean, Cynthia, Ken. I really appreciate it. And I'm looking forward to seeing the book.

Thanks, Paul. Thanks for joining the show. Visit our website, afirm.org. You'll see all our other podcasts.

And be on the lookout for the new book. You go to amazon.com. You can pre-order it today, actually. So, yeah, it'll be available wherever you buy your books.

So, until next time, this is Paul Marshall signing off for Risk Chats with AFIRM. You go to the next episode. You go to the next episode. You go to the next episode.

You go to the next episode.

Frequently asked questions

How long is this episode of AFERM Risk Chats?

This episode is 28 minutes long.

When was this AFERM Risk Chats episode published?

This episode was published on March 18, 2020.

Can I download this AFERM Risk Chats episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.