techleadcoaching / coaching Goto Github PK

Currently, the coaching/mechanics.md page is just a stub.

This is an important page because the idea behind it is to give the new coach very prescriptive guidance that will help them a) give a consistent/great experience to a tech lead and b) give the new coach some confidence about how to structure the conversations.

Currently the intro is in index.md, which should probably be renamed to README.md.

The purpose of the introductory section is to give an overview of the section for people who are tech leads and might be interested in getting coaching through the Tech Lead Network. (There is a different section of the site for people interested in being coaches, which will be the subject of a different issue momentarily.)

Part of the goal of an overview is to state the factual contents of the section, which is a fairly straightforward summary of the contents in the section.

The second part is to encourage readers to go beyond the introductory section with some compelling quotes and vision for why reading more of this, and possibly signing up for the network, could be worth their time investment.

Currently, the content at tech-leads/skills.md is a placeholder and needs content.

The idea is to take the current tabular content from the coaching section, coaches/model.md, and write it up as a narrative form (not the tabular form) to describe the skills that we think tech leads should really focus on.

Currently, the introductory section of the coaches section is in intro.md, which should probably be renamed to README.md.

Similar to issue #1, we should also clarify a summary of the section in terms of its subtopics and other factual stuff.

But more than the factual basics of this section, it should really inspire people who are exploring the section who might be curious about being coaches to both invest more time into exploring it and, hopefully, signing up for being a coach :-)

The topic Being a Tech Lead is currently documented in intro.md, which maybe should be renamed to something more obvious, like 'being-a-tech-lead.md', but there are more substantive issues too:

Some specific issues:

• The section needs an introduction with a bit of an overview
• We repeat Pat Kua's definition and then offer our own but don't really explain the different
• Better cohesion between the sections
• We may seriously want to consider breaking the section "What is Tech Lead Coaching" into it's own page

Currently, the content in being-coached.md is only stubbed out.

The idea for this topic is to document some guidance for new tech leads to get the most out of coaching: certain behaviors or mindsets that might be helpful and ways to send the right kinds of signals to the coach for certain needs.

Page: tech-leads/being-coached.md