Most people have standards. Fewer have written them down. The gap shows up in the awkward moments: the invoice with an error in your favour, the favour a friend asks for that you would rather refuse, the meeting where staying quiet is easier than telling the truth.

A personal code of conduct decides those moments in advance. Not a manifesto and not a vow of perfection — a working reference you can read in two minutes and apply in ten seconds. Here is how to build one that survives contact with real life.

Why a written code beats good intentions

Intentions are vague by design. They let you feel principled without committing to anything specific. A written code names the behaviour, so you can tell whether you followed it.

The aim is not rigidity. It is to move a decision out of the moment when you are tired, flattered or embarrassed, and into a quiet half hour when you can think clearly. Keep the result to one page. If it takes ten minutes to read, it becomes decoration.

There is a second benefit: a written code is portable. You can carry it in your head, but writing it down forces you to choose. A doctor who says “do no harm” has a principle. A doctor who writes “I will explain risks in plain language before asking for consent” has a practice. The same difference applies to you.

Start with evidence, not aspiration

Aspirational lists produce words like “excellence” and “integrity” that nobody can act on. Begin with what you already do. Your calendar, your bank statement and the messages you sent when you were annoyed are honest evidence of what you actually prioritise. Then ask yourself:

• What did I do recently that I would happily do again, even if no one had noticed?
• Which decision left me uneasy, even though it worked out well?
• When have I felt most like myself, and what was I doing?

Write down every value word that surfaces — fifteen or twenty is fine — then group and cut. Most will merge: honesty, candour and straight dealing are often one instinct. Five or six values, used often, beat a long list you cannot recall.

Turn each value into rules you can follow

A value is a direction; a rule of conduct is a step. Convert each value into two or three specific behaviours, phrased as “When X happens, I will Y”, so you can tell whether you kept it.

• Fairness: I will correct a mistake that benefits me, even when nobody notices.
• Reliability: I will give a clear yes or no within a day, not a hopeful maybe that lasts a week.
• Respect for other people’s time: I will arrive when I said I would, or message before I am late — never after.
• Credit: I will name who did the work, not just the people in the room.
• Money: I will not spend money I have not yet earned on things I do not need.

If you cannot picture yourself breaking a rule, it is too vague. Rewrite it until it names a real temptation.

Test it against real scenarios

Write six short scenarios from your own life — past ones and likely ones — and work out what the code tells you to do. Include a few of each type:

• Temptation: a small gain, little chance of being caught, no obvious victim.
• Pressure: someone senior, loud or loved pushes you the other way.
• Conflict: two values pull apart — loyalty against honesty, kindness against fairness.
• Exhaustion: it is late, you are worn out, and the easy option is right there.
• Ambiguity: nobody is clearly wrong and any choice will disappoint somebody.

Three questions to ask of each rule

• Can I keep this when I am tired, rushed or embarrassed?
• Would it hold up if everyone kept it — and if nobody did?
• Would I be comfortable if my rule and my record against it were made public?

Where a scenario leaves the code silent, treat that as useful information. The gap is not failure; it is the next rule waiting to be written. If you cannot decide in advance, decide now what you would want to have done, then add a line. If two values genuinely conflict, do not pretend there is a clean answer. Write down the priority order for that specific conflict. For example: honesty first, then kindness; or safety first, then loyalty. A code is not a machine that produces answers. It is a set of commitments that makes your defaults better.

Put it in a format you will actually use

One page. Plain language. No footnotes. A simple structure works well:

1. My five values: the words that matter most.
2. What each value means in practice: two or three rules per value.
3. When values conflict: the order I will choose, and why.
4. My warning signs: the situations where I am most likely to drift.
5. My repair rule: what I do when I break my own code.

Keep it somewhere you will see it. A note on your phone, the inside cover of a notebook, a file called “read me first”. The point is not to admire it. The point is to consult it before a hard conversation, a financial decision, or a favour that makes you uneasy.

Review it before life tests it

A code written once and never revisited becomes a museum piece. Set a regular review: every three months, or after any week that felt ethically messy. Ask three questions.

• Which rule did I keep most easily, and why?
• Which rule did I break, bend or forget?
• What new situation has appeared that the code does not cover?

Then make one small change. Add a rule, sharpen a vague phrase, or delete something that sounded noble but never affected a decision. A code that grows to twenty pages is no longer a code; it is an archive. Keep cutting until every line can pass the ten-second test: can I remember this when it matters?

Use examples to make it concrete

Abstract rules collapse under pressure. Concrete examples hold. Suppose your value is generosity. A rule like “be generous” is useless at 11 p.m. when a friend asks for money you cannot spare. A better rule is: “I will give to causes I have chosen in advance, and I will not make lending decisions when I am tired or guilty.” That rule protects both your generosity and your household.

Suppose your value is courage. “Speak up” is not a rule. “In meetings, if I disagree with a decision that affects people I manage, I will say so once, clearly, before the meeting ends” is a rule. It tells you when, where and how much. You can review it later and know whether you did it.

Decide what happens when you fail

You will break your code. Everyone does. The question is whether the failure becomes a lesson or an excuse. Build a repair rule before you need it:

• Acknowledge it: name the rule you broke, at least to yourself.
• Repair it: correct the error, apologise, return the money, credit the colleague.
• Learn from it: ask what made the rule hard to keep. Was it too vague, too strict, or badly timed?
• Revise it: adjust the rule if it was unrealistic, or strengthen it if you simply ignored it.

Shame is not a strategy. Repair is. A code that cannot survive your worst day is not a code; it is a performance.

Keep it small, honest and yours

A personal code of conduct is not a legal contract, a religious vow, or a personality. It is a tool for aligning your actions with your values when the pressure is on. It should sound like you on a good day, not like a corporate values poster.

Start with five values. Turn each into two or three rules. Test them against temptation, pressure, conflict, exhaustion and ambiguity. Write down what you will do when two values collide. Review it regularly. Repair it when you fail.

Do that, and the awkward moments lose some of their power. You will still face them. But you will not be deciding from scratch. You will be keeping a promise you made to yourself when you could think clearly — which is exactly when a code earns its keep.

Photo: Larry Hyler / Pexels