Invisible Design: Frictionless Giving in Fundraising
play Play pause Pause
S2 E43

Invisible Design: Frictionless Giving in Fundraising

play Play pause Pause
Speaker 1:

Welcome to this edition of the Click Pledge's Fundraising Command Center podcast. Yeah. Where we talk the why, the what, and, the how in the Click and Pledge ecosystem. This is the why series and today we are tackling a really foundational design challenge. It's something that impacts, I think, every nonprofit organization that's trying to grow online.

Speaker 1:

We're calling it the invisible form. And for today's deep dive, we are going to challenge a core assumption, which is that a donor needs to spend their time telling you things you probably should already know. Our mission is to understand why the ideal donation flow has, well, zero fields.

Speaker 2:

And that idea, the zero field ideal, it might sound a little bit like science fiction, you know, some kind of wishful thinking, but it's actually the standard for modern commerce. It's what people expect now.

Speaker 1:

Right.

Speaker 2:

So if you're a nonprofit and you're still relying on complex multi page forms, you're basically subjecting your donors to what we call interrogation marketing.

Speaker 1:

Interrogation marketing, I like that.

Speaker 2:

Yeah, and we want to show you the strategic need to just eliminate every single piece of that friction, every unnecessary question. You do that by letting the technology deduce the answers.

Speaker 1:

Okay, let's unpack that. To get to that level of radical simplification, we recommend looking completely outside of the fundraising sector. We need to look at legendary design that really change what consumers expect.

Speaker 2:

I think I know where you're going with this.

Speaker 1:

And that's where we bring in Steve Jobs. Mhmm. He famously, and I love this, he viewed any physical button on a device as a failure of design.

Speaker 2:

That's absolutely right. For him, a button was it was a confession. It meant the device just wasn't smart enough to figure things out on its own.

Speaker 1:

It's asking the user for help?

Speaker 2:

Exactly. It's asking the user to make a decision to input data that the device should have just anticipated or deduced from the context. And this isn't just some fun anecdote, it's a huge shift in thinking about user experience.

Speaker 1:

Well, yeah. And if you think about the shift that philosophy created, it's just astonishing. We went from the Blackberry era right?

Speaker 2:

Oh yeah, the thumb keyboard.

Speaker 1:

40 physical keys, a complex menu, all of it demanding input from you. And we went from that to the iPhone which offered one contextual screen that wasn't just aesthetics It was literally eliminating the mental work of 40 different decisions.

Speaker 2:

It really was. The design standard went from how many features can we cram into this thing to how little do we actually need from the user to get them where they wanna go. The system deduces your intent when you check the screen instead of making you hunt for a specific button. And that level of simplicity, that expectation, it's now just baked into every modern consumer experience you have.

Speaker 1:

Except it seems for fundraising.

Speaker 2:

Often, yes. Except for the donation experience.

Speaker 1:

And that brings us right to the point. If the iPhone replaced that 40 button BlackBerry, what's the fundraising equivalent of that obsolete clunky device?

Speaker 2:

Well unfortunately I'd say most generic online donation forms are the blackberry of fundraising.

Speaker 1:

That's a great way to put it.

Speaker 2:

Non profits are just you know they're stuck in that old interrogative mindset. We are so guilty of asking for data we don't truly need and demanding answers to questions where the context, the page they're on, the device they're using it already gives us the answer.

Speaker 1:

And that's where people drop off.

Speaker 2:

It's where the most significant drop off happens especially for those spontaneous smaller GIFs.

Speaker 1:

Okay, let's detail some of those specific failure points because they're the things that are killing that momentum you mentioned.

Speaker 2:

Yeah.

Speaker 1:

When we look at the data, two habits really stand out that we recommend eliminating immediately. The first is what we call the address problem.

Speaker 2:

