Seven Essential Meta Questions of Every Beta lists some key questions that each site needs to decide -- scope, tagging, etc. New sites in private beta get a link to this post at the top of their meta, which gives users the impression that these issues should be brought up and decided early. For some that's true; issues of scope are pretty essential, for instance.
But that list also includes "who should the moderators be?" and "what should our site design be?". The first can lead to early drama (SE chooses the pro-tems, and not until a few weeks in), and the second is very premature (a site doesn't get its design until graduation, which can be a year or two after beta).
I'm currently watching a private beta where some users seem to be obsessing over the former and some are expending energy on the latter. That doesn't seem very productive to me.
In addition, as pointed out in comments, some users see this list and think it calls for seven meta posts, one per essential question. However, some of the essential questions, like FAQ contents and tagging, are really categories of questions, and over-arching questions don't address the need.
Could we instead link to something better for early beta, like the real essential questions of every beta (which is now a FAQ entry)? It seems like the current post + linkage can be a little misleading and distracting at just the wrong time. The other issues are important, but maybe not on Day 1.