Paul, of course, it's far easier to write out a suggestion than to
actually do it, and free advice on the Internet is seldom worth what you
pay for it. Anyhow, my idea
might help...
I might be misunderstanding your "ahead of the aircraft" statement, but
personally, I think it's unreasonable for you to expect YC partners to
be "ahead" of the startups in a batch. In fact, if YC partners are not
behind in understanding a startup, then that startup is in trouble. The
startups may not have the benefit of experience possessed by the YC
partners, the startup founders should always know the state of their own
business and market better than the YC partners do.
I believe one of the reasons why you regularly advocate being concise is
due to your own personal overload problems as well as the stated problem
of all YC partners not keeping up with all of all of the issues in all
of the startups in a given batch. It's the classic many-to-many
communication problem where the ability of partners to assist and advise
startups is limited by their ability to stay informed.
Even if you're never able to isolate every single metric a YC partner
should know, identifying as many of these metrics as possible and having
a reporting mechanism would still reduce the load on YC partners. Though
its not publicly known, I'd bet you do already do something along these
lines, either formally or informally. Your "growth.html" essay seems to
hint in this direction. None the less, making improvements to your
identification, collection, and reporting of useful metrics should still
be a worthwhile investment.
I sincerely doubt you would want my help implementing a startup metric
collection and communication system, but I'll offer to help anyhow. It's
a fascinating problem and it seems like a really fun challenge.