Tammuz Dubnov - When Our PM Started Writing Code: What Merge Rate Taught Us About AI Adoption - AI N
The shift toward 'AI native' organizations means that the primary bottleneck is no longer code generation speed but organizational alignment and handoff efficiency. The speaker argues that empowering non-technical decision-makers (PMs, Designers) with agentic tools allows them to execute work directly, collapsing gaps that previously required multiple sprints or lengthy coordination. Success in this transition is measured by the 'merge rate'—the percentage of Pull Requests (PRs) opened by non-technical users that successfully land in production.
Key takeaways
-
Redefining AI Native
2:00
AI native means that the person who cares about a feature has the authority and ability to execute the work, collapsing the traditional handover gap between PMs/Designers and Developers. The bottleneck shifts from coding speed to decision-making capacity.
-
The Importance of Merge Rate
6:00
Merge rate (the percentage of PRs that land in production) is the key metric for measuring if an organization is successfully adapting to AI-driven workflows. A high merge rate indicates trust and quality between non-technical contributions and the dev team.
-
The Role of Guards and Architecture
11:20
As organizations move fast, it is critical not to abandon engineering principles or 'guards' (like testing, architectural standards). The agent must be designed to learn the codebase deeply and maintain these constraints.
-
Measuring Non-Technical Contributions
14:20
To measure impact, track: 1) Count of PRs opened by non-technical individuals. 2) Merge rate (e.g., an average merge rate of 74% was cited). 3) Percentage of merged PRs that require zero developer intervention.