Find resources to solve your technical leadership challenges
A TPM team thrives when it follows six clear principles: strong charter, data-driven metrics, defined career ladders, cross-functional partnership, intentional hiring, and a culture of psychological safety.
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
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
Master the Takahashi Method: using massive text as visuals to create memorable, high-impact presentations without complex graphics
Transform your presentations and documents with 5 simple typography rules that take minutes to learn but make a professional difference
Avoid common OKR pitfalls with 10 battle-tested tips from companies that have successfully scaled with objectives and key results
GitLab's open handbook on OKRs showing how a fully remote company implements and scales objectives and key results transparently
Startups should use lightweight OKRs that split manager-level objectives from maker-level execution, keeping focus and avoiding heavyweight bureaucracy.
50+ real OKR examples across engineering, product, sales, and HR with practical tips for crafting effective objectives and key results
The definitive OKR resource hub with guides, templates, case studies, and tools for successful implementation at any scale
Strip away OKR complexity with a lean approach focusing on what truly matters: outcomes over outputs and continuous learning
Angus Davis's strategies from Swipely for implementing OKRs effectively at startups through collaboration, transparency, and separation from performance reviews
Practical guide to implementing OKRs with templates, examples, and a proven framework for quarterly and annual planning cycles
Replace SMART goals with FAST goals: frequently discussed, ambitious, specific, and transparent for better organizational performance
Pavel Samsono's insights on why low-performing teams choose problems based on what they'd like to solve rather than what customers actually need
Stephen Meszaros's framework for engineers to evaluate product roadmaps through strategic alignment, customer focus, and achievability assessment
Kellan Elliott-McCrea's planning principles for engineering leaders, emphasizing fewer things, avoiding pure bottom-up planning, and framework-driven decision making
Prioritize leading indicators in OKRs to get fast feedback and avoid decisions based only on lagging metrics like revenue or churn.
Product teams should be measured against full business outcomes, even when control is partial, rather than narrow, esoteric metrics like isolated A/B test results.
Visual guide to understanding and implementing Key Performance Indicators with best practices for data visualization and reporting
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.