A practical, copy-pastable operating system for healthy, high-performing engineering teams in remote-first SaaS environments.
This playbook is an operating system for engineering leadership. It's opinionated, practical, and designed to be used—not debated.
Focus areas:
- Team operations — Cadences, rituals, working agreements, async communication
- People growth — 1:1s, feedback, growth plans, hiring, performance management
- Delivery — Planning, quality, incident response, technical debt, metrics
- Culture — DEI strategy, engineering culture, psychological safety
- Platform — Reliability practices, scalability, platform themes
- Leadership — Development paths, decision-making, vision and strategy
Who it's for:
- Engineering Managers
- Tech Leads
- Staff+ Engineers
- Anyone building or leading engineering teams
What makes it different:
Every document answers six questions:
- What problem does this solve?
- When should I use this—and when not?
- Who owns this, and what are their responsibilities?
- What does "good" look like in practice?
- What usually goes wrong?
- What can I copy-paste and use today?
- Python 3.10+ (for MkDocs)
- Node.js 18+ (for linting and formatting)
- Git
# Clone the repository
git clone https://github.com/dreamingechoes/engineering-leadership-playbook.git
cd engineering-leadership-playbook
# Create and activate a Python virtual environment
python3 -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activate
# Install Python dependencies
pip install -r requirements.txt
# Install Node.js dependencies (for linting)
npm install# Activate virtual environment (if not already active)
source .venv/bin/activate
# Start the development server
mkdocs serve
# Open http://127.0.0.1:8000 in your browser# Build the static site
mkdocs build
# Output will be in the ./site directory.
├── docs/ # All documentation content
│ ├── index.md # Home page
│ ├── principles/ # Core principles, decision-making, ethics
│ ├── team-ops/ # Cadence, rituals, working agreements
│ ├── people/ # 1:1s, feedback, hiring, growth
│ ├── delivery/ # Planning, quality, incidents, tech debt
│ ├── platform/ # Reliability, scalability, themes
│ ├── metrics/ # Engineering and team health metrics
│ ├── culture/ # DEI, engineering culture
│ ├── collaboration/ # Working with Product, Design
│ ├── crisis/ # Crisis management, outage comms
│ ├── scaling/ # Scaling teams and systems
│ ├── leadership/ # Leadership development
│ ├── case-studies/ # Real-world examples
│ └── resources/ # Templates and tools
├── src/
│ └── overrides/ # Theme customizations
├── mkdocs.yml # MkDocs configuration
├── requirements.txt # Python dependencies
└── package.json # Node.js dependencies (linting)
mkdocs serve # Start development server
mkdocs build # Build static site
mkdocs gh-deploy --force # Deploy to GitHub Pagesnpm run lint # Run all linters
npm run lint:md # Lint markdown files
npm run lint:md:fix # Fix markdown issues
npm run lint:format # Check formatting
npm run format # Format all filesReady-to-use templates are available in /docs/resources/:
- 1:1 Agenda
- Retro Template
- Postmortem Template
- ADR Template
- Growth Plan Template
- Hiring Scorecard
- Working Agreement
- Runbook Template
- Outage Comms Template
- Roadmap Review Template
- Conflict Resolution Template
Contributions are welcome. Please:
- Fork the repository
- Create a feature branch (
git checkout -b feature/improvement) - Run linting before committing (
npm run lintandnpm run lint:md:fix) - Submit a pull request
- Code and templates: MIT License
- Content: CC BY 4.0 — Attribute "Iván González Sáiz" with a link to this repository
Created by Iván González Sáiz — Engineering Manager / Team Lead focused on remote-first SaaS teams.
- 🌐 Website: dreamingecho.es
- 💼 LinkedIn: ivan-gonzalez-saiz
- 🦋 Bluesky: @dreamingechoes.bsky.social
- 📧 Email: hi@dreamingecho.es