How to write a personal principle about creativity
Most attempts at a creativity principle land in one of two failed shapes. The first is a mood: "be more creative," which cannot be violated, so it never gets tested and never changes anything. The second is a quota: "write 500 words a day" or "post something every day," which can be violated, but ends up optimized against exactly like a habit streak — the words get written, the post goes up, and none of it is the thing you actually wanted to make more of. A creativity principle that works is neither of those. It is a rule about the conditions you protect and the habits you keep around starting and finishing, not a rule about how much gets produced.
Why "make something every day" turns into filler
A daily output quota does exactly what any tracked number does: it gets defended once it exists, and the cheapest way to defend it is to lower the bar for what counts. Three weeks into "write every day," most people are still writing every day — a paragraph they would delete on any other week, kept alive purely so the count does not break. The quota cannot tell the difference between a page that came from real attention and a page that came from not wanting to lose a streak, because both produce a page. The thing you actually cared about — making something you would not be embarrassed to look at again — was never what the number was measuring.
Mine the actual conditions, not the ideal ones
Do not start with "when am I most creative," because you will answer with a romantic guess — early morning, a candle, silence — that is often not true of your own history. Ask instead:
- Think of the last three things I made that I was genuinely glad to have made. What was happening in the hour before I started each one?
- What is the thing that most reliably kills an attempt before it starts — not a big obstacle, the small one that shows up almost every time?
- Is there a version of "bad" I refuse to let myself produce, even as a first draft, and does that refusal cost me more finished work than it protects?
- When I look back at something I made that I am proud of, was the first version of it good, or was it something I was willing to fix later?
Write the specific pattern, not the flattering story. "I only ever finish something when I let the first pass be genuinely bad and fix it the next day" is real material. "I do my best work under pressure" is usually just the one time pressure happened to work, remembered because it is a better story than the ten times it did not.
Write the rule about the condition, not the count
A quota measures output. A principle protects the thing that makes output possible. "I make something every day" is a rule about a tally. "I let the first version be bad on purpose, and I do not judge it until the next sitting" is a rule about a habit that determines whether anything gets finished at all. The second one can still be violated — did you rewrite the first line four times instead of pushing through a bad draft, yes or no — but violating it says something real about what happened, instead of just registering that the quota was missed.
Run the same two checks that apply to any principle. Can it be violated — is there a specific, nameable moment this week where you either protected the condition or let something override it? Does it cost something — a creativity principle that never once means turning down an easier, more finished-looking task in favor of the messy unfinished one is not actually steering anything.
Attach behavior standards that describe the habit, not the product
The principle stays about the condition; the standards underneath it should be checkable without judging whether the result was any good. For a principle like I protect unfinished time before I protect finished-looking time, useful standards might be: the first thing I open in a work session is the unfinished thing, not email; I do not evaluate a first draft — I only ask whether it exists; once a week I look at something I abandoned and decide, on purpose, to continue it or let it go, instead of leaving it in limbo by default. None of these ask whether Tuesday's output was good. They ask whether the conditions that make good output possible were actually protected that day, which is the question a principle can answer honestly and a quota cannot.
Where this differs from a productivity goal
A goal like "finish the draft by March" is aimed at a specific outcome and is genuinely useful for that. A principle is aimed at something that outlives any one project — what you do, by default, at the start of a session, in the face of a bad first attempt, when something you made did not turn out how you wanted. The goal changes every time the project changes. The principle should still be true on the next project, and the one after that, which is what makes it worth writing down separately instead of folding it into whatever you happen to be working on this quarter.
Stress-test it against the last thing you abandoned
Take something you started and quietly stopped finishing, and run the principle against it honestly. If the rule would have caught the actual moment it stalled — the point where you started judging the draft instead of continuing it, or the day the condition you needed simply was not protected — it has teeth; keep it as written. If it would not have changed anything about that specific failure, the principle is probably still describing an ideal version of how you work rather than the real one, and is worth rewriting around what actually happened, not what you wish had happened.
Creativity is not one of CreedOS's six named categories on its own; it tends to show up inside the cognition and efficiency templates, two of the six areas the app ships curated creeds for, alongside social, emotion, money and health, each with behavior standards already written that you can take as they are or edit until they describe the actual condition that decides whether you finish something, not the count of things you produced. It is free, with no in-app purchases.