Skip to main content
Lenny's Podcast

How Block is becoming the most AI-native enterprise in the world | Dhanji R. Prasanna

86 min episode · 2 min read
·
Dhanji R. Prasanna

Episode

86 min

Read time

2 min

Topics

Productivity, Remote Work, Startups

AI-Generated Summary

Key Takeaways

  • Organizational structure drives outcomes: Block shifted from GM-led business units to functional organization where all engineers report to one leader, enabling singular technical focus and AI adoption. This structural change proved more impactful than any individual tool, allowing teams to share platforms, move between projects, and align on technical strategy company-wide.
  • Goose agent delivers measurable productivity: Engineers using Block's open-source AI agent Goose report 8-10 hours saved weekly, with company-wide manual hours savings trending toward 20-25%. The agent uses Model Context Protocol to orchestrate across systems like Snowflake, Tableau, and Git, building features autonomously overnight and opening pull requests without human intervention.
  • Non-technical teams gain most from AI tools: Enterprise risk management, legal, and support teams building their own software tools show the highest productivity gains, compressing weeks of work into hours. This eliminates waiting for internal development teams and enables self-service automation, representing a fundamental shift in who can build software within organizations.
  • Code quality disconnects from product success: YouTube succeeded with videos stored as MySQL blobs and slow Python stack, while Google Video failed despite superior architecture. Engineers should focus on solving user problems rather than refactoring code, as technical excellence doesn't correlate with product-market fit or business outcomes in practice.
  • Future work involves continuous AI operation: LLMs should work overnight and weekends building multiple experimental approaches simultaneously, not sit idle. Engineers will describe several solutions in detail, let AI build them all asynchronously, then evaluate and discard most versions—fundamentally changing from choosing one path to exploring many paths in parallel.

What It Covers

Dhanji Prasanna, CTO of Block, explains how his company became AI-native through organizational restructuring, building the open-source agent Goose, and achieving 20-25% manual hours saved across 3,500 employees while prioritizing technology-first culture.

Key Questions Answered

  • Organizational structure drives outcomes: Block shifted from GM-led business units to functional organization where all engineers report to one leader, enabling singular technical focus and AI adoption. This structural change proved more impactful than any individual tool, allowing teams to share platforms, move between projects, and align on technical strategy company-wide.
  • Goose agent delivers measurable productivity: Engineers using Block's open-source AI agent Goose report 8-10 hours saved weekly, with company-wide manual hours savings trending toward 20-25%. The agent uses Model Context Protocol to orchestrate across systems like Snowflake, Tableau, and Git, building features autonomously overnight and opening pull requests without human intervention.
  • Non-technical teams gain most from AI tools: Enterprise risk management, legal, and support teams building their own software tools show the highest productivity gains, compressing weeks of work into hours. This eliminates waiting for internal development teams and enables self-service automation, representing a fundamental shift in who can build software within organizations.
  • Code quality disconnects from product success: YouTube succeeded with videos stored as MySQL blobs and slow Python stack, while Google Video failed despite superior architecture. Engineers should focus on solving user problems rather than refactoring code, as technical excellence doesn't correlate with product-market fit or business outcomes in practice.
  • Future work involves continuous AI operation: LLMs should work overnight and weekends building multiple experimental approaches simultaneously, not sit idle. Engineers will describe several solutions in detail, let AI build them all asynchronously, then evaluate and discard most versions—fundamentally changing from choosing one path to exploring many paths in parallel.

Notable Moment

One Block engineer has Goose continuously watch his screen and listen to conversations. When he discusses a feature idea with colleagues on Slack, Goose autonomously builds that feature and opens a pull request hours later without explicit instruction, demonstrating autonomous anticipatory development.

Know someone who'd find this useful?

Episode Transcript

There's a lot of talk about productivity gains through AI. There's this camp of people who are, like, so overhyped. Nothing's working. Nobody's actually adopting this at scale. We see a significant amount of gains. We find engineering teams that are very, very AI forward are recording about eight to ten hours save per week. Whenever I hear a stat like this, I think an important element is this is the worst it will ever be. This is now the baseline. The truth is the value is changing every day, so you need to ride that wave along with it. There's a story I heard you share on a different podcast where there's an engineer who has Goose watch him. He'll be talking to a colleague on Slack or an email, and they'll be discussing some feature that they think is useful to implement. Now a few hours later, he'll find that Goose has already tried to build that feature and opened a PR for it on Git. What level of engineer is most benefiting from these tools? What's been surprising and really amazing? The non technical people using AI agents and programming tools to build things. The people that are able to embrace it, to optimize for their particular work day and their particular set of tasks are really showing the most impact from these tools. How do you think things will look in a couple years in terms of how engineers work that's different from today? All these LLMs are sitting idle overnight and on weekends while humans aren't there. Like, there's no need for that. They should be working all the time. They should be trying to build in anticipation of what we want. What's maybe the most counterintuitive lesson you've learned about building products or building teams? A lot of engineers think that code quality is important to building a successful product. The two have nothing to do with each other. Today, my guest is Danji Prasanna, Danji's chief technology officer at Block, where he oversees a team of over 3,500 people. With Danji's leadership, Block has become one of the most AI native large companies in the world and has basically achieved what many eng and product leaders are trying to achieve within their companies. In our conversation, we chat about their internal open source agent called Goose that, by their measure, is saving employees on average eight to ten hours a week of work time, and that number is going up. How AI specifically making their teams more productive and the teams that are benefiting most? Interestingly, it's not the engineering team. What it took to shift the culture to be very AI oriented, the very boring change they made internally that boosted productivity even more than any AI tool, also lessons from building Google Wave and Google Plus and Cash App, and so much more. This episode is for anyone curious to see what a highly AI forward technology driven large company looks …

Get the full transcript (14,955 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all Lenny's Podcast transcripts →

You just read a 3-minute summary of a 83-minute episode.

Get Lenny's Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • GooseRecommendedBy guest

    by Block

    building the open-source agent Goose, and achieving 20-25% manual hours saved across 3,500 employees while prioritizing technology-first culture. ... Block's open-source AI agent Goose report 8-10 hours saved weekly
  • The agent uses Model Context Protocol to orchestrate across systems like Snowflake, Tableau, and Git
  • The agent uses Model Context Protocol to orchestrate across systems like Snowflake, Tableau, and Git
  • The agent uses Model Context Protocol to orchestrate across systems like Snowflake, Tableau, and Git
  • The agent uses Model Context Protocol to orchestrate across systems like Snowflake, Tableau, and Git
  • When he discusses a feature idea with colleagues on Slack, Goose autonomously builds that feature and opens a pull request

More from Lenny's Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Product Management Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Startups & Product Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Lenny's Podcast.

Every Monday, we deliver AI summaries of the latest episodes from Lenny's Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime