First must come acceptance.
Here are some great mistakes in technical leadership.
This may be common sense to a lot of people, but I've bet everyone in any sort of leadership position (whether reflected in title or not) has done something on that list.
I've found it's very easy to say, "well, just this one time I'm going to do this..." where "this" is take a juicy technical problem for yourself, or come down on someone for breaking the build etc...it's a very slippery slope from "I'm just going to do this once" to adapting into your leadership style, especially if you're new to the leadership game. All sort of internal justifications are created that really aren't very good reasons.
I'm working very hard to break some of these mistakes, which quickly became habits for me. Not only do I have to break them as habits myself, but I have to change the perception of these as my shortcomings. That's even harder.
Make like easy on yourself, don't pick up bad habits from the beginning. There can always be a "good" reason not to delegate or trust your team, but in the long run those reasons don't typically hold water.
Me, I'm primarily guilty of 4, 5, 6, 7, 11, 15, and 17.
Those are my things to work on, and some of them I hadn't realized until reading through the entire list and thinking about it.
This is Rob Meyer's weblog, a weblog focused on software development and system administration based on 10 years of experience. Want to explore further? You can find out more me or see the rest of my website.
Wondering if I've written on something in particular? Try searching:
You might want to take a look at some of the more requested postings (as judged by incoming traffic):
Want more? Subscribe to this site 
or contact me at rob at big dis dot com.
See my writings on: