See also: Why Coaching?
How can we help?
coaching your coaches
Who is this for?
Chief Executive Officer
Chief Technology Officer
VP/Head of Product
VP/Head of Engineering
Together, we create goals and track them. We define these at beginning of the coaching relationship, and update them periodically.
Why set goals? These help focus our efforts, making sure the coachee gets the most out of the engagement.
Who sets the goals? The coachee, directly. Sometimes externally-set goals are a part of the process, but to be successful goals must be defined and agreed to by the coachee.
Example Goals for a CTO
fostering a culture where employees can speak up
being aware of issues before they arise
Example Goals for a Product Manager
deliberate, transparent prioritization
communicating effectively with stakeholders
working better with developers
Example Goals for an Architect
balance contributing and consulting
making people are aware of your contributions
approach for choosing a language/framework
The bulk of coaching progress is made in weekly, 60-minute one-on-one conversations. Talking through problems with someone else who really gets it is so powerful. It's hard to overstate how powerful it is.
Coaching engagements are done for 3 months at a time, which is 12 coaching sessions per coachee.