# Measurement Scaffolding Is Not the Work It Measures ## Claim A framework built to report on progress will be mistaken for the process that creates it, and teams will then execute the report instead of the work. <!-- atomicity: 1 idea ✓ --> ## Evidence **Source**: [[3. Resources/Readwise/Articles/How to Close $100K+ Enterprise Deals, Step by Step Jen Abel|How to close $100K+ enterprise deals, step by step]] — Jen Abel The five familiar CRM stages — intro, demo, proposal, contracting, closed — exist to weight a forecast: roughly 10% at intro, 50% mid-funnel, 80% at contracting. They are an accounting instrument. > [!quote] > That's not the stages you take a client through. Like those are just the broad buckets. Because the buckets are the only visible structure, people run their actual process against them: five stages, therefore five meetings. Abel puts the share of practitioners making this error at 90% — an invented number, but the direction is well-supported by the rest of her account. The real motion is roughly fifteen steps, and the ten missing ones are the intel-gathering and coalition-building that the forecast has no column for. The corrective she states is the general lesson stripped of its domain: > [!quote] > Enterprise sales is mirroring their buying process. It's trying to control their buying process. It's not plopping these people into your sales process. ## Scope & conditions - Holds wherever a measurement artifact is more visible than the underlying process — CRM stages, OKRs, release milestones, maturity models, contribution dashboards. - The diagnostic tell is a round number of stages nobody can explain the derivation of. Real processes rarely have five of anything. - Distinct from Goodhart's law. Goodhart is about a measure degrading once targeted; this is about a measure being **mistaken for the method** in the first place. - Fails where the framework was deliberately designed as a process guide and documented as such. The failure is silent substitution, not the existence of stages. ## Links - [[Product & Startup Instincts MOC]] — why teams execute the forecast instead of the process it was built to report on - [[3. Resources/Permanent Notes/A Growing Categorized Issue Queue Measures Triage Capacity Not Just Backlog]] — the same confusion about what a number is actually reporting - [[3. Resources/Permanent Notes/An Agent Optimizing a Metric Will Find Hollow Wins]] — what happens once the scaffolding is targeted rather than merely mistaken - [[3. Resources/Permanent Notes/A Working Strategy Is Measured by What It Lets a Team Refuse]] — contrasts: a framework that constrains action rather than describing it - [[3. Resources/Permanent Notes/Rewarding AI Usage Manufactures Usage Not Value]] — the incentive layer that hardens the substitution - [[3. Resources/MOCs/Evidence & Claims Literacy MOC]] — the reporting apparatus mistaken for the process it reports on - [[3. Resources/Permanent Notes/An Open Source Adoption Claim Without a Dated Target and a Measurement Is Talk]] — contrasts: an open source adoption claim needs a dated target and a measurement before it counts as adoption.