Deciding whether to build a community usually happens in a meeting where the exciting parts get most of the airtime. Customers are already asking each other for help, leadership wants retention (or product feedback, or advocacy), and somebody usually has a platform in mind. What gets skipped, pretty often in my experience, is whether the conditions are actually there for a community to work, and what to do if one of them isn’t.
I wrote about why the weakest condition decides what happens in Is Your Company Ready to Build a Community?, so I won’t make that whole case again here. This is the working version: a scored assessment you can run with your team before anyone commits to a platform, a headcount plan or a launch date.
What this is for
The point of the assessment is to turn “are we ready?” into an actual decision: build, pilot, wait, or don’t build at all.
It tests four conditions:
Member need
Business need
Value exchange
Organizational capacity, which mostly comes down to ownership
A high score means the basic conditions are strong enough to justify trying something. It doesn’t tell you how big to go, though. That’s a separate decision.
How to use it
Score each statement from 1 to 5 based on what’s true today, not what’s planned.
No evidence.
Weak or anecdotal evidence.
Some evidence, with important gaps.
Strong evidence.
Clear, repeated evidence.
Use real evidence wherever you can: how customers already behave, what the business is actually prioritizing right now, and who would really do the work. Real talk: if you score from enthusiasm inside the company, everything comes out inflated.
The assessment
Member need
People already seek peer advice, context, connection or examples around this problem.
The need recurs, rather than appearing only at launch, onboarding or a single event.
Peer interaction adds something the company can’t provide as effectively on its own.
We can identify a specific audience with this need.
We have direct evidence from customer or member behavior, beyond internal belief.
Business need
Community would support a current business priority.
The priority is big enough that leaders will keep paying attention after launch.
We can describe the behavior or signal community could plausibly influence.
Relevant leaders understand why community may help.
We can identify what the company would learn or improve if the program works.
Value exchange
Members get real value from participating.
The company gets real value without depending on extraction.
The contribution asked of members is proportionate to what they receive.
There is a credible reason for people to return.
The value exchange still makes sense if the company stops offering novelty or swag.
Organizational capacity
There is a clear program owner.
The owner has enough time and resources to steward the experience.
The owner has access to the internal teams that need community signal.
The organization is willing to respond when members surface problems.
The product and customer experience are stable enough that community isn’t being asked to compensate for basic failures.
Read your results
Score each section out of 25.
5–10: Not ready. The basic condition is missing. Solve that problem before building.
11–17: Test carefully. There’s enough signal for research or a small pilot, but not enough for a large commitment.
18–22: Ready to pilot. The underlying conditions are strong enough to test a focused community experience.
23–25: Strong foundation. The condition is well supported. Keep validating it as the program grows.
Then look at your lowest section, because that’s your constraint. Three strong sections don’t cancel out a weak value exchange or a missing owner, and adding the four scores together hides the one thing you most need to see.
An example
This one’s a composite rather than any one company’s numbers, but it’s a pattern I’ve seen many times. A founder decides the company should have a community and sets up a Discord server. Customers join, and a lot of them are really interested in talking to each other about the product. Leadership likes the idea because it could help with retention. The catch is that nobody’s job includes running it, so whoever’s keeping an eye on it is doing that in their spare time.
If that company ran the assessment, I’d expect it to score well on member need and reasonably well on business need. Value exchange would probably land somewhere in the middle, since members are getting something out of it but nobody has really thought through what the company is asking of them. Organizational capacity would land squarely in “Not ready”: no clear owner, no protected time, and no line into the teams who’d need to hear what’s coming up.
Averaged together, that looks like a company that’s more or less ready. Read by the lowest score, it’s a company that needs a real owner before it does anything else, ideally before the server gets popular enough to spiral.
What to watch for
The big one is averaging away a fatal weakness. A community with no member need won’t be rescued by executive sponsorship, however enthusiastic the sponsor is. And a community with strong member demand but no owner can turn into a group of frustrated customers the company can’t support.
The assessment has limits, too. It’ll tell you where the risk is, but it won’t pick your platform or your programming for you.
Apply the code
Score all four conditions. Do it with the people who’d actually be involved, including whoever would own it.
Identify the lowest score. That section is your constraint, whatever the other three look like.
Decide whether a small pilot can test that gap. If it can, design the pilot around it. If it can’t, fix the gap first.
Design the smallest useful pilot. One audience, one focus, and a real owner.
Define what evidence would justify expansion. Write it down before the pilot starts.
Set a date to decide. When it arrives, choose whether to scale, redesign, wait or stop.
Checklist
The member need is based on real behavior.
The business need is current and specific.
The value exchange works for both sides.
There is a real owner, with protected time.
We can run a small test before a large platform or headcount commitment.
We know what evidence would change our decision.
The assessment at a glance
Member need. People already want to learn from and connect with each other around this problem, and you can see it in their behavior.
Business need. Community supports a current priority that leaders understand and will stay focused on.
Value exchange. Members get enough to keep coming back, and the company benefits without extracting from them.
Organizational capacity. A real owner with time, resources and access to the teams who need what the community surfaces.
The lowest of the four is your constraint.
Try this
Score only the organizational capacity section for your community (or the one you’re planning), and be strict about “clear program owner” and “enough time.” If that section comes in below 18, I’d work on ownership before anything else, however strong the rest looks. And if you’re not sure community is the answer at all, I wrote about that in When Community Is the Wrong Fix.