Why Shared Language is the Foundation for Audience-First Organizations

Over the past few months, I’ve noticed something interesting.

It doesn’t seem to matter where a conversation begins. Sometimes it’s about AI. Other times it’s about donor journeys, audience-first fundraising, customer data platforms, omnichannel strategy, or organizational alignment. The topics are different, but they almost always converge on the same challenge.

We assume everyone is speaking the same language.

More often than not, they aren’t.

That observation has changed the way I think about organizational alignment. For years, we’ve talked about breaking down silos, integrating systems, and creating a single view of the constituent. Those are important goals, but they all assume something that organizations rarely stop to examine.

They assume we’ve already agreed on what our words mean.

A few months ago, I wrote about the work WHYY was doing to create a shared understanding of its constituents. At the time, one of the things that impressed me most was how intentionally the organization worked to establish common definitions, shared metrics, and a shared understanding of the audience across departments. The technology mattered, but it wasn’t the story. The story was that people from different parts of the organization had begun making decisions from the same understanding of the constituent.

Since then, I’ve started seeing that same idea everywhere. The more conversations I have, the more convinced I become that many of the technology challenges nonprofits are trying to solve are actually vocabulary challenges in disguise.

We Think We’re Talking About the Same Thing

Every organization develops its own language.

We talk about engaged constituents, active donors, major gifts, members, advocates, volunteers, and lapsed supporters as though everyone shares the same definitions. Those words become part of the culture, repeated often enough that nobody thinks to question them.

Until they do.

Ask a fundraiser to describe an engaged constituent and you’ll probably hear about giving history and philanthropic commitment. Ask someone in marketing and the conversation quickly shifts to email engagement, content consumption, and digital behavior. Programs may define engagement through participation, while analytics tries to combine all of those signals into a single model.

Every answer is reasonable. Every answer reflects the priorities of the person giving it.

The problem isn’t that people disagree. The problem is that organizations often don’t realize they’re operating from different definitions in the first place.

Without intending to, fundraising builds one version of the constituent. Marketing builds another. Dashboards measure one interpretation while campaigns optimize another. Leadership believes everyone is talking about the same audience because everyone is using the same vocabulary.

They’re just attaching different meanings to the words.

Shared Language Comes Before Shared Technology

Several months ago, I wrote another article called Question Before the Dashboard. The premise was simple: organizations should agree on the questions they’re trying to answer before investing time building dashboards to answer them.

Looking back, I think shared language is the step that comes even earlier.

Before we can agree on the questions, we have to agree on the language behind the questions. Before we can measure engagement, we have to define engagement. Before we can identify major donors, we have to agree on what qualifies someone as a major donor. Before we can ask AI to identify our most valuable constituents, we have to decide what “valuable” actually means.

Technology quietly assumes we’ve already done that work.

Every CRM field, dashboard, audience segment, workflow, AI model, and automation rule is built on definitions someone had to establish. Someone decides what constitutes an active donor. Someone determines when a constituent becomes lapsed. Someone defines the engagement signals that should trigger a stewardship journey or a marketing campaign.

Technology doesn’t challenge those assumptions. It operationalizes them.

That’s why organizations can spend months implementing new technology and still struggle to create the connected constituent experiences they envisioned. The systems are integrated. The dashboards are accurate. The automations are functioning exactly as designed.

The underlying assumptions simply weren’t shared. Technology didn’t create the misalignment. It revealed it.

Categories Help Organizations. Relationships Help People.

The same pattern appears in the way nonprofits categorize constituents.

Organizations need categories because categories help organize work. They determine campaign eligibility, stewardship strategies, portfolios, reporting structures, and ownership. Donor. Volunteer. Member. Advocate. Event attendee. Major donor.

Those categories are useful, but they’re also incomplete.

Most people don’t experience your organization one category at a time. Someone may volunteer, consume your content, attend events, advocate for your mission, and make annual gifts. Every one of those interactions tells you something about the relationship, yet organizational structures often encourage departments to focus on only the portion they own.

That’s one of the ideas I explored in Your Donors Don’t Care About Your Org Chart.

Donors don’t experience fundraising, marketing, digital, and constituent services as separate functions. They experience one organization. The more I think about that article, the more I realize organizational alignment doesn’t begin with reporting structures or governance models.

It begins with a shared understanding of the constituent. Categories help organizations organize work. Shared language helps organizations understand people.

Alignment Starts with Agreement

One of the most valuable leadership exercises I’ve seen doesn’t require new software, another integration, or an AI strategy.

It starts with a conversation.

Bring together leaders from fundraising, marketing, programs, digital, analytics, and constituent services. Then ask a handful of deceptively simple questions.

What do we mean by engaged?

How do we define an active supporter?

When does someone become lapsed?

What qualifies as a major donor?

The objective isn’t to determine which department has the correct answer. It’s to discover where different interpretations have quietly developed over time and to decide, together, which definitions will guide the organization moving forward.

Those conversations don’t produce flashy demonstrations or implementation roadmaps. They rarely make conference agendas or vendor presentations.

What they do create is something much more valuable. Shared understanding.

Once that foundation exists, everything else becomes easier. Dashboards become more meaningful because everyone interprets the numbers the same way. AI becomes more useful because it’s working from shared definitions. Donor journeys become more intentional because every team is responding to the same understanding of the relationship.

Technology finally has something consistent to scale.

Looking back over the past few months, I realize these conversations have all been pointing in the same direction. Question Before the Dashboard argued that organizations should agree on the questions before building reports. The WHYY story showed the value of creating a shared understanding of the constituent. Your Donors Don’t Care About Your Org Chart explored why connected donor experiences depend on organizational alignment.

This article simply adds one more piece to that conversation.

Before you ask technology to connect your systems, make sure your people have connected their thinking. Shared dashboards don’t create shared understanding. Shared language does.

Am I speaking your language? Let’s Talk!