There are many blog writers and internet sites that surf the web for great information and then provide links to it. While my main goal is to write "fairly" original content, I often find it helpful to point readers toward a superb article or something that will benefit those who came to this blog looking for leadership wisdom and personal growth material.
Oftentimes, quality leadership principles are true in a variety of experiences.
1. While studentl.inc is written with student leaders in mind, much of the material translates into a wide variety of leadership contexts.
2. There are a variety of leadership articles and posts out there that are very applicable to student leaders even though they were written toward a different type of leadership audience.
While this article deals with issues that those who serve as the Technical Lead in software development may face, it is immensely valuable for those who are in student leadership. My philosophy has always been to allow student leaders to make mistakes and learn from them. Yet, it is also beneficial to learn from the mistakes of others and work to not make them oneself.
Here's the list of mistakes (I encourage you to read the whole article to get a better understanding of each one):
Mistake #0: Assuming the team serves you
Mistake #1: Isolating yourself from the team
Mistake #2: Employing hokey motivation techniques
Mistake #3: Not providing technical direction and context
Mistake #4: Fulfilling your own needs via the team
Mistake #5: Focusing on your individual contribution
Mistake #6: Trying to be technically omniscient
Mistake #7: Failing to delegate effectively
Mistake #8: Being ignorant of your own shortcomings
Mistake #9: Failing to represent the best interests of your team
Mistake #10: Failing to anticipate
Mistake #11: Repeat mistakes others have already made
Mistake #12: Using the project to pursue your own technical interests
Mistake #13: Not maintaining technical involvement
Mistake #14: Playing the game rather than focusing on the target
Mistake #15: Avoiding conflict
Mistake #16: Putting the project before the people
Mistake #17: Expecting everyone to think and act like you
Mistake #18: Failing to demonstrate compassion