QUIET
Quiet signal
“The design has to be impressive, not simple” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Simple is the flex. Anyone can make it complicated.”
SCRIPT CHECK · 60 SECONDS
Five quick questions show how often it appears, how believable it feels, and what it makes you avoid. You’ll get one private next step.
This is not a diagnosis and there is no pass or fail. It measures the current frequency, credibility, and behavioral cost of “The design has to be impressive, not simple”, including the private rule underneath it: If the work looks simple, it may look easy to replace. So you make it visibly clever, layered, or polished enough that people notice the craftsmanship before they notice how runnable it is.
QUIET
“The design has to be impressive, not simple” appears, but it rarely gets the final say. Keep this line available for higher-pressure moments: “Simple is the flex. Anyone can make it complicated.”
PRESENT
“The design has to be impressive, not simple” wins some small decisions before you catch it. Your useful interruption is: “Delegating proves I built something others can run. That reads as senior, not as spare.”
ACTIVE
“The design has to be impressive, not simple” is shaping action often enough to deserve a deliberate counterexample. Start privately and concretely: In one design file, duplicate the current screen and remove one purely decorative element from the copy. Rename it “plain version” and leave it saved for comparison; do not share it.
DOMINANT
Right now, “The design has to be impressive, not simple” is steering many of the moments you measured. That is a pattern reading, not a diagnosis or character verdict. Begin with one reversible receipt: In one design file, duplicate the current screen and remove one purely decorative element from the copy. Rename it “plain version” and leave it saved for comparison; do not share it.