Active, Passive, and Who's to Blame: The Grammar of Tech Accountability

In 2012, Apple CEO Tim Cook published a public apology over Apple Maps — the notoriously unreliable navigation app that launched with iOS 6. He wrote: "We are extremely sorry for the frustration this has caused our customers."

Notice anything? We are sorry. Active voice. Clear subject. Apple took the hit directly.

Now compare that to a more typical tech company response: "Errors were identified in the mapping data, and improvements are being made." No subject. No one doing anything. Mistakes just... happened. On their own. Apparently.

Welcome to one of the most powerful — and most politically loaded — grammar choices in the English language.

Active vs. Passive: A Quick Refresher

Before diving into how tech companies weaponize grammar, let's make sure the basics are clear.

Active voice: The subject performs the action. "We found a bug in the software."

Passive voice: The action happens to the subject, and the doer is often absent. "A bug was found in the software."

In active voice, someone is responsible. In passive voice, responsibility becomes optional. The doer can simply be left out — and in corporate communication, that's often the entire point.

How Tech Companies Use Passive Voice to Manage Blame

When something goes wrong in the tech world — a data breach, a service outage, a product recall — watch the grammar closely. It tells you everything about how a company views its own accountability.

Here are some real patterns you'll encounter:

Passive to remove the actor: "Customer data was accessed without authorization." Who accessed it? Unknown. Unmentioned. Grammatically erased.

Passive to soften the action: "Some features have been deprecated." Compare: "We removed features you were using." Same fact, very different feeling.

Passive to sound procedural: "An investigation has been launched." This sounds official and serious without committing to who launched it, why, or what it will actually do.

Apple, Microsoft, Google — all of them do this. It's not unique to any one company. It's a standard feature of corporate English, and once you see it, you can't unsee it.

When Companies Go Active (And Why It Matters)

Active voice in a tech apology or announcement is actually rare enough to be noteworthy. When a company does choose it, it usually signals one of two things: genuine accountability, or very confident PR strategy.

Tim Cook's Maps apology used active voice throughout: "We fell short... We are extremely sorry... We are working hard..." Whether that reflected genuine humility or calculated image management, the effect was the same — it felt human. It felt direct. People responded to it.

Compare that to the passive-heavy statements that followed Facebook's Cambridge Analytica scandal in 2018: "Data was shared... privacy settings were not configured..." — language so carefully constructed to avoid naming a subject that it became a case study in how not to apologize.

For English learners navigating tech support or workplace communication, this distinction matters practically, not just academically.

What This Means for You in Tech Support Conversations

If you've ever contacted Apple Support or any tech customer service, you've been on the receiving end of carefully calibrated grammar. Understanding it helps you respond more effectively — and push back when necessary.

When you hear passive voice in support: "It looks like your account was flagged." A useful follow-up: "Flagged by what? By whom? What triggered that?" — you're asking for the missing subject.

When you want to sound professional rather than accusatory: Using passive voice yourself can actually de-escalate a tense conversation. Instead of "You deleted my data," try "It seems like my data was deleted during the update." Same complaint, less confrontational framing.

In written communication: If you're filing a bug report or a support ticket, active voice makes your report clearer: "The app crashes when I tap the share button" is more useful than "A crash occurs when the share button is tapped." Clear subject, clear action, easier to diagnose.

The Workplace Dimension

This grammar pattern also shows up inside tech companies — in emails, Slack messages, post-mortems, and performance reviews.

In a post-mortem (the document teams write after something goes wrong), passive voice is sometimes used to protect individuals from blame in a healthy way: "Insufficient testing was performed" rather than "John didn't test this properly." The goal is to fix the process, not punish the person.

But passive voice can also be used to dodge accountability in less healthy ways. Learning to distinguish between the two — protective ambiguity versus evasive ambiguity — is a genuinely useful professional skill.

A Grammar Habit Worth Developing

Here's a simple practice: whenever you read a tech press release, support email, or company statement, underline every passive construction you find. Then ask: who is missing from this sentence? What are they not saying?

You'll start to see the shape of what companies are hiding — or protecting — through grammar alone. And in your own writing and speaking, you'll become more intentional about when you choose to name the actor and when you don't.

Grammar isn't neutral. In tech communication, it never was.