Transcript for 637_tonymartignetti_nonprofit_radio_20230424.mp3

Processed on: 2023-04-24T14:42:31.765Z
S3 bucket containing transcription results: transcript.results
Link to bucket: s3.console.aws.amazon.com/s3/buckets/transcript.results
Path to JSON: 2023…04…637_tonymartignetti_nonprofit_radio_20230424.mp3.443972876.json
Path to text: transcripts/2023/04/637_tonymartignetti_nonprofit_radio_20230424.txt

[00:01:28.31] spk_0:
And welcome to tony-martignetti non profit radio. Big non profit ideas for the other 95%. I’m your aptly named host of your favorite abdominal podcast. Oh, I’m glad you’re with me. I’d come down with Trigon Itis. If you inflamed me with the idea that you missed this week’s show. Technology governance sounds boring in anyone else’s hands. It might be, but Maureen will be off, brings her energy and lightness to help us understand the symptoms of unmanaged tech, the value of a technology governance group and strategies for easing common technology pain points. Maureen is the nonprofit Accidental Techie. This continues our coverage of N tens, 2023 nonprofit technology conference on tony Steak to a great non profit podcast. We’re sponsored by Donor Box with intuitive fundraising software from Donor box. Your donors give four times faster helping you help others. Donor box dot org. Here is technology governance.

[00:02:18.51] spk_1:
Welcome back to tony-martignetti, non profit radio coverage of 23 N T C. You know what it is. You know, it’s the 2023 nonprofit technology conference hosted by N 10. You know that we’re in Denver, Colorado at the Colorado Convention Center what you don’t know is that now I’m with Maureen will be off. We are sponsored at 23 NTC by Heller consulting, technology strategy and implementation for nonprofits and very grateful for their sponsorship. Maureen will be off is nonprofit digital strategist and technology coach at the nonprofit Accidental Techie with Maureen will be off. So she’s also aptly named and

[00:02:20.58] spk_2:
I say hello right back to

[00:02:23.13] spk_1:
our last interview.

[00:02:24.52] spk_2:
Wonderful. You worked with her where she Firefly partners hired her a million years ago. I, I was, I was one of the owners and a partner for 10 years staying in my hotel room this week. So

[00:02:43.12] spk_1:
I’m going to the Firefly.

[00:02:44.59] spk_2:
So am I will see you?

[00:02:47.30] spk_1:
There were a founder, founder and

[00:03:10.66] spk_2:
another 2008, some silent business partners came together and gave us an opportunity to start an agency. They gave us a little money and we were fully remote from day one when all we had was a O L instant messenger to chat with each other. That will tell you how long ago that was 2000

[00:03:18.04] spk_1:
and

[00:03:36.88] spk_2:
2018. So stayed for 10 years. And then I felt like I was so far away from the organizations themselves to actually lend a hand because we had people like Corley who were working directly with our clients. So I sold my shares and left the organization and started my own solo consultancy. At that point. I’ve

[00:03:43.04] spk_1:
known Jen Frazier. For just a few years. But I didn’t know that I’ve known you since you were on non profit radio last year. I didn’t, I just didn’t know about the connection.

[00:03:52.40] spk_2:
You know, we’re all connected here.

[00:03:55.08] spk_1:
So we’ll see, I’ll see you at the pizza party tomorrow, tomorrow, tomorrow, tomorrow,

[00:03:58.82] spk_2:
tomorrow night.

[00:04:01.13] spk_1:
All right, Maureen. We’re talking about technology governance for accidental techies. Why did you feel that this was important enough that it merited a session at 23 NTC?

[00:04:52.55] spk_2:
Because most organizations, whether they’re large or small have simple technology or very sophisticated technology really struggle with managing it as a holistic ecos system. So the fundraising folks handle their tools, the communications folks handle their tools. But, but you know, when we bring these products, software CRM into our organizations, it’s really tricky to get it all, to talk to each other, to work well, to make decisions for the best interests of the organization as opposed to just the users of that system. So often when I work with nonprofit clients, it’s the first time, the right group of people, like a cross functional, collaborative group of people have sat down and made decisions about technology together with everybody’s interests and needs in mind and it makes your systems work better and it helps you get a return on investment.

[00:05:19.44] spk_1:
So we’re envisioning a nonprofit where there are disparate systems, like there’s an accounts payable there, maybe there’s a treasury system, maybe there’s another bookkeeping system or something. There’s, of course, a fundraising system, there’s an hr

[00:05:34.57] spk_2:
email marketing, peer to peer fundraising volunteers, etcetera.

[00:05:45.78] spk_1:
Now, what about the companies that endeavor to put all these under one, um, mass name? Like, like, I don’t know, the salesforce or Blackball. Do those actually help small and mid size? Our listeners are in small and midsize shops. There’s, there’s no, um, I don’t know, there’s no 1000 employees, uh non profit listening, most likely. So do those big, do those big names work for small and midsize?