The address problem is just pure unnecessary friction. So think about it. A donor is on their phone, they're moved by something, they decide to make a spontaneous $25 gift, they're committed, they want to give, and then boom, they hit a wall of mandatory fields. Street address, city, state, zip code. Why is this still happening?

Speaker 2:

We really recommend against asking for the address when the user is already authenticated.

Speaker 1:

Okay. But let me play devil's advocate for a second. I know our listeners are thinking about their compliance meetings. If we stop asking for the address, are we sacrificing data we need for tax receipts or for our records, especially for, you know, larger gifts? Where do you draw that line?

Speaker 2:

That's a critical question, and it really speaks to how you segment the system. For a large gift, a gift that's tax receipt dependent, then yes, that data is absolutely necessary, and the robust long form is there for that.

Speaker 1:

Okay.

Speaker 2:

But for the vast majority of spontaneous small to mid range mobile gifts, the answer is no. Absolutely not. If the donor is using a digital wallet like Apple Pay or Google Pay, they've already verified their identity with their face or their fingerprint.

Speaker 1:

Biometrically.

Speaker 2:

Biometrically. The transaction is secure, the user is verified, and the wallet already has the billing address. So we suggest that demanding redundant manual data entry at that exact moment is actively annoying the donor. It's killing your conversion rate for data the technology already holds securely.

Speaker 1:

That makes perfect sense. You're making the technology do the work, not the donor. Okay, so the second major mistake we recommend eliminating is the intent problem.

Speaker 2:

The intent problem is just as frustrating I think. It's when we ask the donor, So, where would you like this money to go? When they've already answered that question just by being where they are.

Speaker 1:

Right, by what they clicked on.

Speaker 2:

Exactly. For example, a donor clicks a button that says sponsor a service dog for a veteran and then the form they land on is just this generic portal that asks them to reselect service dog program from a drop down list of like 10 other programs.

Speaker 1:

Oh, I've seen that so many times.

Speaker 2:

They've already told you their intent. Asking them again just slows down that emotional momentum and forces them to reconfirm something that should just be automatic.

Speaker 1:

And you said it before, momentum is everything in spontaneous giving. Yeah. So if you introduce those two friction points, an address you already have, an intent the page already defined, you're basically guaranteeing drop off.

Speaker 2:

You are.

Speaker 1:

So that brings us to the ultimate goal here. This zero field ideal. It's not a form at all, is it? It's more like a trigger for an action, a direct line from inspiration to completion.

Speaker 2:

And we get to that ideal by sticking to one golden rule of new interface design. This is the foundational philosophy we recommend. Don't ask when you can deduce.

Speaker 1:

Don't ask when you can deduce.

Speaker 2:

The system has to be smart enough. It must deduce every possible piece of intent and identity data it can from the context of the donor's environment.

Speaker 1:

So that shifts the whole focus then. It's not about optimizing a clunky form anymore. It's about creating these intelligent giving capabilities that are just everywhere.

Speaker 2:

That's the strategy we recommend to achieve it. We call it omnipresent Instead of forcing every single donor to one generic donate now page, which is just a bureaucratic bottleneck, the donation capability should be embedded, ubiquitous across your entire site.

Speaker 1:

Okay, let's get concrete. Walk us through how that deduction process would work in real scenario.

Speaker 2:

Sure, so imagine you, the donor, you're on a non profit's website, you're reading this really detailed moving story about their scholarship fund for underserved youth. You feel that pull, you feel compelled to donate right now while that emotion is high.

Speaker 1:

Okay. And the traditional mistake here, as we said, is to send me to a main donation page where I'm forced to find scholarship fund in a list of five other options and then type in all my info.

Speaker 2:

Exactly. But with ONDA present context, a payquick.ly button is already there. It's floating on the scholarship fund page itself. And when you click that button, the magic of deductions starts instantly.

Speaker 1:

So what's the first thing it deduces?

Speaker 2:

Intent. Immediately. The system knows your location, it reads the specific URL of the page you are on, and automatically tags that donation to the scholarship fund. The donor never has to type or select a single thing.

