Tammuz Dubnov

When Our PM Started Writing Code: What Merge Rate Taught Us About AI Adoption

In early 2026, our PM started opening pull requests to our production codebase. Not prototypes — real, merged code. This talk is about what that demanded from the engineering team, and from the PM herself.

AI didn't eliminate our bottleneck — it moved it. Code generation stopped being the constraint. Review, coordination, and architectural alignment became the new pressure points. Merge rate — the percentage of PRs that actually land in production — became the signal that told us whether the team was adapting or drowning.

Getting there required change on both sides. Engineers had to rethink how they review, what they gate on, and how much bandwidth they allocate. The PM had to learn which changes she could ship independently and which required coordination first. Neither side got it right immediately.

Once we found that alignment, the effect compounded. Features that used to take a full sprint now land in days. Entire product areas are owned end-to-end by the PM. The developers freed from feature delivery work at a higher level — focused on architecture, patterns, and system design. The team didn't just absorb the change. It got faster because of it.

I'll share the real data, the process breakdowns, and what we changed — from the CTO's chair.