Yükleniyor...
For years, I bought into the dogma that 'every sentence must be active to keep copy punchy'—until I realized I was writing aggressive error messages that constantly blamed the user.
For years in copywriting workshops and books, I worshipped that famous rule: 'Never use passive voice.' Sentences always had to be active. The agent had to be clear; the action had to strike the target directly. I followed this dogma so blindly that over time, the interface copy, notifications, and error messages I wrote turned into a chain of accusations. Every 'You entered an incorrect password,' 'You failed to fill out the credit card form,' or 'You could not upload the file' appearing on screen was effectively a digital scolding wagging a finger at the user. In all these texts, the user was the agent, and the action was an outright failure.
At one point, we were writing copy for the checkout flow of a major e-commerce platform. We were optimizing every single word to reduce cart abandonment rates. I wrote an extremely active, crystal-clear error message: 'You failed to complete your payment because you exceeded your credit card limit.' By the rulebook, it was flawless: agent identified, action clear, cause established. The result? The tone of anger in customer support tickets skyrocketed. Users felt blamed, cornered, and insulted. Here is what we tested: we scrapped that entire active construct and wrote, 'Payment could not be processed. Please check limits and try again.' The result was dramatic: aggressive language in support tickets dropped immediately, and users pivoted to solving the problem. Why did our first attempt fail? Because the active voice pressed a finger right into the reader's chest.
Cognitive linguistics research demonstrates that passive constructions naturally shift the reader's cognitive focus away from the agent (who did it) toward the result or the recipient (what happened). This is an ideal strategy whenever the resolution matters more than the source of the problem. In UX writing, the difference between 'Payment declined' (passive) and 'You failed to pay' (active) is far more than a stylistic preference. By removing direct blame, the passive voice prevents user alienation during system friction.
During customer support interactions, deploying passive voice to explain system outages or user mistakes measurably reduces defensive reactions and creates a far more collaborative troubleshooting environment. While active voice provides momentum and drive, passive voice acts as a linguistic shock absorber in crisis communication—slowing down the narrative and softening the delivery of negative information. When readers encounter the observation 'This happened' instead of the accusation 'You did this,' they lower their defensive shields.
Consider the sentence 'Your account has been debited.' Here, the user does not care who performed the action (the bank's backend infrastructure, the payment gateway, the automated ledger). The action itself takes center stage. If you say, 'Our banking infrastructure debited your account,' you introduce an unnecessary agent and clutter the sentence. The event itself is what matters; questioning who the agent is merely siphons energy away from the sentence.
Yet caution is required when applying this tactic. Defending the passive voice in corporate crisis communication can be dangerous. The notorious phrase 'Mistakes were made,' routinely used by organizations dodging responsibility, is rightfully perceived by readers as an unethical evasion of accountability. Years ago, I made this mistake myself; during a server outage crisis, I tried to deflect by stating 'Issues were experienced in the database,' which severely damaged reader trust. We must use passive voice not to cover corporate missteps, but to ease the user's cognitive load and feelings of guilt.
When a company makes a mistake, saying 'We failed to protect your data' (active) rather than 'Your data was leaked' builds genuine trust. But when a user makes an error, saying 'Password reset link sent' (passive) instead of 'You forgot your password' (active) is a lifesaver. Miss this fine line, and your copy will either devolve into a bureaucratic, sluggish robot or sound like an overbearing teacher scolding the reader.
If the goal of a sentence is not to assign blame but to report a neutral state, take the agent off the stage and place the action in the spotlight. Write achievements, vision, and calls to action in the active voice; write system glitches, security alerts, and user errors in the passive voice.