416 lines
14 KiB
Markdown
416 lines
14 KiB
Markdown
# Edit Library
|
|
|
|
Before/after transformation examples showing specific edit patterns.
|
|
|
|
---
|
|
|
|
## Pattern 1: Throat-Clearing Removal
|
|
|
|
### Before
|
|
> Here's the thing: building products is hard. Not because the technology is complex. Because people are complex. Let that sink in.
|
|
|
|
### After
|
|
> Building products is hard, and the reason is people, not technology.
|
|
|
|
### Changes
|
|
- Removed opener "Here's the thing:"
|
|
- Stated the real reason in one flowing sentence — not a clipped "Not X. Y." fragment pair (that's its own AI tell)
|
|
- Deleted "Let that sink in" emphasis crutch
|
|
- 23 words → 12 words (48% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 2: Filler + Unnecessary Reassurance
|
|
|
|
### Before
|
|
> It turns out that most teams struggle with alignment. The uncomfortable truth is that nobody wants to admit they're confused. And that's okay.
|
|
|
|
### After
|
|
> Teams struggle with alignment because nobody admits they're confused.
|
|
|
|
### Changes
|
|
- Cut "It turns out that"
|
|
- Cut "The uncomfortable truth is"
|
|
- Removed permission-granting "And that's okay"
|
|
- Joined cause and effect into one sentence instead of two clipped fragments
|
|
- 26 words → 9 words (65% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 3: Business Jargon Stack
|
|
|
|
### Before
|
|
> In today's fast-paced landscape, we need to lean into discomfort and navigate uncertainty with clarity while leveraging our core competencies.
|
|
|
|
### After
|
|
> Move fast, handle uncertainty, and use what you're actually good at.
|
|
|
|
### Changes
|
|
- "In today's fast-paced landscape" → cut
|
|
- "lean into discomfort" → cut (filler motivation)
|
|
- "navigate uncertainty" → "handle uncertainty"
|
|
- "leveraging core competencies" → "use what you're actually good at"
|
|
- Kept it as one sentence — a staccato imperative triplet ("Move fast. Handle uncertainty. …") is its own AI cadence
|
|
- 22 words → 11 words (50% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 4: Dramatic Fragmentation
|
|
|
|
### Before
|
|
> Speed. Quality. Cost. You can only pick two. That's it. That's the tradeoff.
|
|
|
|
### After
|
|
> Speed, quality, cost. Pick two.
|
|
|
|
### Changes
|
|
- Collapsed fragmented list into single sentence
|
|
- Removed performative "That's it. That's the tradeoff."
|
|
- 14 words → 5 words (64% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 5: Rhetorical Setup
|
|
|
|
### Before
|
|
> What if I told you that the best teams don't optimize for productivity? Here's what I mean: they optimize for learning.
|
|
|
|
### After
|
|
> The best teams optimize for learning, not productivity.
|
|
|
|
### Changes
|
|
- Removed "What if I told you" rhetorical question
|
|
- Removed "Here's what I mean:" scaffolding
|
|
- Direct statement instead of reveal structure
|
|
- 22 words → 9 words (59% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 6: Hedging Stack
|
|
|
|
### Before
|
|
> I think it's probably fair to say that perhaps most organizations might benefit from potentially considering a more agile approach.
|
|
|
|
### After
|
|
> Most organizations should try agile.
|
|
|
|
### Changes
|
|
- "I think" → cut
|
|
- "probably fair to say" → cut
|
|
- "perhaps" → cut
|
|
- "might benefit from potentially considering" → "should try"
|
|
- 21 words → 6 words (71% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 7: Absolute Claims Softened
|
|
|
|
### Before
|
|
> Everyone knows that nobody ever succeeds without failing first. It's always been this way and it always will be.
|
|
|
|
### After
|
|
> Success usually follows failure.
|
|
|
|
### Changes
|
|
- "Everyone knows" → cut (false absolute)
|
|
- "nobody ever" → implicit
|
|
- "always been/always will be" → "usually"
|
|
- 19 words → 4 words (79% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 8: Meta-Commentary Removal
|
|
|
|
### Before
|
|
> Hint: the answer isn't what you think. Plot twist: it's actually quite simple. Let me explain. Think about it: when you remove complexity, things get easier.
|
|
|
|
### After
|
|
> The answer is simple: remove complexity.
|
|
|
|
### Changes
|
|
- Removed "Hint:" meta-commentary
|
|
- Removed "Plot twist:" performative
|
|
- Removed "Let me explain" / "Think about it:"
|
|
- Direct statement instead of theatrical reveal
|
|
- 27 words → 6 words (78% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 9: Binary Contrast Collapse
|
|
|
|
### Before
|
|
> It's not about working harder. It's about working smarter. It feels like the former is the answer. It's actually the latter. Make no mistake about it.
|
|
|
|
### After
|
|
> Work smarter, not harder.
|
|
|
|
### Changes
|
|
- Collapsed repetitive binary structure
|
|
- Removed "feels like / actually" false drama
|
|
- Removed "Make no mistake about it" emphasis
|
|
- 28 words → 4 words (86% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 10: List Compression
|
|
|
|
### Before
|
|
> There are three things every leader needs: First, they need clarity. Second, they need courage. Third, they need consistency. These three C's are the foundation of effective leadership.
|
|
|
|
### After
|
|
> Leaders need clarity, courage, and consistency.
|
|
|
|
### Changes
|
|
- Collapsed numbered list into single sentence
|
|
- Removed "There are three things" setup
|
|
- Removed "these three C's" meta-reference
|
|
- Removed "foundation of effective leadership" filler
|
|
- 31 words → 7 words (77% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 11: Intensifier Reduction
|
|
|
|
### Before
|
|
> This is incredibly important and truly fundamental to deeply understanding the absolutely essential nature of really effective communication.
|
|
|
|
### After
|
|
> This matters for effective communication.
|
|
|
|
### Changes
|
|
- "incredibly" → cut
|
|
- "truly fundamental" → cut
|
|
- "deeply understanding" → cut
|
|
- "absolutely essential" → cut
|
|
- "really effective" → "effective"
|
|
- 17 words → 6 words (65% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 12: Passive to Active
|
|
|
|
### Before
|
|
> The decision was made by the team after the options were considered by leadership and the risks were evaluated by the analysts.
|
|
|
|
### After
|
|
> Leadership weighed the options, the analysts assessed the risks, and the team made the call.
|
|
|
|
### Changes
|
|
- "decision was made by the team" → "the team made the call"
|
|
- "options were considered by leadership" → "Leadership weighed the options"
|
|
- "risks were evaluated by analysts" → "the analysts assessed the risks"
|
|
- Passive → active throughout, joined as one sentence (three 3-word sentences in a row is staccato)
|
|
- 23 words → 15 words (35% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 13: Fact-Heavy Preservation
|
|
|
|
### Before
|
|
> It's worth noting that in Q3 2024, Acme Corp reported revenue of $47.3M, which represents a truly impressive 23% year-over-year increase. This is a game-changing result for the industry.
|
|
|
|
### After
|
|
> Acme Corp reported $47.3M revenue in Q3 2024, up 23% year-over-year.
|
|
|
|
### Changes
|
|
- "It's worth noting that" → cut
|
|
- "truly impressive" → cut (editorializing)
|
|
- "game-changing result for the industry" → cut (filler)
|
|
- All facts preserved: Q3 2024, Acme Corp, $47.3M, 23%
|
|
- 33 words → 12 words (64% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 14: Conditional Simplification
|
|
|
|
### Before
|
|
> If you want to succeed in the modern marketplace, you need to ensure that you're providing value to your customers in a way that differentiates you from the competition.
|
|
|
|
### After
|
|
> Differentiate through customer value.
|
|
|
|
### Changes
|
|
- "If you want to succeed in the modern marketplace" → cut (obvious)
|
|
- "ensure that you're providing value to your customers" → "customer value"
|
|
- "in a way that differentiates you from the competition" → "Differentiate through"
|
|
- 30 words → 4 words (87% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 15: Question + Immediate Answer
|
|
|
|
### Before
|
|
> What's the key to retention? It's simple: make users feel valued. How do you do that? By listening. And why does that matter? Because people want to be heard.
|
|
|
|
### After
|
|
> Retain users by making them feel valued. Listen to them.
|
|
|
|
### Changes
|
|
- Collapsed Q&A theatrical structure
|
|
- Direct statements instead of rhetorical questions
|
|
- "Because people want to be heard" → implicit in "Listen"
|
|
- 32 words → 11 words (66% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 16: Significance Inflation
|
|
|
|
### Before
|
|
> The Apollo program stands as a testament to human ingenuity, leaving an indelible mark on the history of space exploration and serving as a cornerstone of scientific achievement.
|
|
|
|
### After
|
|
> The Apollo program put twelve people on the moon between 1969 and 1972.
|
|
|
|
### Changes
|
|
- "stands as a testament to human ingenuity" → cut (inflated copula + significance)
|
|
- "leaving an indelible mark" → cut (cliché)
|
|
- "cornerstone of scientific achievement" → cut (inflation)
|
|
- Replaced abstract praise with the specific fact
|
|
- 30 words → 13 words (57% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 17: Promotional Language
|
|
|
|
### Before
|
|
> Nestled in the heart of downtown, the restaurant boasts a world-class menu featuring breathtaking flavors. A hidden gem that's a must-visit for any food lover.
|
|
|
|
### After
|
|
> The restaurant, on Main Street downtown, serves Southern-French fusion. The duck confit tacos are worth the trip.
|
|
|
|
### Changes
|
|
- "Nestled in the heart of" → specific location
|
|
- "boasts a world-class menu" → describes the actual cuisine
|
|
- "breathtaking flavors" → named a specific dish
|
|
- "hidden gem" / "must-visit" → concrete recommendation
|
|
- 27 words → 18 words (33% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 18: Superficial -ing Analysis
|
|
|
|
### Before
|
|
> The company reported 40% revenue growth, highlighting the effectiveness of its strategy, showcasing the strength of its market position, and underscoring the importance of innovation in the tech sector.
|
|
|
|
### After
|
|
> The company's revenue grew 40%. Its new API product drove most of that — enterprise contracts tripled.
|
|
|
|
### Changes
|
|
- Deleted all three participial clauses (highlighting, showcasing, underscoring)
|
|
- Replaced fake analysis with actual causal explanation
|
|
- 31 words → 17 words (45% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 19: Copula Avoidance
|
|
|
|
### Before
|
|
> The library serves as a community hub that functions as a gathering place and represents a vital resource for residents.
|
|
|
|
### After
|
|
> The library is where the neighborhood meets. Residents use it for everything from job searches to story time.
|
|
|
|
### Changes
|
|
- "serves as" → "is"
|
|
- "functions as" → cut (redundant with "serves as")
|
|
- "represents a vital resource" → concrete examples of use
|
|
- 20 words → 19 words (same length, more information)
|
|
|
|
---
|
|
|
|
## Pattern 20: Negative Parallelism
|
|
|
|
### Before
|
|
> It's not just about building a product. It's about building a community. Not only does the platform connect users, but it also fosters meaningful relationships and drives engagement.
|
|
|
|
### After
|
|
> The platform's value is its community. Users keep coming back because they've built relationships there.
|
|
|
|
### Changes
|
|
- "It's not just about X, it's about Y" → stated Y directly
|
|
- "Not only...but also..." → collapsed into cause-effect
|
|
- "fosters meaningful relationships and drives engagement" → concrete behavior
|
|
- 30 words → 16 words (47% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 21: Communication Artifacts
|
|
|
|
### Before
|
|
> Great question! I'd be happy to help with that. Certainly, there are several approaches you could take. I hope this helps — let me know if you need anything else!
|
|
|
|
### After
|
|
> Three approaches work here: [approach 1], [approach 2], [approach 3].
|
|
|
|
### Changes
|
|
- "Great question!" → cut (chatbot flattery)
|
|
- "I'd be happy to help" → cut (chatbot compliance)
|
|
- "Certainly" → cut (chatbot filler)
|
|
- "I hope this helps" / "let me know if..." → cut (chatbot sign-off)
|
|
- 31 words → 9 words (71% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 22: False Ranges
|
|
|
|
### Before
|
|
> The festival attracts visitors from young professionals to retirees, from local residents to international tourists, spanning everything from music enthusiasts to casual attendees.
|
|
|
|
### After
|
|
> The festival draws 50,000 people annually, mostly locals and tourists from neighboring states.
|
|
|
|
### Changes
|
|
- Collapsed three stacked "from X to Y" ranges into specific data
|
|
- Replaced vague breadth claim with actual numbers
|
|
- 25 words → 13 words (48% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 23: Generic Positive Conclusion
|
|
|
|
### Before
|
|
> As the industry continues to evolve, the future looks bright. Exciting times lie ahead for all stakeholders involved. One thing is certain: innovation will continue to shape the landscape.
|
|
|
|
### After
|
|
> Two trends to watch: edge computing costs dropping 30% annually, and enterprise AI adoption doubling each quarter.
|
|
|
|
### Changes
|
|
- "continues to evolve" → cut (says nothing)
|
|
- "the future looks bright" → cut (empty optimism)
|
|
- "exciting times lie ahead" → cut (content-free)
|
|
- "one thing is certain" → replaced with specific predictions
|
|
- 30 words → 16 words (47% reduction)
|
|
|
|
---
|
|
|
|
## Pattern 24: Compound Example (Multiple Pattern Types)
|
|
|
|
### Before
|
|
> In today's rapidly evolving digital landscape, the groundbreaking initiative serves as a testament to the company's commitment to innovation. Not only does it showcase their robust capabilities, but it also underscores the importance of fostering collaboration. Experts argue this represents a pivotal moment. The future looks bright.
|
|
|
|
### After
|
|
> The company shipped a new collaboration tool. Early numbers: 2,000 teams signed up in the first week, 85% retention at day 30.
|
|
|
|
### Changes
|
|
- "In today's rapidly evolving digital landscape" → cut (filler)
|
|
- "groundbreaking initiative serves as a testament to" → named the actual thing
|
|
- "Not only...but also..." → cut (negative parallelism)
|
|
- "showcasing robust capabilities" / "underscoring importance" → cut (superficial -ing)
|
|
- "fostering collaboration" → named the product category
|
|
- "Experts argue" → cut (vague attribution)
|
|
- "represents a pivotal moment" → replaced with data
|
|
- "The future looks bright" → cut (generic conclusion)
|
|
- 47 words → 22 words (53% reduction), information density dramatically higher
|
|
|
|
---
|
|
|
|
## Transformation Principles
|
|
|
|
1. **Cut setup, keep substance** - Remove everything before the actual point
|
|
2. **One structure, not three** - If it can be one sentence, make it one
|
|
3. **Let facts speak** - Numbers don't need emphasis crutches
|
|
4. **Active beats passive** - Who did what, not what was done by whom
|
|
5. **Trust the reader** - They'll get it without "Think about it:"
|
|
6. **Verbs do the work** - Concrete actions, not abstract processes
|
|
7. **Vary the rhythm** - Concise is not the same as staccato. After cutting, check the result isn't a run of tiny sentences or a bare "Not X. Y." contrast — that clipped cadence is its own AI tell. Mix short sentences with a longer one.
|