[00:07:43.13] spk_2:
They can, they can if they’re governed, if someone is paying attention to them, if the right people are talking about what’s working, what’s not working. Usually what happens in the small to mid size shops is the stuff as a whole is not cutting it, you know, or you’ve got redundancy, you’ve got two platforms that do the same thing or more or even something as simple as multiple canvas accounts, you know, like let’s talk about what you have, bring it all together. Um Make sure that users are supported, make sure that you know what you’re spending on this stuff and that the data is moving around between the systems instead of um data silos because that’s really where the power of all these tools comes in is, yeah, you can pay your staff. Yeah, you can collect online donations. But if different people have different needs and they’re not sitting together collaboratively making decisions, it causes friction and frustration. Often folks feel like they need to be a technology expert in order to govern their technology. So they don’t do it or they feel like, hey, I’m paying for this thing. It should just do what it’s supposed to do. It’s like if you hired a new staff person and never on boarded them, they’re professional, they know what they’re doing. They’ll just come in here, we’ll give them a computer and they’ll go not going to perform as well as a person who is managed, overseen and kind of guided to be the best that they can be. Alright,

[00:08:07.30] spk_1:
let’s talk about some of these symptoms of unmanaged technology bundle stack stack like a pro totally pro tech stack. Yeah. What does this look like that? We know we’ve got an ungoverned stack surrounding us, engulfing us. Maybe it’s engulfing us like it’s an Amoeba were a little Amoeba also were something smaller than an Amoeba. Amoeba have to eat two and it’s being engulfed by this Amoeba tech stack.

[00:09:53.73] spk_2:
What some of the symptoms are, are things like I just mentioned, you’ve got multiple of the same function, three email tools. Why, you know, probably just one would be better that way you can get really good at that. In addition to only paying for one thing, staff are due doing a lot of manual work that could be automated. So I’ve worked with an organization, small organization where everything was people powered even though they were paying a lot of money for the technology that they had in house. So change management, user adoption, none of that stuff was actually being taken care of. Um Your technology budget can grow dramatically year over year and no one really knows what you’re paying for everything, waste of money, waste of time. Uh You can also have turnover on your team if they feel like they’re um their pain points or their ideas for improvement are not being heard, they will leave and then you’ll need to start all over again. So it usually hits, there’s a, there’s a plan problem. You don’t have a plan for how you’re going to use all this stuff together. There’s a people problem, your folks are not trained properly or don’t have the right skills to be successful using this stuff, platforms, maybe you’re not in the right system or there’s a big gap or a business process problem. So a governance group small and scrappy meet once a month and kind of do updates with each other. Hey, here’s what we’re working on in our area of the text. We’re

[00:10:04.66] spk_1:
gonna, we’re gonna get to the technology, to your T G technology, technology Governance group, but I just want to see any more, any more symptoms of malfunctioning

[00:10:50.44] spk_2:
large frustration and you might not, you might be confusing your supporters because if they have one platform that they’re using, that looks and feels very different from another platform like I’m a volunteer and donor and the rules are different. Um Depending on which system I’m using. Um You probably are not giving your supporters the seamless experience that all of this stuff that we say we have to have inside our organizations to engage our supporters effectively. Um You’re failing on that promise, you know, you’re paying a lot for something that feels clunky, frustrating lots of manual workarounds. So

[00:11:00.80] spk_1:
a solution is the technology governance can be who should be a part of our T G.

[00:11:32.53] spk_2:
The T G G is an interesting little animal because when you think about another meeting, like I have to be part of another group, I have to go to another meeting. It pre fatigues most of us, right? Like I’m not, not into that so much. But if you pick the main system owners or users, like the person who’s your database manager on the fundraising, somebody from marketing and communications, somebody from finance, you made the point

[00:11:36.59] spk_1:
earlier. This does not have to be a technology

[00:11:38.57] spk_2:
person. No, no, no, no.

[00:11:41.38] spk_1:
You may not even have a tech

[00:11:42.35] spk_2:
person. You probably don’t.

[00:11:44.44] spk_1:
Your, your I T support may be

[00:11:46.35] spk_2:
outsourced or your kid. You know, in some cases, depending on the organization. No, we’re not, we’re not, we’re not past

[00:11:57.47] spk_1:
the server in the dripping, dripping mop closet. Let’s hope.

