CommunityMayNotScale. Certainly a smaller community (or "clique") has a very different feel to a larger community (or "society"), and the success of your site may be dependant on its particular size. This is especially true if you value CommunityOverContent. However, sometimes it may be better to StartAgain.
Fast growth disenfranchises longterm members, who find themselves contributing to a very different community to the one they joined. This can cause these most valuable members of the community to go elsewhere.
If the arrival rate of newcomers exceeds the ability of longstanding community members to tutor them, you can run into problems with NoRespectForHistory or ExcessBaggage. The maximum safe growth rate is proportional to the number of "oldbies", and the amount of time each spends welcoming and tutoring, and inversely proportional to the amount of time each newcomer takes to integrate into the community. You can attempt to increase the safe growth rate, but it may be easier to simply limit growth to that rate.
As a community grows, so do its bandwidth costs. Some of these can be reclaimed by donations, adverts, or MicroContribution?, but these take time to set up, and if a community grows too fast then costs can grow faster than revenue, just as for any business. In the .com boom, venture capital made up the shortfall, but this is no longer true.
The UserLifeCycle can be modelled as:
This provides you with two good places to limit growth. Firstly, you can stop people from becoming readers in the first place. This can be achieved by using a DeepLinkDefense (especially if the bulk of your growth comes from a specific external source), by becoming a GatedCommunity, by emitting "no-archive" tags to discourage site indexing by google, by reducing the amount of promotion of the site elsewhere, and in other ways.
Secondly, you can stop readers from becoming occasional contributors. MetaFilter requires logins, and simply disables the "new user" page whenever fast growth becomes a problem. You can also make the "new user" process complex and slightly tedious. If your site allows a guest account (perhaps because otherwise LoginsAreEvil), the guest account can be disabled during high growth times. You can also use an EconomicSolution: place the EditThisPage button somewhere obscure, or require it to be turned on in preferences, thus gently discouraging new contributors until they know more about the community. LayeredWikiInterface is a complete solution built around this. LiveJournal required that new contributors get a recommendation from an existing member.
It is possible to limit growth by preventing occasional contributors from becoming core contributors, or by driving away current contributors. This is counter-productive for the community, as it prevents bonds from forming, and limits grass-roots social solutions. However, because it keeps the community weak and pliable, it is sometimes used by GodKings to avoid the need to DevolvePower.
The above text is PrimarilyPublicDomain
Clay Shirky's essay at http://shirky.com/writings/group_enemy.html has the meta-filter example, and is partial inspiration for the above.
I created MeatballWiki to demonstrate how to administrate a wiki; as an experiment to see if I could do it. I've learnt a few things in the past few years, including that it really isn't about learning how to administrate a wiki, but learning how to facilitate a group of people. Once you extend beyond a coherent group into the mass populace at large, the only way to go is laissez faire, while the smart people go found another more coherent group elsewhere. -- SunirShah