CreedOS

Home / Guides

How to write a personal principle about giving feedback you will actually keep

"Say something when something's wrong" is advice almost everyone already agrees with, and almost everyone still has a list of things they meant to say to someone and didn't — not out of dishonesty, but because the moment never quite felt like the moment. A personal principle about giving feedback is not a resolution to communicate better in general. It is a rule about the exact point where you notice something worth saying and have to decide, right then, whether to say it now, save it for later, or let it pass — written down on a day when you are not currently sitting on something you should probably mention.

Why "be more direct" cannot be kept or broken

"Be more direct," "speak up sooner," "don't let things fester" — these fail the same way "be more honest" fails. They describe an outcome you would like to be true of you in general, but they name no specific moment where you either did the thing or didn't. You can sincerely believe you are someone who says what needs saying, right up until you notice, months in, that a coworker has been doing the same thing that bothers you since the day you met them, and you have never once mentioned it. Nothing about "be more direct" would have caught that, because it never pointed at a moment small enough to notice while it was happening.

The two failures are opposites, and only one of them is yours

"I need to give feedback better" usually means one of two very different things, and it matters which one, because the fixes point in opposite directions.

The first is silence that accumulates. Something small happens, you decide it isn't worth mentioning, and you are right — once. It happens again, and you decide the same thing again, now partly because you didn't say anything the first time and raising it feels like it would also require explaining why you didn't. By the fourth or fifth time, you are not sitting on a small thing anymore; you are sitting on a pattern, plus your own silence about the pattern, and what eventually comes out is disproportionate to whatever triggered it — a small thing gets an oversized reaction, because it was never really about the small thing.

The second is the opposite problem wearing the same name: feedback that does get said, but said as a verdict on the person rather than a description of what happened. "You're careless with deadlines" lands as an accusation about someone's character; "the last two deadlines slipped and I didn't hear about it until the day of" describes two events. The first version is honest in the sense that you believe it, and it still tends to produce a defensive answer instead of a changed behavior, because a character judgment is something to argue with, not something to act on.

Most people lean toward one of these two far more than the other. A rule aimed at the wrong one will not help — telling someone who already blurts things out to "be more direct" makes the actual problem worse, and telling someone who already accumulates silently to "think it through more carefully first" gives them a better reason to keep saying nothing.

Mine your own pattern instead of guessing which one you are

Do not start by asking "am I good at giving feedback." Ask instead:

  • Is there something I have been meaning to mention to someone for more than a couple of weeks? What, specifically, has stopped me each time I almost said it?
  • When I think back to the last time I did say something critical, was it planned, or did it come out in a moment I hadn't chosen — mid-argument, at the end of a long day, in front of other people?
  • What did I actually say — a description of what happened, or a claim about what kind of person does that?
  • Is there a relationship where I notice I have simply stopped mentioning things, because the last time I tried it went badly or nothing changed?

Write the specific instance, not the tidy self-assessment. "I've been annoyed for three weeks that my roommate leaves dishes for me to deal with, and I keep deciding tonight isn't the night" tells you exactly where a rule needs to live. "I should communicate more openly" is a sentence you could write without learning anything about your own pattern, and it will not tell you what to do the next time the dishes are still in the sink.

Write the rule about the trigger and the wording, not the intention

A principle here needs two parts, because the two failures above are about two different moments: when you decide to say something, and how you say it once you have decided.

For the accumulation pattern, the rule is about a threshold, not a mood: if the same thing bothers me twice, I say something before there is a third time names a specific, countable trigger — you can point to the exact moment you either raised it or let it become "twice" again. For the verdict pattern, the rule is about form: I describe what happened and what effect it had, not what it says about the person gives you something to check a sentence against before you say it, not after.

Run the same two tests that apply to any principle. Can it actually be violated — is there a specific instance where you can say, honestly, whether you kept it or not? And does it cost something — a rule that never once pushes you to speak up when staying quiet was easier, or never once slows down a sentence you were about to fire off, is decoration rather than a principle.

Attach behavior standards you can actually check

The principle stays general; the standards underneath it are specific enough that someone else — or you, a week later — could tell whether you met them. For a principle like I raise something before it becomes a pattern I'm resenting instead of a moment I mentioned, useful standards might be: the second time the same thing happens, I name it within a day rather than waiting for a third; I describe one specific instance rather than a general tendency; I say what I need to happen next, not just what went wrong; if I notice I'm about to say something in anger, I wait until I'm not before I say it. None of these require the conversation to go well. They only require that you can look back and say whether you did the thing, which is what keeps this from being a private intention nobody, including you, can actually check.

Where this differs from honesty, and from taking criticism well

A principle about honesty governs what you say when you are already speaking — not misrepresenting what you believe to be true. A principle about giving feedback governs something upstream of that: whether you volunteer an observation nobody asked you for, aimed at someone who could actually act on it, when staying quiet was the easier and equally honest option. You can be scrupulously honest and still let something small turn into resentment for a month, because honesty was never the part that was missing — the decision to speak was. And this is the mirror image of a principle about taking criticism well, not the same principle from a different angle: that one governs the ten seconds after someone tells you something hard; this one governs the moment before you tell someone else something hard, which is a different kind of difficult, on a different timeline, and usually needs a different rule.

Stress-test it against the thing you're actually still sitting on

Take the specific thing from your own pattern-mining above — the coworker, the roommate, the friend — and run the rule against it directly. If the rule would have had you say something by now, in the specific way it describes, it has teeth; keep it as written. If it wouldn't have changed anything about this exact situation, the rule is aimed at the wrong moment and needs rewriting, not abandoning — the pattern you found is still real, the first draft of the rule just didn't reach it. This is also where you find out whether the version you wrote is actually yours, or borrowed from advice aimed at someone whose failure mode runs the opposite direction from your own.

Social is one of the six areas CreedOS ships templates for, alongside efficiency, emotion, money, health, and cognition, if you would rather start from an existing shape than a blank page. Each check-in has a note field for what specifically happened, not just a score, which is where a rule like this earns its keep — the pattern of what you keep almost-saying is usually invisible day to day and obvious the moment a week of notes sits next to each other in the review. It is free, with no in-app purchases.