[00:13:45.46] spk_2:
Let’s hope everybody’s in the cloud and they’re paying attention to security and password management and all that good stuff. But the technology Governance group meets once a month for four months, for an hour a month. And you’ve got to appoint somebody to come up with an agenda so that it’s a real meeting. It’s not just everybody sitting and complaint. I hate this. I’ve asked six times to get a new whatever, what, that’s not the point of this meeting point of this meeting is to talk about what you’re doing in your systems, maybe make some business process decisions. I’m working with an organization right now who is starting to make plans to text their supporters. They’ve got the platform in place, but they don’t have any business rules around it. So the data guy, the communications person and um a couple of other folks are part of this T G G and we just had our April meeting a couple days ago on Monday and the everybody shared updates for a few minutes, got the mic for about 10 minutes and then we spent the second half an hour hammering out what the communication policy was going to be for collecting text cell phone numbers and using them across the organization. So they were really able to say we want to provide the same experience to everybody, whether they’re filling out a survey or making a donation. And here’s how we’re going to set up our system so that they align with our business rules. They had never had a policy before. Never thought about texting organizations. So rather than having that happen in a silo just in communications, you need your data person who is going to make the change that says, you know, here’s my cell phone number and the check box that says, yep, I’m opting in you. Folks can text me that would have probably taken six months to pull off if we had not sat down and talked about it for 25 minutes. As a group,

[00:14:57.76] spk_0:
it’s time for a break. Stop the drop with donor box, the online donation platform. How many possible donors drop off before they finish making the donation on your website? That is tragic. You can stop the drop and break that cycle with donor boxes. Ultimate donation form added to your website in minutes. It’s freaking easy. So easy. When you stop to drop the possible donors become donors four times faster. Checkout easy payment processing, no setup fees, no monthly fees, no contract. You’ll be joining over 40,000 U S nonprofits donor box helping you help others donor box dot org. Now back to technology governance.

[00:15:02.65] spk_1:
Why did you say the group only needs for

[00:15:53.22] spk_2:
four months? Because when you’re first starting out, it feels like a big deal to say we’re going to be every month for the rest of our lives as long as we’re working here. So we’re taking a four month increments, four month increments. Um The other thing is these groups take a little while to gel. Right. You’ve never really talked about this stuff is a group before. Um, what, what gets raised in here, what needs to be, uh, turned into its own initiative with an owner like, hey, Kathy, you’re going to go work with whoever on this texting thing and then report back to the group next month. Um We’ve even had conversations like, um, what do we need from each other on these, um, codependent technology initiative improvements, problem solving stuff like that.

[00:15:56.26] spk_1:
All right, this is all fodder for the agenda, an agenda

[00:16:26.82] spk_2:
has to be an agenda. And you know, my, if I’m running the group for an organization, which I do often in these first couple of months to just like set it up and run it, facilitate these meetings, then I just hand it over to somebody at the organization and they keep running it. Um Do you know the four stages of group dynamics? Four stages of group formation? Okay. So you have forming storming, which is where the second meeting happens and people are like, you’re not letting me do what I wanted to. Then there’s nor ming where you start to settle in. That’s month three performing, you hit at month four where people know what to expect at these meetings. You often

[00:16:46.14] spk_1:
you’ve governed

[00:16:46.93] spk_2:
your technology, you are all done, then

[00:16:49.81] spk_1:
you have to start again with form.

[00:17:49.03] spk_2:
Every time somebody new hits the team, you go through these stages. But that’s another, another interview for something else. But the first four months you’re sort of figuring it out. Your jelling, you’re developing your group rules and the things that are important enough to talk about at these meetings and then send notes around. Somebody takes notes or you record the meeting and send the recordings around and everybody’s responsible for following up on their stuff. So at the end of every T G G meeting, you’ve got a little five minutes where you say, all right, here’s the action items coming out of this meeting. You’re going to do that, you volunteered to do this, you two are going to work together on that. And then the life of the meeting extends outside the meeting and between meetings and kind of gets people rowing the boat in the same direction instead of in a circle, which is what it feels like sometimes,

[00:17:52.03] spk_1:
right? So there’s work between the meetings collaborative like you expect of your committee’s on your, on your board should be right. You know, hopefully your board is not only working one quarter, two hours every quarter. That’s a, that’s a,

[00:18:07.17] spk_2:
that is a low performing board,

[00:18:10.24] spk_1:
right? Yes, that’s exactly responsibility, accountability, of course.

[00:18:16.58] spk_2:
And you’re working together in the in service of helping this technology meet your mission instead of individual teams, you know, kind of elbowing each other out of the way to

[00:18:32.69] spk_1:
anything else about our technology governance group. We

[00:18:35.64] spk_2:
should know it should go longer than four months. So I’ll just say most of the time you

[00:18:40.45] spk_1:
keep wrap it up,

[00:18:47.86] spk_2:
the other benefit to these meetings can be helping you with at budget time because tech is often spread, tech funding is often spread between different business units or cost centers at an organization. And so coming together and talking about what’s going to be in my budget, what’s going to be in your budget. So we need to work on something that benefits both of us whose budget should that go in? Um helps you earmark those funds for when it’s time to work on those projects.

[00:19:16.50] spk_1:
Let’s let’s move to um problem solving methods for for common pain points. So we identified the pain points that they’re more. Don’t hold out on non pop radio listeners like redundancy turnover,

