More members won't fix an engagement problem

The instinct when a programme isn't working is to add people to it. More members, more ambassadors, more partners. It feels like progress because the number goes up.

It almost never works, and there's a good line for why. Growth makes whatever is already there louder.

That's Brianna Leever's phrasing, from a piece about paid communities. It's the most useful sentence I've read about this work in a while, and it holds for developer programmes too.

If people join and go quiet, more people means more quiet. If your ambassadors produce content nobody watches past the first minute, more ambassadors means more of that. You have not fixed anything. You've bought a bigger version of the thing that wasn't working.

What actually produced the 4x

At Firecrawl, creator-attributed referrals went from 1.7K to 7.2K weekly.

That happened on ten creators. Not forty.

I've written up how the tiers worked and how they were paid, but the part that matters here is what the growth was made of. It was better content, by people who understood what they were building with, because they had been picked by hand and briefed properly.

Signing thirty more creators would have been faster, more impressive in a weekly update, and worse. The referral numbers would have flattened — same total volume, spread thinner, with a brief nobody had time to enforce. And I'd have spent every week on intake instead of on the content.

The honest version: the ceiling on that programme was never the number of creators. It was how much attention I could give each one.

The number that hides this

Here's why teams get it wrong. Member count is the easiest number to move and the easiest to report.

You can add fifty people to a programme in a fortnight. You cannot make fifty people care in a fortnight. So when someone asks how it's going, the honest answer takes a paragraph. The flattering answer takes a number, and the number is always there.

Then it becomes the target. That's the whole failure. I've argued elsewhere that activity counts don't survive a budget review. This is the same problem, one step earlier. They don't survive contact with reality either. They just take longer to fall over.

Check these before you add anyone

That last question is the one worth sitting with. When I asked it about the ambassador programme, the answer was "the brief". I was the only person enforcing content quality, and I was already at capacity at ten. That told me the next investment wasn't recruitment, it was making the brief good enough to work without me.

Which is exactly what I got wrong at the time. I fixed the brief after the first cohort turned in weak drafts. I should have written it properly before recruiting anyone.

The exception

There is one, and it's real. Some things genuinely need a minimum number of people before they work at all.

A forum with four people in it isn't a small community, it's an empty room, and no amount of engagement work fixes that. Same with anything that depends on members answering each other. Below a certain size the thing you built cannot do its job.

So: if you're below the floor where the format works, grow. Above it, growth is not your problem and adding people will hide the one you have.

The way to tell them apart is straightforward. If a handful of members are getting real value and the rest are quiet, you have a quality problem and growth will make it louder. If nobody is getting value because there's nobody to get it from, you have a scale problem and you should recruit.

Most teams asking how to grow are in the first case and hoping they're in the second.