Find resources to solve your technical leadership challenges
Increment's comprehensive framework for building successful distributed teams through intentional communication, coordination, and culture
Zapier's strategies for maximizing remote team productivity through streamlined communication, flexible schedules, and intentional tool usage
Apple's alternating strategy of revolutionary redesigns followed by incremental refinements in product development cycles
Google's crisis management approach where teams drop everything to intensely focus on solving existential problems through parallel solutions
Fabian Zeindl's hierarchical framework prioritizing build performance and testability as foundations for sustainable feature development
Shai Yallin's balanced perspective arguing that while estimates have limited value, some estimation practices can improve team collaboration
Hacker News community wisdom on defending estimates, managing pushback, and communicating technical complexity to non-technical stakeholders
Shubhro Saha's practical techniques for extracting more accurate estimates through informal questioning and confidence tracking
Honeycomb's approach to replacing unreliable time estimates with flexible delivery rhythms and graduated planning cycles
Gergely Orosz's pragmatic case for estimation as a tool for focus, stakeholder trust, and continuous improvement despite inherent challenges
Ben Kuhn's battle-tested approach: focus intensely (6+ hours daily), maintain detailed victory plans, run fast OODA loops, and overcommunicate
Jason Fried's guide to rescuing failing projects: reduce scope, clarify ownership, communicate honestly, and focus on shipping something valuable
Kevin Sookocheff's guide bridging the gap between engineering and project management with practical frameworks and techniques
Lucas F. Costa uses Little's Law to prove limiting work-in-progress dramatically improves cycle times and team predictability
Gergely Orosz reveals Big Tech secret: engineers lead projects with high autonomy, no Scrum - 'competent people need less structure'
Arbitrary deadlines force engineers to deliver 'Something™ by the Date™' creating chaos and features nobody wants - try parallel experiments instead
DoorDash's Sophia Vicent shares 6 principles for world-class TPM teams: centralized structure, high leverage, fierce prioritization, technical clarity, blameless culture, and organizational recognition
Shift from monolithic projects to 1-3 week milestones that deliver value incrementally and create constant achievement streams
Jacob Kaplan-Moss: estimation is notoriously hard but critical for career advancement - treat it as a learnable skill through practice and reflection
GitLab's DRI model assigns single-person accountability for every decision and project, eliminating confusion about ownership
Gergely Orosz's comprehensive guide for engineers stepping into project leadership: from kickoffs to retrospectives with practical steps
Gergely Orosz's four pillars of efficient project management: clarity from start, directional milestones, ongoing transparency, and proactive dependency management
Martin Fowler explains why Waterfall persists despite fundamental flaws: it seems logical but assumes stable requirements that rarely exist
Jatin questions the obsession with arbitrary deadlines and asks who we're really trying to impress with unrealistic timelines
Dave B's burnout-preventing methodology: 3 weeks on, 1 week off, no death marches, minimal meetings, and developers actually rest
Jon Evans argues JIRA fragments project vision, turning developers into ticket-completing machines who lose sight of the bigger picture
20-year journey through software methodologies reveals they're 'collective fictions' - useful for collaboration but not sacred texts
Thoughtful analysis of deadline effectiveness, distinguishing between helpful constraints and harmful pressure in software development
Quick diagnostic tool to assess project health through critical success factors and early warning indicators
Basecamp's project-centric approach to team organization emphasizing transparency, centralized communication, and flexible team management
Essential principles from Occam's Razor to Hofstadter's Law that reveal software development's human and organizational challenges
LinkedIn's Developer Productivity and Happiness framework for measuring and improving engineering team effectiveness
Toyota's management principles of continuous improvement and respect for people that revolutionized manufacturing and software development
Martin Fowler's analysis of how functional silos create destructive product vs engineering conflicts in scaling companies
How Amazon's 'Working Backwards' process of writing press releases before building products helped AWS reach $11.5B revenue
Inside look at Dropbox's product management scaling strategies and organizational structure evolution
Andrew Chen's analysis of how well-intentioned values like collaboration create self-replicating bureaucracies that kill innovation
Bob Sutton explores how intention and structured boundaries distinguish productive organizational chaos from destructive dysfunction
Bob Sutton and Kathleen Eisenhardt discuss how clear, customized simple rules create liberation not constraint in complex organizations
Joel Spolsky's quick 12-question test for evaluating software team quality and development discipline
John Cutler's three-step framework for decoupling urgency from value to make more objective prioritization decisions
Rich Mironov's analysis of how organizational politics and conflicting stakeholder demands make prioritization more than just spreadsheets
Alex Turek's framework for achieving more by ruthlessly focusing on one priority at a time and saying no to everything else
Information Architects' guide to applying the Five Canons of Rhetoric for powerful presentation design and delivery
Master the art of memorable presentation endings with a simple technique that leaves audiences inspired rather than relieved
Navigate executive presentations successfully with Will Larson's strategies for handling interruptions, staying strategic, and getting decisions
The Columbia disaster case study: how a single cluttered PowerPoint slide contributed to a fatal decision that cost seven lives
Learn the neuroscience and techniques behind compelling storytelling that makes your presentations memorable and persuasive
The stdlib collection is a community-curated library of practical, immediately useful, battle-tested resources for technical leadership. Each resource is designed to be immediately applicable to your role. New resources are added based on community feedback and emerging best practices.