[00:19:32.59] spk_2:
frustration out of control

[00:19:40.71] spk_1:
budget doing the same thing. What is there more? I think

[00:19:46.55] spk_2:
the other one that I think is poor business relationships with your technology vendors. Very

[00:19:53.70] spk_1:
good one. Alright. Frustration talking to

[00:19:57.99] spk_2:
them. Yeah. Not getting good service or not getting your solutions. Would

[00:20:22.51] spk_1:
we, we would probably default and say it’s the vendors problem. It could be, it could be our own, could be our own internal problems because we’re, we’re feeding the vendor six times a day with disparate number one priorities. No hr who told you fundraising was number one hr is number one and who told you that it was accounts payable that person is whacked. It’s hr, so you’re on the phone with me now.

[00:20:29.58] spk_2:
I’m number one now. Yeah. Um, the other way to think about that problem may not be the vendors problem and it might not even be a technology problem. Tony

[00:20:40.77] spk_1:
person. Right.

[00:21:17.03] spk_2:
Because we blame the technology 1st, 2nd and 3rd, the stupid XXX, whatever it is because we don’t have to interact with that thing. I don’t have to go to lunch with that CRM or whatever it happens to be its inanimate. So it’s easy to complain about the whatever but often you peel that back and that’s not the root cause. So if you fix what you think the technology problem is, you have the same problem later and it starts to become this unsolvable problem at your organization. You don’t have the app to take another run at it after the first couple and you just start living with it, which is never a good idea because it’s always going to get accommodation

[00:21:27.35] spk_1:
in your personal life in your technology boundaries, accommodation. These things are

[00:21:32.99] spk_2:
important, the right root cause. That’s right. Alright. So

[00:21:36.12] spk_1:
some, some you have some methods.

[00:21:44.30] spk_2:
Yeah. Yeah. So one of them is the five wise, have you heard

[00:21:46.86] spk_1:
the four stages of group dynamics? I know the seven colors of the rainbow, yellow, green, blue indigo

[00:21:55.21] spk_2:
violet.

[00:22:11.71] spk_1:
Those five crime families in New York? Bonanno, Colombo, Gambino Genovese crime families in New York. I do not know the wise. Okay.

[00:22:15.85] spk_2:
So the five wise are someone makes a statement like a problem.

[00:22:20.73] spk_1:
The three Wise Men Balthazar Melchior and the other

[00:22:25.68] spk_2:
one. Oh, gold Frankincense. And, but I don’t know who brought what

[00:22:34.06] spk_1:
Balthazar Melchior. See, I don’t even know the three Wise Men. Ebenezer. No, that’s, no, that’s the, that’s the Christmas story. Caspar Caspar Balthazar and Melchior. I think I’m pretty sure that

[00:22:46.85] spk_2:
I

[00:22:56.27] spk_1:
interrupted, rudely interrupt the guests. I know something else. I think of something else. I know so few things that I know. I have to shout them out whenever I get an opportunity. Alright, I’m sorry, the five wives,

[00:24:06.79] spk_2:
five wives of root problem identification. So somebody might say this email tool is terrible. I can’t segment my audiences like I can’t send to donors and non donors. It’s a pain in the neck to do that. Can’t do with stupid email tool. Why can’t you do? That is the first way and someone might answer that question. Well, um I can’t do it because we’re collect, we’re getting data from other places and putting it into the email tool. And so we’re not collecting that information over here. All right. So it’s not an email problem. It’s actually a data problem and it’s tagging, right? Like donor Tony’s donor, Maureen’s a non donor. There’s no easy way in your database to pull those audiences out and make sure that they get the right message. So that is probably a business process problem, not necessarily a technology problem. So that was a simple little example of one of those problem solving techniques

[00:24:09.43] spk_1:
that why was, why can’t you, why can’t we do this?

[00:24:12.69] spk_2:
Why can’t we do this? Well, I don’t get the data in the way that I need. Why don’t you get the data in the way that you need because we collected over here. Well, why do you collected over there? So yes, five wise people get annoyed. First two wives are easy as you go through wise 34 and five people get annoyed because they really have to dig deep and think about it.

[00:24:38.20] spk_1:
Okay. We can have the we could have the play on the five wise, the wise, wise, wise, wise, wise, wise, wise guys or the five wise

[00:24:53.50] spk_2:
problem solving. Another problem solving method

[00:24:57.75] spk_1:
method. You’re asking these questions internally, you’re asking these five questions. Okay.

[00:25:22.96] spk_2:
And literally sitting with it um in your technology governance, in your governance group or in a little spin off. Yeah, everybody’s got technology gripes and pain points and wishes that it was different or easier. They want the easy just today the Q R code to open my hotel room door did not work on my phone. So yes, I am right there with

