Clarity Over Tooling: Velocity & Building Teams Without Drama with Loïc Houssier // CTO @ Superhuman Mail
From acquisition carve-outs to 100ms interaction rules: Engineering velocity through team clarity, not tool proliferation
Loïc Houssier
What drives execution velocity—better tools or better clarity? Loïc Houssier, CTO of Superhuman Mail (post-Grammarly acquisition), argues that most velocity problems stem from unclear team missions, not inadequate tooling. He shares hard-won lessons from steering DocuSign's French acquisition through complex carve-out negotiations and building Superhuman's offline-first architecture with a 100-millisecond interaction rule. Loïc discusses engineering metrics that actually matter (PR per engineer per week trends over absolutes), when to resist microservices (until it's genuinely painful), and why promotion frameworks determine product quality. Technical leaders will learn how vertical team alignment eliminates dependencies, why guild structures maintain consistency without blocking speed, and how European safety nets create underappreciated opportunities for technical risk-taking.
Show notes.
TOPdesk: Discover the future of internal IT in the DACH region with the "Inside ITSM 2026" report – featuring exclusive data on AI, DEX, and collaboration from 6,000 IT professionals. Download the report here
How do you maintain execution velocity while building quality products? Loïc Houssier (CTO of Superhuman Mail) argues that most velocity problems stem from unclear team missions, not inadequate tooling.
Loïc brings a unique perspective on technical leadership, drawing from his time at French defense contractors, his role in DocuSign's complex acquisition, and his current work leading Superhuman through its Grammarly acquisition.
Key insights for engineering leaders:
- The "Less Bad" Metric: Why tracking "PRs per engineer per week" trends is better than absolute metrics for measuring velocity.
- Monorepo Philosophy: Why you should resist microservices until the pain is undeniable, and how Moduliths reduce complexity.
- The 100ms Rule: Superhuman's strict requirement that every UI interaction completes in under 100ms, driving their offline-first architecture.
- Vertical Alignment: Organizing teams around experiences (e.g., "Compose", "Calendar") to eliminate cross-team dependencies.
- Promotion & Quality: How your promotion framework implicitly defines your product quality (if you don't promote for quality, you won't get it).
- Acquisition Survival: Lessons from the DocuSign/French government carve-out and how execution protects teams during mergers.
- Framework Skepticism: Why copying Spotify or GitLab models often fails without the underlying context.
Chapters:
[00:51] Superhuman, Grammarly, and the rebrand to Superhuman Mail [09:53] DocuSign's French acquisition: Navigating labor law and Ministry of Finance approvals [12:16] Execution velocity: Getting shit done fast as a competitive advantage [18:58] PR per engineer per week: The "less bad" velocity metric [24:22] Monorepo philosophy: Resist microservices until it's genuinely painful [32:30] Guild structure: Formalizing existing technical conversations [42:05] 100-millisecond rule: Offline-first architecture for instant interactions [48:38] Promotion frameworks determine product quality