[{"data":1,"prerenderedAt":495},["ShallowReactive",2],{"navigation":3,"/blog/025-when-measurement-becomes-the-job":110,"/blog/025-when-measurement-becomes-the-job-surround":491},[4],{"title":5,"path":6,"stem":7,"children":8,"page":109},"Blog","/blog","blog",[9,13,17,21,25,29,33,37,41,45,49,53,57,61,65,69,73,77,81,85,89,93,97,101,105],{"title":10,"path":11,"stem":12},"Why Most Small Businesses Don’t Need Digital Transformation — They Need Clarity","/blog/001-no-digital-transformation","blog/001-no-digital-transformation",{"title":14,"path":15,"stem":16},"Building the Right Thing First: A Senior Architect’s Approach to Small Projects","/blog/002-building-the-right-thing-first","blog/002-building-the-right-thing-first",{"title":18,"path":19,"stem":20},"Practical AI for Real Businesses (Specific Recommendations That Actually Work)","/blog/003-practical-ai-for-real-businesses","blog/003-practical-ai-for-real-businesses",{"title":22,"path":23,"stem":24},"Practical Technology Guidance for Small Businesses in North Texas","/blog/004-practical-technology-guidance","blog/004-practical-technology-guidance",{"title":26,"path":27,"stem":28},"Modern SEO — Optimizing for Humans and AI","/blog/005-modern-seo-optimizing-for-humans-and-ai","blog/005-modern-seo-optimizing-for-humans-and-ai",{"title":30,"path":31,"stem":32},"The Hidden Cost of “Cheap” Software for Small Businesses — When Saving Money Becomes Expensive","/blog/006-the-hidden-cost-of-cheap-software","blog/006-the-hidden-cost-of-cheap-software",{"title":34,"path":35,"stem":36},"Modernization Without Mayhem — Replacing Legacy Systems Incrementally","/blog/007-modernization-without-mayhem","blog/007-modernization-without-mayhem",{"title":38,"path":39,"stem":40},"Small Studio, Serious Work — How Boutique Teams Deliver Government-Grade Software","/blog/008-small-studio-serious-work","blog/008-small-studio-serious-work",{"title":42,"path":43,"stem":44},"When a Small Business Should (and Shouldn’t) Build Custom Software","/blog/009-when-to-build-custom-software","blog/009-when-to-build-custom-software",{"title":46,"path":47,"stem":48},"Common AI Uses for Small Business — Tools That Actually Work","/blog/010-common-ai-uses-small-business","blog/010-common-ai-uses-small-business",{"title":50,"path":51,"stem":52},"What Government Software Projects Fail At — And How to Avoid Repeating Those Mistakes","/blog/011-government-software-failures","blog/011-government-software-failures",{"title":54,"path":55,"stem":56},"The High Cost of Cool — Why Boring Tech Wins","/blog/012-high-cost-of-cool","blog/012-high-cost-of-cool",{"title":58,"path":59,"stem":60},"Decomposing Legacy Monoliths — A Practical Strategy","/blog/013-decomposing-legacy-monoliths","blog/013-decomposing-legacy-monoliths",{"title":62,"path":63,"stem":64},"The State of AI Augmentation — Doing More With The Team You Have","/blog/014-state-of-ai-augmentation","blog/014-state-of-ai-augmentation",{"title":66,"path":67,"stem":68},"Co-Intelligence: Working With AI Instead of Just Using It","/blog/015-entering-era-of-cointelligence","blog/015-entering-era-of-cointelligence",{"title":70,"path":71,"stem":72},"Beyond Shooting From the Hip: Designing a Content Strategy That Scales","/blog/016-scaling-digital-content-strategy","blog/016-scaling-digital-content-strategy",{"title":74,"path":75,"stem":76},"Fewer, Better Local Relationships — How to Choose Community Partners That Actually Help Your Business","/blog/017-local-resources-community-impact","blog/017-local-resources-community-impact",{"title":78,"path":79,"stem":80},"How Small Technical Teams Turn Delivery Problems Into Shared Capability","/blog/018-level-up-technical-teams","blog/018-level-up-technical-teams",{"title":82,"path":83,"stem":84},"Document the Parts of Your System People Need to Operate and Hand Off","/blog/019-modern-software-documentation","blog/019-modern-software-documentation",{"title":86,"path":87,"stem":88},"Your Software Has No Owner's Manual -- That's Why Your Team Is Afraid to Touch It","/blog/020-software-has-no-owners-manual","blog/020-software-has-no-owners-manual",{"title":90,"path":91,"stem":92},"The Hidden Cost of \"We'll Figure It Out Later\" Architecture — You Already Have Architecture. It's Just Accidental.","/blog/021-hidden-cost-of-well-figure-it-out-later-architecture","blog/021-hidden-cost-of-well-figure-it-out-later-architecture",{"title":94,"path":95,"stem":96},"Skilling Up vs Calling an Expert — Teach Repeat Work, Buy Judgment for High-Risk Work","/blog/022-skilling-up-vs-calling-an-expert","blog/022-skilling-up-vs-calling-an-expert",{"title":98,"path":99,"stem":100},"The 3 Levels of AI Adoption — And Where You Probably Are","/blog/023-the-3-levels-of-ai-adoption","blog/023-the-3-levels-of-ai-adoption",{"title":102,"path":103,"stem":104},"The Missing Layer Before AI: Your Business Has to Be Reachable by Software First","/blog/024-the-missing-layer-before-ai","blog/024-the-missing-layer-before-ai",{"title":106,"path":107,"stem":108},"When Measurement Becomes the Job — Escaping Goodhart's Law","/blog/025-when-measurement-becomes-the-job","blog/025-when-measurement-becomes-the-job",false,{"id":111,"title":106,"author":112,"body":116,"date":482,"description":483,"extension":484,"image":485,"meta":486,"minRead":487,"navigation":488,"path":107,"seo":489,"stem":108,"__hash__":490},"blog/blog/025-when-measurement-becomes-the-job.md",{"name":113,"avatar":114},"Bo Clifton",{"src":115,"alt":113},"bo-avatar.jpg",{"type":117,"value":118,"toc":471},"minimark",[119,123,140,143,148,156,163,169,172,180,184,187,209,212,215,218,222,225,228,280,283,286,289,292,295,299,302,335,338,342,345,348,403,406,410,413,458,462,465,468],[120,121,122],"p",{},"A metric is useful when it helps you make a better decision. It becomes harmful when people optimize the number instead of the work it was meant to represent.",[120,124,125,126,133,134,139],{},"That is the practical problem behind Goodhart's Law. In his 1975 paper, later published by Springer as ",[127,128,132],"a",{"href":129,"rel":130},"https://link.springer.com/chapter/10.1007/978-1-349-17295-5_4",[131],"nofollow","\"Problems of Monetary Management: The U.K. Experience\"",", Charles Goodhart wrote about statistical regularities breaking down when they are used for control. The familiar line, \"when a measure becomes a target, it ceases to be a good measure,\" is a useful paraphrase, not a direct quote. For a lighter introduction to the law itself, see ",[127,135,138],{"href":136,"rel":137},"https://en.wikipedia.org/wiki/Goodhart%27s_law",[131],"Wikipedia's Goodhart's law page",".",[120,141,142],{},"You do not need a data team or a new dashboard to avoid this problem. Start with a shared spreadsheet or the tracker you already use. Choose three things: one decision you need to make, one outcome signal that tells you whether it helped, and one guardrail that tells you when to stop.",[144,145,147],"h2",{"id":146},"separate-outcomes-proxies-and-targets","Separate outcomes, proxies, and targets",[120,149,150,151,155],{},"An ",[152,153,154],"strong",{},"outcome"," is the result you care about: customers get correct answers, releases are dependable, or a support team resolves requests without unnecessary delay.",[120,157,158,159,162],{},"A ",[152,160,161],{},"proxy"," is an observable signal that may help you judge that outcome. First-response time, reopened tickets, deployment frequency, or time spent reviewing a draft can all be useful proxies.",[120,164,158,165,168],{},[152,166,167],{},"target"," is what happens when you attach a threshold, reward, deadline, or management pressure to the proxy.",[120,170,171],{},"The distinction matters because proxies are incomplete. If you set a target of closing more tickets, people can close tickets quickly and leave customers to reopen them. If you reward story points completed, a team can split work into smaller estimates or choose easy work. If you require more AI-drafted replies, people can send weak drafts just to meet the count. The incentive changes the work.",[120,173,174,179],{},[127,175,178],{"href":176,"rel":177},"https://www.infoworld.com/article/4195756/from-story-points-to-tokenmaxxing-why-engineering-keeps-measuring-the-wrong-things.html",[131],"InfoWorld's discussion of story points and \"tokenmaxxing\""," is a useful prompt to examine your own incentives. It is not evidence that every engineering metric is broken. Ask: what behavior would this target reward, even if it doesn't improve the result you want?",[144,181,183],{"id":182},"make-the-delivery-example-concrete","Make the delivery example concrete",[120,185,186],{},"Suppose your delivery lead wants work to move through the backlog faster.",[188,189,190,197,203],"ul",{},[191,192,193,196],"li",{},[152,194,195],{},"Incentive:"," recognize teams for completing more story points each sprint.",[191,198,199,202],{},[152,200,201],{},"Outcome:"," customers receive useful, reliable changes on the agreed priority.",[191,204,205,208],{},[152,206,207],{},"Guardrail:"," track production defects and customer-reported regressions for released work.",[120,210,211],{},"Story points can still help a team plan a sprint. They should not become a cross-team performance score. Once compensation, comparison, or pressure attaches to them, teams have a reason to make estimates look good rather than make delivery better.",[120,213,214],{},"The same applies to ticket counts, pull-request counts, lines of code, and individual \"flow\" scores. Do not build a universal productivity score, use metrics to surveil people, or rank individuals by work-item throughput. Software work varies too much in ambiguity, risk, maintenance burden, and collaboration to make those comparisons fair or useful.",[120,216,217],{},"Use team-level measures to improve a system. Use manager judgment, customer context, and direct review for people decisions.",[144,219,221],{"id":220},"run-a-reversible-ai-support-reply-pilot","Run a reversible AI support-reply pilot",[120,223,224],{},"AI support drafting is a good place to practice disciplined measurement because the work has visible inputs, a human review step, and a clear fallback.",[120,226,227],{},"Run this pilot through your existing help desk and a shared spreadsheet:",[229,230,231,256],"table",{},[232,233,234],"thead",{},[235,236,237,241,244,247,250,253],"tr",{},[238,239,240],"th",{},"Outcome",[238,242,243],{},"Proxy",[238,245,246],{},"Guardrail",[238,248,249],{},"Sample",[238,251,252],{},"Owner",[238,254,255],{},"Stop condition",[257,258,259],"tbody",{},[235,260,261,265,268,271,274,277],{},[262,263,264],"td",{},"Customers receive accurate, timely order-status replies",[262,266,267],{},"Median human minutes to review and send an eligible reply",[262,269,270],{},"Any material factual error in review, or two customer corrections tied to drafts in one week",[262,272,273],{},"Review 10 drafted replies each week, chosen across eligible cases",[262,275,276],{},"Support lead",[262,278,279],{},"Pause drafting, return to manual replies, and review the failure before restarting",[120,281,282],{},"Start with a baseline. For five business days, record the normal review-and-send time for eligible tickets, plus corrections and escalations. Do not claim improvement until you have something comparable.",[120,284,285],{},"Define eligible cases narrowly: new email tickets asking only for order status, where the order number is present and the order system shows a current status. Exclude refunds, cancellations, delivery disputes, account changes, threats of legal action, complaints, VIP handling, and any ticket without a clear record.",[120,287,288],{},"For two weeks or a set volume such as 50 eligible tickets, let the tool draft a reply using approved order data. A support agent must check the facts and send every reply. The tool does not send messages, change orders, issue refunds, or make promises.",[120,290,291],{},"The support lead owns the pilot, reviews the weekly sample, records corrections, and decides whether to continue. If the stop condition is met, pause immediately. Keep the manual process available throughout. That makes the test reversible.",[120,293,294],{},"The goal is not \"maximize AI usage.\" The decision is whether drafting saves reviewer time without increasing customer harm. One outcome signal and one guardrail are enough for that decision.",[144,296,298],{"id":297},"audit-a-metric-before-you-target-it","Audit a metric before you target it",[120,300,301],{},"Before a proxy becomes a target, spend 10 minutes answering these questions in writing:",[303,304,305,308,311,314,317,320,323,326,329,332],"ol",{},[191,306,307],{},"What decision will this number change in the next month?",[191,309,310],{},"What outcome are we trying to improve?",[191,312,313],{},"Why is this proxy connected to that outcome?",[191,315,316],{},"What important quality, risk, or cost does it fail to show?",[191,318,319],{},"How could a reasonable person improve this number without improving the outcome?",[191,321,322],{},"What incentive will the target create?",[191,324,325],{},"What guardrail would reveal harm early?",[191,327,328],{},"Who owns interpreting the result and acting on it?",[191,330,331],{},"What result would make us pause, change, or retire the measure?",[191,333,334],{},"When will we review whether this metric is still useful?",[120,336,337],{},"If you cannot write clear answers, keep the number as context, not a target.",[144,339,341],{"id":340},"keep-a-decision-log-not-a-reporting-ritual","Keep a decision log, not a reporting ritual",[120,343,344],{},"A decision log is for decisions with tradeoffs: whether to continue a pilot, change a workflow, alter a service level, or retire a metric. It is not a replacement for routine operational reporting.",[120,346,347],{},"Use a tab in the same spreadsheet:",[229,349,350,376],{},[232,351,352],{},[235,353,354,357,360,363,365,367,370,373],{},[238,355,356],{},"Decision",[238,358,359],{},"Baseline",[238,361,362],{},"Expected outcome",[238,364,246],{},[238,366,252],{},[238,368,369],{},"Review date",[238,371,372],{},"Observed result",[238,374,375],{},"Keep, change, or retire",[257,377,378],{},[235,379,380,383,386,389,392,394,397,400],{},[262,381,382],{},"AI drafts for eligible order-status tickets",[262,384,385],{},"Five-day manual handling-time sample and correction count",[262,387,388],{},"Lower human review-and-send time without lower accuracy",[262,390,391],{},"Pause for a material factual error or two draft-related customer corrections in a week",[262,393,276],{},[262,395,396],{},"Two weeks after launch",[262,398,399],{},"Record at review",[262,401,402],{},"Decide at review",[120,404,405],{},"The cadence should match risk. Review fast pilots weekly or at a volume milestone because failures can compound quickly. Review stable measures monthly or quarterly, when enough work has accumulated to support a useful decision.",[144,407,409],{"id":408},"use-frameworks-as-checks-not-scorecards","Use frameworks as checks, not scorecards",[120,411,412],{},"A few resources can improve your questions without creating another measurement program.",[188,414,415,424,432,441,450],{},[191,416,417,418,423],{},"The ",[127,419,422],{"href":420,"rel":421},"https://queue.acm.org/detail.cfm?id=3454124",[131],"SPACE framework"," helps you remember that developer productivity includes satisfaction, performance, activity, communication, and efficiency. It does not support compressing people into one score.",[191,425,426,431],{},[127,427,430],{"href":428,"rel":429},"https://dora.dev/capabilities/",[131],"DORA's capabilities research"," is useful for examining delivery practices and outcomes together. It is not a recipe for judging individual engineers from deployment data.",[191,433,434,435,440],{},"Google SRE's guidance on ",[127,436,439],{"href":437,"rel":438},"https://sre.google/sre-book/postmortem-culture/",[131],"postmortem culture"," is a reminder to study failures without turning measurement into blame.",[191,442,443,444,449],{},"The UK government's ",[127,445,448],{"href":446,"rel":447},"https://www.gov.uk/government/publications/the-magenta-book",[131],"Magenta Book"," provides evaluation guidance: define the question, compare against a baseline where possible, and state limits.",[191,451,417,452,457],{},[127,453,456],{"href":454,"rel":455},"https://nvlpubs.nist.gov/nistpubs/ai/NIST.AI.100-1.pdf",[131],"NIST AI Risk Management Framework"," is useful for assigning accountability and managing AI risk. It does not certify an AI workflow as safe.",[144,459,461],{"id":460},"start-with-one-real-decision","Start with one real decision",[120,463,464],{},"Pick one decision your team is already struggling to make. Write the outcome, choose one proxy, add one guardrail, and name an owner.",[120,466,467],{},"Then run the smallest reversible test you can.",[120,469,470],{},"If the measure improves while the work gets worse, believe the work.",{"title":472,"searchDepth":473,"depth":473,"links":474},"",2,[475,476,477,478,479,480,481],{"id":146,"depth":473,"text":147},{"id":182,"depth":473,"text":183},{"id":220,"depth":473,"text":221},{"id":297,"depth":473,"text":298},{"id":340,"depth":473,"text":341},{"id":408,"depth":473,"text":409},{"id":460,"depth":473,"text":461},"2026-07-15T00:00:00.000Z","How small and midsize teams can use engineering and AI metrics to make better decisions without turning proxies into the work.","md","https://images.pexels.com/photos/590016/pexels-photo-590016.jpeg?auto=compress&cs=tinysrgb&w=1260&h=750&dpr=1",{},8,true,{"title":106,"description":483},"eFdzrINaeshN0rYJ-NUSJndY59IaGGSX03Rue_GHF2Q",[492,494],{"title":102,"path":103,"stem":104,"description":493,"children":-1},"A practical guide for spotting the operational gaps that make AI agents unsafe or ineffective before you build on top of them.",null,1784129533444]