After receiving my instructions, he successfully completed pc board layout. I then introduced him to Computer Automated Engineering (CAE). I showed him how to drag electronic components from a library, use mouse to draw circuit paths, make computer simulate function of circuit, and then make computer layout a pc board for circuit.

He was able to easily master complex technology because he now understood that he wasn't stupid. Computers ARE complex. When he needed help, he studied help files or asked someone for help. Eventually, his CAE skills became known and I lost him to another manager. "His last stop before being booted out door?" I don't think so. There's no way Motorola is going to let this valuable employee get away.

Even though it's programmers fault that computers and software are too complex, that doesn't relieve you of all responsibility. You must make an effort. Like my friend at Motorola, you must study help files or ask someone for help when you need it. Not only must you study help files, but you must also be willing to "try things".

Many people fear that if they click on wrong thing, computer will blow up and they will be blamed for it. A properly designed software application prevents user from making a fatal mistake, either by making it impossible, or by providing a warning message. A properly designed application lets user "back out of" or reverse any action. One of best ways to learn is to "try things". If computer blow ups because you made a mistake, you're using improperly designed software.

When you're learning how to perform a function with a computer, if you expect you may need to perform that same function again, take notes. No one will think you're stupid if you take notes. But if you keep asking over and over again how to perform same function, they will think you're too stupid to take notes.

When I worked at Motorola, I used a technique called "strokes" to make symbols appear and move around computer screen like magic. Some people called me "Electronic God". How did I get so good? I tried things. I failed. I studied. I tried again. I understood that technology IS complex. So what?

In today's society, being computer illiterate is equivalent to being functionally illiterate. Make effort to study help files and to "try things". Don't get discouraged or blame yourself if you don't succeed on first try. The computer won't blow up if you make a mistake. You can't be successful at work if you fail to embrace computers and technology.

---------------------------------------------------------- Resource Box: Copyright(C) 2004 Bucaro TecHelp. To learn how to maintain your computer and use it more effectively to design a Web site and make money on Web visit bucarotechelp.com To subscribe to Bucaro TecHelp Newsletter visit http://bucarotechelp.com/search/000800.asp ----------------------------------------------------------

After that, Lloyd suggests you check in twice during year. "Don't wait and be surprised," she says. "Check in and say 'How am I doing against what we talked about? These are expectations you said (write them down beforehand). How am I doing against them? And if I'm not at an excellent level, please tell me how I can get there so at end of year I'm eligible.'"

Then if you've been getting feedback throughout year and keeping communication channels open with your boss, his jaw won't slacken at your request for a salary increase when you make "the ask".

About two months before performance reviews, or before appropriate budget cycle at your company if you don't have performance reviews, give your boss a heads up about your specific desire for a raise or bonus. Why? Because your boss needs time to present your case to his boss, owner or human resource department and to do so before budget has been finalized for year.

So be proactive and initiate a conversation about your performance at that time, says Lloyd. Don't stay silent, possibly indicating you're satisfied with things as is or just plain getting lost in shuffle on your boss' to do list.

And when you ask for raise, don't make demands or whine but rather be factual and make a very strong business case, Lloyd advises. Consider even putting your case in writing so you make it easier on your boss to restate if he must take your request to someone higher in company.

Your case should include previously discussed expectations and how you fulfilled them and what results you attained. Or make a chart showing your responsibilities at start of year and your current increased responsibilities and decision-making authority.

"It should be pretty evident to manager that you want more money and that you are open to taking on more responsibility or improving your performance," says Lloyd. "So this [salary request] shouldn't come as a surprise at end of year or cycle."

And before you make your case, always have a plan B. You may truly warrant a raise, and your boss may truly want to give you one. But for whatever reason, a raise may not be plausible this year at your company. So plan B could include what else you'll settle for in lieu of a raise, such as a couple more days of paid vacation, a flexible work schedule that allows you to work at home one day a week or just a spot bonus.

"If you're a good employee, bosses don't want to lose you and they feel just as badly as you do that they can't reward you for what you're doing," Lloyd says. "And thing that worries every manager when they can't give a raise is 'Am I going to keep my good people?'" Plan B might just answer that question for both of you this year. And then next year is a whole new ballgame.

© 2004 Karen Fritscher-Porter