[00:25:30.96] spk_1:
you. I still go for the, I still go for the cards. You so you go this

[00:25:35.82] spk_2:
time. But guess what? I had to go to the desk and get a card.

[00:25:40.32] spk_1:
I haven’t, I’ve never, I’ve never tried opening the, just give me a card, boarding

[00:25:46.67] spk_2:
passes, print the boarding pass and have it on my phone

[00:25:50.90] spk_1:
for the,

[00:25:52.50] spk_2:
everybody’s got their lines that they

[00:25:55.11] spk_1:
won’t do the hotel room because I don’t want to be tired

[00:25:57.83] spk_2:
and not able to get in and, you

[00:26:10.63] spk_1:
know, looking for my nap and then I gotta go downstairs again. Talk about first world problems. I have to go down to the lobby again. You’re more trusting on the hotel front.

[00:26:15.34] spk_2:
This time. I tried it. That would be the Hyatt Regency across.

[00:26:26.05] spk_1:
Can you stay on track?

[00:26:32.03] spk_2:
Apparently not. Apparently not. So that was one problem solving technique. What’s the problem and why are we having the problem so that you’re fixing the right thing,

[00:26:43.75] spk_1:
fixing the right past

[00:27:57.30] spk_2:
that one. So another um another common situation is uh people get frustrated because the technology doesn’t work. I don’t know how to do this or it’s too hard to do a thing. Um That’s usually a training issue, right? Like someone got hired, they gotta log in and thoughts and prayers. Here you go, you’re young, you can figure it out. You gotta people. If you take nothing away from this interview, please, please, please budget for training and support. Um Everybody needs it. Some of us are more naturally agile when it comes to technology. Others, not so much but the way you get a return on your investment of the state stuff that you’re buying and using is if your team is empowered to use it well, efficiently, effectively. And when we figure it out on our own, we usually don’t figure out the easy and effective way to do it. We sort of stab our way through it. I made it work that’s fine. So empowering your staff to be competent and confident in the systems that they’re using to do their jobs. Um, staff morale goes up. You’re spending way less time fighting the technology and more time using it. So, a common problem is this thing isn’t working for me or I can’t figure it out. So pay for some training. That would be. So,

[00:28:12.46] spk_1:
which is, which, why, why is this? Why can’t I do this?

[00:28:17.40] spk_2:
Why does, why is this so

[00:28:19.15] spk_1:
hard? Why doesn’t it work? Why doesn’t this work for me?

[00:30:06.95] spk_0:
It’s time for Tony’s take two non profit radio is listed on nonprofit news feeds. List of the great non profit podcasts. And if they numbered the list, we’d be number one, we’re top of their list. In fact, I believe their list is misnamed. It ought to be the great non profit podcast plus a couple others, but very great. Right. We’re at the top of the list. Very thankful, very grateful to non profit news feed. Thank you very much for the recognition and I would be remiss if I didn’t. Thank you, our listeners. You help us get the recognition. You keep the show. You know, it’s not always. Number one nonprofit radio has been on lots of lists where it’s like number 14 out of 12. Um, you know, we’ve been down, we’ve been down on some list but doesn’t matter, you know, the ranking doesn’t really matter. Although if I was gonna do one I would do it. Alphabetical. I think I’d do alphabetical with nonprofit radio at the top. Of course, because the alphabet is going to start with the end and then, and then it reverts back to a etcetera. The boring way. That would be, that would be my list. So thankful to non profit news feed and I’m thankful to you are dear listeners. Thank you very much for helping us get the recognition. It really is gratifying to be on any list of non profit podcasts. But, but I mean, if you could be at the top of the great one, you know, you may as well and that is Tony’s take two. We’ve got boo koo, but loads more time for technology governance with the very un boring Maureen will be off

[00:31:37.87] spk_2:
another problem solving technique that is uh really easy is to map your ecosystem, like use power point or video or Miro or some white boarding tool. Zoom has a white board tool and literally make bubbles of all of the things that you have make a circle. My website is purple over here and my day databases over there and lay out what you have. Like most of the time, collectively, nobody really knows all the stuff that you have and the stuff that you’re using and what’s working and what isn’t. So figuring that piece out and having that map, that changes when we swap email tools or we change our volunteer system or a finance system, um, making that map be accurate will also help you pinpoint where the problems are really coming from. Uh blah, blah, blah. I hate our website but whatever, like it doesn’t work on a phone. Maybe that’s a problem who should be working together on fixing that problem? Is it really a problem or is it just a problem for somebody who’s using a Windows phone, you know, from 2015. So taking the time to have those collaborative conversations is also really, really helpful once you’ve got it all written out. Um And you can then, you know, we do have six email tools or three people have canvas accounts. We should probably consolidate that stuff. And

[00:31:56.98] spk_1:
what is this uh consolidated under what? Why, which, what, why are we

