OLD SCRIPT DETECTED
Try this response:
“I can carry out the change without pretending it improved the work.”SEE THE PRACTICE
THE THOUGHT
“They made me make it worse”
YOUR RECORDED RESPONSE
“I can carry out the change without pretending it improved the work.”
ONE PRIVATE MOVE
Open a past or current file and, in a private note field, write two columns: “my recommendation” and “what was changed.” Add one sentence under each, then save and close it without sending anything.
SCENE_01
You’re staring at the latest mockup on your screen, and the logo has already been nudged up again. It sits there heavier than it did an hour ago, louder in the header, and you feel the familiar jolt: They made me make it worse. Not because you wanted this version, but because the direction came down after you’d already seen the cleaner one.
SCENE_02
What stings isn’t the change itself. It’s the private conclusion that follows: if you can be pushed into making something clumsy, then maybe your eye was never the point. So you start softening your own judgment in advance. You offer too many options, phrase your recommendation like a shrug, and call your actual instinct a preference instead of a read.
SCENE_03
A more accurate read is simpler: you can execute someone else’s request without agreeing that it improved the work. The edit is theirs; the judgment still belongs to you. On the next round, you can mark which version you stand behind, keep a note of why, and leave the file with one clear recommendation instead of hiding it inside three nearly equal choices.
TRACE · 01/04
SOURCE_LOCATED · 02/04
The Client Override
If someone overrules the cleaner version, then your judgment must be unreliable, so the safest move is to flatten your opinion before anyone can reject it again.
FORGING_REPLACEMENT · 03/04
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
When I think
“They made me make it worse”
I say
“I can carry out the change without pretending it improved the work.”
Then I do one thing
Open a past or current file and, in a private note field, write two columns: “my recommendation” and “what was changed.” Add one sentence under each, then save and close it without sending anything.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
Then the thought still needs separating from the fact. A bad revision does not prove your judgment was worthless; it only shows the final decision was shared or overridden. Naming that difference helps you stop treating every future request as evidence against yourself.
Because once a change has landed badly, it can feel safer to sound neutral than to be visibly wrong. But neutrality can erase useful guidance. A clearer move is to name your read once, in plain language, and let the outcome be separate from your worth.
No. The point is not to resist every edit. It’s to stop converting a revision you didn’t choose into a verdict on your competence. You can still implement the change while keeping track of what you thought was stronger.