Every template here has been used in production by engineering leaders managing real teams. They're opinionated on purpose. Take them as-is, or fork the structure for your team's context.
Showing 40 of 40 templates
A structure for meaningful conversations with direct reports — beyond status updates, into coaching, growth, and friction.
Weekly or bi-weekly 1:1s with engineers, tech leads, and managers.
A concise format for communicating progress, risks, blockers, and decisions to stakeholders without burning a half-day to write.
Weekly updates to your manager, cross-functional partners, or execs.
A practical way to evaluate ideas using Reach, Impact, Confidence, and Effort — so trade-offs become explicit instead of political.
Roadmap planning, quarterly bets, and backlog triage.
A blameless post-incident review format focused on learning and prevention. Severity, timeline, contributing factors, and follow-ups that actually ship.
Post-incident reviews for SEV-1 and SEV-2 incidents.
A lightweight way to track delivery, quality, reliability, and team health — the few numbers that change behaviour, not the dashboard that makes you feel productive.
Monthly operating reviews and quarterly health checks.
A framework for helping engineers identify goals, strengths, and growth areas — turning vague career talks into a concrete next step.
Quarterly growth conversations and pre-promotion planning.
A structure for meeting your reports' reports — building trust, surfacing ground-truth signal, without undercutting the manager in between.
Directors and above holding periodic skip-levels with engineers or ICs.
A worksheet for writing performance reviews that are specific, fair, and forward-looking — not a rehash of the last sprint.
Half-year and annual performance reviews.
A humane, rigorous structure for putting someone on a formal improvement plan — clear expectations, fair timeline, and a real chance to succeed.
When informal coaching hasn't closed a sustained performance gap.
A role-specific scorecard that translates a job description into observable signals — so interviewers evaluate the same thing and the debrief is a real decision.
Every open role, before the first candidate hits the loop.
A checklist for designing an interview loop that evaluates the right signals, respects the candidate's time, and produces a decision you can defend.
New roles, new levels, or loops that keep producing weak decisions.
A concrete first-quarter plan that gets a new engineer or manager to real contribution fast — without the ambient anxiety of "figure it out."
Every new hire, but especially senior ICs and new managers.
A one-page document that answers why the team exists, what it owns, how it decides, and how it measures success — so new hires and partners don't have to guess.
New teams, reorged teams, or teams with unclear scope.
A lightweight matrix for naming who's responsible, accountable, consulted, and informed — turning ambiguous decisions into ones that actually get made.
Cross-team initiatives, org design, or any decision that keeps getting relitigated.
A planning template that keeps OKRs to a few outcomes people can actually remember — not a 40-line spreadsheet no one reads.
Quarterly planning at team, department, or org level.
A single-page roadmap that communicates direction, bets, and trade-offs to stakeholders — without pretending you can predict Q3 in July.
Sharing team direction with execs, partner teams, and the team itself.
A retro format that surfaces real friction and produces changes the team can actually feel next sprint — not a wall of stickies no one revisits.
End of every sprint or bi-weekly cycle.
A short, dated record of a significant technical decision — the context, the options considered, the choice, and the consequences.
Any decision the team would regret losing the reasoning behind.
A structured inventory of your team's tech debt with severity, cost of delay, and remediation size — so debt conversations become trade-offs, not moods.
Teams whose 'we need to fix debt' conversations never turn into work.
A checklist for designing an on-call rotation that catches incidents, respects engineers' lives, and produces learning instead of burnout.
New on-call rotations, or old ones producing burnout signals.
A worksheet for defining Service Level Objectives your users would recognize — availability, latency, correctness — with error budgets you'll actually enforce.
User-facing services, especially ones with reliability trade-offs to make.
A pre-launch checklist covering reliability, security, observability, comms, and rollback — so you find the gaps a week before launch, not the morning of.
Any launch big enough that a bad rollout matters.
A kickoff agenda that gets product, design, engineering, and support on the same page in 60 minutes — before the project accumulates its first misunderstanding.
The first meeting of any project spanning more than one team.
A one-page brief that gives an executive everything they need to make a decision in five minutes — situation, options, recommendation, ask.
Getting a decision, budget, or air cover from a busy exec.
A script for the conversations you've been putting off — behaviour feedback, expectation mismatch, boundary-setting — delivered with respect and without ambiguity.
Any conversation you've rehearsed in the shower more than twice.
A framework for deciding what to delegate, to whom, and at what level of autonomy — so you build capability instead of just offloading tasks.
Managers and leads whose calendars are the constraint on the team's growth.
A quarterly audit of where your time and energy actually go — versus where they should go for the role you're being paid to do.
Managers who feel busy but not effective.
A canvas for thinking through a reorg before you announce it — the problem you're solving, the shape you're proposing, the risks, and the rollout.
Any org change big enough that people will talk about it after work.
A matrix for evaluating vendors and build-vs-buy decisions with consistent criteria — cost, fit, risk, and time-to-value.
Any purchase over ~3 months of engineering time.
A tracker that keeps post-incident action items alive after the postmortem meeting — so learnings actually become changes to the system.
Any org that generates action items faster than it ships them.
A weekly, monthly, and quarterly cadence of the meetings and rituals your team actually needs — and permission to delete the rest.
New managers inheriting a team, or leaders whose calendars have quietly filled up.
A short, opinionated statement of how your engineering org makes decisions — written to be usable in a code review, not framed on a wall.
New orgs, post-merger teams, or when culture drift is becoming visible.
A structure for closing candidates with a strong offer conversation — anchored in leveling, transparent on trade-offs, and free of last-minute surprises.
Hiring managers closing mid-to-senior engineers.
Questions that get past the polite reference and toward real signal — how the candidate showed up on their worst week, not their best.
Senior IC and manager hires where the downside of a mis-hire is high.
A written standup template that respects deep work, keeps distributed teams aligned, and surfaces blockers without a 15-minute daily meeting.
Distributed, hybrid, or focus-heavy teams looking to reclaim mornings.
A structured way to review every recurring meeting on your team's calendar — keep, kill, shrink, or move to async — twice a year.
Any team whose calendar has quietly filled with recurrences no one remembers scheduling.
Situation-Behaviour-Impact: a two-minute structure for delivering feedback that lands, works for both reinforcement and course-correction.
Every manager, every week — reinforcing feedback and course-corrections.
The first 30, 60, and 90 days for a newly promoted or newly hired engineering manager — with concrete deliverables at each checkpoint.
First-time managers, or experienced managers joining a new org.
A one-page QBR structure that shows leadership what shipped, what didn't, what you learned, and what you're betting on next — without the 40-slide deck.
Directors and above presenting engineering outcomes to execs each quarter.
A short recurring pulse survey — 8-10 questions — that surfaces trends in engagement, clarity, and trust before they show up as attrition.
Any team lead who wants a leading indicator on culture, not a lagging one.
Leadership lessons, frameworks, and field notes for modern engineering teams. No motivational fluff.
Trouble seeing the form?Subscribe on Beehiiv instead
Free. One email a week. Unsubscribe anytime.