[00:32:06.51] spk_2:
talking? It’s uh it’s have as small a footprint as you can get away with. Just, just because you think you need something, people can sneak tools in without telling anybody, you know, like somebody inside a fundraising team goes a little rogue and says we’re going to add something new. Nobody else knows about it and you’re not getting the benefit of having that thing used to its fullest extent because tech is expensive and it’s kind of frustrating.

[00:32:31.66] spk_1:
Doesn’t have to start with. No,

[00:32:35.14] spk_2:
no. The five wise we was one of the problem solving techniques. The five wise is one of the problems solving

[00:32:39.88] spk_1:
techniques. So aren’t we on the five wise, we only did two of

[00:33:04.70] spk_2:
the five wise is a thing all unto itself. So the five wise helps you identify the root cause of your problems so you can fix the right thing. These are other symptoms with problem solving ideas for teams to use. If they’ve got people who say this is too hard for me to use. Why is this so hard? Not everything maps back to why you need to Google the five wise after this.

[00:33:15.49] spk_1:
In other words, you don’t

[00:33:16.50] spk_2:
know. I do know, but I think we’ve mixed them up a little bit. We’ve mixed our metaphor slightly.

[00:33:23.11] spk_1:
I guess you want to blame it on a lackluster host. No,

[00:33:25.66] spk_2:
never, never the

[00:33:27.58] spk_1:
most lust, lust, lust,

[00:33:32.81] spk_2:
lust.

[00:33:34.67] spk_1:
Alright. So, alright, so don’t look for everything to start with A Y like I was all right. We are on number four though now. So we finished mapping, we finished mapping looking where we have redundancies. People snuck shit in should not have your technology governance group advised you not to do that correct. We told you now your rogue rogue and do we boot you off or do we try to keep you in the group and remediate, you always

[00:34:04.63] spk_2:
get you to come along to the group dynamics. Please stick around and be one of us.

[00:34:14.92] spk_1:
Yeah, you’re better off on the inside.

[00:34:34.95] spk_2:
That’s right. That’s right. And then the last technique for the second to last is what I call a no filter, pain point activity. And what that means is you grab your team and if it’s virtual there, if you come to the session tomorrow, I do have in the collaborative document because it’s not possible. So if you want to make an Excel spreadsheet, it’s a no filter pain point worksheet

[00:34:55.07] spk_1:
and not on the website. It is.

[00:34:59.04] spk_2:
Yes, it’s under free resources.

[00:35:00.91] spk_1:
So, what’s your site?

[00:35:03.22] spk_2:
Meet Maureen dot com? Oh,

[00:35:05.17] spk_1:
that’s clever. I liked it from last year. I remember that Maureen dot com. Click free resources,

[00:35:10.61] spk_2:
resources in the top navigation. You will find this worksheet

[00:35:14.04] spk_1:
there. Okay. Now, let us know what the worksheet

[00:35:17.06] spk_2:
is.

[00:35:18.89] spk_1:
So much stuff, so

[00:35:35.09] spk_2:
much stuff. Um The no filter pain point worksheet is a place. It’s sort of a meeting and a worksheet all in one. So you grab your team and you dedicate 90 minutes and everybody is allowed and encouraged to list everything about your technology that bugs them

[00:35:44.20] spk_1:
even

[00:36:39.15] spk_2:
if, even if they’ve mentioned it 60 times and nobody did a damn thing about it. Even if um it’s from a new staff person who has fresh eyes and is looking at some wacky thing that you’re doing to work around some technology problem. And they’re like, is there a better way to do this? So everybody gets a chance to list out their stuff and then you organize it into those four P categories. Is this a plan problem? Is it a platform problem? A people problem or a business process problem? So that also helps you get to the root cause these meetings are super helpful. They’re cathartic number one, because people can unburden themselves of like I really hate this X Y or Z thing. You also start to talk about things like maybe tony hates this product, but Amy loves it. You might want to match up Amy and tony so that Amy can help tony figure out, you know, to get beyond the things that are frustrating or friction for you. So it’s a good way to kind of get allies there. If everybody’s like we hate this thing, then you can make plans to replace

[00:37:03.24] spk_1:
it from the bottom up. Yeah. Uh I’m thinking of a verb for change. We can advocate for change. Advocate. Advocate is the noun advocated. So from the bottom up to try to

[00:37:22.15] spk_2:
make change, that’s right because often the leaders that your organization to have allies. Yeah, often the leaders of your organization sort of, you know, that things are a problem but they don’t use these systems every day or even often at all. They’ve got an assistant who’s pulling reports or, you know, giving them the information,

[00:37:32.31] spk_1:
especially if it’s the God fly, the perennial tech whiner coming, you know, that that person needs, needs allies.

