How to Craft Public Policy that Actually Does what You Need it To Do - Part 1 - Episode 50
Almost every aspect of a nonprofit's work is touched by public policy in some way. And sometimes we come to the realization that the way to achieve a particular goal or to solve a particular problem is that we need a new or different public policy around that.
But here's the thing. The landscape is littered with well-intentioned policy that did not succeed at doing what it was intended to do. Because the language was not crafted in such a way as to generate the desired result. Sometimes that's because the policy is a product of so many cooks in the kitchen and so much compromise that the final [00:01:00] product is unrecognizable relative to the original idea that was behind it. And sometimes it's because the policymakers didn't have enough clarity about how the thing would work on the ground.
You don't want any of that. You want policy that will actually do what you need it to do. Getting there takes a lot of things from you as an advocate. And the theme of it all is, the devil is in the details.
In this week’s episode, the first of a 2-part series, we take you through the complete process of preparing a policy proposal that will have everything you need to achieve the results you want.
In this episode, we share:
- The top two reasons many advocate-led policy initiatives wind up yielding disappointing results
- The three sets of policy you need to have on your radar to make sure you get your desired results
- How to triage and prioritize the problems you’re trying to solve through policy change
- The four most important questions to answer as you develop your policy proposal
- Which key details your proposed policy actually needs to contain
- The most common blind spot that causes nonprofit leaders to miss critical policy details
- The essential skill you need to craft successful public policy, and how to build or increase that skill
If you found value in this episode, please share it with other progressive nonprofit leaders. And I’d be grateful if you would leave a rating and review on Apple podcasts, which will help even more people find out about this podcast.
Thanks!
0:00 You're listening to the Nonprofit Power Podcast. In today's episode, we reveal how to craft public policy that actually does what you need it to do. So stay tuned. If you want to have real and powerful influence over the money and policy decisions that impact your organization and the people you serve, then you're in the right place. I'm Kath Patrick and I've helped dozens of progressive nonprofit leaders take their organizations to new and higher levels of impact and success by building powerful influence with the decision makers that matter.
0:40 It is possible to get a critical mass of the money and policy decision makers in your world to be as invested in your success as you are. To have them seeking you out as an equal partner. And to have them Bringing opportunities and resources to you. This podcast will help you do just that. Welcome to the Nonprofit Power Podcast. Hey there folks. Welcome to another episode of the Nonprofit Power Podcast. I'm your host, Kath, Patrick. I'm so glad you're here for today's episode. Almost every aspect of a nonprofit's work is touched by public policy in some way.
1:22 And sometimes we come to the realization that the way to achieve a particular goal or to solve a particular problem is that we need a new or different public policy around that. But here's the thing. The landscape is littered with well-intentioned policy that did not succeed at doing what it was intended to do. Because the language was not crafted in such a way as to generate the desired result. Sometimes that's because the policy is a product of so many cooks in the kitchen and so much compromise that the final product is unrecognizable relative to the original idea that was behind it. And sometimes it's because the policymakers didn't have enough clarity about how the thing would work on the ground.
2:06 You don't want any of that. You want policy that will actually do what you need it to do. Getting there takes a lot of things from you as an advocate. And the theme of it all is the devil is in the details. The reason most advocate-led policy initiatives wind up yielding disappointing results, is that the advocates didn't go deep enough into the details and they didn't embed themselves in every step of the policy development process. The reality is that throughout the process, language is constantly being added, I changed and subtracted, based on input from a lot of different stakeholders.
2:48 I've seen many instances where initially great language was undermined by a last minute change that advocates didn't catch. And all their work was rendered null when the final policy was approved with language that wouldn't do the job of getting the results they were seeking. Like it or not, you need to have your hands in this process from beginning to end if you really want to see public policy look the way you want it to look and do the things you need it to do. And you're going to need some specific skills. So we're going to go deep on how you can make sure that when you go to advocate for better policy, you get the results you really need. As I began to lay out all the stuff we need to cover here, I pretty quickly realized it is too long for a single episode.
3:34 So this is going to be a two-part series. We'll do the first half this week. And then the second half will be at next week's episode. Just to give you an overview, let me share all the pieces you're going to need to get your end result. You start with your big idea. The problem you want to solve with policy. Or the new thing you want to do with policy. And then you get really detailed about that. You need to understand the existing policy landscape relative to the thing you're trying to do. What are the applicable policies already in place? You clarify in detail what about the existing policy is working well for you and what is not.
4:16 It's rarely just one or the other. It's usually a mixed bag. So you need to be super clear about what's already working well, that you want to keep. Get into deep detail about all aspects of the thing you do want, whether it's to create a new policy or to change a bad or inadequate one. And identify all the places existing policy will need to be changed. That's a tricky one because there'll be the main home for that piece of policy and there'll be all kinds of related policy hanging around. That if you don't change those too, you may wind up not having the impact you wanted. Needless to say, you need to describe in detail what the new policy will include.
5:01 That's kind of basic. But critically important and often not done in enough detail in order to be effective. Want to identify the best home for any new policy. And sometimes there's a choice. And that is very often a strategic choice more so than a logical choice. So we're going to talk about each of those and how you make the decision. Once you've done that you engage the policymakers armed with all this information and perspective and strategy that you've already put together. So that you're operating from a position of knowledge and strength. Then you have to anticipate and plan for, and have a strategy for how administering agencies will react to any changes, and how to get them to engage cooperatively.
5:50 And that's both as an agency and then down to key individuals. You will need to work with the legal team that is part of any legislative or administrative entity of any size. Their job is to craft the legalese version of the policy and make sure that it is structured correctly for satisfying legal requirements. So you've got to be able to work with those legal teams and know how to do that very effectively. As part of your work with that legal team, you're going to make sure that any place within the overall legislation or administrative policy that the issue might come up, you're addressing it in each of those spots with relevant language.
6:34 And then. This is key. You have to stay on top of the entire process once the policymakers and the legal teams are involved. To make sure that your intended result stays front and center throughout the process. And that the result you get at the end is the thing you wanted. When you put all of that together, then you've got a really solid winning approach to getting policy to really work for you. So in this first episode, we're going to tackle all the stuff that you do before you go and seriously engage the policymakers. And then in next week's episode, we'll tackle the second half, which is what you do once you're engaging with the policy makers, the legal teams, and the various administrative entities that may eventually be involved.
7:20 So first thing. What's your big idea? What are you trying to make happen? You trying to solve a problem? Create something brand new? It seems obvious, but you do want to be clear on that before you go any further. And then a key second piece to that is, why does it matter? It's going to be important for your ultimate messaging all of these policymakers and other folks you're going to have to deal with. But it also matters for you and for your team because, as you may have gathered from what I just laid out, this can be a pretty long and intensive process. It generally is a lot of work. And there can be times when it feels slow and frustrating and aggravating and all the things.
8:06 And in those moments, being able to reconnect to your why is really, really important. To be able to come back to, yeah, this is a pain, but boy, if we get the results we want, if we really get this policy to work right the way we know it can. That will change all these things. They will have such a big impact. And then you are clear about what that big impact is, and you just reground yourself in that vision for the impact that will ultimately be the result and that'll help keep you going. So you've got your big idea, you know, what you're trying to build or change. You know why. You know the problem you're solving, the thing you're creating. So. The first thing you got to do is analyze the policy that's already there.
8:50 At this point in life, there are very few concepts around which there does not already exist at least some public policy. Whether it's legislation or administrative policy. So we have to understand the policy environment we're working in. We have to know what that policy looks like now. And we have to know that in quite a bit of detail. You're going to hear that detail word a lot. And as I said, that's where all the success or failure generally lies, is in how well you nail the details. So until we do that, we can't have a coherent conversation with policy makers or anybody else about what's needed instead of, or in addition to what is already there.
9:37 So the vast majority of the time there's going to be policy already in place that touches on the thing you're concerned about. And there may be a lot of existing public policy. It really just depends on what you're trying to make happen. And it could be legislative policy, it could be administrative policy, or it could be some of each. And it could also be language accompanying appropriations. If you're doing anything that has to do with funding of a particular service or initiative, there will very likely be appropriations language that will also be necessary. And so you're going to need to familiarize yourself with the existing appropriations language that covers the thing you're talking about.
10:17 So there's three places to look and you want to be attentive to all of them. Part of this understanding the landscape process is ultimately you're going to need to be able to read and analyze the policy language that already exists. To understand exactly which parts of that language are causing the problem or are missing the thing that you want to create. Now, if you're coming up with something that is brand new, which does happen from time to time. You've got a great idea and you want to do something that is new. Even so, chances are good that this thing will have a home somewhere in existing policy infrastructure. If you're already really familiar with that existing infrastructure, you can probably figure out on your own or make a pretty good guess about where your things should live.
11:03 But if you're not sure that's going to be one of the first questions you'll need to answer. And I'm going to assume that we're not talking about federal policy for purposes of this conversation, because when you do that, you are then working with national organizations, you're engaging people across the country to make something like that happen. There are very few instances in which one organization in one state is going to change federal policy on their own. So I'm going to assume we're talking about state and local types of policy, whether legislative or administrative. So I just mentioned that one of the key skills you're going to need is to be able to read and interpret policy language. And that comes up right away at this initial stage, and it's going to be true throughout the process.
11:46 Because at every point, any time new language is proposed, language is changed or tweaked or added or subtracted. Every time that happens you have to be able to know, how is that going to translate on the ground? What's that really going to mean? And there are a million considerations that go into that. So this is a skill that you're going to want to develop or improve. Wherever you are on the skill development process with this. The good news is that there are fairly standard formats in which policy language tends to be constructed. It does tend to be dense and somewhat obtuse at first exposure.
12:29 But once you become more familiar with how that language is structured and how it works, you'll start to recognize that there are patterns to it. Once you learn the patterns, it's much faster to read and ultimately interpret the policy language. And you go from being confronted with a really long piece of policy, maybe a couple hundred pages in some instances. You want to be able to get through that fairly quickly and find the parts that matter. So that's part of the skill is knowing which pieces are going to likely be relevant to you. And then to be able to read the actual language and know how to interpret it. And again, once you learn some basic patterns and key quirks, if you will.
13:11 This gets a lot easier. But it is an absolutely necessary and fundamental skill. You just won't be in a strong position working with policy makers, if you don't have it. And we're going to talk in this episode a little bit about how you begin to develop that skill or improve it as you go. And I'm going to give you a lot of tips for how to come at this, but you know, really the best teacher is practice. And working with somebody who already is really good at this is really helpful. You can do a first cut and then they can come behind you and say, oh, you didn't catch this. Here's why this is important. So definitely get mentors for this locally because it's super helpful. It will take quite a bit of repetition before you get really good at this.
13:54 If it's your first major foray into policy analysis. It helps to start with a policy that's already related to one of your funding sources or that governs a chunk of your services. And you know what those are. If you get state money, there'll be state policy attached. If you get city or county money, there'll be policy attached. And remember that if you have federal money, the way most of these programs work, there will also be state and local policy that are part of that administrative structure, because they tend to set it up so that there is state and local decision making authority as well. Start with this thing that you already have a working relationship with. And then read the heck out of the key sections of policy that govern your stuff.
14:39 And if there's appropriations language that governs your stuff, you should read that too. Go through those key sections and make notes all over the place about stuff that doesn't make sense to you. Stuff that looks problematic, stuff that you have a question about. Stuff that you think is really good. And you'll probably need to read it multiple times if you're not already pretty skilled at this. But repetition and recognizing patterns is the fundamental ingredient to getting good at reading and interpreting policy language. It will help. If you can be a little bit patient with the learning curve on this. So let's come back to your big idea. You're thinking about an area of policy that impacts your work.
15:23 A key question for you to answer is, what about that existing policy is working well for you? And what is not? And that's really a question you want to answer from two perspectives. There's what is and is not working well for your organization, and your ability to deliver the services at the level of quality that you care about and to be compensated appropriately for that. And then there's what is and is not working well for the people that you serve. Because the sets of problems can be way different. And you want to be alert and attentive to both. So when you're looking at how things are working for the people you serve, you're looking at things like ease of access.
16:04 And that includes are the rules clear and simple without a lot of friction to accessing the services? Or do folks have to jump through a lot of hoops. Do they have to reapply on a regular basis and do they automatically get kicked off the service if they don't go through the re application process? There's all kinds of hurdles and barriers that often exist for our clients to be able to consistently access our services or to even qualify for them. And I'm sure you're very familiar with it, because you're experiencing it on your end. And you're also hearing about it from your clients. But you want to really drill down into that. Ultimately where we're headed is you're going to be crafting actual proposed policy.
16:45 And so you want to be really clear on, of what's already there, what's working and what's not. From your client's perspective, what about the existing policy makes it easy and wonderful and great. And what about the policy makes it difficult and full of friction and frustrating and problematic. And, you know, it's usually some of each. Very rarely is a policy so bad, so poorly constructed that it just sucks for everybody all the time. Usually there's some stuff that works at least okay, and some stuff that works really well. So you want to be able to speak to that too. There's a lot of reasons for that. Partly, it makes you a more credible partner with the policymakers you're going to be working with.
17:28 To be able to say, Hey, you know, this piece over here is working great. We want to build on that. This over here, not so much. This is a problem we need to address. That goes over a whole lot better than the whole thing is terrible. We need to replace it wholesale. So when you're looking at how things are working for your organization. I mean, I probably don't even need to tell you this because you live this every day. But you're looking at things like, how easy is it for you to provide the services that you know are necessary for a client to succeed and thrive? Is it that you can only provide some of the services and get paid for them, but not others that are equally critical. Is it that you can provide all the services, but the rate at which you are compensated is unsustainable.
18:15 It could be that there are administrative issues with record keeping that is overly burdensome for your organization. Or that would require you to go out and purchase massively expensive software in order to be compliant with a set of rules that may or may not really need to be that stringent, where you're concerned. And don't forget, if there's stuff that's working well, that you are happy with, you want to enumerate that as well. And it's more than just becoming a credible partner with the policymakers, although that's very important. But it's also, once you start going to change existing policy. If you're not careful, sometimes the stuff you like that's already in there could inadvertently get disappeared.
18:59 Or watered down or made to work less well. So you need to have your eye on both. It's not just about how do we make this work better? It's how do we keep the stuff we have that's working well. And when you're doing all this, it's important to be aware of a potential blind spot. There can be areas of policy that are really problematic that you've been working around for so long that you've kind of lost sight of how bad the policy really is. For example, there could be policy that creates a lot of barriers and friction for your clients. But your organization, in order to make clients' lives easier, has constructed an elaborate set of support to take as much of that burden off of the clients as possible.
19:43 That's awesome. But then what that means is your team is dealing with all those barriers and friction to try to minimize the burden on the clients. But it's still a serious policy problem if you're having to do that. The policy should be frictionless for everybody. For the organization that is providing the services and for the client, who's receiving them. So just be super attentive to that because especially if it's something you've been doing for a long time, It's kind of baked in to your services at this point. And you're not necessarily even thinking about, yeah, but the only reason we have to do all this stuff over here is because the policy is set up in a way that's really problematic for our clients.
20:25 And, so then if you wanted to write your ideal policy, you would change it so that you didn't have to do that work because the barrier is removed. No friction for the client, no friction for you either. That is the goal. So check that stuff. Now, similarly, if there are barriers and friction in policy that are specific to just your organization and don't necessarily have as much impact on the client. There could be barriers in policy that you found a work around organizationally by developing relationships with key players in those systems. So for example, you know, you were having a problem accessing funds in a timely manner because of policy, but then you made a friend in the administrative agency who makes sure you get paid on time anyway.
21:13 But then you've got to think about, well, what if that person left their job? You'd be back to being stuck with a policy that really doesn't work well. And you want to fix that. So that, believe it or not, is just sort of the surface level of what's not working. Then you go deep on the details of what's not working. So, for example, if there is an aspect of policy that makes it difficult for the clients to access services. You could stop there, but that won't help you. Difficulty in accessing services is a category of problem. But underneath that you want to enumerate exactly what that problem looks like. So that you will ultimately be able to change the policy in all the ways it needs to be changed to make it work properly.
22:01 So let's say for example, clients have to reapply every six months to be eligible for a service. And in order to demonstrate eligibility, they have to bring to a physical location, multiple documents, and go through an on-site process to reestablish eligibility. Another problem might be there's a lifetime limit on the amount of services they can receive. Or there could be a limit on how many months of services they can receive in a year. But the reality is they need the service 12 months a year. And the need doesn't go away in a year. That's a problem. And so on. You want to drill down in as detailed and specific a fashion as you can, because policy language is extremely specific.
22:43 You have to be specific in defining the problem in order to craft policy language that will actually fix it. And you also go deep on what is working well. Because again, you're going to want to protect this. So let's say that in a particular situation that you're interested in improving policy. The policy is currently written in such a way that the system allows your organization to provide the full spectrum of services that the client needs. Great. And there is adequate financial support for the provision of those services under the policy. Also great. Then when you've got good stuff like that, go ahead and enumerate all of the services that are covered that are essential and that are part of your wraparound service profile.
23:29 Get that captured so that you make sure that continues to be what is covered going forward. A lot of the times, part of the battle is keeping the good stuff. And you want to have detail on what the good stuff looks like. Similarly for clients, if there's a simple, easy process for demonstrating and maintaining eligibility currently in place, make a note of that. You want to keep that. And then detail the specifics of that. For example, the eligibility requirements are such that eligibility can be determined through an interview without the client having to supply any documents. And that interview is part of your intake process. If that ease of access is rooted in policy, want to write down the details of that and why it works so well.
24:16 Once you've detailed, all that out. Then it's time to take a look at how can the policy be improved so that it will work even better for your organization and the people you serve. So you kind of do this in two pieces. First you go back to the things that you said are a problem. Start there. And you kind of triage the problems because If it's pretty crappy policy, you might have a really long list. But the truth is some of those are more impactful problems than others. So you want to kind of triage the problems and identify, you know, starting from, which is the very worst, most problematic. To which is down in the category of annoying, but not major.
24:57 And for each of them, go through and clarify, what would need to be in place in order for this thing to work perfectly, to have zero friction and do a really good job. In the world. We're not doing policy language yet. Okay. Now when you do this, you're going to find that for some of the problems, it would take a major overhaul. And for others, it would be like, gosh, if we just did this one thing a little bit differently it would probably take care of it. You're not in policy language yet. You're just thinking in terms of, from a practical standpoint, what would make this work better? What if we had a system that did it this way instead of that way? And then you detail that out.
25:39 You describe that. What all would have to be in place? And so, for example, you don't just say clients wouldn't have to supply any documentation. You would say in detail, what would be a process for determining eligibility that would be frictionless for the client. And then you lay that out. Whatever those details are that in your situation would make this just easy peasy for our client. And hopefully not create massive extra work for your organization because you don't want to just shift the friction from one place to another. You also want to be aware that there's probably more than one way to make something better. Right. And if you're finding that's the case.
26:20 That there could be multiple solutions to this problem. You want to write down all the possible solutions that you think would be pretty workable. Because again, that's going to give you a negotiating room. There might be one of your proposed changes that would make things work better that would make some stakeholder somewhere completely freak out and say, under no circumstances can we do it that way! And you might have another one of your solutions that they'd be like, yeah, we could do that. Well, obviously if they're both reasonably equal in terms of solving the problem, you'd go with the one that doesn't cause the freak out on the part of a stakeholder, who then either will try to stop the change from happening in policy.
27:01 Or, and we'll talk about this next week. As you know, Administrative agencies and the people who work there, if they don't want to do something, they will find a way not to do it. So, if you can create a situation where it's easier for them to buy in, by all means you're going to want to do that. So in situations where there is multiple ways to come at a fix or at a way to do a new thing, write them all down. It's also good to have a conversation with your team internally about okay, there seemed to be a couple of ways we could do this. Is one or the other of these better for us? Because if it affects multiple aspects of your operation, You might be really aware of some aspects and less aware of how another department might think about that.
27:44 So you want to run it by your own team so that you don't inadvertently create a problem for an aspect of your work that you hadn't totally thought about. This isn't as big a problem for relatively small staff organizations. But if you have a hundred people working for you. You know, you don't know what everybody's doing. Right. You have a management structure for that. So you want to check in with people. And obviously, if it's something that's going to affect your clients, be sure to ask them. What would work best for them? Don't just assume that you know the right answer. You probably have a pretty good idea. But it is always good to check. Because I promise you they will have additional insights and perspectives that you're going to find valuable.
28:25 And that should be part of this process, for all kinds of reasons. Okay. So you've done all that. Then. After all that. It's time to begin crafting an actual proposed policy solution to the things you're concerned about. But I see this all the time. What usually happens is, advocates will go from I see a problem, I'm going to propose a policy solution., And they skip everything that I just talked about. And they go right to, here we go. I'm going to rough out a one pager on the policy we need to have. But now that we've walked through all this, you can see why, while that is a way to go, it's probably not the most strategic. It's definitely not the most strategic.
29:07 Spoiler alert. And you would also be so much less prepared to have a really deep conversation with policymakers, and then ultimately administrative folks and the legal team who are actually turning this into real policy language. So. Now you're ready. You've done the deep analytic work. And deep work of crafting your answers to critical questions. And it's time to actually propose a solution. Not surprisingly, your proposed solution should be as specific as possible. Because we are all about the details here. So, for example, we've been talking about the eligibility issue. So let's say your recommendation might be, change the current requirement for eligibility, which calls for five separate documents to be submitted at least once a year.
29:54 Change that to eligibility criteria that are answerable without documentation. And that can be collected in an interview with a client, to be conducted at intake. And then you go further and you lay out what those eligibility criteria should be and you list them all out. And you might go further to say that renewing eligibility can also occur in an interview conducted by phone. You give that as an option. It can be conducted either in person or by the phone. Now, these are just examples. You'll know what the best fix is for the challenge at hand. but I'm giving these examples so you can see the level of detail you need to be prepared to supply, so that they can become the new policy that will actually work.
30:39 And get the results you want. Okay. Once you've done all that. Then you're ready to go engage policymakers and start talking to them. About your idea. About the problem you're trying to solve or the new goal, the new ambition you're trying to make happen. And part of what's so great about your role as a direct service nonprofit leader and advocate is that you bring to the policy conversation an incredibly valuable perspective. You are close to the problem on the ground. Far more so than policymakers ever will be. Far more than administrators will ever be. Your organization is providing the services directly to the folks who need them and who are the beneficiaries of the policy.
31:23 Or the victims of it, depending on what's going on. You have a very clear and detailed view of how well a given policy is working, or isn't. And your ability to share that with policymakers is tremendously valuable. When you come to policy makers not only with details, but having thought through strategically all aspects of the problem and the solutions that would truly make things markedly better and more impactful. You are showing up as their dream problem solving partner. Already that is going to shape how they deal with you and how seriously they take you, and how much they want to invest in working with you on this policy proposal.
32:05 In next week's episode, we'll get into all the pieces of working with policymakers and their staff to make sure you get an end result of policy that does what you need it to do. But for now. Go ahead and, even if you don't have a policy proposal in mind, I would encourage you to just go exploring a little bit. In a piece of policy that is directly relevant to the work that you're doing and the people you serve. And go poking around in there. And take a crack at just reading it through a couple of times and going through that exercise of finding stuff that you think looks good. Stuff that looks possibly problematic. Stuff you don't understand or have questions about.
32:45 Stuff that doesn't make sense. And just see what you come up with. It's kind of nice to do that in a totally low stakes environment. Now I know you're busy, so you don't have to spend hours at this. But play with it a little bit. And certainly if you have anything either current or on the horizon. If you use this process that I've laid out, you will be setting yourself up to have an absolutely fantastically productive and engaging conversation with policymakers, and they are going to be super excited to be working with you. Thanks for listening. And I'll see you in the next episode right here on the Nonprofit Power Podcast.
Apple Podcasts
Spotify
Pandora
Amazon Music