My manager once described my internal writing as 'very thorough.' I beamed. I filed it away as a compliment and kept doing exactly what I was doing for another year. Then, in a different conversation entirely, I finally understood that she had meant 'very thorough' the way people say 'very detailed' about a four-hour movie they would absolutely not recommend to a friend. My proposals, retrospectives, and process docs were technically complete and completely unreadable, and the specific disease at the root of it was passive voice.
Here's the trap with passive voice, and the reason it's so hard to cure: you cannot see your own. It feels neutral, professional, even responsible while you're writing it. 'It was decided that we would proceed' sounds like the measured language of a serious person. It's actually the language of someone hiding from a verb. And because it feels correct from the inside of your own head, no amount of re-reading your own drafts will catch it — your brain reads what it meant, not what it wrote.
Fourteen rows in four paragraphs
I ran an old proposal through the Rewrite Passive, Hedging Prose into Active, Confident Writing prompt on Grok 4.3 and got back a change table with fourteen rows. Fourteen passive constructions in four short paragraphs. 'It was decided by the team' — decided by whom, exactly, and when? 'The results were analyzed' — by which person, using what method? And my personal signature crime, the phrase that opened roughly every third sentence I had ever written at work: 'It should be noted that.' Noted by whom? Noted how? It was noting all the way down, an infinite regress of nobody doing anything.
- 'It was decided by the team' became the four-word 'The team decided'
- 'The results were analyzed' became 'We analyzed the results'
- 'It should be noted that the deadline slipped' became simply 'The deadline slipped'
- 'Has been determined' became 'determined' — the auxiliary was pure ballast
- 'Mistakes were made' stayed flagged as the most cowardly sentence in the English language
Why the table, not the rewrite, did the teaching
I want to be specific about why this worked when years of vaguely knowing 'passive is bad' had done absolutely nothing. It's the side-by-side format. Seeing my original sentence sitting in one column, the rewrite in the next, and a short blunt reason in the third — 'subject buried, actor unclear' — made the pattern visible in a way the rewrite alone never could. A clean rewrite just looks better and teaches you nothing; you nod and move on. The diff, with a reason attached to each row, actually teaches, because it shows you the move you made and the move you should have made, right next to each other, on your own words.
I picked Grok 4.3 for this on purpose. It's quick and confident — it doesn't agonize over the edit, it just makes the call and shows its work, which is exactly the brisk energy a voice edit needs. Hand-wringing models second-guess every passive construction; this one names it, fixes it, explains it, and moves on. I now run it on every document before I share it, and the whole thing takes about thirty seconds, which is a rounding error against the cost of writing something nobody finishes reading.
The intentional-passive tag matters more than you'd think
The genuinely satisfying part is that the prompt taught me to spot my own tells, and so the table keeps shrinking over time. My next proposal had three passive constructions, and the model tagged all three [PASSIVE - INTENTIONAL] — exactly the cases where the actor truly didn't matter and the passive was simply correct. That tag matters enormously, by the way. A tool that mindlessly murders every passive construction is its own kind of broken, because sometimes 'the building was demolished in 1992' is just the right sentence — nobody cares which crew swung the wrecking ball. Good writing isn't passive-free; it's passive-on-purpose.
When the writing is also bloated on top of being passive — which, for me, on a tired Friday, it frequently is — I'll follow up with my Tighten a Wordy Paragraph to Half Its Length prompt for a second pass, because limpness and length are two separate problems with two separate fixes. Grab the Rewrite Passive, Hedging Prose into Active, Confident Writing prompt on Prompt Dock and run it on the most official-sounding thing you've written this month. Count the rows in the table it hands back. I promise it's more than you think, and every single one is a sentence you'll be able to fix on your own from now on.