[00:38:20.97] spk_2:
They do and they need to feel heard and then you sort of prioritize stuff, you’re not going to get to all of it. Another way to break the pain point. Worksheet results down is what are issues, things that are problems and what our opportunities we want to grow. Our monthly giving program. Our current system makes us manually run our supporter credit cards every single month. I don’t want to grow my monthly giving program. If it means I’m going to have to hire somebody else to start to run these credit cards. So what are we going to do about our technology so that we can grow without it turning into a problem for our team? Yeah, issues and opportunities another way and you just pick, you keep that list as a parking lot. You can add new stuff as it bubbles up or appears and you just methodically work your way through those things. Instead of being an individual experience of a problem, you’ve kind of made it an organizational list of things that need to be addressed.

[00:38:44.22] spk_1:
I always bristled at the parking lot metaphor. It’s childish. It’s Q, it’s Q, it’s a, it’s a, it’s a wait list. You know, we’re gonna put your, your ideas. Plus I heard it said one

[00:38:58.84] spk_0:
since

[00:39:23.47] spk_1:
some training, I think I may have to go back to when I, when I was a miserable employee years ago, decades ago. And yeah, we were in some training and some, some facilitated. Well, that’s not quite on point. Let’s put your very good idea into the parking lot. And he was talking, he was talking to, what was a guy talking to a woman? Like he should have patted her on the head. It was so condescending, so condescending. He may as well have patted her on the head. I didn’t mean he should have, he may as well have just. The parking lot

[00:39:36.17] spk_2:
was supposed

[00:39:36.46] spk_1:
to be so proud. Look. I made the sticky, that’s over the window that nobody can see because the light’s coming

[00:39:43.46] spk_2:
through.

[00:39:44.00] spk_1:
Yeah. In the closet. I made the sticky on the back side of the closet door. My parking lot,

[00:39:49.78] spk_2:
a lower priority list.

[00:39:52.88] spk_1:
It’s just, it’s a, it’s a list of priorities.

[00:39:55.70] spk_2:
I’m gonna start using Q or waitlist. You’ve changed my mind.

[00:40:01.70] spk_1:
I don’t know. It seems like a very pedantic

[00:40:04.57] spk_2:
metaphor. It is. People get it. But I understand that the connotation that it can have. I told you,

[00:40:11.87] spk_1:
I don’t know. It seems like a child’s game.

[00:40:16.55] spk_2:
All right, you’re playing candy land and you kind of get stuck in the parking,

[00:40:25.53] spk_1:
remember? Candy land? Yeah. Right. Exactly. A parking lot. Or, or, or, yeah, or, or it’s like being in jail for monopoly

[00:40:28.84] spk_2:
or in the sand trap. If you

[00:40:30.42] spk_1:
golf golfer. Let’s not go too far with sports,

[00:40:34.20] spk_2:
not my

[00:40:35.19] spk_1:
metaphors sand trap is golf. Golf, golf, golf. I think we have one more. Y one more of the five wise which don’t all start with a

[00:40:46.46] spk_2:
complete misnomer. Yeah, I

[00:40:48.89] spk_1:
wouldn’t put it in the parking lot, but it’s just misnamed. We have one more,

[00:40:54.76] spk_2:
one more which is decided you’re going to focus on internal problems or external technology problems, things that affect your supporters, your subscribers, your volunteers, your donors or your internal process

[00:41:08.38] spk_1:
accounts, payable sources.

[00:41:23.99] spk_2:
Right. Right. So that’s the other way to kind of tackle these things. Usually, it’s a little of both. It’s a little of both. It’s very tempting to do either or it’s very tempting to be internally focused or completely externally focused at the expense of

[00:41:29.03] spk_1:
your ignore us. We need to help our supporters, our fundraisers, fundraisers are volunteers or donors

[00:41:37.77] spk_2:
on my back

[00:41:40.85] spk_1:
in the parking lot and

[00:42:22.45] spk_2:
we don’t want to lose value people. So a bit of a balance is good and, and take small bites. That would be my, my other guidance here is when you’ve laid it all out there and you can see it like in all its gross glory, all the things that you’re struggling with, you can either feel very pre fatigued like we’re never going to work our way through these things or we got to do them all. Like right now now that we know what they are just take small bites, be realistic. Figure out how much time your tech governance team, your T G G can spend on this stuff. Be realistic in your deadlines and expectations if people can go fast and it’s possible to go fast, let them but always be honest with yourselves about what you have capacity to do. Otherwise this will just be another governance group or another initiative that is too frustrating and

[00:42:37.86] spk_1:
nothing ever happens. Talk about another example, very big on preventing fatigue. I am not keeping track.

