Just need to run this by product audience managers, will do at the end of the month when I'm in SF (April).

Thank you for this draft.

While all the details about the Technical Collaboration Guideline might be difficult to memorize, the principles behind it should be simple and memorable, worth spelling them out.

Here the principles could be:

• Development teams make calls for feedback at specific project stages.
• The main goal is to find potential blockers.
• The calls are made in a systematic way.
• All stakeholders participate in the same calls.
• Results of each call are documented in the project plan.

I think the current list at https://www.mediawiki.org/wiki/User:Keegan_(WMF)/Agreement2 is consistent with this principles, but could be simpler and clearer, also at defining the kind of feedback expected.

For instance (not intended to be final copy):

1. A project proposal. Check against principles, strategy, existing plans.
2. A design concept. Usability, look & feel.
3. Translatable content. Usability, i18n, L10n.
4. A prototype. Usability, performance, bugs.
5. A release plan. Identification of early and late adopters.
6. A beta in production. Last details before final release.

Adding some scope in the examples as per @Qgil's suggestions, makes sense to me. Will refine when I go over it with product people.