Leap the Nonprofit Discoverability Gap

Website projects tend to have endings.

The new site launches. The board approves the design. The agency submits its final invoice. Everyone celebrates and returns to other work.

The mission does not stop changing when the website launches.

New programs appear. Old programs close. Staff responsibilities shift. Events return. Eligibility rules change. Artists and suppliers update their information. New questions emerge from the public.

Discoverability is therefore not a project completed every five years.

It is an ongoing organizational function.

The website is one part of that function. So are staff knowledge, content workflows, data ownership, measurement, advertising, and partnerships.

Every asset needs an owner

A page without an owner will eventually become unreliable.

Ownership does not mean one employee must write, design, publish, measure, and maintain everything. It means someone is accountable for the accuracy and usefulness of the information.

For each important mission asset, the organization should know:

• Who verifies the facts?
• Who approves changes?
• Who publishes updates?
• How often should the information be reviewed?
• What happens when the program ends?
• Which public questions should the page answer?
• What action should be measured?

These responsibilities should be distributed across several people.

The person who understands the program may not know how to write for search.

The person managing the website may not understand the program.

The person running advertising may see search demand but lack authority to create new content.

The executive director may recognize the opportunity but lack time to coordinate everyone involved.

Discoverability requires cooperation because no single department owns the entire connection between public need and mission response.

• Program staff know the work.
• Communications staff translate it.
• Web systems publish it.
• Distribution channels carry it.
• Measurement shows what happened.
• Leadership decides what matters.

The operating system connects these responsibilities.

A simple operating rhythm

The system does not need to be elaborate.

A monthly review might ask:

• What new programs, resources, events, or opportunities need public pages?
• What has changed?
• Which information is outdated?
• What questions are staff answering repeatedly?
• What are people searching for?
• Which pages are helping people take action?
• Where are visitors encountering confusion?
• What should be created or improved next?

A quarterly review can examine larger patterns:

• Which parts of the mission remain poorly represented?
• Which audiences are not finding the organization?
• Which pages support several programs or channels?
• Which content should be shared with partners?
• What should be removed, consolidated, or rebuilt?

The objective is not to produce more reports.

It is to make discoverability part of ordinary operations.

Structured information

A strong operating system also separates information from the individual place where it appears.

An artist’s name, biography, medium, location, photograph, and website should not have to be re-entered for every festival page, newsletter, directory, and partner site.

The same principle applies to suppliers, programs, events, resources, locations, and volunteer opportunities.

When information is collected in a consistent structure, it can be reused.

One record can support:

• A dedicated profile
• A directory result
• An event listing
• An email feature
• A partner website
• An advertising destination
• A report

This reduces duplication and makes updates more reliable.

The organization stops creating isolated pieces of content and begins managing mission assets.

Maintenance is mission work

Maintenance is rarely inspiring.

No one launches a fundraising campaign around correcting old contact information. Boards do not applaud the removal of expired deadlines. Annual reports rarely celebrate the number of broken links repaired.

But outdated information creates real barriers.

A family arrives when a location is closed. An artist misses an application because the previous deadline remains online. A business owner contacts an employee who left six months earlier. A volunteer abandons the process because the registration form no longer works.

Accuracy is part of accessibility.

If the public cannot trust the information, the organization is not fully discoverable.

Start smaller than the mission

An operating system should not begin with an attempt to rebuild everything.

Choose one meaningful area of the mission.

Inventory it. Create or improve the necessary pages. Assign owners. Connect the pages to distribution. Measure the resulting actions. Establish a maintenance rhythm then expand.

A working system for ten programs is more valuable than an ambitious inventory of two hundred assets no one has the capacity to maintain.

Discoverability requires infrastructure, but it can be built gradually.

The more important shift is in how the organization thinks. It moves from…we need better content.

to…we need a reliable way to turn the mission into information people can find and keep that information useful.

That is an operating system.

---

Key Take Aways

Chapter 7 of Leap The Nonprofit Discoverability Gap emphasizes that discoverability is an ongoing organizational function rather than a one-time project. Key takeaways include:

• Discoverability as an Operating System: Because organizational needs and program details change over time, discoverability requires a sustainable process—an operating system—rather than a static website project that “launches” and then ends.
• Asset Ownership: Every public mission asset must have a designated owner who is accountable for its accuracy, relevance, and updates. Without clear ownership, information naturally becomes outdated and unreliable.
• Collaboration is Necessary: Discoverability requires cooperation across different roles—program staff understand the work, communications staff translate it, and web systems publish it. An operating system connects these departments.
• Standardized Rhythm: Organizations should adopt a simple operating rhythm, such as monthly or quarterly reviews, to check for outdated information, identify missing assets, review search demand, and plan improvements.
• Structured Information: To avoid repetitive work, organizations should store information in a consistent, structured format (e.g., artist profiles, supplier records, event details) so that one record can be reused across multiple pages, emails, directories, and partner sites.
• Maintenance is Mission Work: Keeping online information accurate is not just an administrative task; it is critical mission work. Outdated information creates real barriers for people seeking help, and accuracy is a form of accessibility.
• Start Small: Organizations should not attempt to fix everything at once. They should build the operating system gradually, starting with one part of the mission, establishing a rhythm, and then expanding over time.