Engineering thread prescribes 10 ETV metric

Bachel J published an engineering management thread on X this week laying out a set of operating metrics for software teams, including a target of 10 “ETV” per developer per month, 75% roadmap alignment and AI spend below $15 per ETV. The post also paired those output measures with two management priorities: psychological safety and tech-debt reduction. A separate X post by Dunya Kirkali earlier this month described a “compass” framework for steering teams, priorities and growth, a phrase that appears to overlap with the management vocabulary in the newer thread. ### What exactly did the X thread prescribe? The Bachel J post listed three numeric targets for what it described as high-performing teams: 10 ETV per developer per month, 75% roadmap alignment and under $15 in AI spend per ETV. The same post said teams should also protect psychological safety and reduce tech debt rather than chase throughput alone. The thread did not, in the material available for review, provide a formal public definition of ETV in the same post preview. (x.com) That leaves the number as a house metric unless the author defines it elsewhere in follow-up posts, replies or linked material. ### Where does the “compass” framework come in? Dunya Kirkali wrote in an earlier X post about a “compass” framework for engineering management, describing it as a way to steer teams, priorities and growth. (x.com) The social briefing tied that post to practical roadmaps and team direction, and the newer Bachel J thread appears to sit in the same discussion about how managers choose a small set of operating measures. The two posts were separate and by different authors. The available material does not show Bachel J explicitly crediting Kirkali in the same source snapshot, so any direct connection between the two should be treated as thematic rather than confirmed collaboration. ### Why are psychological safety and tech debt in the same scorecard? Bachel J’s post put psychological safety and tech-debt reduction alongside delivery metrics, which suggests the thread was not framed as a pure velocity dashboard. (x.com) The author’s wording, as summarized in the source briefing, treated those items as priorities rather than side constraints. (x.com) That combination is common in engineering management discussions because teams that accelerate delivery with unresolved codebase issues or weak internal trust often see slower execution later, though the post itself was presented as advice on X rather than as a research paper or company filing. ### What should readers be careful about in using numbers like 10 ETV? (x.com) The most important caveat is definitional. Because the reviewed source snapshot does not spell out what counts as one ETV, readers cannot compare the target across companies, teams or codebases without more detail from the author. A second caution is organizational context. A team building internal tools, maintaining legacy systems or operating under strict compliance requirements may record very different output and AI-spend patterns than a startup shipping narrow product features. (x.com) The posts on X presented a framework and suggested KPIs, not a universal benchmark backed by disclosed methodology. ### Where can the thread be checked next? The two source posts are on X under Bachel J’s metrics thread and Dunya Kirkali’s “compass” framework post. Any fuller explanation of ETV, roadmap alignment or the AI-spend threshold would most likely appear in the authors’ replies, follow-up posts or linked documents attached to those threads. (x.com)