Developing, Design, and Content vs. Product

When ever given the choice to work on design or content, any designer chooses design. However front end design requires content to be able to get a true feel for what you are designing for. My conundrum is often that I have little to no content from clients to work with in the beginning stages, and I have the writing skills that would make an english major scream and throw windmill punches at the monitor until my content went away.

In house, I keep building things for The Animal House, with the expectations of the staff providing content to fill. Then the project never gets finished, because there is no content coming in to turn out a finished product. One can say that in house that is management problem on my end, and I did agree with that assessment, but I am beginning to look differently at this. If I can’t get my employees excited about something, then how on earth can I get an end user excited about product. The product concept itself has to have a well thought out usage validity, then the product has to be developed around the concept of the product with the user interaction in mind, and then design has to highlight the end product to enhance the user experience. (English majors, commence windmill punching…)

In short, which is much too late, after all that