David Singleton

Chief Technology Officer

Stripe

🔍 User Research (1)🎯 Product Strategy (1)🚀 Career & Leadership (1)

Key Takeaways

1.Hire product-minded engineers who want to understand the 'why' and talk to users, allowing you to delay hiring dedicated PMs until scale demands it.
2.Operationalize 'Meticulous Craft' by linking error messages directly to documentation—a small detail that creates a massive competitive advantage.
3.Use 'Friction Logging' not just for bugs, but to document the emotional and tactical resistance a user feels during a specific workflow.
4.Leaders must practice 'Engineerications'—taking 3-4 days off management duties to push code to production—to truly understand developer velocity and toolchain friction.
5.Reliability does not require slowness; achieve velocity via automated testing that runs in parallel with code review and auto-deploys within 45 minutes.
6.Adopt the 'Inverted W' planning process: Teams submit ideas (bottom-up), leaders synthesize strategy (top-down), teams validate impact (bottom-up), leaders finalize (top-down).
7.Co-create complex products with a small set of 'Alpha' users via shared Slack channels, rather than building in isolation.

Methodologies(3)

The Friction Logging Protocol

by David Singleton

🔍 User Research

A disciplined practice where a team member (often a PM or Leader) simulates a specific user persona to complete a core task, recording every moment of hesitation, confusion, or delight.

Core Principles

1.Select a specific Persona: Do not just 'test.' Adopt a mental model (e.g., 'I am a developer at Atlassian trying to integrate Billing').
2.Stream of Consciousness: Write down thoughts in real-time. Note where you get stuck, what feels slow, and what is confusing.
3.Full Stack Audit: Don't stop at the UI. Open the docs, use the API, and write the code required to finish the task.
+2 more...

"You need to put yourself in a particular user's shoes. It's actually important to have a very clear idea of who is the person I am kind of modeling the friction for right now."

#friction#logging#protocol

View Deep Dive →

The Co-Creation Alpha Loop

by David Singleton

🎯 Product Strategy

Instead of building in stealth, identify a small cohort of users pushing the boundaries of the problem space and build the product alongside them with high-touch interaction.

Core Principles

1.Identify 'Boundary Pushers': Find existing users who are hacking your current product to do things it wasn't designed for.
2.Shared Infrastructure: creating shared Slack channels between your engineers/PMs and the customer's team.
3.Continuous Exposure: Show them incomplete product/code on a regular basis, not just at milestones.
+2 more...

"We decided to co-create the product with them... And only when that original kind of Alpha group was super, super happy with the product did we then think it might be ready to go to a broader audience."

#co-creation#alpha#strategy

View Deep Dive →

The Engineercation Loop

by David Singleton

🚀 Career & Leadership

A management practice where leaders clear their schedule to act as an Individual Contributor (IC) for a set period, pushing actual code to production.

Core Principles

1.Clear the Calendar: Block 3-4 days entirely. Treat it like a vacation from management duties—decline all meetings.
2.Find a Buddy: Pair with an existing engineer on the team who can guide you through setup and review your PRs without bias.
3.Ship Real Value: Pick a small but complete task (a feature or fix) that goes all the way to production.
+2 more...

"I'll clear several days... join a team, pick up a small task, hopefully a small feature that we can get all the way from start to finish in production and do that going through the exact experience the team has."

#engineercation#career#leadership

View Deep Dive →