Goal: Process Document for Busy People should be tailored to key busy people: technical editors and contributors. They most often need to know how to make progress on a spec. This doc should start there and describe how everything else is in service of it.

tl;dr start with the actual work product of the W3C, specifications, then go meta one step at a time, section by section. Rough outline:

• Making specs to improve the web is why we are here (how are they made? and updated? flow charts)
• WGs are in service of making specs within a particular area (Charter scope) that are ready (incubation - link Rec Track Readiness)
• The TAG is in service of making sure specs make sense across WGs.
• IGs/CGs are in service of incubating proposals towards specs, either to hand-off when ready to an existing WG, or to motivate a new WG. Members can also submit things in service of incubating proposals.
• Anyone can help start a CG, the W3C Team drives creating IGs, WGs
• The AC is in service of prioritizing (voting) which WGs and IGs should be created or continue to exist and worth spending W3C resources on. Also voting for the TAG.
• The AB is in service of the making/updating the process of all the above as efficient and consensus based as possible. The AB is also elected by the AC.
• Appendix: Other random FYI W3C stuff that doesn't directly impact how specs are made, or the groups that support that: e.g. Communications, Workshops, Liasons.

Modest proposal: start with W3C Recommenation (Technical Report) Flow: The "Recommendation Track" — that diagram is key and perhaps the most referenced thing (second perhaps is the Modifying a W3C Recommendation diagram and section). Include all the material up through just before Communication.

Everything else, e.g. W3C Groups, TAG, AC, AB, Leadership section should all follow from there.

Label(s): Process