🧭 Engineering Leadership · Staff+ Operating Models
Write tech strategy documents that get funded
Current-state honesty, bets with falsifiable outcomes, and resourcing asks tied to business narratives.
advanced~50 minEngineering ManagersTech LeadsStaff Engineers
Steps
- 1Open with business context in executives' language, quantified pressure points
- 2Present 2-3 strategic bets with explicit what-we-stop-doing tradeoffs
- 3Each bet carries success metrics + review date + kill criteria upfront
- 4Resource ask maps line-items to bets; no orphan headcount requests
- 5Circulate draft to skeptics privately first; incorporate visibly
- 6Present decisions needed today separately from information-only sections
Common Pitfalls
- ▲Technology-first documents searching for a business rationale
- ▲Everything-priority strategies funding nothing
Commands
Install with skills CLI
$ npx skills add aniruddhaadak80/skills --skill staff-plus-track-tech-strategy-doc-craftInstall globally
$ npx skills add aniruddhaadak80/skills --skill staff-plus-track-tech-strategy-doc-craft -gTags
#strategy#writing#planning#engineering-leadership#staff-plus-track