Blog: ...created equal? Pt. 3 - Process: how it should, but often doesn't, work.

Jul 14, 2008

Pages: 1 | 2

As noted in our development process document (and corresponding blog - read here), there is a definite need for a proper development process to keep a web project on track. Unfortunately, many web designers don't make the extra effort to discuss and nail down all of the "boring" aspects like competitor research and content development.



As a client, it's important to understand the way the process should work and not be so eager to "see" something like a graphic proof or comp. When a project is rushed to graphic proofs, expect lots of potentially costly changes before a final end product is decided upon. Furthermore, if a less-than-stellar proof is rushed into production, you're looking at more changes that often lead up to a anticlimactic project launch with a "let's just get this finished and over with already" mentality. Not exactly an enjoyable experience. Enjoy the pre-graphic parts of the web process knowing that your website will contain valuable content.

Of course, reserve some excitement for when you do see graphic proofs of your site. While comparing proofs, layouts, etc., attempt to put aside any personal preferences as much as possible. Place trust in your development firm that they are providing a well thought out design that speaks correctly to your demographic and does just as good of a job framing your content.

If you are the lead contact on a project and are responsible for gathering feedback from your company or organization, steer people away from settling on feedback like: "I just don't like that shade of blue" or "I think the logo needs to be moved a little bit to the right." The important consideration when gather feedback is: Will a change in this item actually make the website more effective? There are millions of minor tweaks possible, focus on only what's really important.

What kind of feedback is good from the developers perspective? Feedback like, "We like Proof 2 the best. However, when we showed it around, Product B seemed more important and we need Product A to most prominent. We like how Proof 3 balanced out Products A and B." Perfect. The development firm can then focus on the design concept of Proof 2, while modifying it based on knowing that a specific layout area of Proof 3 was better received.

Pages: 1 | 2


Comments

SELECT * FROM thrive_comments WHERE module_owner_index=7 AND approved='yes' ORDER BY date DESC
No Comments Found. Don't be shy! Leave a comment.
© 2008 SLD Interactive. All Rights Reserved.