Staff‑to‑head 90‑day playbook
- A playbook was shared detailing the first 90 days for leaders inheriting engineering teams, with practical transition steps. - It recommends structured leadership reviews, stakeholder mapping, quick wins, and clear communication rhythms as early priorities. - The playbook is pitched as a checklist to stabilise teams and surface risks during leadership handovers. (x.com)
A short leadership thread on X has turned a familiar management idea into a practical engineering checklist: what to do in the first 90 days after inheriting a team. (x.com) The post points readers to a playbook for leaders stepping into an existing engineering org, not building one from scratch. Its early moves center on reviewing the leadership bench, mapping stakeholders, logging risks, and finding a few quick fixes without overhauling everything at once. (thegarnetwiki.com) That sequence matches a long-running leadership-transition framework popularized by Michael Watkins in *The First 90 Days*, which Harvard Business Review describes as a guide for getting up to speed quickly in a new role. Harvard Business School’s research summary says a leader’s first months have an outsized effect on eventual success or failure. (hbr.org) (hbs.edu) The engineering version is more specific about the handoff problems new managers face. A new head of engineering can inherit unresolved incidents, unclear service ownership, open hiring gaps, and cross-functional conflicts long before they touch architecture or roadmaps. (leadshift.dev) (lethain.com) That is why stakeholder mapping shows up so early in these playbooks. Engineering Manager Tools describes it as a way to identify people who can block releases, redirect priorities, or control budgets, especially during transitions and reorganizations. (em-tools.io) The other recurring theme is restraint. Will Larson, writing about the first 90 days for a Chief Technology Officer or vice president of engineering, says the standard advice is heavy on learning first and warns against rushing to “show value” before understanding how the business works. (lethain.com) In practice, that pushes new leaders toward operating rhythms rather than big restructures. The playbook format emphasizes one-on-ones, regular check-ins, shared status updates, and a visible risk register so teams know what is changing, what is staying put, and who owns the next decision. (thegarnetwiki.com) (leadshift.dev) The appeal of a checklist is that leadership handovers are messy even when the strategy is not. A 90-day plan cannot solve product-market fit or staffing shortages, but it can make the first quarter less opaque for the people already shipping the software. (hbs.edu) (thegarnetwiki.com)
