CreedOS

Home / Guides

How to write a personal principle about self-doubt you can actually keep

Start with what this cannot do. A personal principle will not make the doubt stop arriving the moment you have made a decision, sent the email, or finished the draft. Nothing written on a page reaches the feeling itself, and if you are waiting for certainty before you trust your own judgment, you may be waiting on a feeling that was never going to show up on schedule. What a principle can reach is one layer downstream — the decision you reopen for the third time with no new information, the message you ask someone else to read before you can send it, the finished piece of work you keep polishing past the point it needed polishing. Those are actions, and actions are the one part of self-doubt a rule was ever built to hold.

Why "just trust yourself" fails the moment it is tested

"Just trust yourself," "go with your gut," "you already know the answer" — these fail for the same reason "calm down" fails when you are already anxious. They name a feeling to have, not an action to take, and you cannot manufacture certainty on command any more than you can talk yourself out of doubting something the moment it shows up. You can have checked the numbers twice and still open the spreadsheet a third time before sending it, because the checking and the doubt run on separate tracks — one is about the work, the other is a habit of mind that does not care how thorough the work already was. A principle aimed at "feel certain" is aimed at something no rule was ever going to move.

There is a second reason advice aimed at the feeling keeps missing: the re-checking looks responsible from the outside, so it rarely gets questioned, including by you. Reading an email one more time before sending it, asking a second person the same question you already asked a first, rewriting a paragraph that was already clear — each one looks like diligence, not doubt, which is exactly why the pattern can run for years without ever being named as the thing costing you the evening. A principle aimed at "stop doubting yourself" is asking you to catch something dressed up as care. A principle aimed at the specific re-check — the fourth read, the second opinion you did not need, the redo of something that was already done — works on something you can actually see yourself doing.

Mine your own pattern instead of guessing at the cause

Do not start by asking "why don't I trust myself." The list of plausible reasons is long — a parent who checked your homework, one early mistake that got magnified, a field where you started later than the people around you — and it will not tell you what to write. Ask instead about the re-check, since the re-check is the specific, repeating thing:

  • What is the last decision I reopened after already making it, with no new information having arrived — a reply I second-guessed after sending, a plan I quietly reconsidered after already telling someone I'd go with it?
  • What did I ask someone else to confirm recently that I had, if I am honest, already checked myself and already knew the answer to?
  • What is a piece of work I redid a third or fourth time, where the first version, looked at now, was actually fine?
  • What happens in the moment someone raises an eyebrow, or says "are you sure," at something I had already decided — do I hold my read of the situation, or drop it on the spot, before they have even given me a reason to?

Write the actual instance, not the tidy label. "I sent the proposal, then opened it again forty minutes later to check a sentence I had already read six times, found nothing wrong, and still felt like I needed to look" tells you exactly where a rule needs to live. "I'm not a confident person" is a sentence you could write without any of that having happened, and it will not help you the next time you finish something that was already fine.

Write the rule about the re-check, not about feeling certain

A principle that names the feeling — "I will trust my own judgment" — aims at something you cannot directly command, and it fails the same test every mood-shaped sentence fails: there is no exact instance where someone could show you kept it or broke it. Aim the rule at the behavior instead. "I do not reopen a decision within a day of making it unless something genuinely new has come up" is a rule about an action: there is a moment you can notice, a specific thing to do instead of reopening it, and someone could describe afterward whether you did.

Run the same two checks that apply to any principle. Can it be violated — is there a visible instance where you either let the decision stand or went back to relitigate it with nothing new to go on? And does it cost something — a principle that never once stops you from checking something a second time, or never leaves a piece of work at "done" a little earlier than felt comfortable, is not actually redirecting anything. It is a sentence you agree with in the abstract and abandon the moment an actual send button is in front of you.

Attach behavior standards someone else could actually notice

Keep the principle general and put the specifics underneath it, since the specifics are what change as you learn more about your own pattern. For a principle like a decision I've made stays made unless new information arrives, useful standards might be: once I have sent something, I do not reopen it to reread it; if I want a second opinion, I ask for it before I decide, not after, so it is information rather than reassurance; I name out loud, to myself, when I am asking a question I already know the answer to; a piece of work gets one more pass after it first feels finished, and then it ships. None of these require the doubt to be gone first. Each one can be confirmed or denied by looking at what you actually did, which is what keeps this from being a private resolution nobody, including you, can check.

Where this differs from being closed to feedback

This is not a rule against changing your mind, and it is not license to ignore a colleague or a partner who is telling you something you would genuinely benefit from hearing. Real new information — a fact you did not have, a consequence you had not considered, a person with more context than you — should move you, and a principle that never bends to any of that is not confidence, it is just a different way of not thinking. The distinction this principle is actually drawing is between updating on evidence and updating on the mere presence of a question. "Are you sure?" is not evidence. A number you had not seen is.

Stress-test it against the time it actually cost you

Take the specific instance you can still describe in detail — the message read six times before it was sent anyway unchanged, the plan quietly reconsidered after you had already told someone you'd go with it, the draft polished for another hour past the point anyone would have noticed the difference — and run the principle against it directly. If letting the decision stand, or shipping the piece of work on the first pass that felt finished, would have changed how that day went, the rule has teeth; keep it as written. If it would not have changed anything, look again at what the doubt was actually protecting — sometimes the honest version of the principle is not about the re-checking at all, but about a specific outcome you are bracing for, and the rule needs to be rewritten to reach that instead.

Self-doubt is not one of CreedOS's six named categories on its own; it tends to show up inside the cognition template, one of the six areas the app ships templates for, alongside efficiency, social, emotion, money, and health, each with curated creeds and behavior standards already written that you can take as they are or edit until they name the exact moment your own pattern actually starts. An AI coach can also help think through what the standard should be once you have named the pattern. It is free, with no in-app purchases.