<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Role-Design on David R. Longnecker - Converting Coffee to Code</title><link>https://drlongnecker.com/tags/role-design/</link><description>Recent content in Role-Design on David R. Longnecker - Converting Coffee to Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 23 Oct 2026 09:00:00 -0600</lastBuildDate><atom:link href="https://drlongnecker.com/tags/role-design/index.xml" rel="self" type="application/rss+xml"/><item><title>When AI Evals Move to the PM, What Moves Out?</title><link>https://drlongnecker.com/blog/2026/10/pm-role-scope-grows-who-clears-plate/</link><pubDate>Fri, 23 Oct 2026 09:00:00 -0600</pubDate><guid>https://drlongnecker.com/blog/2026/10/pm-role-scope-grows-who-clears-plate/</guid><description>&lt;p&gt;I had coffee recently with two product managers who were spending their afternoons learning to write and score evals. Not data scientists. Not machine learning researchers. Senior product managers.&lt;/p&gt;
&lt;p&gt;They weren&amp;rsquo;t poking at chat prompts for fun. They were knee-deep in trace logs, annotating failure modes, and wrestling with whether a model&amp;rsquo;s summary hallucinated an edge case or merely summarized it aggressively.
With product leaders getting deeper into the muck while working on generative AI products, evaluations have migrated from the research lab directly onto the product desk. What struck me as they described their weeks wasn&amp;rsquo;t that they were taking on the work—they were genuinely engaged by it. What struck me was that nobody had asked what they were putting down to make room for it. Earlier this week I wrote that a team can only absorb so much change at once (&lt;a href="https://drlongnecker.com/blog/2026/10/what-we-stopped-to-make-room"&gt;Capping In-Flight Change&lt;/a&gt;). This is the same constraint at the scale of a single job description.&lt;/p&gt;</description></item></channel></rss>