How to write a personal principle about leadership (for when nobody has to follow you)

"I lead by example" cannot be violated, because it does not name a moment. Nobody can point to the specific instance where you failed to lead by example the way they can point to the meeting where you stayed quiet, or the account of a failure you gave in private that did not match the one you gave in front of the team. A personal principle about leadership is not a claim about your style. It is a rule for the two ordinary moments that actually test it — and neither one requires a title.

You do not need the word "manager" for this to apply

Leadership, for the purpose of a personal principle, is not an org-chart fact. It is a structural one: it is any moment where someone else is taking a cue from what you do, because you have more information, more standing, or more experience in the room than they do. The oldest sibling deciding whether to name a problem at a family dinner, the person who has done the job longest quietly setting what "normal" looks like for the new hire, the friend who always organizes the trip and is the one everyone will credit or blame when it goes well or badly — all of these are leadership positions with no title attached, and all of them get tested by exactly the same two moments a manager faces.

The first moment: staying quiet is a decision, not an absence of one

Something is being decided badly in a room you are in, and you are the person with the most relevant information or experience. Saying nothing costs you nothing in the next five minutes. It is also, whether you intend it or not, a vote — your silence reads to everyone else as "this seems fine to the person who would know." The cost of staying quiet is real, it is just delayed and distributed across everyone who took your silence as a signal, which is exactly why it is easy to keep doing. A principle worth having names this moment directly, not the general virtue of "speaking up," which cannot be checked against any single meeting.

The second moment: what you do with credit and blame that could go either way

A result comes in that was genuinely a mix of your call and someone else's execution, or someone else's call and your oversight of it. This is the moment that actually reveals what "I put my people first" means in practice, because the two easy defaults both look reasonable from the inside: take the credit when it is ambiguous and hand off the blame when it is ambiguous, or the reverse. What you do here — specifically, whether your private account to yourself matches your public account to the person involved and to whoever else is listening — is the entire content of a leadership principle. Nothing else about the job is actually being tested in this moment except that.

Mine your own record instead of writing a value statement

Do not ask "what kind of leader do I want to be." Ask instead:

• The last time I was the most experienced or informed person in a room where something was going wrong, did I say so once, clearly, before it happened — or after?
• When a result was ambiguous, whose fault did I say it was, and did I tell the same story privately and publicly?
• Is there someone I currently let make a decision they are worse-positioned to make than me, because it is easier than either doing it myself or teaching them?
• Whose standard for "normal" have I quietly set just by what I do, without ever having said it out loud — and would I stand behind it if I had to say it out loud?

Write the specific instance. "I let the launch date stand because objecting again would have made me the difficult one, and I was the only person in the room who had seen this timeline fail before" tells you exactly where the rule needs to live. "I lead with integrity" tells you nothing you could ever check.

Write the rule about the moment, not the trait

Convert the pattern into an instruction for the specific instant, not a description of your character. Not "I lead by example," but "I say my objection once, clearly, before a decision is made, even if I am not the one making it." Not "I put my team first," but "my private account of a failure and my account to the person involved say the same thing." Run the same two tests as any principle: can it be violated — is there a real meeting where you would have to admit you did not do this — and does it cost something — spending the social capital of being the person who raises the awkward point, or giving up the comfortable version of a story where the mistake was not really yours to own.

Attach standards that don't depend on having authority

For a principle like I say the objection before the decision, not after it fails, useful standards might be: I raise it once, directly, to the person deciding, not afterward to someone else; if I did not raise it and the decision goes badly, I say so before anyone asks; when I am unsure whether something is my call to make, I say that out loud instead of quietly deciding it is. None of these require a job title, a direct report, or a meeting where you are formally in charge. They only require that you were, in that moment, the person with more information than someone else.

Where this differs from a management technique

Delegation cadence, how often you run a one-on-one, whether you give feedback in public or private — these are tactics, and tactics are meant to be swapped when circumstances change. A leadership principle sits above them: it is the rule that decides whether a given tactic is even being used honestly, or is being used to look like leadership while avoiding the two moments above. A very well-run one-on-one schedule can still coexist with someone who has never once told their team the real reason a project failed.

Stress-test it against the case you'd rather not think about

Take the specific instance where you had more standing than someone else and the outcome was bad — the meeting, the failed handoff, the decision you let stand. Run the principle against it directly. If naming the objection, or matching your private account to your public one, would have changed what actually happened next, the rule has teeth. If it would not have changed anything, you have found a different, more accurate principle hiding underneath the one you started with — write that one instead.

Leadership is not one of the six areas CreedOS ships templates for, but the moments it describes — naming a problem before it happens, keeping one account of a failure instead of two — fit naturally under the social and efficiency templates, each with behavior standards already written that you can take as-is or edit until they name your actual pattern. The daily check-in has room for one concrete thing you did or didn't do, which is the right size for the fact this kind of principle asks you to record. It is free, with no in-app purchases.