In this episode, Dave and Jamison answer these questions:
\n\n\u201cI\u2019m into my second job of leading a team of software engineers and want to level up my coaching skills. In my first role I accidentally fell into the deep end of management \u201cfun\u201d by taking on a team of 10 people. One of the big problems I faced was being the \u201cgo to\u201d or \u201csign off\u201d person for a lot of different things, and I perpetuated this problem by showering people with my incredible answers (based on my obviously incredible know-it-all-ness) and thus reinforcing my goto factor. I was aware of coaching as a concept then, but didn\u2019t incorporate it into my leadership style, which I believe contributed to my eventual burn out in the role.
\n\nOver the last year in my current team lead role I\u2019ve been much more deliberate about various aspects of leadership, but my coaching prowess is still struggling. When I\u2019m asked questions by my team, my default response is to jump to a specific answer based on my own opinion, and it\u2019s only afterwards that I slap my forward and yell out \u201cmissed coaching opportunity!\u201d (as people near me back away slowly with concerned looks on their faces).
\n\nWhat are some effective techniques to try and build a habit of using coaching as a primary means to help my team work through problems?
\nI just became a technical lead for a team at my company. I\u2019ve never held a leadership role like this before. Do you have any advice for how to do a good job?
\n