What Creators and Innovators Can Learn from Own Your Greatness
Putting original work into the world, a design, a piece of writing, a product nobody has quite built before, means there is no established rubric to prove you did it right. It is easy to treat every wave of hesitation before hitting publish as proof the work, and you, are not good enough yet. Own Your Greatness offers a steadier read: that hesitation is a familiar pattern with a shape, not a verdict on your creative ability.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Naming the exact moment doubt shows up
A creator's doubt tends to spike at specific points, right before sharing new work publicly, after a lukewarm response, or when comparing a rough draft to someone else's finished piece.
Treating the doubt as a permanent verdict on your talent, rather than tracing it to the launch or comparison that triggered it, makes it harder to work with directly.
After a spike, name the exact trigger, the launch, the review, the comparison, rather than letting it collapse into a broad statement about whether you are a real creator.
Questioning the story before it stalls the work
Once triggered, a familiar story often follows fast, something like this only worked because of luck or timing, and it can stall the next project before the story is even examined.
Starting the next piece while still carrying the last launch's story means the same hesitation shows up regardless of what actually happened with that earlier work.
Check the story against the evidence, the actual response and what you actually controlled, then take one small step, sharing the draft, submitting the pitch, instead of waiting to feel certain first.
Practicing until sharing feels less exposed
Handling one hard launch well does not mean the next one feels easy, because a single success does not retrain the underlying pattern on its own.
Treating one well-received project as proof the doubt is solved skips the repetition that actually builds a steadier response across projects.
After each launch, pitch, or public share, briefly note which step helped, naming the trigger, questioning the story, or acting anyway, so the pattern strengthens with each new piece of work.
When the field itself is part of the story
A creator working in a field with few people from their background, or facing consistently harsher scrutiny than peers releasing similar work, may be noticing something real about the field, not manufacturing doubt from nothing. Own Your Greatness is careful here: some impostor feelings reflect a genuinely uneven creative landscape, not solely an internal distortion to fix alone. Holding both the framework and a fair look at the field keeps the practice honest rather than turning it into private self-blame.
A sudden trigger, a harsh comment right after a launch, can land in the same week as a slower doubt that has built since a project stalled months ago. When that happens, handle the nearer moment first, using the three-step sequence to get through today's reaction, then return to the slower pattern once the immediate sting has faded. Trying to resolve months of accumulated doubt in the hours after one launch usually leaves neither concern well handled.
Name one thing, honestly
- Which specific creative moment, a launch, a review, a comparison, most reliably triggers your doubt? - What story do you tell yourself after a quiet or harsh response, and does it match what you actually controlled? - Where might the field or platform, not just your own thinking, be shaping how confident you feel sharing your work?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
After each launch, pitch, or public share, briefly note which step helped, naming the trigger, questioning the story, or acting anyway, so the pattern strengthens with each new piece of work.