# Automation Amplifies a Foundation Rather Than Fixing It ## Claim Adding automation to a broken process scales its output volume, not its quality, so the underlying process has to be sound before automation is worth adding. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Holds for any process where automation increases throughput of an existing workflow — sales outreach, content generation, community engagement, support response. - Breaks when the existing foundation is already sound, in which case automation is purely additive rather than an amplifier of dysfunction. - Distinct from the question of *where the resulting toil goes* (see linked note) — this claim is about whether automating a bad process makes it worse, not about who absorbs the leftover supervision work once it's automated. ## Evidence Common Room's AI SDR playbook argues that bolting AI onto an already-broken outbound sales process — poor targeting, generic messaging, missed follow-up windows — doesn't fix those problems, it just produces "more noise, faster." The fix has to happen at the targeting layer first (work live signals instead of static lists) before automation adds real value rather than amplified waste. > [!quote] > bolt AI onto a broken foundation and you don't fix the foundation, you just produce more noise, faster ## Links - [[DevRel MOC]] — why tooling advocacy fails when the underlying process is the actual problem - [[3. Resources/Permanent Notes/Automation Relocates Toil Into Supervision]] — because contrasts: that note describes what happens to labor *after* automation is correctly applied to a sound process (toil becomes supervision); this note describes what happens when automation is applied to an *unsound* process (the dysfunction scales, not the toil). - [[3. Resources/MOCs/AI & the Future of Knowledge Work MOC]] — because applies-in: this is a general diagnostic for evaluating any AI-automation pitch, not specific to sales. ## Tests / falsifiers - Find a case where automating a genuinely dysfunctional process produced better outcomes anyway (e.g., the automation itself corrected the underlying flaw as a side effect) — would complicate the claim's generality. - Measure whether output quality (not volume) degrades, holds steady, or improves when automation is added to a process with known targeting/quality problems, across a sample of real deployments rather than a single vendor's illustrative scenario. ## Maintenance - Last tended: 2026-08-16 - Next review: 2026-11-16 ## Source - [[3. Resources/Readwise/Articles/The AI SDR Playbook]] — Common Room vendor blog post on AI-native outbound sales workflows.