     |
||
|
You and What Army?
My background includes both visual design and programming. In college-degree-speak, that's a BFA in Graphic Design and a BS in Computer Science. Since then, I have worked almost exclusively on web-based projects ranging from a distributed weather tracking application, to a team management document sharing application, to a medical application used by cardiologists to prepare patient dosages. This diverse set of experiences uniquely qualifies me to address problems out-of-scope for many designers and programmers.
 Repeat After Me. The end user should be considered in all phases of the design of a project. Their involvement starts with requirements gathering, continues on through interim testing, and concludes with quality assurance. If you forget your target audience, you will inevitably build the wrong product. I have seen teams develop wonderful solutions to problems their clients did not have. [ think : user-centered design strategies ] Quick, low-resolution sketches of concepts are critical in reaching workable solutions to identified problems. By quickly moving from thoughts and ideas to paper and screen, problems with a proposed solution can be identified before time and money are spent on development. Paper, pen, and pixels can adapt and move much faster than lines of code. [ think : rapid prototyping ]
It wasn't raining when Noah built the arc. (Howard Ruff) PRO-activity is the right thing to do, RE-activity is the easy thing to do. (me) Clients typically wait until a known issue forces a redesign or a change in the development direction before taking action. Taking the time to assess a project before a problem arises can prevent catastrophic consequences. [ think : proactive ]
|
