Board Thread:Support Requests - Community Management/@comment-3335785-20130314201106/@comment-310-20130316001702

452 wrote: Lachlan5963 is an admin of a wiki with 1,250 pages who did not receive the email. He, nor I, see any reason for him to be excluded. I'm the admin of a 1,022 page wiki - any information which is relevant to me is also relevant to Lachlan5963, and any other admin - and any other user who may be interested.

Once a newsletter email goes out - where do new Admins go to read past emails? Some emails contain a link to read it online, but this one didn't.

Blog posts are there forever, which anyone can reference any time. They add to the sum of total knowledge available on Community Central.

If these Admin emails are going to contain valuable information, what reason is there to not have it available to everyone at any time?

There are already multiple staff blogs which have information that is not relevant to everyone, and there's already a "Founders and Admins" blog category. So for a better answer to that question, you'll need to ask Wikia staff why the "Founders and Admins" blog category exists.

Think it's about time I waded in here.


 * The E-mail uses a cut-off to decide who gets the e-mail, and who doesn't. There is naturally going to be discrepancies like this the further down you go, in terms of article page count, because other criteria are used as well, such as page views, traffic, etc. I don't think this point has been understood.
 * E-mails are designed to give a snapshot of how the situation looks at present, as well as serving a valuable point from earlier: They are not designed to be available to everyone.
 * Staff blogs are different, because they cover a wide range of topics, that many users (and that goes for both Admins, and Users) find useful.

I also find your comment (that infers that that speedier Contact requests are from Admins with 'entitlement issues'), to be quite offensive. Speaking from an operations point of view, sooner or later, it becomes economically necessary for a corporate business to devote greater attention to larger projects. Every single company that I have either worked for has followed this priority system, both small business, and corporate.
 * Larger Wikis are also more complex, and require more business resources and technical attention than smaller ones (as a rule). Allocating people support to enable shorter response times ensures potential problems are sorted quicker, and actually allows the business additional time to focus on other wikis, by streamlining their approach to support.
 * Larger projects = greater revenue = greater investment. There should be an incentive for communities (and their leadership structure(s)) to grow larger, and the faster response times are a way of doing that.