Rules to Live (or Work) By 8/2000

Focus on user value- If the system doesn't improve user value, then it isn't worth anything: This is an important concept for me as a web developer and designer. I want to design complex web sites offering the latest in graphic and dynamic capabilities. However if the end-user becomes overwhelmed or confused by my content, I have failed. Everything I design and develop should improve the site value to the user, not just show off new techniques or technologies.

Take risks, and manage them- If you don't take risks nothing will ever change: This is a very meaningful statement to me. It can be applied to both my personal life and my career. In my early-mid 20's I can't be afraid to take intelligent risks in life. As a young IT professional, I also cannot be afraid to take intelligent risks concerning my career. As a web developer for a traditional/conservative organization, I want to push the limit (using new technology), while at the same time managing any risks that come along with it (CYA).

Document- CYA: As a recent graduate and someone who is somewhat new to the work force this is an important concept for me to adhere to. I must cover my ass by documenting what my superiors tell me, what work I do, and how I feel about certain recommendations. I will make it clear in documentation, if I agree or disagree with a decision being made.

Negotiation: Everyone must believe that a settlement is possible: It is important for people not to go into negotiations with the attitude of "This isn't going to get us anywhere" or "We are never going to agree on this". This gives you a negative outlook on the situation from the beginning, and you will be less likely to give a sufficient effort in the negotiations. It's also important to recognize when the other side doesn't believe a settlement is obtainable, and if possible take the necessary steps to change their mind.

Negotiation: Know what you want up front: Go into negotiations knowing what you are willing to compromise on and what you are not willing to compromise on. If there is something that you are not overly concerned with, and the other side thinks it is important to you, they will perceive it as you giving something up. This may allow you to gain something that is important to you in return.

Conflict almost always has a positive: It is important to recognize the positive side of conflict, because much can be learned from conflict. Removing yourself personally from a situation of conflict is important. Don't look at conflict or criticism as a attack on you, but rather look at what can be gained and learned from the experience.

Conflict is unavoidable, expect it and deal with it: This is particularly important in the IT field. One must realize that their will be opposition or conflict associated with new systems and technology. Anticipate user feedback and conflict, and have steps ready to deal with it. Don't expect your work to be accepted without conflict.

Implementation: The goal is to get the client and users from the "Oh boy a new system" to the "how did we live without it". Getting through the "Oh Shit" and "Oh Well" phases is what is challenging. Training is the way to get users through this process. You must have an effective training plan in place to ensure a successful implementation.

One of the most important concepts I have learned is to under promise and over deliver. This is important because it will save you from failing to deliver what was promised, and will allow you to please the client by delivering more than what was discussed. When developing Web sites I should promise what I know is feasible, and try to deliver what I think is possible (a step above what was discussed).