# A Metric Nobody Else Acts On Is a Diary A DevRel metric earns its place when someone's decision changes because of it, and the decider is usually outside DevRel. Drew Gorton, speaking from five DevTools companies where DevRel was started or restarted (00:08:52), calls evidence the third of four constraints for a team. There's no single clean number for all of DevRel, so track many things, including what the leadership "first team" cares about, such as sign-ups and page views (00:13:13). The test: if a metric never changes a decision, "it's just decoration," and if it doesn't influence the rest of the org, "it's just a diary" (00:14:39). The payoff Gorton names is relational. When the numbers matter to other teams, they propose campaigns that use DevRel content, and DevRel stops nagging for attention (00:13:57). The first-team idea underneath is that a DevRel leader's top priority is the leadership group, not DevRel's own reports (00:06:42), so a metric attaches to the highest company goal available, in the business's language (00:09:35). Joel Lord reaches the same test from education at MongoDB. A good metric "aligns with the rest of the company," and Lord encourages CSMs, sales, and marketers to "make decisions based on" the skill data (00:22:14). A trip report saying "3,000 badge scans" drew "so what" (00:20:03). A dashboard showing an account with no search training changed the agenda for that customer visit and led to a workshop (00:20:47). Two speakers, two programs, one test: not how precise the number is, but who acts on it. The check is runnable. For each metric on the dashboard, name the person or team and the decision that changes between a high and a low reading. No name means it's a diary. This differs from sorting a metric by whether it proves value or locates a page to fix, because here the audience for the decision sits outside DevRel. Where this breaks. Both accounts are anecdote. Gorton's framework comes from experience at five companies with no outcome data (00:08:52), and the Sentry figure of about 70% of spend on brand awareness is second-hand, with a note that it isn't Gorton's story (00:14:39). Lord's account example has no comparison account. A slow metric can inform no decision this quarter and still matter, since DevRel programs can take years to show results. And a metric that only informs DevRel's own choices passes the other job test even if no other team uses it. The captions garble the surname and "Sentry" ("Century"), so I used the corrected forms. <!-- atomicity: 1 idea ✓ --> ## Why This Matters Before the next quarterly review, I'd list every docs or DevRel number I report and write next to each the decision it changes and who makes it. Numbers with no name beside them come off the slide or go to the parked pile. For the ones that survive, I'd show the owner the number before the meeting, so the decision is theirs to make. ## Links - [[3. Resources/Permanent Notes/A Docs Metric Earns Its Place by Naming Which Job It Does]] — extends: that note sorts a metric into proving or improving, and this one adds a decision-owner test where the decider sits outside the docs team. - [[3. Resources/Permanent Notes/A Metric Is Vanity Only Against Your Own Outcome Data]] — contrasts: that note tests a metric against an outcome, this one tests it against a decision; a number can pass one and fail the other. - [[3. Resources/Permanent Notes/DevRel Programs Take Three to Five Years to Show Results]] — constrains: slow-moving outcome metrics may change no decision this quarter yet still belong in the report. - [[3. Resources/Permanent Notes/DevRel Autonomy Requires Leadership Trust Not Just Budget]] — applies-in: attaching metrics to the first team's goals is one way to build the trust that note names as the precondition. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: choosing which metrics a DevRel team keeps. - [[3. Resources/MOCs/Events/DevRelCon NYC 2026 MOC]] — applies-in: measurement cluster, alignment before autonomy. ## Source - [[3. Resources/Readwise/Articles/The Soloist Trap Fixing Autonomy Without Alignment in DevRel — Drew Gorton|The Soloist Trap: Fixing Autonomy Without Alignment in DevRel — Drew Gorton]] - [[3. Resources/Readwise/Articles/Turning Education Signals Into Account Intelligence — Joel Lord|Turning Education Signals into Account Intelligence — Joel Lord]] - https://www.youtube.com/watch?v=tcmG9ZzXyMo