Yükleniyor...
For years, I believed so firmly in the rule that 'passive voice is lazy' that I ended up pointing fingers at the user in every interface message I wrote.
For years, I believed so firmly in the rule that 'writing in the passive voice is lazy' that I ended up pointing fingers at the user in every interface message I wrote. I thought I was being clear by saying 'You entered your password incorrectly,' but in reality, I was just putting the user on the defensive.
When I first started editing, driven by a high-school reflex, I treated passive sentences almost like grammatical errors. I tried to make every text active, believing every action required a distinct subject. The copy was high-energy, yes. But it also sounded aggressive, exhausting, and at times overtly accusatory.
During the checkout phase of an e-commerce project, this exact 'active voice fetish' led to a major blunder. When a user entered an incomplete credit card number, the alert on the screen read: "You typed an incomplete credit card number."
Extremely clear, right? We explicitly stated who took the action (the user) and what went wrong (incomplete typing) using the active voice. But once the analytics started rolling in, we noticed a sharp spike in cart abandonment rates among users who saw this specific error. The problem wasn't clarity; the problem was making the user feel 'stupid.' The screen was essentially shouting, 'You made a mistake.'
So we rewrote the message: "The credit card number entered is incomplete." (Or even more passive: "Credit card number was entered incompletely.")
The culprit disappeared. The accusation vanished. The focus shifted from 'who did something wrong' to 'what needs to be fixed.'
What helped me grasp this transformation was Mailchimp's Content Style Guide. Mailchimp is widely recognized as an industry benchmark for voice and tone. Studying the error message section in their guide made me realize just how critical it is to avoid blaming the user.
Nielsen Norman Group's error message guidelines support this exact point: the system must be polite and help users resolve the issue without increasing their cognitive load. While active voice is generally preferred in UX writing for clarity and actionability, at points of friction like error messages, it can quickly turn accusatory.
Passive voice, on the other hand, shifts the focus from the actor (the user) to the action itself or the system, creating a more empathetic, neutral tone in moments of crisis. Passive constructions like 'An error occurred in the system' or 'Required fields were not filled' remove the culprit from the equation and lower the user's cognitive stress.
This doesn't mean we should use passive voice everywhere. Over-praising the passive voice might lead inexperienced writers to use it in onboarding flows or calls-to-action (CTAs), which degrades overall readability.
It's all about balance. The takeaway from Mailchimp's approach is this: celebrate success and action with the active voice ("You successfully sent your campaign!"), but soften errors and issues with the passive voice ("There was an interruption during sending").
Active voice is great for taking ownership of positive actions; passive voice is an elegant tool for cloaking the culprit during a crisis and solving the issue without personalizing the blame.
Workshop Rule: If an action deserves praise, deliver it to the subject with the active voice; if an action calls for forgiveness, anonymize it with the passive voice.