Write Your Personal Code of Conduct

Overview

You are going to write down the rules you choose to live by — not the rules your parents enforce, not the rules at school, but the ones you set for yourself because you have decided what kind of person you want to be. Knights had codes. Athletes have creeds. The best people you admire are running on a set of principles, whether they ever wrote them down or not. Over the next two to three weeks, you are going to figure out yours, put them into clear words, commit to them, and then test them against real life for thirty days.

This is one of the most grown-up things a person ever does. Most adults have never done it. They drift through their choices reacting to whatever shows up, with no standard to measure against. You are going to do better than that, starting now.

The Deliverable

A written, signed, dated Personal Code of Conduct — between 5 and 10 principles, each stated as a clear commitment in your own words, with a one-line explanation of what it means in practice. Plus a 30-day field-test log where you record, briefly, where you lived up to your code and where you fell short.

"Done" looks like this: a clean final copy you would be willing to read aloud to someone you respect, that survived thirty days of real testing, and that you have revised at least once because reality taught you something. A code you never tested and never changed is just a wish list. A code you tested, broke, and refined is a real instrument.

Materials & Tools

Project Phases

Phase 1: Plan (Session 1) — What Is a Code, and Why Have One?

A code of conduct is a set of principles you decide in advance, so that when a hard moment comes, you do not have to figure out who you are on the spot. You already decided. The decision is made in calm, and it carries you through the storm.

Spend this first session looking at examples — not to copy them, but to feel how they work. Read a scout law, an athlete's creed, a line from a historical figure you admire, a family motto. Notice two things: real codes are short (you can remember them), and real codes are specific enough to fail at (you can tell whether you kept them).

Then, in your drafting notebook, answer these warm-up questions. Do not write your code yet. Just gather raw material:

• Name three people, real or in stories, whom you genuinely admire. For each, what is the one quality that makes you admire them?
• Think of a time you were proud of how you acted. What did you do? What value was that?
• Think of a time you were not proud of how you acted. What value did you betray?
• If someone described you to a stranger, what would you want them to say? What would you not want them to say?

These four questions are your ore. Your code will be smelted out of them.

Phase 2: Build (Sessions 2-4) — Draft, Sharpen, Test for Realness

This is the core work. Expect to write things, hate them, and rewrite them. That is normal and good.

Milestone 1 — Rough principles (Session 2). Go back through your warm-up answers and pull out the values hiding inside them. If you admire your grandfather's honesty, "honesty" is a candidate principle. If you were ashamed of quitting, "I finish what I start" is a candidate. Write down as many as you find — ten, fifteen, it doesn't matter yet. Don't edit. Just harvest.

Milestone 2 — Cut and sharpen (Session 3). Now you become ruthless. Two jobs here:

First, cut to the real ones. You cannot live by twenty principles; you'll remember none of them. Cut to between five and ten — the ones that are actually yours, not the ones that sound good. Here is the test: for each principle, ask, "Have I ever broken this and felt bad? Could I break it tomorrow?" If a principle is impossible to break, it's not a principle, it's a description. "I breathe air" is not a commitment. "I tell the truth even when it costs me" is.

Second, make each one specific enough to fail. This is the most important step in the whole project. Vague principles are useless because you can never tell whether you kept them.

• Vague: "Be kind." → Specific: "I treat people who can do nothing for me as well as people who can."
• Vague: "Be honest." → Specific: "I do not lie to get out of trouble, even when the lie would work."
• Vague: "Work hard." → Specific: "I finish what I start, or I decide on purpose to stop — I do not just quietly quit."
• Vague: "Be brave." → Specific: "I say the true thing in the room, not just to my friends afterward."

For each principle, write the commitment, then one line: "In practice, this means ______." The practice line is where vague dies.

Milestone 3 — The honesty pass (Session 4). Read your draft alone, slowly, and ask one brutal question of each line: Is this what I actually believe, or is this what I think a good kid is supposed to say? Cross out anything you put there to impress someone. A borrowed principle is worthless — you won't keep it under pressure because it was never yours. What's left after this cut is small, and true, and yours.

