OLD SCRIPT DETECTED
“The founder's cousin redlined my file”
Try this response:
“A comment from someone with no design background is one input, not a verdict.”SEE THE PRACTICE
Build a response for this thought—and one move to prove it.
THE THOUGHT
“The founder's cousin redlined my file”
YOUR RECORDED RESPONSE
“A comment from someone with no design background is one input, not a verdict.”
ONE PRIVATE MOVE
Open one file with the cousin's redlines and privately write a single line explaining your original reasoning before you touched anything.
Red Pins From a Cousin Who Doesn't Design
- 01 / The Comment Pin With No Portfolio Behind It
You open the file expecting your own notes and instead find a fresh column of red comment pins. Not from the founder. From the founder's cousin, who joined the review thread last quarter because he 'does branding on the side' and now weighs in on every layout. There's no brief attached to the notes, no rationale, just a string of opinions with the same authority as a client sign-off.
- 02 / Why Agreeing Out Loud Feels Safer Than Disagreeing
You make the changes fast and say 'good catch' in the thread, because pushing back risks looking precious in front of someone with the founder's last name, and the fastest way out of that discomfort is compliance. The relief is immediate: the thread goes quiet, the tension drops. But each time you do it, your own read on the work gets a little quieter too, until you stop forming one before you even open the file.
- 03 / The Second Read Before You Touch the File
The interruption point is the gap between seeing the red pins and clicking into the layout to fix them. Before you touch anything, read your own original reasoning for that choice once, in your head or on paper, as if it still counts. Then make whatever change you're going to make. The point isn't refusing the note — it's making sure your judgment gets a hearing before it gets overwritten.
TRACE · 01/04
How this script runs you
- You reopen a file after the cousin's redline and start changing it before rereading your own notes on why you made that choice.
- In the comment thread you write 'good catch' about a note you privately think weakens the layout.
- You've started keeping two versions of a layout in your head: the one you'd defend and the one built to survive his pass.
SOURCE_LOCATED · 02/04
The hidden rule underneath
The Client Override
If someone shares blood with the founder, their opinion on a design outranks your training, your process, and your own eyes, regardless of what their comment is actually based on.
FORGING_REPLACEMENT · 03/04
Replacement lines (record these)
- A comment from someone with no design background is one input, not a verdict.
- I can make the change without agreeing it improved anything.
- Being related to the founder isn't a design credential.
Generated per person in the app — these are the flavor, not your script. Yours is built from your exact words.
INSTALL · 04/04
The protocol, on one card
When I think
“The founder's cousin redlined my file”
I say
“A comment from someone with no design background is one input, not a verdict.”
Then I do one thing
Open one file with the cousin's redlines and privately write a single line explaining your original reasoning before you touched anything.
STATUS: READY_TO_INSTALL
Wipe this thought4 minutes. Your voice. Free.
The wipe protocol
- Write the thought exactly as it plays: "The founder's cousin redlined my file". Word for word — the wipe targets the sentence, not the vibe.
- Trace the rule and the avoided action. What does this thought conveniently excuse you from doing?
- Record the replacement lines below in your own voice. Speak like you mean it — no recording, no install.
- Run the loop: play it every morning and night, log one proof action a day for 7 days.
Straight answers
Does it matter that the redline came from the founder's cousin instead of the founder?
It changes who holds informal authority over the file, not whether the design reasoning behind your original choice was sound. The family tie explains why the note landed with extra weight, not whether the note itself was correct.
Is it wrong to make the change if I still think my original version was better?
Making the requested edit and privately keeping your own read of the work are two separate things. You can execute a note without treating it as proof your first instinct was wrong.
What if the cousin redlines nearly every file, not just this one?
A pattern across many files is worth noticing as a pattern rather than a series of unrelated one-offs. Naming that to yourself is enough for now — it doesn't require deciding anything about the working relationship today.
Related old scripts
Related self-checks
Related science
Researchers to explore
Related mechanisms
The research behind this script
- AIGA Design Census 2022 — AIGA, 2022
- Graphic Artists Guild Handbook: Pricing & Ethical Standards — Graphic Artists Guild, 2022