engineering-culture
Build strong engineering culture using frameworks from 19 product leaders.
- Diagnose current state across team size, practices, and pain points, then identify bottlenecks in developer experience, org structure, talent, or process
- Core principle: Conway's Law means organizational structure directly dictates architecture and product quality; align teams to desired outcomes
- DevEx is foundational; optimize for flow state, cognitive load, and feedback loops rather than toolchain selection
- High-talent density reduces process overhead; pair programming is underutilized for knowledge transfer and finding elegant solutions
- Optimize for "clock speed" through frequent experimentation and shipping; require all functions to engage directly with engineering tools and workflows
Engineering Culture
Help the user build strong engineering culture using frameworks from 19 product leaders who have built high-performing engineering organizations.
How to Help
When the user asks for help with engineering culture:
- Diagnose the current state - Understand their team size, practices, and pain points
- Identify the bottleneck - Determine if the issue is DevEx, org structure, talent, or process
- Design for the right outcomes - Focus on speed, stability, and developer satisfaction
- Balance structure with autonomy - Help calibrate how much process is needed
Core Principles
DevOps is capabilities, not tools
Nicole Forsgren: "DevOps is not a toolchain you buy. Marketing teams labeled toolchains DevOps because they wanted your money. DevOps is a set of capabilities - technical capabilities, architectural capabilities, cultural capabilities, and lean management practices." Focus on integrated capabilities, not just implementing specific tools.
Conway's Law is powerful
More from refoundai/lenny-skills
personal-productivity
Help users manage their time and tasks more effectively. Use when someone is overwhelmed with work, struggling with focus, trying to balance multiple responsibilities, or asking how to get more done.
4.6Kcompetitive-analysis
Help users understand and respond to competition. Use when someone is positioning against competitors, evaluating market threats, running competitive war games, or deciding how much to focus on competitors versus customers.
1.9Kbrand-storytelling
Help users craft compelling brand narratives. Use when someone is defining brand strategy, writing company positioning, creating pitch narratives, developing messaging frameworks, or trying to make their company story more memorable.
1.8Kwriting-prds
Help users write effective PRDs. Use when someone is documenting product requirements, preparing specs for engineering, writing feature briefs, or defining what to build for their team.
1.7Kcontent-marketing
Help users build content marketing strategies. Use when someone is starting a blog, building SEO, creating thought leadership content, or deciding on content formats and distribution channels.
1.7Kvibe-coding
Help users build software using AI coding tools. Use when someone is using AI to generate code, building prototypes without deep technical skills, or exploring how non-engineers can create functional software through natural language.
1.7K