Speaker 1:

That handles the intent which is huge, but what about the other friction points? What other deductions are now standard in this zero field framework?

Speaker 2:

Well, the beauty of modern tech is that we can make several key deductions instantly just by leveraging the context of the device and the page.

Speaker 1:

Okay.

Speaker 2:

So first, we deduce the payment information. We recommend against asking for the card number, the expiration date, any of that. The digital wallet Apple Pay, Google Pay it already has it stored securely, it just links it.

Speaker 1:

Second, we're deducing the verification and address. We recommend against asking for the address manually.

Speaker 2:

Because the biometrics, right, the face ID, the fingerprint, that secures the transaction and validates the user right there on the device.

Speaker 1:

So that covers the two big problems we talked about.

Speaker 2:

And third, and this is a really powerful deduction that's often overlooked, we can deduce the suggested gift amount and frequency.

Speaker 1:

Oh, now that's interesting. How does that work?

Speaker 2:

Well, if you're a known donor, the system should recognize your device and your identity instantly. If you've historically given $100 every quarter, we suggest that the system should present the $100 recurring option as the primary one click choice.

Speaker 1:

Ah, so you're using their history as context.

Speaker 2:

The context of your past giving informs the suggested future action. It removes the need for you to type in an amount or choose a frequency. It's already done.

Speaker 1:

I find that third point really powerful. You're moving from just optimizing a checkout to proactively predicting behavior based on their own data. But what's the technical lift here? For a nonprofit to move from their current generic form to this omnipresent capability, that sounds like a big project.

Speaker 2:

It does require shift in how the back end systems talk to each other. The technology has to be integrated so that the environment, the website, the donor's wallet, their past giving records are all communicating seamlessly with the transaction portal. And that's precisely why we advocate for tools that have this level of contextual awareness built in. It allows the technology to do the heavy lifting of data collection and security in the background. The core value we provide is moving the focus away from optimizing a bureaucratic data entry process to optimizing an instantaneous emotional action.

Speaker 1:

So we're really optimizing for the mobile spontaneous, you know, time crunch donor, the real growth engine for a lot of organizations. Right. But you did mention earlier that the traditional robust forms still have a place. We're not saying get rid of them entirely for say the legacy donor who likes that detailed desktop experience.

Speaker 2:

No, absolutely not. The full spectrum of options has to exist. You have to be inclusive. For the donor who wants to sit down at their desk and meticulously enter every detail for their tax records, that traditional long form path must be available.

Speaker 1:

Good for it.

Speaker 2:

But our strategic focus for new donor acquisition for growth with that modern mobile demographic. It is entirely dependent on removing friction, making that path from inspiration to completion instantaneous. And that's where the deduction framework is just crucial.

Speaker 1:

It really changes the whole paradigm. It goes from being a mandatory bureaucratic process Mhmm. To just a quick emotional trigger. One that respects the donor's time and their motivation.

Speaker 2:

And to summarize it all, contextual giving leverages everything the donor's already doing, the page they're on, the device they're holding, their own giving history to complete the transaction seamlessly. When we stop interrogating and we start deducing, we respect the donor's spontaneous impulse. And when you do that, you see significantly higher rates conversion and completion. It just works.

Speaker 1:

So here's a provocative thought for you to mull over. Think about the longest form you currently ask a donor to fill out for a small gift. Look at every single field on that page. How many of those are truly essential, you know, required by law or finance and how many are simply a failure design questions you should have already deduced the answer to that gap. That's where your next major gain in fundraising efficiency lies.

Speaker 1:

For more information about this and all Click and Pledge products, make sure to visit clickandpledge.com and request for a one on one training or demo. Whether you are a client or curious about our platform, just ask us and we will gladly get together with you to chat. And don't forget to subscribe to this podcast to stay up to date with all the latest and greatest features of the Click and Pledge fundraising command center.