Yükleniyor...
I used to think rewriting every passive sentence into active voice improved the copy—until I saw how saying "You entered the wrong password" antagonizes the reader.
For years at the editorial desk, I crossed out every passive sentence with a red pen and forced it into the active voice. I believed I was boosting the prose’s energy, grabbing the reader by the collar. The moment I spotted a passive verb, I’d strike through it, ask "Who did it?", and pin that agent to the front of the sentence. That lasted until I saw how insisting on "You entered your password incorrectly" in an error state accused users and put them on the defensive. Passive voice is not an enemy; it is simply a focusing lens whose use cases we have forgotten.
For a copy craftsman, the active voice spotlights the actor. But a true artisan knows how to deploy the passive voice as a strategic shield when the entity affected by the action—or the action itself—matters far more than the agent. To dismantle the common dogma that treats passive voice as sheer bloat, I use a three-step filter at my desk every day. I call it the Passive Voice Decision Matrix.
Before drafting a sentence, you must test whether the agent adds value or dead weight. Is the actor more important, or the recipient of the action?
Years ago, while drafting a data breach notification, we wrote: "Hackers leaked the customer database." The sentence was active, short, and punchy. Yet it failed because it directed the reader’s attention to the wrong place. For an affected customer, the identity of the actor (the hackers) is secondary at that initial moment; what matters is the status of their own data. When we shifted the sentence to the passive structure—"The customer database was compromised"—the grammatical subject aligned directly with what the reader cared about. If the agent’s identity carries less critical information than the outcome, removing the agent does not weaken the copy; it sharpens it.
In user experience (UX) writing and crisis communication, active voice can turn into a hostile weapon. We tried it and paid the price: on a checkout screen, when a user made an error, we displayed "You entered your credit card incorrectly." It followed every active-voice rule in the book. The result? Customer support tickets spiked because the interface explicitly blamed the user.
As research from UX Writing Hub highlights, passive voice in UI error messages is used strategically to avoid blaming the user, reducing emotional defensiveness and cognitive friction. A passive construction like "Card details could not be verified" acts as a bridge toward a resolution without personalizing the fault. Instead of telling the user "you messed up," it grammatically signals "an issue occurred—let’s resolve it together."
In technical or enterprise communication, constantly repeating the agent suffocates the flow. Imagine a maintenance screen announcing: "We are updating the system." The "we" provides zero utility to the reader while introducing unnecessary corporate posturing.
Microsoft Style Guide’s technical writing guidelines note that passive voice is often used to keep focus on the system’s behavior or outcome rather than the user or organization performing the action. This ensures the object of concern remains the grammatical subject. Writing "The system is being updated" minimizes cognitive load. The reader already knows people are working in the background; you only need to report the state of the process.
There is a trap to avoid when defending the passive voice. Passive voice is meant to reduce cognitive friction, not dodge accountability. In crisis management, stating "Mistakes were made" represents passive voice at its most cowardly. When an organization or individual needs to own a failure, active voice is mandatory. Saying "We made a mistake" demonstrates craftsmanship and integrity; saying "Mistakes were made" is just cheap PR deflection. Using the passive voice where you ought to accept responsibility is not craft—it is evasion.
If the entity performing the action carries less value than the outcome, or if naming them risks antagonizing the reader, wear the cloak of the passive voice. Construct the sentence not to flatter the agent, but to deliver clarity with the lowest possible friction.