Key Takeaways
1. Build software or risk extinction in the digital age
Build vs. Die is becoming a natural law of business, just as evolution defines organic life on earth.
Digital transformation is imperative. Every industry is rapidly becoming a software industry as customer expectations evolve. Companies that fail to adapt face existential threats from digital disruptors. The ability to build software in-house, rather than just buying off-the-shelf solutions, is becoming a key competitive advantage.
The new software supply chain. Modern software development leverages cloud platforms and microservices, allowing companies to focus on their core differentiators. This "Third Great Era of Software" enables faster innovation and lower costs. Key examples:
- Amazon Web Services (AWS) for computing and storage
- Twilio for communications
- Stripe for payments
Case study: ING Bank. ING transformed from a traditional bank to a software company, building its own contact center system rather than buying a commercial solution. This allowed for rapid iteration, cost savings, and better customer experiences.
2. Understand developers as creative problem-solvers, not just coders
Code is creative.
Developers are artists, not just technicians. Writing software is more akin to creating music or writing a book than doing math or science. The best developers are creative problem-solvers who can translate customer needs into innovative solutions.
Empower developers to solve problems. Instead of giving developers detailed specifications, share customer problems and let them find creative solutions. This approach leads to:
- More innovative products
- Higher job satisfaction
- Better retention of top talent
Examples of developer creativity:
- Instagram: Built by two engineers, sold for $1 billion
- WhatsApp: Created by two developers, sold for $19 billion
- GroupMe: Developed in 18 hours at a hackathon, sold for $80 million
3. Foster a culture of rapid experimentation and learning
Experimentation is the prerequisite to innovation.
Embrace failure as a learning opportunity. Create an environment where teams can take calculated risks without fear of punishment. Celebrate the process of experimentation and learning, not just successful outcomes.
Key principles for effective experimentation:
- Start small and iterate quickly
- Set clear hypotheses and metrics for success
- Learn from failures and pivot as needed
- Share learnings across the organization
Blameless postmortems. When things go wrong, focus on identifying systemic issues rather than blaming individuals. This approach encourages transparency and continuous improvement.
4. Recruit and retain top talent by offering autonomy, mastery, and purpose
It doesn't make sense to hire smart people and tell them what to do. We hire smart people so they can tell us what to do.
Autonomy. Give developers freedom to make decisions and solve problems in their own way. This fosters ownership and creativity.
Mastery. Provide opportunities for continuous learning and skill development. Invest in training, mentorship, and challenging projects.
Purpose. Connect developers' work to meaningful customer impact and broader company mission. Share customer stories and feedback regularly.
Compensation considerations:
- Pay fairly, but don't rely on bonuses as primary motivators
- Offer equity to align long-term interests
- Focus on intrinsic motivators over perks like ping-pong tables
5. Organize into small, empowered teams with clear missions
Small teams and single-threaded leaders help minimize the chances that people find themselves in that third position—disempowered and victimized by decisions they disagree with.
Two-pizza teams. Keep teams small enough to be fed by two pizzas (typically 5-10 people). This reduces communication overhead and increases agility.
Single-threaded leadership. Assign a dedicated leader to each team who is fully focused on that team's mission. This increases accountability and decision-making speed.
Team structure principles:
- Define clear customer, mission, and metrics for each team
- Use "mitosis" to split growing teams while maintaining focus
- Formalize interactions between teams as "service contracts"
6. Prioritize customer empathy and direct developer-customer interaction
Hospitality exists when you believe the other person is on your side.
Wear the customer's shoes. Develop deep empathy for customer needs and pain points. Encourage all team members, including developers, to interact directly with customers.
Break down silos. Avoid treating developers as "code monkeys" isolated from customer feedback. Instead, create opportunities for developers to:
- Participate in customer support
- Attend sales meetings
- Conduct user research
- Build demo applications
Case study: Bunq. The Dutch mobile banking app involves developers directly in customer feedback forums, leading to rapid innovation and high customer satisfaction.
7. Implement Agile methodologies thoughtfully, not dogmatically
Agile isn't the panacea that converts sometimes describe.
Core Agile principles:
- Anticipate and embrace change
- Break work into small, manageable chunks
- Maintain close collaboration between business and developers
Potential pitfalls:
- Overly rigid processes that stifle creativity
- Treating developers like assembly line workers
- Excessive meetings that disrupt flow
Balanced approach: Adopt Agile practices that work for your team, but remain flexible. Focus on outcomes rather than strict adherence to methodology.
8. Invest in robust infrastructure to enable innovation at scale
Great infrastructure is the foundation of innovation.
Importance of infrastructure investment. Allocate significant resources (often 30-50% of R&D budget) to building internal tools, platforms, and processes that make developers more productive.
Key infrastructure investments:
- Continuous integration/continuous deployment (CI/CD) pipelines
- Developer tools and libraries
- Monitoring and observability systems
- Security and compliance frameworks
Case study: Facebook. Investment in release engineering and infrastructure allowed Facebook to "move fast with stable infra," enabling rapid innovation while maintaining reliability.
Last updated:
FAQ
What's Ask Your Developer about?
- Focus on Developers: The book highlights the critical role of software developers in modern businesses, emphasizing that companies must become software builders to thrive in the digital economy.
- Empowerment and Collaboration: It advocates for a shift in mindset where business leaders collaborate with developers, sharing problems instead of dictating solutions to foster creativity and innovation.
- Practical Framework: Jeff Lawson provides a framework for understanding, motivating, and integrating developers' insights into business strategies.
Why should I read Ask Your Developer?
- Relevance Across Industries: As every business becomes digital, this book is essential for leaders in various sectors to understand the role of developers.
- Bridging Gaps: It helps bridge the gap between technical and non-technical teams, promoting better collaboration and understanding.
- Actionable Insights: The book offers practical advice and real-world examples that can be applied immediately to improve organizational effectiveness and innovation.
What are the key takeaways of Ask Your Developer?
- Developers as Key Assets: Developers are not just code writers but creative problem solvers who can drive business success.
- Experimentation is Crucial: Encourages a culture that tolerates failure as a learning opportunity, essential for innovation.
- Empowerment and Autonomy: Leaders should empower developers by sharing problems and allowing them the autonomy to find solutions, leading to better outcomes.
What is the Ask Your Developer mindset?
- Problem Sharing: Involves sharing business problems with developers instead of prescribing solutions, allowing them to leverage their creativity.
- Collaboration Focus: Emphasizes collaboration between business leaders and developers, fostering an environment where both parties can contribute to solutions.
- Encouraging Innovation: By adopting this mindset, organizations can unlock the full potential of their technical talent, leading to innovative products and services.
What does Jeff Lawson mean by "Build vs. Die"?
- Survival of the Fittest: Companies must learn to build software to survive in a rapidly changing digital landscape, akin to Darwinian evolution.
- Shift from Cost Center: IT has shifted from being a cost center to a strategic asset that drives competitive advantage.
- Necessity of Building: Businesses that fail to adapt and build their own software will ultimately become obsolete.
How does Ask Your Developer define the new software supply chain?
- Component-Based Approach: Describes a shift from monolithic software solutions to a supply chain of reusable components, primarily through APIs.
- Specialization: Companies can specialize in their core competencies while leveraging third-party services for other functionalities, enhancing efficiency.
- Third Great Era of Software: This new approach allows businesses to build applications faster and more flexibly than ever before.
What are the best quotes from Ask Your Developer and what do they mean?
- "If you want to build a ship...": Emphasizes inspiring developers to pursue their passions and creativity rather than just following orders.
- "It is not the strongest species...": Highlights the necessity for businesses to adapt quickly to survive in the digital age.
- "Code is creative.": Underscores the idea that software development is an art form, requiring creativity and innovation, not just technical skills.
How can I motivate my developers according to Ask Your Developer?
- Empowerment: Give developers the autonomy to solve problems creatively, fostering a sense of ownership and engagement.
- Recognition of Creativity: Acknowledge that coding is a creative process and provide opportunities for developers to express their creativity in their work.
- Encourage Experimentation: Create a culture that tolerates failure and encourages experimentation, allowing developers to learn and innovate without fear of repercussions.
How does Ask Your Developer define autonomy for developers?
- Empowerment to Make Decisions: Autonomy allows developers to make decisions without constant oversight, fostering innovation and ownership.
- Guardrails for Guidance: While autonomy is important, it should be balanced with some rules or guardrails to help developers navigate complex environments.
- Influence in Key Decisions: Inviting developers to participate in significant decisions shows that their expertise is valued, enhancing their commitment to the company's goals.
What is the significance of mastery in Ask Your Developer?
- Continuous Learning: Mastery involves the desire for developers to continually improve their skills and knowledge, attracting and retaining top talent.
- Mentorship Importance: Mentorship helps developers achieve mastery, accelerating their professional development and enhancing team performance.
- Soft Skills Matter: Mastery includes developing soft skills like communication and collaboration, crucial for success in team environments.
How does Ask Your Developer suggest creating a culture of purpose?
- Connecting Work to Impact: Developers want their work to matter; leaders should articulate how their contributions align with the company's mission.
- Celebrating Successes: Recognizing and celebrating the impact of developers' work can reinforce their sense of purpose.
- Involving Developers in Decision-Making: Including developers in strategic discussions enhances their sense of purpose and motivation.
How does Ask Your Developer recommend fostering collaboration between developers and business leaders?
- Open Communication Channels: Establish clear communication channels between developers and business leaders, including regular check-ins and collaborative planning sessions.
- Involving Developers in Customer Interactions: Encouraging developers to engage directly with customers enhances their understanding of customer needs.
- Shared Goals and Metrics: Aligning on shared goals and metrics helps bridge the gap between technical and business teams, making collaboration more effective.
Review Summary
Ask Your Developer receives mostly positive reviews, praised for its insights on leveraging developers in business and creating environments where they can thrive. Readers appreciate the practical advice, real-world examples, and focus on innovation. Many find it valuable for executives and non-technical leaders to understand software development's importance. Some criticize the book for being too basic for experienced tech professionals or overly promotional of Twilio. Overall, it's considered a useful guide for companies adapting to the digital economy.
Similar Books










Download PDF
Download EPUB
.epub
digital book format is ideal for reading ebooks on phones, tablets, and e-readers.