explaingit

ksindi/managers-playbook

5,504Audience · pm founderComplexity · 1/5Setup · easy

TLDR

A practical written guide for engineering managers covering one-on-ones, feedback, coaching, hiring, onboarding, and strategic thinking, especially useful for engineers stepping into management for the first time.

Mindmap

mindmap
  root((repo))
    People Management
      One-on-ones
      Feedback
      Coaching
    Team Health
      Autonomy
      Mastery
      Purpose
    Process Topics
      Hiring process
      Onboarding new hires
      Code review workflow
    Leadership
      Managing upward
      Strategic thinking
      Decision making
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

First-time engineering managers looking for a concise reference on how to run one-on-ones, give feedback, and build a healthy team

USE CASE 2

Experienced managers who want a quick refresher or a second opinion on common management dilemmas

USE CASE 3

Team leads preparing to step up into a full management role and wanting a structured checklist of responsibilities

Getting it running

Difficulty · easy Time to first run · 5min

This is a written document, not software. Just read it on GitHub, no installation required.

No explicit license mentioned in the explanation.

In plain English

Manager's Playbook is a written guide containing practical advice for engineering managers. It is not software, but a living document in a GitHub repository. The author compiled it from personal experience and observations of other managers, and it is aimed primarily at people moving into management for the first time, though experienced managers may also find it useful. The guide covers the full range of concerns a team manager typically faces. There are sections on one-on-ones (regular private check-ins with each direct report), giving and receiving feedback, coaching, making decisions, strategic thinking, and managing upward toward your own leadership. It also covers more process-oriented topics like how to run a hiring process, onboard new hires, manage a ticket and code review workflow, and announce changes to the team. Some sections include concrete techniques. The one-on-ones chapter suggests a monthly health check where you ask your report to rate on a scale of one to ten how they feel about predictability, ownership, purpose, progress, and belonging in their role. The coaching and feedback sections draw on recognized frameworks. The guide also addresses a common question for engineering managers: how technical should you be? The author recommends against managing people until reaching at least a senior engineer level, and advises that managers with more than seven direct reports should generally avoid coding in the critical path so they do not block the team. The document describes effective teams as needing three qualities: autonomy (the ability to work without depending on other teams), mastery of their domain, and a clear sense of purpose. The README notes the guide is intentionally kept short and focused. It also links out to further reading for anyone who wants to go deeper on individual topics.

Copy-paste prompts

Prompt 1
Using the Manager's Playbook approach, write me a monthly one-on-one health-check template that asks my direct report to rate predictability, ownership, purpose, progress, and belonging on a 1-10 scale.
Prompt 2
Based on the Manager's Playbook, draft a structured 90-day onboarding plan for a new software engineer joining my team.
Prompt 3
I have 9 direct reports. According to the Manager's Playbook guidance on span of control, what should I change about how I spend my time?
Open on GitHub → Explain another repo

← ksindi on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.