In this guide7 sections
You already do the work. The problem is nobody sees it. You ship a landing page, fix a funnel, test three hooks, and all of it dies inside your own head or a private Notion doc. Meanwhile the operators building an audience are not smarter than you. They just let people watch.
Austin Kleon's Show Your Work! is the manual for that. This is the applied version: how to run his ideas as a repeatable loop, powered by AI, so your real build sessions become posts without you turning into a self-promotion machine you hate.
Show your work, applied, means treating every build session as raw material: you document what you actually did that day, then use AI to shape the useful part into one short public post. You share the process, not a pitch, so an audience compounds as a byproduct of work you were doing anyway.
What does "show your work" actually mean?
Kleon's Show Your Work!: 10 Ways to Share Your Creativity and Get Discovered (2014) makes one core move: stop hoarding the finished product, start sharing the process. His chapter titles are the whole playbook, and a few matter most for a solo operator:
- You don't have to be a genius. Kleon replaces the lone-genius myth with "scenius," a whole scene of people trading ideas in the open. You do not need a big result to share. You need to be in the scene.
- Think process, not product. The finished asset is one post. The forty decisions it took to get there are forty posts.
- Share something small every day. Not a manifesto. One useful scrap: a screenshot, a before/after, a thing that broke.
- Don't turn into human spam. Show the work, do not beg for attention. The difference is whether the reader learns something without you asking for anything.
The trap most operators fall into: they think "showing work" means broadcasting wins. It does not. It means letting people see the messy middle, which is the part they can actually learn from and the part that builds trust.
Why does sharing the process beat sharing the result?
A result is a billboard. A process is a story, and people follow stories.
When you post "launched my course," there is nothing for anyone to do with that. When you post "here is the exact opt-in headline I tested against my control, and why the loser lost," you have handed a stranger something usable. Kleon's point is that human beings are interested in what other human beings do, the reasoning and the fumbling, not just the trophy at the end.
For a solo operator this solves the hardest content problem: what do I even post? You stop inventing content and start reporting it. Every build session is already generating the material. Documenting the process also compounds a brand moat, because a body of work showing how you think is far harder to copy than a single polished output.
How do I turn a build session into a post without it feeling like bragging?
Run a fixed loop so it stops relying on motivation. Five steps, ten minutes at the end of a work block:
- Capture (during the work). Keep a scratch file open. When something is decided, breaks, or surprises you, drop one raw line in. No formatting. "Cut the second CTA, page felt cluttered." "Hook C beat A, curiosity gap did the lifting." This is Kleon's "document, don't create."
- Pick one. At the end of the session, choose the single scrap a peer would find most useful. One post, one idea. Resist dumping the whole day.
- Shape with AI. Feed the raw scrap plus context to your model and have it draft a short, process-first post in your voice. You are not asking it to invent, only to structure what you already did.
- Add the reasoning. The line AI cannot supply is why you made the call. Paste in your actual thinking. That sentence is what makes it yours and what makes it trustworthy.
- Publish and move on. Ship it the same day while it is still true and specific. Then get back to building.
The anti-bragging safeguard is built into step 2: you are sharing a decision and its logic, not a victory lap. A reader finishes it slightly smarter. That is the line between showing work and human spam. To go wider, one documented session can also seed a thread, a short video, and an email: capture once, publish in several places.
Prompt to turn a raw build session into a build-in-public post
Paste your scratch notes into the brackets. The prompt keeps the post process-first and stops it drifting into a pitch.
You are my ghostwriter for a build-in-public post. I am a solo operator building and selling digital assets. Voice: direct, no fluff, no hype, no guru-speak. No em dashes. Here are my raw notes from today's build session: [PASTE RAW SCRATCH NOTES: what I worked on, what I decided, what broke, what surprised me] The single most useful idea for a peer here is: [ONE-LINE PICK, e.g. "why I killed the second CTA on the sales page"] My actual reasoning for that decision: [YOUR REAL THINKING IN A SENTENCE OR TWO] Write ONE short post (under 120 words) that: - Opens with the specific decision or thing that broke, not a windup - Shows the process and the reasoning, teaches one usable takeaway - Does NOT pitch, sell, or ask for follows, likes, or shares - Ends on the takeaway, not a call to action - Reads like I typed it between work blocks, not a marketer Then give me 3 alternate one-line openers I could swap in.
Do not ship the raw output. Read it, cut any line that sounds like a brand account, and make sure the reasoning sentence is truly yours. AI structures the scrap. You supply the judgment. If you want the post to sound less synthetic, run it through the same lens as writing copy with AI without sounding like AI.
The honest limits
Showing your work is not a growth hack and this loop will not go viral on day three. A few things to be straight about:
- It compounds slowly. The value is a body of work over months, not one breakout post. Kleon's tenth chapter is literally "stick around." If you quit at week four you get nothing.
- Not everything should be public. Unshipped client specifics, unverified numbers, and half-baked strategy you have not tested yet stay in the scratch file. Show decisions, not confidential details.
- AI drafts, it does not decide. The model cannot generate the reasoning that makes a post worth reading. If you skip step 4, you are publishing filler, and readers can smell it.
- Do not fake the process. The whole trust mechanism depends on it being real. Inventing a "journey" you did not live is the fastest way to burn the audience you are trying to build.
Used honestly, the loop is close to free. You were already doing the work and already thinking through the decisions. You are just leaving the door open while you do it.
Frequently Asked Questions
What is Austin Kleon's "Show Your Work" about in one line?
It argues that sharing your creative process daily, not just your finished results, is how you build an audience and get discovered. Kleon frames it as self-discovery over self-promotion: let people watch how you work, teach what you know, and generosity does the marketing for you.
Isn't building in public just bragging or self-promotion?
Only if you post trophies. The fix is to share a decision and the reasoning behind it so the reader learns something usable. Kleon calls the bad version "human spam," where you demand attention. The good version hands over a takeaway and asks for nothing, which reads as generous, not needy.
How is this different from just posting on social media?
Random posting means inventing content and chasing trends. This is reporting: you document real build sessions and publish the most useful scrap. The raw material already exists, so you never face a blank page, and every post is grounded in work you actually did rather than a take you manufactured to fill a slot.
How often should a solo operator post to make this work?
Kleon's rule is "share something small every day," but consistency beats frequency. Pick a cadence you can hold for months, even two or three times a week, and never miss it. One documented session can also be repurposed into a post, a short video, and an email, so a few work blocks a week can feed several channels.
Where to take this next
Pick your next build session and keep a scratch file open the whole time. Capture the decisions as they happen, run one scrap through the prompt above, and ship a single honest post before you close the laptop. Do that for thirty days and you will have a body of work no competitor can copy, built entirely from work you were doing anyway. Show Your Work! sits inside a wider stack of operator books worth applying, mapped in the Operator's Bookshelf hub. When you are ready to build the loop with other operators who show their work daily and pressure-test each other's posts, join the operators inside Asset Academy.
Stop reading about copy. Write it with operators who ship.
Inside the Asset Academy community we build the copy, funnels, and offers together, with the prompts and the feedback. $96/mo, or save with annual.
Join the community →
