Every added feature is a future added negotiation. There are, however, a number of things the W3C could do, including simply doing less. Doing less and doing it more slowly might give development communities time to provide meaningful feedback. Allowing specifications to mature through implementation before layering on top them would reduce the risk of building on uncured, uncertain foundations. Similarly, presenting W3C output in smaller pieces, deliberately fragmenting specifications into useful atoms, would help developers absorb and implement the standards.
Smaller standards are easier to implement and integrate.
Current W3C activity suggests that this is not the route its members want to follow. The W3C claims that it creates Recommendations, not standards, and is set up to a significant extent as a research lab. Taking that seriously means that developers should treat everything the W3C is doing as experimental and potentially unstable, worthy of careful evaluation rather than strict observance.