Custom Instructions That Actually Change Output
Two fields, filled in once, rewrite the default voice of every conversation you'll ever have with ChatGPT.
Where the two fields live
Custom Instructions live at Settings → Personalization → Custom Instructions. Inside, there are exactly two text boxes, and understanding what each one is actually for is most of the battle. Field one asks: "What traits should ChatGPT have?" Field two asks: "Anything else ChatGPT should know about you?"
They sound similar enough to blur together, and most people who do open this screen write one vague sentence in the first box, skip the second entirely, and leave with the impression that custom instructions "don't really do much." That impression is backwards. The two fields aren't redundant — they answer two different questions, and skipping either one leaves half the configuration unset.
Field one: who is this, and what do they need
Field one is where you establish context ChatGPT would otherwise have to guess at, or worse, never bother asking for. Two things belong here:
Role / context. Who is on the other end of this conversation, and in what capacity? "A high school biology teacher planning lessons" gets a different kind of answer than "a biology PhD student writing a dissertation," even for an identical question about mitochondria. Naming the role up front means every answer gets pitched at roughly the right altitude by default, instead of you correcting the altitude after the fact, every time.
Background. These are standing facts that shape a meaningful share of your questions — your field, your team's tech stack, a project you're mid-way through, a constraint you're always working within. The test for whether something belongs here: would it change how ChatGPT should answer more than one type of question? If yes, it's background. If it's true for exactly one conversation, it doesn't belong in a setting that applies to every conversation forever.
Field two: how should it actually talk to you
Field two is where the real behavioral change lives, and it breaks into three useful sub-parts, even though the box itself is just one open text field.
Tone rules. Blunt or gentle? Formal or casual? Willing to disagree with you, or inclined to hedge? Most models default to a warm, agreeable, slightly hedged tone — perfectly pleasant, and often not what you actually need from a tool you're using to get real work done. Naming a tone preference explicitly overrides that default.
Format defaults. Bullets or prose? Headers or none? A rough length ceiling? Without a stated default, ChatGPT guesses at format per-message, which means the same kind of question can come back as three sentences one day and a twelve-bullet outline the next. A stated default makes output shape predictable.
Things to avoid. This is the field most people skip entirely, and it's often the highest-leverage sentence in the whole configuration. A concrete, named behavior to eliminate — no disclaimers, no "as an AI" framing, no softening a clear verdict into a maybe — does more to change the feel of every response than three paragraphs of positive instruction.
Notice what changed between those two panels: not the facts, not the model's capability — just the shape and directness of the delivery. That's the entire mechanism custom instructions run on. Nothing about the underlying reasoning improved; the packaging changed because the packaging was finally specified.
Why vague instructions quietly do nothing
"Be helpful and professional" is the single most common thing people type into field one, and it's close to useless — not because it's wrong, but because it describes the model's existing default behavior almost exactly. Telling ChatGPT to be helpful and professional is like telling water to be wet. There's no delta between the instruction and what would have happened anyway, so nothing visibly changes.
The fix isn't longer instructions — it's more specific ones. A rule like "structural feedback before wording feedback" or "cap first-pass answers at 150 words unless I ask for more" gives the model something to actually diverge from its default on. If you can't picture a concrete example of an answer changing shape because of a given instruction, that instruction probably isn't specific enough yet.
Build it: your own custom instructions
You're going to fill in a complete, realistic custom-instructions template for a specific persona — an engineering manager who wants blunt, structural feedback instead of generic encouragement — following the same field-one / field-two structure this lesson just walked through. Filling in someone else's persona first is deliberate: it's easier to spot vague, do-nothing instructions in a stranger's draft than in your own, and the pattern you learn to catch there transfers directly when you write your real ones afterward.