I think we often focus on designing or building an element, without researching the other elements it should connect to—without understanding the system it lives in.
If you’ve ever wondered what it would be like to be a fly on the wall at a CSS Working Group meeting, Richard has the inside scoop.
The consensus building is vital. Representatives from all the major browsers were in the room, collaborating closely by proposing ideas and sharing implementations. But most fundamentally they were agreeing together what should go in the specifications, because what goes in the specs is what gets built and ends up in the hands of users.
Mikey compares a few different decision-making processes (and in the process describes the fundamental difference between the W3C and the WHATWG).