By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
Lenny's PodcastThe GitLab way: Kindness, transparency, and short toes | David DeSanto (CPO)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Inside GitLab: Radical transparency, remote culture, and product at scale
- GitLab CPO David DeSanto discusses how GitLab operationalizes extreme transparency through public meeting recordings, an open handbook, and a public issue tracker, and how this fuels community contribution and customer trust.
- He explains GitLab’s cultural values—kindness, short toes, assuming positive intent, and results-focus—and how they enable a fully remote, async-first company of 2,000+ people to function effectively across 60+ countries.
- DeSanto shares practical guidance on making remote work succeed (outcomes over hours, overcommunication, clear written requirements, and periodic in‑person time), plus how GitLab evolved from breadth-over-depth product strategy to deepening key areas of its DevSecOps platform.
- He also outlines GitLab’s AI principles—full lifecycle coverage, privacy-first, and using the right model for each use case—and how GitLab Duo aims to materially increase productivity without compromising customers’ intellectual property.
IDEAS WORTH REMEMBERING
5 ideasTransparency can be an execution advantage, not a competitive risk.
By publicly sharing team meetings, their handbook, roadmap, and issue tracker, GitLab attracts community contributions, builds trust with customers, and reduces internal silos—while relying on fast execution (12 releases a year for 12+ years) as the real moat.
Codified values are essential for making remote and transparency work.
Values like kindness, assuming positive intent, short toes (not personalizing feedback), and “negative feedback is one-on-one” reduce conflict and misinterpretation in an async, text-heavy environment and make high transparency psychologically sustainable.
Remote success requires clear writing, overcommunication, and async-first habits.
GitLab expects PMs to write crisp requirements, use issues as the single source of truth, document decisions in the handbook, default to async communication, and only escalate to meetings (e.g., Zoom) when written back-and-forth stalls.
Focus on outcomes and adoption, not tasks and hours.
Instead of measuring success by features shipped or bugs closed, GitLab encourages outcome metrics (e.g., percentage of customers using a feature) and sees “celebrate adoption, not shipping” as key to both remote management and better product decisions.
Use breadth-over-depth early to find your platform edges, then go deep where it matters.
GitLab initially expanded broadly across the DevSecOps lifecycle to discover where it could truly differentiate, then pivoted to depth in core areas like SCM, CI/CD, security, planning, and AI, letting adjacent areas benefit from the platform halo.
WORDS WORTH SAVING
5 quotesIf everyone's really annoyed at you, you're probably actually doing your job well.
— David DeSanto
It's about the work, it's not about you.
— David DeSanto (on the value of having 'short toes')
Sometimes it's actually a lot easier to be transparent than it is to not be transparent.
— David DeSanto
You can't be as transparent as we are without having our values, and you can't have our values unless you’re putting them into a remote work environment.
— David DeSanto
It's just software, so anything's possible.
— David DeSanto
High quality AI-generated summary created from speaker-labeled transcript.
