· A technology leader stands at the head of the group and asks the other members to follow as he or she addresses the tasks before them. A manager asks the group members to work as hard as they can, but to be sure to come and show what they've done so he can check their work.
· A technology leader doesn't ask anyone to pull cables, write programs, test applications or write documentation when he hasn't or wouldn't do it himself. A manager thinks these, and other, tasks are for underlings.
· A technology leader shows the kind of genuine commitment to the project he expects everyone else to show; by implication, he wouldn't be involved if he didn't believe in the project. A manager just follows orders and puts in time.
· A technology leader has the highest professional and personal standards. A manager will often tell others to do what it takes to get the job done.
· A technology leader holds his position because he's shown he has what it takes to get the job done. A manager often occupies his position because he's been there the longest, knows somebody or just happened to be appointed to the position.
· A technology leader doesn't necessarily know everything, but as long as he can apply the skills of other experts, the project can succeed. A manager feels he might fail personally if someone else is shown to know something he perhaps should.
· A technology leader puts the project first; if it fails he fails. A manager usually has somewhere else to affix blame.
Copyright © 2026 eLLeNow.com All Rights Reserved.