[00:43:50.14] spk_2:
Yeah, I think our nonprofits and generally people are at capacity, kind of tired running on fumes. A lot asked to do more with less um in our small to mid sized nonprofits, that’s really hard. You know, like they don’t have the budgetary shock absorbers that a larger organization might have to toss another consultant added or by another thing or throw money at a problem to fix it. Small to midsize guys got to be scrappy. They’re all spread really thin. Um And so I just want to make sure that people are not using magical thinking when they’re trying to fix their technology. It’s very tempting to do that. Um If you think you’ve got a technology problem and your first impulse is to switch it with something else, stop do those five wise, find out what’s really going on because you might move, spent all that time and money moving into something new and you still have the same problem and that’s, that’s not great. That’s not a good thing. I like people to be happy and optimistic at work. I feel like they’re set up for success to the best extent possible and that they are going to work together to solve problems. That’s kind of what nonprofits do and

[00:44:12.91] spk_1:
technology’s role is to support that,

[00:44:16.23] spk_2:
make it easier.

[00:44:17.24] spk_1:
Yet another support.

[00:44:19.63] spk_2:
Often it is something that is, does not provide good feelings. Yeah. Like my key card, like my Q R code this morning.

[00:44:47.86] spk_1:
Exactly. Right. I would love to get your, we only have a couple minutes left. I’m going to ask you to be brief on this. I can Artificial intelligence, chatbots, chat, GPT there. The, here they, I see. I’m not, I’m not stopping it, but I, I see more, I see more risks than then benefits. I don’t know, maybe it’s maybe at 61. This is the technology that I’m going to be the Luddite around. But what’s your, what’s your take? I don’t, I don’t want to prejudice your, your strong, strong willed person. You’re not gonna be prejudiced by my opinion.

[00:45:11.86] spk_2:
Um, I think that it’s not going away. So I think, uh, people like us who are, you know, hesitant, worried, um, concerned should get to know it and then decide for ourselves where it is beneficial and where it is not in our own work lives, our personal lives because it’s common is here now.

[00:45:27.94] spk_1:
Talking about boundaries, then get acquainted with it. Yeah,

[00:45:34.17] spk_2:
I know thy enemy, you know what I mean? Or know what I’m worried from the outside. Let me find out what I really should be worried about by playing with this thing or interacting with it. Um, I can tell you that I’ve got some organizations who are using it to write fundraising appeals in 30 seconds.

[00:45:50.44] spk_1:
Right. They use it as the first draft and then they modify, they put their own tone to

[00:45:56.35] spk_2:
it. So it can’t, you know, we’ve all been faced with that blank piece of paper. I know

[00:46:24.34] spk_1:
my concern is what my concern is. That that’s the most creative thing that a fundraiser that you take your example can do is be faced with a blank screen and create from that blankness versus seeding that most creative task to the artificial intelligence and then you reducing yourself to copy

[00:46:25.04] spk_2:
editor,

[00:46:53.10] spk_1:
copy editor. I’m not diminishing copy editors in the audience, the two or three of you and that may be listening, but it’s not as creative a task as working from, from nothing and creating something. So and then so that leads to my concern. Do we become less creative? Does that mean we become dumber on an individual level? On a community level? On a on a world level? Is it a dumbing down because it’s a seeding of the most creative work that I think we can produce?

[00:47:22.12] spk_2:
I hear you and I do agree with you to a certain extent. I also think if your Annual Giving manager is spending hours writing appeals when they could be stewarding a major donor prospect or doing some relationship building or mentoring a new staff person. If they don’t have time to do all that stuff, it might make sense to offload some things. Not that you’re going to use them just as is, but give yourself a bit of a starting point

[00:47:33.92] spk_1:
or use them sometimes

[00:47:36.01] spk_2:
but not rely on them all the time. Right?

[00:47:40.30] spk_1:
We’ve got to leave it there. Maureen. Brilliant.

[00:47:42.05] spk_2:
Always wonderful

[00:47:46.01] spk_1:
in Portland, Oregon

[00:47:50.01] spk_2:
24 24. Tony. Thank you.

[00:48:07.59] spk_1:
My pleasure, Maureen will be off non profit digital strategist and technology coach at the nonprofit Accidental Techie with Maureen will be off meet Maureen dot com. So smart. I love that meet Maureen dot com. Thank you for, thank, thank you,

[00:48:11.05] spk_2:
my

[00:48:11.57] spk_1:
pleasure to and thank you for being with our coverage of 23 N T C the nonprofit technology conference 2023 where we are sponsored by Heller consulting technology strategy and implementation for nonprofits

[00:49:17.65] spk_0:
next week. Best and worst of non profit newsletters and digital self care and healing. If you missed any part of this week’s show, you know what I beseech, you find it at tony-martignetti dot com. We’re sponsored by Donor Box with intuitive fundraising software from donor box. Your donors give four times faster helping you help others donor box dot org. Our creative producer is Claire Meyerhoff. The shows social media is by Susan Chavez Marc Silverman is our web guy and this music is by Scott Stein. Thank you for that affirmation. Scotty B with me next week for nonprofit radio, big nonprofit ideas for the other 95% go out and be great.