In addition to picking up some of the basics, I suggest that at least part of the problem lies with the developers. Part of engineering is understanding the needs of non-technical people and translating those needs into actionable technical requirements.

This isn't necessarily in the skill set of every engineer, but in a well rounded team, there should be maybe a couple of engineers who are recognized for being able to do this. From time to time, the question has arisen on HN, as to what a "senior" engineer consists of, and the ability to interface with a larger community (e.g., managers, marketeers, users, etc.) is often mentioned.

You might not be able to solve that problem right away, but it could figure into your future hiring practices.