Avoid Technical Debt & Your Technical Roadmap




Avoid Technical Debt
Our 24NTC coverage continues, to help you avoid crushing tech debt that would bust your budget and cause you a big headache. Our panel encourages you to manage and maintain your IT infrastructure and software so that costs are managed. They’re Jagan Narayanan, from Fourth Dimension Technologies, and the tech speaker, writer and consultant, Karen Graham.
Your Technical Roadmap
Another way to steer clear of a technology budget crisis is to prioritize and plan your investments. Kestryl Lowrey shares the best practices for creating your tech roadmap. He’s with Cloud for Good.
My Guest
Here’s the transcript
Tony MartignettiHello listeners, it's Tony. Every week for the past 14 years I've produced a show. This week, I'm sorry, I just— I, I, I could not pull it together. Personal problems, technology problems, It's just, it was just overwhelming. I, I could not— I'm sorry, it's April Fools'. It's our April Fools' show. Hello and welcome to Tony Martignetti Nonprofit Radio. Big nonprofit ideas for the other 95%. I'm your aptly named host and the podfather of your favorite hebdomadal podcast. Oh, I'm glad you're with us. I'd suffer the embarrassment of somasthenia if you weakened me with the idea that you missed this week's show. Here's our associate producer Kate with what's going on this week.
Kate MartignettiHey, Tony, it's a technology management show. First, avoid technical debt. Our 24 NTC coverage continues to help you avoid crushing tech debt that would bust your budget and cause you a big headache. Our panel encourages you to manage and maintain your IT infrastructure and software so that costs are managed. They're Jagan Narayanan from Fourth Dimension Technologies and the tech speaker, writer, and consultant Karen Graham. Then, your technical roadmap. Another way to steer clear of a technology budget crisis is to prioritize and plan your investments. Kestryl Lowrey shares the best practices for creating your tech roadmap. He's with Cloud for Good. On Tony's Take Two.
Tony MartignettiI've been dreaming.
Kate MartignettiWe're sponsored by Virtuous. Virtuous gives you the nonprofit CRM, fundraising, volunteer, and marketing tools you need to create more responsive donor experiences and grow giving. virtuous.org. Here is Avoid technical debt.
Tony MartignettiWelcome back to Tony Martignetti Nonprofit Radio coverage of the 2024 Nonprofit Technology Conference. We're in Portland, Oregon, and we are sponsored by Heller Consulting, technology strategy and implementation for nonprofits. With me now are Jagan Narayanan and Karen Graham. Jagan is CEO at Fourth Dimension Technologies, and Karen is speaker, writer, consultant, and co-founder Welcome back to both of you. You've both been on the show before. It's good to have both of you back. Jagan, Karen, welcome back.
Jagan NarayananThanks. Thank you.
Tony MartignettiPleasure. So, you've done your session and your topic is Avoid Technical Debt from Killing Your Nonprofit. Not just damaging or injuring, killing. Killing. Jagan, why is this an important topic? Why do we need this session?
Jagan NarayananBasically, it's more to do with being able to keep up with technology and trying to address issues as and when they come up and not let them pile up. Once you let the issues pile up, then it kind of grows to such an extent that it becomes a very difficult task to manage at that point in time. And that's why we're talking about being able to kill them, because suddenly you find yourself in a situation where you have a huge technology challenge and you probably don't have the resources and both financial as well as technical, to be able to address that.
Tony MartignettiOkay, and it could have been avoided with better management through the years?
Jagan NarayananAbsolutely. Better management in terms of planning and probably spreading it out over a period of time.
Tony MartignettiOkay. Karen, do you want to add something to our introduction to the topic?
Karen GrahamSure. I think, I mean, you asked why this topic here, why this conference. I think it's especially important for nonprofits to think about this because they have so many pressures that that send them in the direction of accumulating more technical debt, of putting off purchases, of underinvesting in technology because of the way that they're funded, because of the— just all of the different ways that they operate. I think nonprofits are perhaps more susceptible to technical debt than any other kind of organization.
Tony MartignettiSo some of the things we want to— let's stick with you, Karen. I'm just reading from your session description. What are the negative impacts of technical debt? I mean, Jagan sort of alluded to them. Do you want to go into more detail or maybe tell a story of some of the implications of putting off proper investment and management of technology?
Karen GrahamSure. I'll use a really simple example. And this is kind of an embarrassing example because it's a way that I am accumulating technical debt myself by keeping a laptop for longer than I would ever advise a client to do. I would usually tell people to plan to replace their computers every 3 to 5 years. I've got a laptop that's 6 years old. And I'm just crossing my fingers that it's not going to die in the middle of this conference. And then I would be forced to go out and sort of panic purchase a new machine without shopping for sales, without really thoroughly looking at what my options are. And so in that way, I'm probably not making a very smart decision. And could end up— the impact of that could be that I would spend more. I wouldn't get the right kind of computer for the next one that I buy. And that's just kind of a microcosm of what happens on a much larger scale with a lot of kinds of enterprise technology systems in organizations.
Tony MartignettiWell, I admire you sharing your own personal, I don't know, shortcoming or oversight. Hypocrite is the word that comes to mind.
Karen GrahamYeah, yeah.
Tony MartignettiBut at least you're honest. You're an honest hypocrite. You're not a concealed— you know, you're— all right. I love Karen. Karen's been on the show many times. We've talked a lot. We email. So I know she doesn't object to my comments.
Karen GrahamI feel the same kinds of pressures that a lot of people working in nonprofits do, where, you know, I want to make the best use of my funds. I don't want to overspend. And so sometimes I can be kind of a cheapskate. Double!
Tony MartignettiDouble hypocrite. You're underinvesting and you're not turning over the technology as it ought to be upgraded. All right, Jagan, is there a story maybe that you want to share about proper— let's go to the other end of the spectrum from Karen now to the proper management and investment in technology.
Jagan NarayananActually, we manage IT for a lot of organizations. And as a part of our job, it's a part of our job to let them know how they're accumulating debt and what are the risks they carry. And what we see sometimes is actually quite surprising. We have clients who still use versions of operating systems like Windows 2000 just because it works.
Tony MartignettiOh my gosh, Windows 2000.
Jagan NarayananThey want to use it. They want to use it. They're not changing it because the change will either cost them money—
Tony MartignettiIt's no longer supported. It's no longer supported. It's risky, isn't it?
Karen GrahamOlder than some of the people attending this event.
Jagan NarayananAbsolutely. So that's the risk that they carry. Risk is whether if they're using, let's say, unsupported versions of either operating systems or some of the systems that they have, they risk the possibility of security processes. So that's the biggest risk. And again, security is like insurance. The general perception is if it's not happened to me, I'm safe. So it's a kind of a situation where until it hits you, until
Tony Martignettiit does happen to you.
Jagan NarayananAbsolutely. So I think this is where the challenge is. We need to take— that's why people need to take proactive measures. So when I talk about my own experiences with organizations, this is what we see in a lot of organizations. And even then, they would want to probably extend it As much as possible, because at the end of the day, upgrades also cost money.
Tony MartignettiYeah.
Jagan NarayananAnd I think that's the challenge that they have.
Tony MartignettiBut Karen, we should look at this as an investment, right?
Karen GrahamWell, I don't know why you're asking me questions because I've now completely undermined my own credibility.
Tony MartignettiNo, no, no. Well, let me take a moment then to rehabilitate, because Karen, I've known Karen for years. She is a very smart, very savvy tech reviewer, tech consultant. tech person, professional. She used to produce reports about technology, and I had her on the show talking about them. So this is all— that was, that was all in fun. Karen is a very savvy and very smart consultant. Karen Graham Consulting. I know her little bio doesn't say Karen Graham Consulting, it just says speaker, writer, consultant, coach.
Karen GrahamWell, I've named my business after myself.
Tony MartignettiKaren Graham Consulting. And as I— Tony Martignetti Nonprofit Radio, Martignetti Planned Giving Advisors. I think that's the right way to go because you're a well-known name in technology. So Karen Graham Consulting has gravitas.
Karen GrahamThank you.
Tony MartignettiAnd that's not just a gratuitous rehabilitation. It's all deserved. Besides, we've made such terrible fun of you, I want to make sure that I go— I just want to make sure I rehabilitate and set the record straight. Again, that was not a gratuitous rehabilitation. It's all true. Thank you. As a savvy, smart tech consultant at Karen Graham Consulting, we should be viewing this as an investment, right? Not expenditure, not spending, but we're investing in tech just like we should invest in our people.
Karen GrahamRight. Yeah, we should. But in order to make a proper investment, you need to save for that. You need to budget for it, and you need to understand how to evaluate return on investment. And I actually think that's sometimes how these things start to fall apart, is that people don't understand how to really evaluate the ROI. They don't understand how to persuade someone of that. That's something we talked about in the session a bit. There were a lot of people in the room that were IT and operations people that do understand this already. And yet, they're sort of inhibited from implementing really smart technology investments in their organization because their leaders don't understand the importance of it. Their boards don't understand the importance of it. Their funders don't understand the importance of it. And so, I think it's our responsibility as technology leaders to acquire the skills to be able to really make a strong case for those investments, and to do it in the language, to use the the kinds of arguments that are relevant to the people that are making those decisions.
Tony MartignettiWell, let's stay with you. How do we start to budget for this?
Karen GrahamLet's take websites, for example. Almost everyone, almost every nonprofit organization does some kind of website refresh or maybe even a complete overhaul redesign every 3 to 5 years, and yet few organizations budget for that in the years that they're not doing it. And so, to smooth out that cash flow and to be prepared for a major website redesign, a few organizations have a practice of setting aside a little bit of money in a fund that's dedicated for that as they're building up to it.
Tony MartignettiOkay.
Karen GrahamBut many of them just wait until it's kind of past due, and then they'll maybe go to a funder and say, oh, we need many tens of thousands of dollars to be able to do this redesign. And they just cross their fingers that somebody's going to say yes.
Tony MartignettiWhat about for the— Jagan, what about for the kinds of technology that's palpable? Karen was talking about her laptop. I'm thinking of servers. I mean, I'm not a tech person, but you are. How do we budget for what those expenses are going to be? The laptop upgrades, the server upgrades, things like that. How do we know how much to plan for?
Jagan NarayananSee, actually, if you are a technology person, normally the roadmap for technology is laid out by the vendors. You take the large vendors, be it the network vendors like Cisco and Juniper, or you take the server vendors like Dell or HP. I mean, all of them have set a roadmap, and I think that roadmap is available for us as technologists. So we know where technology is headed in terms of virtualization. So Very clearly, that road— once that roadmap is available, there is a possibility that you can therefore start seeing that this is when I need a refresh, this is when I need an upgrade and stuff like that. While you may not know the exact amounts which are required for these exactments, but as Karen said, if we put together a plan and start setting aside some money straight away, so at least it doesn't hit you when in a big time when it actually happens. Right. You start setting aside funds for it over a period of time and then start rolling it out on an annual basis rather than doing it at one shot. Every year you set aside a certain amount of money for upgrades, for, let's say, now we're using the word technical debt, for, let's say, managing technical debt and you set aside some money and then you know what comes in at that point in time and start using it for that purpose.
Tony MartignettiOkay. And the large providers have a roadmap, roadmaps for us that—
Jagan NarayananMost of them have. That we can— Most of them. We have some visibility into what's in store. It's not that they just throw something at us. I mean, there is obviously an available in terms of, if you go to Microsoft, I'm sure Microsoft will tell you when is the next release planned for their operating system. And they will also tell you when is the support stopping for the earlier version of the operating system. So you certainly have a timeline for you to plan.
Tony MartignettiOkay. And hardware, hardware as well.
Jagan NarayananAnd same with hardware.
Tony MartignettiAs you mentioned, HP, etc. All right. All right.
Karen GrahamAnd there might be a lot of people listening that are not with an organization that has an IT professional on their staff. And so maybe they don't have somebody that really has the knowledge to keep track of these kinds of things. In that case, they should find somebody like Jagan or, you know, someone who can advise them, maybe outsource that, um, who can help them make those plans.
Tony MartignettiOkay.
Jagan NarayananActually, it's a good idea to have a periodic audit. Let's say do an annual audit to see where you are and what is it that you need to address. That's probably a good way to address it in that sense.
Tony MartignettiAuditing software, hardware?
Jagan NarayananAbsolutely. That's right.
Tony MartignettiOkay. Vendor relationships, backup plans?
Jagan NarayananAll of it together. Do an infrastructure IT audit to see where you are and what are the gaps that you have to fill. And then plan for it. At least you can plan for it the next year.
Kate MartignettiIt's time for a break. Virtuous is a software company committed to helping nonprofits grow generosity. Virtuous believes that generosity has the power to create profound change in the world and in the heart of the giver. It's their mission to move the needle on global generosity by helping nonprofits better connect with and inspire their givers. Responsive fundraising puts the donor at the center of fundraising and grows giving through personalized donor journeys that respond to the needs of each individual. Virtuous is the only responsive nonprofit CRM designed to help you build deeper relationships with every donor at scale. Virtuous gives you the nonprofit CRM, fundraising, volunteer, marketing, and automation tools you need to create responsive experiences that build trust and grow impact. Virtuous.org. Now back to Avoid Technical Debt.
Tony MartignettiSomething I'm curious about. I know both of you, but I know I'm not the person who introduced you. How did the two of you come together to do this session together? Oh, that's interesting.
Jagan NarayananThat's interesting. Actually, I've gotten to know Karen Only the last few weeks, okay? We have another gentleman in our organization who's been talking to her for a long time.
Tony MartignettiRanga.
Jagan NarayananRanga, that's right. So Ranga has been driving this, and that's how we got set up. And we've been in this nonprofit technology thing for the last couple of years. So we've been working with multiple people and reaching out to a lot of people. And Karen was certainly one of the— on our list, she was on top of our list.
Tony MartignettiOutstanding. Fourth Dimension, of course, you were a sponsor of Nonprofit Radio.
Jagan NarayananOh yes, we are.
Tony MartignettiAnd you were on our 650th or 600th show.
Jagan Narayanan600th show.
Tony Martignetti600th show, I interviewed you in Moynihan Station in New York City.
Jagan NarayananOh, you remember so well.
Tony MartignettiMoynihan Hall, pardon me, Moynihan Hall in New York City. And then we had a very nice dinner together.
Jagan NarayananThat's right.
Tony MartignettiSo I know, I know the both of you well. I just, regrettably, I'm not the person who brought you together, but Ranga found Karen. Top of her list, top of his list. Let's talk a little about ROI. Let's stay with you, Jagan. Yeah. And then Karen, I'll turn to you to fill in some too about how do we start to estimate ROI? Because this is something that if everything is going along fine, then the C-suite may just say, well, everything's going along fine. I don't see any downside to continuing with With Windows 2000, for instance. Why should we bother? How do we quantify the value of upgrading to the current operating system, for instance?
Jagan NarayananOkay, there are multiple ways of doing this. There are multiple ways. One is very simply, is there a productivity impact because of the fact that you're running older systems? Productivity, okay. That's one way to look at it. And when you look at productivity impact, that's something we can straightaway add money value to it and do it. The other is a potential risk that you carry. Like when you say security risk, it's a risk, but to be putting a money value on it, we need to put a model by which you can say, hey, in case we have a security incident, what is the impact that this has on organization? Okay. So these are the 2 things that comes to my mind straightaway.
Tony MartignettiSecurity-wise, we We can look at some of the headlines.
Jagan NarayananAbsolutely.
Tony MartignettiRansomware attacks on, I mean, sometimes even on nonprofits. We don't even have to just look at the commercial, the corporate side of hacks, like Yahoo is the one that comes to mind, but there have been others since then. But some nonprofits have been attacked.
Jagan NarayananIn fact, I'll tell you a very good example of technical debt which actually had an impact on general users. Sometime back, we had an issue at Southwest. But I think the systems came down. I think this is about— Southwest Airlines? Southwest Airlines. This happened, I think, about 3, 4 years back. And I think one of the reasons was that some of the systems were not upgraded in time. Okay, so having said that, I mean, I'm saying even for large organizations it happens.
Tony MartignettiYeah.
Jagan NarayananBecause we tend to ignore it in a lot of ways, right? So having said that, from an ROI, look at the impact. And so if you look at it as an impact, somebody has to put together and saying, hey, in case this happens, what are the costs involved? Therefore, it's better to invest now and prevent an incident happening sometime down the line.
Tony MartignettiOkay. Then also, as you mentioned, productivity.
Jagan NarayananProductivity is a very simple model.
Tony MartignettiYeah, we're working, right, Karen, suppose let's take this Windows 2000 example. Aside from the security risks of using an operating system that hasn't been supported for I don't know how many years or decades or a decade or so, but just, you know, like the workarounds. Like if you want to integrate Calendly, let's say, or something, you know, to your email or, you know, to, to use something modern with something that's 24 years old, um, that, that's enormously unproductive.
Karen GrahamRight. Well, and just to put some numbers to this, and I hope I'm not—
Tony MartignettiBring the technical side to it.
Karen GrahamI hope I'm not doing the math wrong spontaneously here, but I was just thinking like, let's say So, say you have 10 minutes a day that your old computer, your old operating system, your workarounds are slowing you down by 10 minutes a day. And then, if you multiply that out, say, by like 40 hours a week and 50 days a— or 50 weeks a year with some vacation, things like that. Yeah. Say you have somebody that's being paid $50 an hour. If you take the value of their time, I think that's $2,000. A year, right?
Tony MartignettiOne employee.
Jagan NarayananOne employee. Right.
Karen GrahamSo, I mean, for $2,000, would you want to upgrade their operating system? It seems like that would be a pretty clear yes.
Tony Martignetti$2,000 of ongoing costs each year.
Karen GrahamRight.
Tony MartignettiAnd then on top of that, the risk, the security risk. We haven't quantified that.
Karen GrahamRight. Now, by making the investment of time and money into upgrading the operating system, you're not really going to save $2,000. You're still going to be paying that employee, right? You're not going to be paying them for 10 fewer minutes every day.
Tony MartignettiHow much productivity?
Karen GrahamBut they're going to have 10 more minutes that they could be using to do something that is advancing your mission, that is raising more money for your organization, that is increasing your reach. You know, there's all kinds of things they could be doing. So, it's really more of an opportunity cost in reality. But if we want to put numbers to it and be able to use that to compare ROI of different options, Then that's a way that you can do it.
Tony MartignettiOkay, okay. I'm just reading from your session description. Best practices for managing and maintaining IT infrastructure and software systems. Have we covered that?
Karen GrahamHave we covered that, Jagan?
Jagan NarayananYeah, we did talk about it. We did
Tony Martignettitalk about managing and maintaining.
Jagan NarayananThat's right. One of the things that came across during our session itself was One was the periodic audit itself, which kind of gives you an idea of where you are and where you want to be. The other was, I think one of the participants themselves brought this out, was to put together a plan. I mean, while he spoke about a 5-year plan, I mean, my personal view is in technology, 5 years is a long time. It's a very long time. I mean, things change a lot.
Karen GrahamThink about where we were 5 years ago. That's right. And how many things didn't even exist. Absolutely.
Jagan NarayananBut to put together at least a plan saying, hey, this is my technology plan over the next few years, and then start implementing it in phases so that you spread out your cost over a period of time. So these are primarily— one is an audit to see where you are, because we are so much into the issue that you become a part of the problem and not a part of the solution. Yeah. All right? So one way is to step back, get somebody to do an audit and look at it and give you feedback. The other is to spread out, put together a plan for the next few years. I would rather say 3 years and spread out your costs over a period of time rather than have them stuck, I mean, thrown at you at one time. Yeah. These are the 2 things which came across that point. Okay.
Karen GrahamI would say with technology planning, because things change so much and it's nearly impossible for that reason to make anything more than even a 1-year plan, I would say, in the environment that we're in right now, It's equally important to have a technology strategy. And to me, that means priorities. For example, in security, there is often a trade-off or friction between higher security and higher convenience for the end users. Yeah. And so, to have sort of a philosophy, like, when those 2 things are in conflict, we're going to lean in one direction or the other. Or if it's a matter of, Like investing more money versus— I'm trying to think of what the trade-offs might be here. There's all kinds of dichotomies where you can say, our philosophy, our approach is going to be that we're going to lean in this direction. And those kinds of things can guide the decisions that you don't even anticipate you're going to have to make a year from now when some new technology arises or when something changes in your environment or your organization. Yeah.
Jagan NarayananTalking about security, there is no limit to the level of paranoia that you can have, right? So which means there is no limit to it.
Tony MartignettiIt's clear which side you would defer. As Karen said, decide one way or the other. It's clear which way you would— which direction.
Jagan NarayananSo the question is, where do you want to draw the line and say, hey, I'm willing to live with a certain set of risks? But you need to be sure that you're not taking the one— you can't be one extreme or the other. Yeah, right.
Karen GrahamIf you're pursuing perfect security, I mean, you're just going to drive yourselves crazy. It's impossible.
Tony MartignettiRight. And you'll have quadruple-factor authentication.
Karen GrahamYeah. So you have to kind of decide, like, what's—
Tony MartignettiPeople have started quitting because they spend half their day logging on.
Karen GrahamYeah. So you have to decide what's good enough. And it's probably not what you're doing right now. But there is something that's probably good enough. Another thing that I was thinking about when you were talking about return on investment is user adoption and training. And, um, and I often see really great technology investments sort of go to waste because people don't take advantage of them. It's, it's like the treadmill that I have in the basement right now, which is collecting dust. Uh, you know, that's not going to help me get more fit.
Tony MartignettiYou don't have to tell your own personal story about the treadmill now too. But, but, but, um, share— is there— it sounds like there's— you've seen some evidence of that, or you've seen cases of this.
Karen GrahamI most often see that in CRM, um, databases, and, you know, other kinds of software applications, but mostly CRM.
Tony MartignettiBuying something much more robust than needed?
Karen GrahamWell, or even buying the exact thing that's needed, but then if staff don't fully utilize it, if they're not well trained on it, then you're just leaving a lot on the table.
Tony MartignettiWe had a session yesterday. I spoke to, uh, some folks actually from Heller Consulting about leaning more on your existing tech stack before you go to an outside shiny object that does just one discrete thing. It may be very well buried in your Microsoft 360 subscription or your Google subscription. And they were using calendaring as an example, like calendar polls that exist in Microsoft 360 and also in Google. Beyond— oh, whiteboards. Yeah. Whiteboards, that's buried in Microsoft 360. 360. A lot of people don't know that. So using— that's also your— to your point, Karen, knowing, knowing what you, you're paying for and, and using it, utilizing it fully,
Karen Grahamright? I always tell people, don't be so scared to click on things. Yeah, you're not going to break anything, right? You know, just like go through, go through the whole menu and just click on every single thing and see what it does, and you'll probably find all sorts of things that can improve your productivity and avoid extra Because you have already something that will solve the problem.
Jagan NarayananYep.
Tony MartignettiVideo conferencing was another. And transcribing video conferencing.
Jagan NarayananOh, yes.
Tony MartignettiThat stuff is all buried in Google and Microsoft. You may very well be paying for it. All right. That was another— that was a session yesterday. Utilizing your existing tech stack before you go outside. All right. Well, so you spoke to folks for an hour yesterday, and we've We've only been talking a little over 20 minutes, so don't hold back on Nonprofit Radio listeners, or otherwise I can't have either of you back. So if I know you're giving short shrift to our listeners, so don't do that. So what else did you talk about yesterday that we haven't talked about today, or go deeper in something maybe that we've covered but not sufficiently?
Jagan NarayananActually, we had a lot of participation from the audience, and a lot of them are willing to share what they had done in their organizations. And if you look at some of the, what should I say, takeaways that happened, it is all more from participants sharing their views as much as what we were talking about. And this 5-year plan, in fact, one of them came up and said, hey, we do a 5-year plan, which I think was very impressive when everybody heard about it.
Tony MartignettiBut maybe ill-advised, it sounds like. Like 1 to 2 years is more realistic.
Karen GrahamHaving a rigid 5-year plan is probably ill-advised, but having a flexible 5-year plan, that sounds fantastic.
Tony MartignettiOkay.
Jagan NarayananWell, more importantly, having a plan.
Tony MartignettiOkay. What else from the audience? Questions or things folks said privately? What else came from the audience?
Jagan NarayananAnything that you remember, Karen, that you quickly can—
Karen GrahamIt's funny, being in the moment, I was just I was listening to everybody, and now I'm trying to remember exactly what was the most juicy stuff that came out of that. All right. But I will say that it felt a bit cathartic for people to just have a gripe session together too and compare notes. You know how that is when you experience things in isolation. Maybe you are the only IT person in your organization. I think that was true for a lot of those people. They're not part of a big department. They're in a relatively small organization. So they might not even be an IT professional. Maybe they're the operations person, and that's one of 5 different areas of responsibility that they have. And the chance to connect with other people and understand that other people also experience this, and they have figured out ways to overcome technical debt, or at least to move in that direction, that seemed to feel good for people. And a few individuals commented to me about that afterward.
Jagan NarayananAnother thing comes to my mind, Karen, I think there was some thought in terms of how do we present— all of them are mostly IT professionals, and if they need to present it to their boards or to their CXOs, how do we present technology challenges in a manner which the senior management understands? Yeah. I think there was a need to see— I mean, be aware that this is something we need to be presenting it differently from what we probably do, because normally we tend to talk technology language. So we probably need to talk the business language for the senior management to understand the impacts of what we do, and therefore get your budget sanctioned.
Tony MartignettiKaren, you alluded to that earlier. You were talking about using the right language. Do you have advice about converting tech language to business language?
Karen GrahamYeah. Think about the audience and what they care about, right? So you're going to present probably a different message to your CEO or executive director than you would to your CFO or to your board. Boards care about risk management. They care about big picture strategy and how is this going to help our organization be successful in the long term. I think CEOs and executive directors care about the same kinds of things, but they're also more operationally oriented than a board of directors would be. But they also, above all, probably care about the mission. And so, that's something we talked about is, as soon as you can connect a technology investment to serving people better, providing better quality of service, or better reach, or quicker response times, or things like that to whoever your constituents are, then that starts to get people's attention more than talking about this This license is going to expire, this product is no longer going to be supported, and there's security patches that won't be happening anymore, la la la. People kind of tune out when you start talking like that. But if they can translate to what this means is that our food shelf might not be able to continue providing services, we might have a disruption, then it becomes very real. Mm-hmm.
Tony MartignettiAll right. How about we leave it there? That sounds like good motivation and advice. All right. She's Karen Graham, speaker, writer, consultant, coach at— I'm going to add— at Karen Graham Consulting. And with her is Jagan Narayanan, CEO at Fourth Dimension Technologies, all about avoiding technical debt from killing your nonprofit. Jagan, Karen, thank you very much.
Karen GrahamThanks. It's been a pleasure.
Jagan NarayananThank you, Tony.
Tony MartignettiGood to see both of you. Thank you. Thank you. And thank you for being with Tony Martignetti Nonprofit Radio coverage of the 2024 Nonprofit Technology Conference, where we are sponsored by Heller Consulting, technology strategy and implementation for nonprofits. Thanks for being with us.
Kate MartignettiIt's time for Tony's Take Two.
Tony MartignettiThanks, Kate. I had a dream recently. It was a fundraising dream. I was hosting a Jerry Lewis Labor Day telethon. Now, if you're not 50 or older, you may not know what that even means, but the actor Jerry Lewis used to hold— used to host Labor Day telethons over the Labor Day weekend to raise money for the Muscular Dystrophy Association, MDA. So, uh, but in the dream, I was the host. So Jerry Lewis, that hack, he's out. Second-rate comic, he's out. I'm the host, and we're raising money not for muscular dystrophy, but we're raising money for a philharmonic in the dream. And I asked the executive director of the Philharmonic, what is the all-in cost of a production night? So all the rehearsal, backstage, front of house, performers, everything. What, what's, what's the total cost? And he says $300,000. And right away a donor comes to us, and I don't remember whether it was online or actually phones were ringing. That's the way it used to be done in the In the Jerry Lewis Labor Day days, the phones would be ringing, but whatever. A donor comes to us and he pledges $3 million, which is enough for 10 performances. So we acknowledge that transformative gift and we shut down the— shut down the fundraiser. It's over. We're done because this is— it's an amazing gift. But the funny thing is the The donor had the voice of the actor Paul Benedict. Now, he's not a very well-known actor, but in, in a movie that I love— remember, this is my dream, so I'm entitled to put anybody in who I want. In the movie I love, which is Waiting for Guffman, it's a Christopher Guest film. Paul Benedict plays kind of a savior. Character in that movie, Waiting for Guffman. So it makes sense that, that he would be the sort of savior for the, for the fundraising telethon that we were doing. All right. So then, so then after the dream, then I got up and I went to the bathroom. But so what's the takeaway? You know, after the bathroom, you gotta think about, well, why am I having this dream? All right. So the takeaway, I think, is there's bona fide for fundraising. Share your real need with your donors. Don't, you know, don't pretend that you can get away with less than you really need. I asked the executive director, what's the full cost of a performance? And, and he shared it. So I think you should share your full needs. And then when you're budgeting and planning, plan for full needs, not sort of get-by type needs. Yeah. I think if you share your full need with your donors, they're going to be very much more likely to step up and fund you, just like Paul Benedict did in my dream. That is Tony's Take Two. Kate.
Kate MartignettiThat was such a vivid dream. I feel like when most people remember their dreams, they're like, oh, I was just falling in the middle of nowhere. You had like faces and voices.
Tony MartignettiWell, I have those too, but I, I made some notes, uh, right after this dream, so I was able to help— that helped me remember it.
Kate MartignettiWell, we've got beaucoup but loads more time. Here is your technical roadmap.
Tony MartignettiWelcome back to Tony Martignetti Nonprofit Radio coverage of 24NTC, the 2024 Nonprofit Technology Conference. We are still in Portland, Oregon at the Oregon Convention Center, and this conversation kicks off our day 3 coverage of the conference. Maybe you can hear that in my voice just a little bit. We're sponsored at 24 NTC by Heller Consulting, technology strategy and implementation for nonprofits. I am now with Kestryl Lowrey. Lowrey. He is Managing Director for Technical Services at Cloud for Good. Kestryl, welcome to Nonprofit Radio.
Kestryl LowreyThanks for having me. Great to be here.
Tony MartignettiAbsolutely, pleasure. Thanks for being with us early in the morning. Uh, your session— you've done your session already, I assume?
Kestryl LowreyUh, no, it's this afternoon at 1:15.
Tony MartignettiOh, you're one of the last ones. Okay, okay, this afternoon. So a little preparation for you. It's Oh, the Places We'll Go. Building a Technical Roadmap. All right, so I'm going to start with just the basic, why did you feel we need this session? What are nonprofits not quite getting right about their technical planning?
Kestryl LowreyI think that a lot of nonprofits end up in a very reactive place when it comes to their technology, that instead of being able to really think ahead, you know, where are we going to be in 3 years, in 5 years, and what tools do we need to support that? It becomes a, oh, we've been prioritizing, you know, our outcomes and our mission-driven delivery, and technology becomes kind of an afterthought. And I think that there can be a lot of impact by thinking ahead and saying, what tools are out there? What could we be doing differently? How could that increase our impact? Instead of Having it come from a reactive place.
Tony MartignettiOkay. Um, and maybe even avoiding a crisis? Exactly.
Kestryl LowreyPerhaps?
Tony MartignettiYeah. Okay. Um, so I'm just drawing from your, your session description, uh, how to prioritize tech investments based on the growth and maturity of your organization. Um, how do we, like, you know, how do we forecast what our needs are going to be? And you even talk about our growth and maturity. Help us to look ahead. How do we do that?
Kestryl LowreyYeah, so a big part of it first is to both look at where you are and what you're using, and think realistically about what you have the capacity to absorb there. I think one thing that a lot of nonprofits end up doing is, you know, there can be some great free tools out there, both enterprise-level tools that will give free licensing for nonprofits, or also things that are deeply discounted. And so someone might adopt a tool that is frankly bigger than what they need. You know, I say with the free licensing, sometimes it's free like puppies.
Tony MartignettiYes. Somebody 2 days ago said free like kittens. Yeah, exactly the same thing.
Kestryl LowreyYou know, just because you have the tool doesn't mean necessarily that it's the right fit for your use case or that you have the team to support it. So then you can end up with some pretty tremendous technical debt. You know, you've got all your data into this thing or you've built all this automation, and you're not able to manage it well. So some of that technical roadmapping is thinking through, like, what's the right fit size for your organization? And not just what do you need to implement it, but what do you need to be successful with it long-term?
Tony MartignettiYeah, but how do you figure that out? What factors, what variables are we looking at to determine that? What's right for us?
Kestryl LowreySo things to look at for figuring that out, of course, first of all, looking to your peers, you know, looking to other organizations with similar size or that do comparable work in other industries, even essentially for what you're doing. Conferences like NTC can be a great place to kind of start seeing what's out there and what your options are. Looking at what the, what the tool is best at, which is hard sometimes when you're talking to salespeople, you know, because every salesperson is going to tell you it's the best thing for or anything you would want to do, but trying to actually get some references from them of how are other people using this tool, and then really taking a step back and not saying, oh, well, gee, this cool— this thing, this marketing tool looks awesome. It can do all of this stuff. Look at how you're doing marketing right now. If you're sending a scheduled email on a weekly basis that's a newsletter and you don't have journeys or drip automation, if you don't have responsive campaigns, Then those might be things to look at bringing in, but you probably don't need the broadest feature set just to start with. So think about whether or not you're going to be able to support that.
Tony MartignettiAnd that something like that, like an email journey, that may even be in your existing stack already. Your email provider may already have that for you.
Kestryl LowreyYeah, exactly. Like when you're building your roadmap, it doesn't necessarily mean tool change. It can mean staying on the same thing that you're using and using it better. Mm-hmm. I think the first, with any technical change, really you start from features and capabilities that you need. Like, you start from what does your organization actually need to do? And that's what should be driving any of the conversations that you're having and decisions that you're making for the technology. What you need to do might be about your marketing, might be about your fundraising, might be about security and compliance, but you should start with What do we actually need it to do? And then find the tools to suit that instead of starting with, this looks like a really cool tool, let's find a way to use it.
Tony MartignettiOkay. Yeah, very smart. And, you know, seems common sense, but very worth saying because a lot of times I think the shiny, right, the shiny object gets our attention. Plus other people, my friends are using it.
Kestryl LowreyYeah, exactly.
Tony MartignettiI just saw it and the interface is so simple. It was so easy for me.
Kestryl LowreyYeah, well, I was able to just turn it on and now I have this thing and I can send out text messages. Okay, well, have you thought about how you're going to use text messages for your organization? Are they actually going to move you forward? Have you thought about compliance for that? Can people opt out? Like, anytime you bring in then a new shiny object, you're actually opening a whole can of worms of other things to think about.
Tony MartignettiYeah, that's brilliant. Right. Um, who should we be getting input from? Uh, who should be at the table making these decisions? Well, these are not tech implementation decisions, but thinking through, you know, what do we need? What are our needs? Who should we be getting this input from?
Kestryl LowreySo I think that any of these changes, really, it's a whole organization conversation. Like, you want to get input from staff that are going to be using the tool. You want to— you don't want it to just be coming, you know, from IT. You don't want it to just be your executive that said, look, I went to a conference and saw this cool thing. We're implementing it. Like, you need, you need to actually think about what, what is our organization doing? What supports our processes better? What is our vision for how we're going, where we're going to be, and what we're going to be delivering in 2 or 3 years? I can speak from my own experience. Oh, yes. One nonprofit that I used to work directly at. Where we were a legal advocacy organization, and we were expecting a specific Supreme Court decision to come within the next year, and that was going to be a tremendous spike in our case volume. And so what we were looking at was, what tooling do we need to be able to scale up to— I think in the days after the decision that we were concerned about, we went from typically having about 10 to 30 inquiries a day to over 1,000 inquiries in one day. Wow.
Tony MartignettiMy, yeah.
Kestryl LowreyIt was tremendous. And so, part of my role as the IT director there, as we were planning for that, was to look at what do we need to accelerate response times for our paralegals? What can we set up for knowledge management so that more people can help faster? Um, what did our existing database have that could do that, and what did we need to bring in to support that? So, to get to that decision, I was then taking and talking both To our paralegals, to our lawyers that would be taking the kind of the equivalent of like tier 2 or tier 3 cases to do it. Mm-hmm. Talking to our different legal compliance people of, okay, if we have this high volume in, what do we have to then retain later for it to make sure that we're doing everything to cover our requirements there? What sort of scalability considerations am I not thinking about talking to other IT partners with that so I could really get the full picture on it. It turned out in that case that the system we had, and we were working on Salesforce at that point, was able to scale up to what we need. But we did end up implementing a few other pieces of the platform in order to support that fast responsiveness. So in some ways, it's really you've got to both look at what's coming, talk to the people who are actually going to be using the tools that are implemented, look at what you have, whether or not you can expand what you have, if that works in the timeframe you do. Or if that's not gonna work, then what other tools are out there that you can bring in and support what you need to be doing?
Tony MartignettiThat's incredible scale. It sounds like overnight, I guess, when the decision was released.
Kestryl LowreyWhen the decision was released, you know, and that there were—
Tony MartignettiWas it a Supreme Court decision?
Kestryl LowreyIt was a Supreme Court decision, yeah. Supreme Court decision related to gay marriage. So that was a significant one. And we had not just You know, the, like, technical planning there, but there was additional planning even of, like, document access for our, uh, our C-suite because they were often traveling all over. And so what was the planning to make sure that, you know, our director of legal could read the decision as soon as it came out when we knew she might be on an airplane? Right. So how do we make sure that that document availability was going to be there? Um, so, which I suppose points to that your, your technical roadmap and your technical planning should factor in not just the day-to-day tools, but what do you have for handling specific moments of surprise or crisis communication?
Tony MartignettiYeah. That's a good story. Thank you. Incredible scale. You've got some— well, I guess we're starting to get into them— best practices for creating this tech roadmap. So I'm going to let you take over, tick through some in preparation for your session this afternoon. Oh,
Kestryl Lowreythank you. Yeah. So best practice, first of all, is that your technical roadmap, approach it like a project. Like approach working on that roadmap not as something that you're doing just off the side of your desk, but that you devote resources and time to actually making it happen. I've seen too many organizations that kind of say, you know what, things are on fire, we need to start changing things now. And if you jump in too quickly, then you might end up not really having any direction of where you're going. Yeah. You know, and so you can spend a significant budget and significant time and not have the progress you'd want to show for it because you might end up working against yourself. You might implement one thing and then realize a year later, oh wait, this doesn't really go where we needed to, and change course. So first best practice, actually take it as a project. It is a good phase 0. to start about. Next thing I would say is make sure that you have a good diversity of people in the room. It shouldn't just be IT. It shouldn't just be executives. It shouldn't just be line staff. You should have a variety of voices across the organization. You should probably bring in another point of view outside your organization to talk to you, whether that's through other nonprofits that you partner with that might have done similar things before. Mm-hmm. consulting partner to work with you, other people to help push a little on your ideas and think through, like, is this where you want to be? Here are the things that you're not thinking about. Here's what I've seen at other organizations. That's some of what I end up doing a lot as a technical architect is help people think about the bigger picture.
Tony MartignettiThat outside perspective is valuable. Help benchmark. You've seen other cases. Yeah. Yeah. All
Kestryl Lowreyright. I'd say the next one is really avoiding a lift-and-shift mentality. So a lot of times I'll see nonprofits that mostly will say like, okay, well, we've been using this database for 10 years. Maybe it's time for us to move to something more modern. And then they roadmap out essentially rebuilding the same system that they had on whatever the new tool is. Yeah. Without anyone stopping to think about like, oh gee, is that process, is that way that we do things the way we do it because the tool made us do it that way, or because it's the most efficient way to work. One story I like to tell for this, actually, that— so when I was a kid, I would always watch and help out when my mom was making a roast. And I noticed that she would always cut off the ends of the roast on either end of it and make the roast. And so that was then how I learned to make a roast leg. And I assumed it must have been that there's something wrong with the meat on either end of a roast.
Tony MartignettiThe juices.
Kestryl LowreyYeah, or something. It'll cook better without the fat. The heartstrings or something. Yeah, that's what I figured. And then a couple of years ago, I was cooking with a friend and she noticed me doing this and she said, that's perfectly good meat. Why are you cutting that off? And I said, oh, well, this is how my mom taught me. It's just, it's what I always saw growing up. She was like, hmm, that's weird. You should ask about that. And so I asked my mom and her response was, oh, well, when you were a kid, we had a really small oven. And the pan that I had wouldn't fit something larger, so I had to cut the ends off so things would fit in. Yeah. And so, you know, it's the same thing there of just that lift and shift of I took the process that I saw and moved it forward without understanding the context of it. And we see that sometimes with nonprofits also, of that because processes get adapted to fit whatever your current situation is, because sometimes you have a level of turnover that means that people who are doing the process now don't understand why it came to be that way and just know like, oh, well, I have to tick these 3 boxes in the system and then fill in this field here and enter this data. And I don't really know why we do it that way, but it's what we do. And so, this next system needs to support ticking those 3 boxes and filling in that piece of information. So, I think you can't do your technical roadmap without also really doing kind of your like business capabilities roadmap and your business processes, and they go hand in hand to make sure that you're actually helping your organization mature and move forward instead of just maintain current state.
Tony MartignettiThat's a touching little story about your mom and the roasts you're watching as a child. Plus, I know baking— you have baking in your bio, that you love to bake. So did your mom influence your baking too?
Kestryl LowreyProbably. A lot of the things I know how to cook came from her, you know, but at least with that, there aren't any where it was like, oh, well, you don't put in the baking soda or something.
Tony MartignettiThat's sweet. It's a sweet story. All right. Go ahead. I mean, other best practices?
Kestryl LowreyOther best practices, I'd say, is to not be trying to make your technical roadmap an indefinite I'd say always work towards deciding what your time horizon is that you're trying to plan within. I think 3 to 5 years is normally a pretty good range.
Tony MartignettiOkay.
Kestryl LowreyBecause if you, if you're trying to make something that's gonna last forever, first of all, it's gonna be really intimidating. Second of all, you're going to close yourself off to what innovation might come in a few years and say, like, well, we have this plan that has us extended 10 years out. We need to stick to that. And then you miss out on innovations like what we're seeing with AI, for instance. 3 years ago, 5 years ago, we didn't probably expect to be where we are now.
Tony MartignettiPlus, your forecast just becomes less reliable beyond 5 years even.
Kestryl LowreyExactly. And also, like, it can, it can help then be a good frame of reference for what investment makes sense for your organization when you think about the total cost of ownership of things that you're gonna bring in. And also, how viable are things that are maybe the solution that you're choosing because it's good enough for right now? You know, like, yes, I know it's not the best to have double entry into the finance system and the donor database, and it would be a lot more efficient for people. It would be less annoying for our team members to have an automated integration. But gee, this is what the automated integration is going to cost, and we only expect this system to be in play for the next 2 years. Is it worth it then? So that sort of thing can help you really think through where to put your investment based on how long you expect a tool to stick around.
Tony MartignettiOkay. There was a panel yesterday that said, it was 2 folks, you know, beyond year 3, you need to build a lot of flexibility into your tech plan. Exactly. Because we don't know, to your point, what the technology is going to be, artificial intelligence as an example. And we're not even certain what direction the organization— I mean, not that you surrender your mission or your core values, but there might be programs in 4 years that we're not anticipating today. So beyond, like, from the 3 to 5 year point, you need to have a good degree of flexibility.
Kestryl LowreyExactly. Sound right? Probably one of the last things in your roadmap is going to be your next roadmap project to then start planning where you're going next. Yeah. You know, because both like— and with that, like, once you make a roadmap, it should not be locked in stone. You should maintain some plan for flexibility and innovation there. You have to be able to be responsive. Um, but also it's really good to be able to finish a roadmap and say, okay, we did what we planned to, we got where we were planning to here, now let's go on to the next one. I think that some organizations get to a point of change fatigue if they essentially are just constantly updating the same plan instead of being able to step back and say, yeah, we got something done. Now where are we going next?
Tony MartignettiDo you have any other best practices to share? I know your session is what, just 30 minutes, right? Just 30 minutes, yeah. I'm not trying to embarrass you or anything, but if you have more best practices, we'd love to hear them.
Kestryl LowreyI think the other best practice is to How to phrase this? Not be afraid of picking up what's happening in other industries that are not nonprofits and using those technical benefits, frankly, towards nonprofit use cases. You know, there's a lot of powerful tools out there that don't necessarily frame themselves as being for nonprofit, and there can be a lot of advantage in looking at, you know, something you're experiencing with, I don't know, your— Yeah. say your supermarket loyalty program or something and figuring out like, how are they doing that? What could we do to better engage our donors with it? How could we, for our museum membership, what about this would actually be more engaging? Like being open to looking more broadly because that's where some of the really transformative change can come in for your technical roadmap is not narrowing your scope to just what's been done before. Okay.
Tony MartignettiWhat else are you going to talk about that you can share with our listeners?
Kestryl LowreyYeah, so other than that, what I'll be talking a bit about is making sure that you do, in that roadmap, use it as an opportunity to improve things like your security and compliance posture. So that's something that we're seeing more and more of with, for instance, data regulations coming up. California has their data rules that in the present I have a list of something like 20 different states and localities that are bringing in new data regulations in 2024. Hmm. Like, increasingly, you're going to see a lot more that you have to be doing from a compliance perspective if you're managing anything that could be considered— excuse me— personally identifiable information. And so, any technical roadmap, you'd rather be looking at that head-on instead of having to kind of retroactively look at your systems and say, oh wait, what do we need to do to actually align with being able to let someone manage their preferences, being able to delete someone's data when they ask for it, being able to send it all over to them? I think that also during these roadmapping times is a really great time to think about how you're handling identity and authentication, making sure that your user management is secure, because that's Part of then what you can either, if you don't have it in place yet, it's a great first place for organizations to start. And then it's something that should just be table stakes for any new tool that you're bringing into the system. Like, can you bring in single sign-on? Does it have multi-factor authentication? How is it going to be managing your data?
Tony MartignettiAll right. So, yeah, compliance and security.
Kestryl LowreyYeah.
Tony MartignettiRight.
Kestryl LowreyYeah.
Tony MartignettiAll right. So, these are things that, you know, especially if you're dealing with the— personally, I Personally identifiable individual information? Is that the right one?
Kestryl LowreyPersonally identifiable information. Just PII.
Tony MartignettiOnly 2 I's, not 3. Okay. Personally identifiable information.
Kestryl LowreyI want to say PII squared, but that one hasn't caught on.
Tony MartignettiOkay. All right. Well, keep trying. Don't give up on your keyword. Yeah. So, if you're dealing with those, something like that, that's just something that you're looking to be A part of whatever, whatever system, app, you're looking to bring in.
Kestryl LowreyYeah, yeah, definitely.
Tony MartignettiOkay.
Kestryl LowreyUm, and then I guess the other, the other thing I would highlight is when you're, you're planning out your roadmap, to not just be thinking about tools, but also to be thinking about staffing for it. So, it's great to bring in a new tool, but you also got to think about the care and feeding of it. Who in your organization already could handle it. Um, but also, you know, every, every nonprofit, people are wearing 7 different hats. Um, I think that particularly at a conference like NTC, at every other conversation you have are people saying, oh, I didn't start in technology. I ended up here because we got this tool for marketing and I really liked it. We got this new CRM. And so—
Tony MartignettiThe accidental techie.
Kestryl LowreyExactly. You know, um, and so either figuring out like, Do you have that person in your organization already that wants to take up whatever the next steps of this roadmap are or specific pieces of it? Or is that something that you need to hire in? Do you need to build that into headcount for your organization? Is it something where, sure, you have someone who can administer it, but you need to bring a partner in to implement it, you know, and figuring out actually what, what the human side is going to be of that technical roadmap? Yeah.
Tony MartignettiOkay. Yeah, that's all valuable. Yeah, I'm not sure people think about the staffing. You know, they're thinking, as you've said, they're thinking about how wonderful this new app is going to be. But is there somebody who can support it, maintain it, the care and feeding, as you said? As you said.
Kestryl LowreyAll right.
Tony MartignettiAnything else that we want to talk about? I don't want to hold out on Nonprofit Radio listeners.
Kestryl LowreyI think we covered a lot of it. Yeah.
Tony MartignettiOkay. All right. Good luck in your Wonderful.
Kestryl LowreyThank you.
Tony MartignettiWhy don't you leave us with a little motivation for the, for the technical roadmap?
Kestryl LowreyMotivation for the technical roadmap?
Tony MartignettiYeah, leave us on a high point.
Kestryl LowreyYeah, so with, with your technical roadmap, it's really an opportunity to take a good look at where you are and where you want to be, and then plot out the steps that it's going to be to get there. It can be a really exciting journey, um, and can also mean that you are much better prepared to weather any of the bumps along the way.
Tony MartignettiOutstanding. Thank you.
Kestryl LowreyWonderful. Thank you.
Tony MartignettiKestryl Lowrey, Managing Director for Technical Services at Cloud for Good. I think Cloud for Good is lucky to have you.
Kestryl LowreyOh, thank you. And thank you for having me on the radio today.
Tony MartignettiMy pleasure. Thanks for sharing. Thanks for sharing with our listeners. And thank you for being with Tony Martignetti Nonprofit Radio coverage of the 2024 Nonprofit Technology Conference, where we are sponsored by Heller Consulting, technology strategy and implementation.
Kate MartignettiNext week, the generational divide. No, that's another April Fool's joke. Next week will be email deliverability and email welcome journeys. If you missed any part of this week's show, I do beseech you, find it at tonymartignetti.com. We're sponsored by Virtuous. Virtuous gives you the nonprofit CRM, fundraising, volunteer, and marketing tools you need to create more responsive donor experiences and grow giving. virtuous.org. Our creative producer is Claire Meyerhoff. I'm your associate producer, Kate Martignetti. The show's social media is by Susan Chavez. Marc Silverman is our Thank
Tony Martignettiyou for that affirmation, Scotty. Be with us next week for Nonprofit Radio, big nonprofit ideas for the other 95%. Go out and be great. Okay, I want to try something. I want to try a second take on The generational divide next week.
I love our sponsors!

Virtuous
Virtuous gives you the nonprofit CRM, fundraising, volunteer, and marketing tools you need to create more responsive donor experiences and grow giving.

More Episodes from 2024 Nonprofit Technology Conference
View All


Exploit Conflict & Intuition To Make Better Programs & Products
with Drew Nelson, Cassi Johnson, and Eve LaCivita




Use Your Tech To Enable Generosity
with Jamie Mueller, Peter Genuardi, and Natania LeClerc



