Quick answer: Use broke when describing an action that damaged, ruined, or stopped something from working. Use made it better when your changes successfully improved, enhanced, or optimized the original subject. In professional writing, always clarify whether a revision caused harm or added value to avoid ambiguity.
In the worlds of editing, software development, and design, a common dilemma arises when describing the outcome of a change: did you break the original, or did you improve it? Writers, developers, and creators often struggle with whether to say they “broke” a system or “made it better,” especially when the results of their revisions are subjective or complex. Understanding the precise grammatical roles, connotations, and professional implications of these terms ensures your communication is clear, accurate, and credible. As a veteran copy editor who has reviewed thousands of manuscripts, cover letters, and technical reports, I can tell you that mischaracterizing a revision can undermine your authority. This guide will give you the definitive rules for choosing between these two critical descriptions.
| Term | Meaning / When to use | Example sentence |
|---|---|---|
| Broke | The simple past tense of “break.” Use it when an action caused damage, failure, or disruption to something that was previously functional. | “I accidentally broke the macro when I updated the spreadsheet formulas.” |
| Made it better | A verb phrase indicating successful improvement, enhancement, or optimization. Use it when a change has positively impacted the subject’s quality or function. | “I reorganized the introductory paragraphs and made it better for the target audience.” |
When to use “broke”
The word “broke” is the simple past tense of the irregular verb “break.” You should use it strictly to describe an action that resulted in damage, fracture, cessation of function, or violation of a rule. It carries an inherently negative or destructive connotation. In professional contexts, admitting that you “broke” something is a declaration of failure or an unintended negative consequence, so it must be used with precision.
the term is widely recognized not just as the past tense of break, but also colloquially to mean insolvent or penniless, as noted in its disambiguation contexts [[1]]. However, in the context of revisions and modifications, we are strictly dealing with its verbal form indicating damage or disruption.
Here are concrete, realistic examples of when “broke” is the correct and only choice:
- In a technical post-mortem email: “The latest deployment broke the login feature for mobile users, causing a 15% drop in session completions.”
- In a writing critique: “You broke the narrative flow by inserting a three-paragraph flashback in the middle of the action scene.”
- In a casual team text message: “Hey, I think I broke the shared drive link. Can you send a new one?”
Notice that in every instance, “broke” describes a specific, completed action that resulted in a loss of functionality or quality. It is never used to describe a state of being in formal writing (for that, you would use “broken”).
When to use “made it better”
The phrase “made it better” is a powerful, positive alternative used to communicate that a modification resulted in a net positive outcome. It combines the simple past tense of the verb “make” with the comparative adjective “better.” “better” functions as a comparative term indicating a higher quality, a more desirable state, or a successful improvement [[2]].
Unlike “broke,” which is a single, blunt verb, “made it better” is a descriptive phrase that takes ownership of a successful enhancement. It is the go-to phrasing for describing edits, optimizations, or refinements that have elevated the original subject. However, because it is somewhat informal, it is best reserved for collaborative discussions, peer reviews, or casual updates, rather than formal performance reviews (where more specific verbs are preferred). For more, see Better.
Here are concrete, realistic examples of when “made it better” is the correct choice:
- In a design review meeting: “I adjusted the contrast on the call-to-action button and made it better for visually impaired users.”
- In a resume bullet point (casual draft): “I reorganized the client onboarding workflow and made it better, reducing the setup time by two days.” (Note: See the “Common Mistakes” section for how to polish this for a final resume).
- In a peer editing comment: “You cut the redundant adjectives in the second paragraph and made it better; the argument is much punchier now.”
When you use “made it better,” you are signaling to your reader that the change was intentional, beneficial, and measurable.
How to remember the difference
If you find yourself hesitating between these two options, here is a simple, editor-level memory trick to lock in the correct usage:
- The “B” vs. “M” Trick: Think of the B in Broke as standing for Broken functionality. If the change caused a failure, an error, or a disruption, you “broke” it. Think of the M in Made it better as standing for Modified successfully. If the change added value, clarity, or efficiency, you “made it better.”
- The Word Count Rule: “Broke” is a one-word action of destruction. “Made it better” is a three-word phrase of construction. You cannot “broke” something into a superior state; the word inherently carries a negative, final connotation.
- The “Can I fix it?” Test: If you have to immediately follow up your statement with an apology or a fix (“I broke it, but I’m fixing it now”), then “broke” is the right word. If you follow it up with a celebration or a metric (“I made it better, and the client loved it”), then the phrase is correct.
I see this confusion constantly in cover letters, where candidates write, “I broke the old system and made a new one.” While grammatically passable, it sounds unnecessarily destructive. A stronger phrasing would be, “I dismantled the outdated system and made it better by implementing an automated solution.”
Common mistakes and exceptions
Even native speakers stumble when describing revisions. Here are the most frequent pitfalls I correct in professional manuscripts, along with how to avoid them.
1. Using “broke” as an adjective
A pervasive error in casual writing and speech is using “broke” as an adjective to describe a current state.
- Incorrect: “The website is broke.”
- Correct: “The website is broken.” “Broke” is the simple past tense verb. “Broken” is the past participle used as an adjective. While “flat broke” is an accepted idiomatic adjective for having no money, it is never correct to say a machine, a sentence, or a process “is broke” in formal English.
2. The subjective trap in professional reviews
Sometimes, a writer or developer thinks they “made it better,” but the client or manager thinks they “broke” it. Because “made it better” is subjective, it can sound defensive or vague in a professional setting.
- Weak: “I changed the code and made it better.”
- Strong: “I refactored the code, which reduced load times by 30% and improved user retention.” Always back up the claim that you “made it better” with concrete evidence. If you cannot prove the improvement, your audience might assume you actually “broke” it.
3. Confusing “broke” with “broken” in perfect tenses
Another frequent grammatical stumble occurs when writers use the wrong verb form with auxiliary verbs.
- Incorrect: “I have broke the formatting.”
- Correct: “I have broken the formatting.” The present perfect tense requires the past participle (“broken”), not the simple past (“broke”).
4. US vs. UK English differences
There is no fundamental regional difference in the core grammatical usage of these terms. Both American and British English treat “broke” as the simple past tense of “break” and “made it better” as a standard phrase of improvement. However, in casual UK English, you might more frequently hear alternatives like “sorted it out,” “improved it,” or “made a better job of it,” whereas “made it better” remains the universally understood standard across all English dialects. For more, see Broke.
Frequently Asked Questions
Is “broke” ever correct as an adjective in formal writing? No. In formal, professional, or academic writing, you should always use “broken” as the adjective (e.g., “The broken link,” “The broken process”). “Broke” is strictly the simple past tense verb or a colloquial slang term for being penniless.
Can I say “I broke it to make it better”? Yes, this is a well-established idiom in software development, engineering, and creative fields. It means that you must temporarily disrupt, deconstruct, or dismantle an existing system in order to rebuild it in a superior, more efficient way.
Why is “made it better” considered weak on a resume? While grammatically correct, “made it better” is vague and lacks impact. Resume scanners and hiring managers look for specific, measurable outcomes. Instead of writing “I made the process better,” write “I streamlined the onboarding process, reducing training time by 20%.” This provides concrete proof of the improvement.
Does using the word “broke” imply intentional damage? Not necessarily. “Broke” simply describes the outcome of the action, regardless of intent. You can accidentally break a vase, a software update can inadvertently break a feature, or a writer can unintentionally break the narrative flow. The lack of intent does not change the grammatical correctness of the word, though it may change how you frame the apology.
What is the difference between “I broke it” and “It broke”? “I broke it” uses the transitive form of the verb, meaning you (the subject) performed the action that caused the damage. “It broke” uses the intransitive form, meaning the object failed on its own without a specified external agent causing it. Knowing this distinction helps you accurately assign responsibility in incident reports.
Daniel Perez is a seasoned editor and author with over 10 years of experience in content creation and word analysis. He graduated with a Bachelor’s degree in English Literature from Stanford University, where he discovered his passion for words and their interrelationships. His initial curiosity about wordplay and puns led him to explore deeper linguistic structures, eventually focusing on English word comparisons. Daniel is known for his analytical skills in distinguishing subtle differences between closely related words and expressions. At CompareMyWords, Daniel writes content that caters to both professional linguists and casual language enthusiasts, offering insight into grammatical intricacies, homonyms, and the impact of technology on modern language usage. He is particularly passionate about making linguistic knowledge accessible and engaging to a broad audience.