Phase 3: Test & Refine — The 30-Day Field Test

A code you've only written is a theory. Now you run the experiment. For thirty days, keep a short log. Each night, ninety seconds:

• Name one moment today where your code was tested — even a tiny one.
• Did you keep it or break it?
• If you broke it, why? (Be honest. "I was tired" and "I wanted to look cool" are real reasons. Write the real one.)

At the end of thirty days, read the whole log. This is where the refining happens, and it is the most valuable part of the entire project:

• A principle you broke constantly is either not really yours (cut it) or stated wrong (rewrite it). Maybe "I never get angry" was always impossible; maybe the real principle is "I don't say cruel things when I'm angry."
• A principle you never even noticed testing might be missing the situations where it matters, or might belong to a part of your life you weren't watching.
• A situation that kept coming up but no principle covered means your code has a hole. Add a principle.

Revise the code based on what thirty days taught you. This revision is not failure — it is the difference between a real code and a fantasy.

Phase 4: Present — Sign It, and Say It Out Loud

Write the final, refined version on your good paper in pen. At the bottom, sign it and date it. The signature matters: it turns a list into a commitment.

Then read it aloud to one person you respect and trust — a parent, a grandparent, a mentor. Not to get permission, and not for them to grade it. You read it aloud because saying a commitment out loud, to a witness, makes it real in a way that a private note never is. Ask them only one thing afterward: "Does this sound like me?"

Keep the signed code somewhere you'll see it — inside a notebook cover, on a wall, in your wallet. Plan to revisit it on your next birthday and revise it again. You are not the same person at twelve that you were at ten. Your code should grow up with you.

Success Criteria

• The code has between 5 and 10 principles, each in your own words, each with a "in practice this means" line.
• Every principle is specific enough that you could actually fail to keep it.
• You can honestly say each principle is yours, not borrowed to impress someone.
• You completed a 30-day field-test log with at least 20 entries.
• You revised the code at least once based on what the field test revealed.
• The final version is written in pen, signed, dated, and read aloud to someone you respect.

Common Pitfalls

• The Saint's Code. Every principle is grand and impossible: "I am always kind, always honest, always brave, never selfish." No human keeps this, so you'll abandon the whole thing the first day you fail. Fix: write principles a real person can keep on a normal Tuesday.
• The Borrowed Code. You copy a scout law or a famous person's creed because it sounds impressive. It won't hold under pressure because it was never yours. Fix: the honesty pass in Session 4. Cut anything you didn't generate from your own life.
• The Vague Code. "Be good. Be kind. Try hard." You can never tell whether you kept it, so the field test produces nothing. Fix: the "in practice this means" line, ruthlessly applied.
• Skipping the field test. Writing it feels finished, so you stop. But the untested code is just a nice feeling. Fix: the field test is not optional — it is where the code becomes real.
• Treating revision as failure. You change a principle and feel like you cheated. You didn't. A code that survives contact with reality unchanged is a code you weren't honest about. Revision is the proof you took it seriously.

Extensions

• The Family Code. Bring your personal code to a family conversation. Could the family write a shared code together, the way teams and companies do? Lead that conversation — it's good practice for the Mentoring and Service projects in this pillar.
• Trace a principle to its source. Pick one principle and write a page on where it came from — a person, an experience, a story. Understanding why you believe something makes it harder to abandon.
• The Annual Revision. Put a recurring date on the calendar — your birthday works well. Each year, re-read last year's code, mark what changed, and write a short note on why. Over a decade this becomes a record of your own moral growth that almost no one else your age will have.
• Stress-test it against a real dilemma. Take one of the hard scenarios from the Ethical Dilemmas discussion in this pillar and run it through your code. Does your code actually tell you what to do? If two principles collide, which one wins — and should you write down the tiebreaker?