Ask a community team to list every program they run, and the list is usually longer than anyone expected, including the team (I’ve watched people get to the end of theirs and look a little surprised). An event series, an ambassador program, office hours, local groups, a webinar series, an advisory board and a forum can all be running at once, each one started for a good reason and few of them ever looked at together.
I wrote about why those programs pile up, and why stopping one is so hard, in Why Community Programs Are So Hard to Stop, so I won’t make that case again here. This is the working version: an audit for looking at your programs as one portfolio and deciding what to do with each of them.
What this is for
The audit helps you check whether your current set of programs is coherent, useful, sustainable and still connected to what members and the business need. It works at two levels. You score the portfolio as a whole across six dimensions, and then you use the same evidence to make a call on each individual program.
It’s built for teams that already have programs running. If you’re still deciding whether to build a community at all, the Community Readiness Assessment is the better place to start.
How to use it
Score each dimension from 1 to 4 based on what’s true today.
Fragmented or inherited.
Partially intentional.
Coherent and actively managed.
Portfolio decisions are evidence-backed and resource-aware.
Bring real evidence to the conversation: program plans, member research, participation data, business outcomes, the staffing each program actually takes, and any recent examples of a program being changed or stopped. If a dimension is hard to score because the evidence doesn’t exist, that’s useful to know too.
The audit
Strategic fit
Do programs map to clear member needs and business priorities?
Many programs exist because they’ve always existed or because someone requested them.
Most programs have goals, but portfolio-level priorities are unclear.
Major programs map to defined needs, use cases and outcomes.
Strategic fit is reviewed regularly, and weak-fit programs lose priority or stop.
Portfolio coverage
Does the set of programs cover the important needs without unnecessary duplication?
Programs cluster around similar activities while important needs go unsupported.
Gaps and overlaps are visible but not actively managed.
Programs have distinct jobs, and important member needs are reasonably covered.
The portfolio is intentionally balanced across lifecycle stages, segments and use cases where those distinctions matter.
Member value
Do programs create enough value that members would reasonably choose to participate?
Participation relies heavily on promotion, incentives or company asks.
Member value exists but is inconsistent or generic.
Major programs solve specific member needs or create valued relationships and access.
Member value is validated through repeat behavior, research or contribution without a lot of prompting.
Business value
Can the team explain what each major program contributes to the business?
Business value is mostly inferred from participation volume.
Programs have intended outcomes but weak logic connecting behavior to outcomes.
Major programs have plausible, measurable ways of influencing outcomes.
Program impact informs portfolio and investment decisions.
Operational load
Is the portfolio realistic for the team’s capacity?
The team is maintaining too many programs, reactively.
Capacity problems are known, but prioritization is weak.
Resources broadly match program commitments.
Operating effort, complexity and what else the team could be doing are explicit inputs to portfolio decisions.
Program evolution
Can programs change or end?
Once launched, programs are effectively permanent.
Programs change when something visibly fails.
Programs are reviewed against current needs and performance.
The team has an accepted practice for scaling, redesigning, consolidating, pausing or stopping programs.
Read your results
Look at the pattern as well as the scores.
Low strategic fit means the portfolio needs a strategy conversation before any optimizing.
Low portfolio coverage with high member value usually means the individual programs are good but the set is accidental. Look for duplication and for lifecycle stages no program serves.
Low operational load is usually a prioritization problem before it’s a staffing problem. More headcount can preserve a portfolio that should have been simplified.
Low program evolution is a warning sign even when everything else looks good. A portfolio that can’t stop anything will eventually become a museum of old priorities.
An example
This one’s a composite rather than any one company, but it’s a pattern I’ve seen plenty of times. A two-person community team runs a monthly customer webinar, a quarterly virtual meetup, weekly office hours, an ambassador program and a forum. The webinar and the meetup both started as ways to share product tips, and they now cover a lot of the same ground for a lot of the same people. Meanwhile, newer customers keep asking basic questions in the forum, and the team doesn’t have time to build anything for them.
Running the audit, I’d expect that team to score reasonably on member value, since people do show up and say nice things. Strategic fit and coverage would land around a 2, because two programs share a job while new customers go unsupported. Operational load would be a 1 (the team is running five programs on two people’s time, ideally while also sleeping occasionally), and program evolution would be a 1 too, since nothing has ever been stopped.
Program by program, the call might look like this: consolidate the webinar and the meetup into one series, keep the forum and the ambassador program, pause office hours for a quarter to see who misses them, and use the time that frees up to build something for newer customers. That’s two portfolio changes, which is about as many as a small team can take on at once.
What to watch for
Low participation alone isn’t enough reason to stop a program. A small program serving a strategically important audience can be worth more than a big one full of people who aren’t very invested.
A stakeholder liking a program isn’t enough reason to keep it, either. Keep it because the member and business case still holds, and be ready to explain that case.
Consolidating doesn’t have to mean one giant program. Different experiences can serve different needs and still share the same infrastructure, the same calendar or the same team.
And the audit has limits. It’ll show you where the portfolio is drifting and which programs to look at, but it won’t design the replacement for you or tell you how members will feel about a change. That part takes talking to them.
Apply the code
List every recurring community program. Include the small ones and the ones only one person remembers starting.
For each program, name its primary member need, business outcome and operating effort. Hours a month is a fine way to describe the effort.
Identify programs doing the same job.
Identify important member needs with no program supporting them.
Mark each program Keep, Improve, Scale, Consolidate, Pause or Stop.
Choose the two portfolio changes that would create the most value or free up the most capacity.
Set a date to review the portfolio again.
Checklist
Every major program has a defined job.
Member value is specific.
Business value has a plausible mechanism.
Programs don’t duplicate each other without a reason.
Important member needs aren’t being ignored because legacy programs take up the team’s capacity.
Operating effort is visible.
The team can stop things.
Portfolio decisions reflect current priorities more than history.
The audit at a glance
Strategic fit. Programs map to clear member needs and business priorities.
Portfolio coverage. Each program has a distinct job, and the important needs are covered.
Member value. People would choose to participate without much prompting.
Business value. Each major program has a plausible way of contributing to the business.
Operational load. The portfolio fits the team’s real capacity.
Program evolution. Programs can change, and they can end.
Score the portfolio, then make a call on each program, and pick the two changes that matter most.
Try this
Do only steps 1 and 2 this week: list every recurring program and, next to each one, write its member need, its business outcome and the hours a month it takes. You’ll probably find at least one row that’s hard to fill in. If any of those programs is newer and you’re still not sure it should exist, run it through the Community Readiness Assessment as if you were deciding whether to launch it today.




The concepts of "Strategic Fit" and "Member Value" really stick out for me, Josh. Understanding the goal of the community within the product strategy is key. But without consistently delivering a high level of value, members have no compelling reason to stay.
Business value is the dimension that usually stalls, because participation volume is the only number sitting there ready. One way out without new tooling: build a comparison group from members who were eligible for a program and never joined, matched on behaviour before it launched. The question stops being how many showed up and becomes what changed for the ones who did. Same move on a stop decision: set the read window before you switch anything off.