Rethinking Operational Excellence in Associations and Nonprofits

Associations and nonprofits have a tricky job.

You’re balancing mission-driven work with the day-to-day reality of running an efficient, sustainable organization.

To remain competitive and viable, associations must compete with leaner, better funded for-profits and even with crowd-sourced, extremely nimble content and product creators.

As member expectations rise (and transformative technology like AI keeps accelerating), “doing good work” isn’t enough—you also need operations, technology, and strategy to line up.

If you’re looking for a practical place to start, we keep coming back to three focus areas: 

• Business process reengineering (fix the work before you buy more tools)
• Project management rigor (turn strategy into shipped outcomes)
• A smart tech ecosystem (core platform + best-of-breed add-ons)

1. Business Process Reengineering: Start with the Work (Not the Tools)

A common mistake I see: trying to modernize by layering new technology on top of old, messy processes.

All that really does is digitize the inefficiency—so the same problems move faster (and cost more).

Business process reengineering (BPR) flips the order. You start by asking: If we were building this process today, from scratch, what would it look like?

For associations and nonprofits, that can show up in places like:

• Identifying disparities between goals and delivery
  • Example: Your goal is to introduce a new, timely product that answers an imminent need, but you use the same product development process you’ve used for years. It ends up taking months just to gain agreement from the working group you had to spin up based on historical practices. The working groups morphs the concept so that the product takes almost a year to market and will be so expansive and difficult to create that it will be another five years before you can revise it based on these pressing, urgent needs.)
  • Problem: When we use the same complex processes that got us where we are today, we are more likely to require complex business rules, excruciating pricing models, and workflows that would make the time travel seem trivial Drop back and simplify.

Occam’s Razor can be your guide in solving the “how” as well as the “why”. Seek out “explanations constructed with the smallest possible set of elements.”

• Finding the gaps where workarounds or manual work takes over
  • Example: Your users don’t trust their systems or data, so they use spreadsheets to reconcile reports, copy/paste between systems, and use “tribal knowledge” steps that only one person knows how to do.
• Simplifying bloated business rules and product offerings that no longer serve you
  • Example: Retiring edge-case policies, consolidating overlapping membership types, and reducing exceptions so the process is easier to explain, automate, and support.

The point isn’t small tweaks. It’s making the work materially easier for your team—and smoother for your members.

When you map the current workflow, spot the handoffs and rework, and redesign around the outcome you want, you cut friction fast. This helps you to avoid costly customizations that ultimately lead to system decay.

2. Project Management Rigor: Turning Strategy into Reality

Great ideas are everywhere. Follow-through is rarer.

Most associations are juggling a lot at once—platform implementations, membership campaigns, credentialing programs, advocacy work—often without a consistent way to plan, prioritize, and deliver.

A few simple project management habits can make a big difference:

• Improve cross-functional collaboration
  • If you find that only one person or one department knows anything about a process, they let that be your blaring warning signal that you have a silo that is not able to capitalize on enterprise efficiencies or even cross-sell opportunities.
• Clarify roles, timelines, and deliverables
  • There is not a lot that a good RACI matrix and project plan cannot improve. Getting something out of your head and into a shared mental space is incredibly powerful.
• Reduce scope creep and budget overruns
  • This of course starts with having a thorough, well-thought-out scope and an informed budget.
• Increase transparency for leadership and stakeholders
  • Sometimes that last thing we want to do is have to entertain critics. It makes for a demoralizing experience. However, sometimes critics can also be champions when they are armed with information. When work happens in a vacuum, we are not only at risk of the “echo chamber” affect but also of missing opportunities.

Agile, Waterfall, hybrid—pick what fits. The win is consistency: clear owners, clear timelines, and a way to surface risks early. 

For some organizations, that means a lightweight PMO. For others, it’s a standard playbook and a weekly cadence that actually sticks.

When resources are tight, execution discipline becomes a real competitive advantage. Remember that great project management spans many product and project types. Whether you are integrating a technology ecosystem or implementing a new set of business processes and rules, project management rules apply.

3. Core Platforms + Specialized Tools: Build a Smart Ecosystem

Most modern associations run on a core platform—an AMS, CRM, or ERP—that holds the member record, finances, communications, and reporting together.  That’s why the strongest teams we work with take an ecosystem approach:  

That’s why the strongest teams we work with take an ecosystem approach:

• Use the core platform for foundational capabilities (member records, billing, reporting)
• Integrate best-of-breed third-party solutions for specialized needs

A few common add-ons I see in association tech stacks: 

• Learning Management Systems (LMS) for certification and education
• Event platforms for hybrid and virtual experiences
• Marketing automation tools for personalized outreach
• Community platforms for member engagement

Expressed as uncommon functional needs, that list looks something like the following:  

• Complex workflows for unique products or programs
• High-visibility, customer experience heavy interactions
• Sporadic needs that may or may not come up during the course of a year
• Products that appeal to a non-core market and are for fixed periods of time

Integration is the make-or-break detail. You want data to move cleanly across systems so you don’t end up with silos, duplicate work, and conflicting reports. However, take care to simplify processes first and create as much standardization across integration methods as possible. In fact, opt for solutions that follow standard integration protocols and then document, document, document.

When the core platform does the fundamentals and the add-ons do what they’re best at, you get more flexibility, easier scaling, and faster innovation.

Bringing It All Together

Each of these areas helps on its own.

But when you put them together, you get an operating model that’s easier to run—and easier to improve over time.

• Cleaner processes so work is simpler and outcomes are consistent
• Repeatable project delivery so priorities don’t stall out midstream
• An integrated tech ecosystem so your tools support the work (instead of getting in the way)