documentation and customer support can really hurt a young product organization, and these are not solved by brilliance, but rather diligence and patience.
But it's also true that a good design can reduce documentation needs (and documentation/code fragility) by a startling amount - not to mention stop floods of customer support calls before they start. It's certainly true that not every job is a design or analyst job; but you'd better not be wrong about when you need a design task done, and the 1x programmer (or boss) can't make that judgement call for you.
