I'm going to assume that, instead of a full guide, what we really need is to clean up the hubs to clarify the powers and abilities of the teams, then make sure that Junior Staff know what they're doing before they get promoted. We can do this best, I feel, by bringing people into SSSC a little earlier and helping them to get acclimated.

Honestly, the fact that some people didn't know what -ARCs are doesn't surprise me. It's been a fairly long time since we've had to archive an SCP, after all. That said, the Archived SCP page spells out exactly what they are, both types. Perhaps the rarity means they simply hadn't been run into them before? I don't know.

That said, the lack of response makes me believe this page isn't really needed. Anyone who disagrees can contact me via Wikidot PM with the things they think should be added to such a page. I'll begin passively drafting one. Until then, I consider this discussion closed.

Please answer seriously. These answers will go into making the new staff FAQ.

I would really like to see everyone put forward what their problems were when they became staff, things they didn't know, things they were worried about, etc. And based on that list, I'd like to create a document to clarify, provide references for people, and provide guidance.

…this is pretty awesome, actually. I fully endorse this course of action.

Either way, sounds useful!

I don't think "Staff Structure" can cover things like that. I think a general FAQ would actually be beneficial. Even on the site proper, the shitty outdated FAQ (well, actually, it's much less shitty now but still outdated) serves as a valuable resource. As opposed to "ask Troy or Moose or flounder".

Hey, it probably would've helped if I clarified the example I was thinking of in the first place, eh? Gold star to me.

It doesn't necessarily even have to be a huge page, I just think it would be helpful. "Non-obvious things you should know as general staff."

No one should be flailing for "what I dooo?" They should be looking at their team page, or in lieu of this, talking to their team members to get ideas. If you're wanting a broad, general "what do I do as a staff member?" page, then I suggest replacing the originally linked document with a broad, general overview and have the captains and their staff work out their policies and roles on their team pages.

That said, it might just be best to find the elements of the staff structure page that need expanded and address things there.

I know that in my case, I kinda got thrown into "unofficial staff" position a few months after I got on the site, and then following full promotion, I was just told "keep doing those unofficial staffy things you were doing before."

Some of the finer points would be helpful. Also, I want to broaden this to all Team Leaders that they do a similar thing for their own teams, like "How 2 Site Crit" so that everyone on the team knows exactly what to do on said team.

So. Thoughts? Does anyone want to help make "Being Staff for Dummies: A Guide for the Rest of Us"?