How to Apply Show Your Work: Learn in Public and Build a Body of Work

Document, Don't Create

Show Your Work! came out in 2014 as the companion to Austin Kleon's earlier hit Steal Like an Artist. The first book was about where ideas come from: you build new work out of the influences you collect. This one is about what to do once you're making things, and its argument is almost embarrassingly simple. Let people see how you work.

The idea that unlocks the rest of the book is the distinction between creating and documenting. Most people freeze at the word "content." It sounds like a second job, like you now have to be a producer on top of being a person who makes things. Kleon's relief valve is that you don't have to create anything extra at all. You're already doing the work. You just have to leave the lights on while you do it.

Think about what that means in practice. A woodworker doesn't need to script a tutorial. She can photograph the half-finished chair on her bench, the jig she built to hold an awkward joint, the cut she had to redo. None of that is invented. It's the residue of a normal afternoon, and to anyone learning the craft it's gold. The work was going to happen regardless. Documenting it costs a photo and a sentence.

This reframe matters because it removes the most common excuse. You don't share because you think you have nothing worth saying yet, and you're waiting until you do. Kleon's answer is that the waiting is the mistake. The byproducts of ordinary work, the scraps and notes and dead ends, are interesting precisely because they're real. Start there, and the pressure to manufacture something impressive disappears.

You Don't Have to Be a Genius

The biggest thing standing between most people and sharing is a quiet belief that you have to be an expert first. Who am I to post about this when I've been doing it for six months? Kleon spends real energy dismantling that, and his case is the part of the book most worth taking to heart.

His phrase is "the amateur." Not as an insult, but as a position with genuine advantages. An amateur is someone who does something for love, who is still close enough to the beginning to remember what was confusing. That memory is rare and valuable. The expert long ago forgot what it was like not to know, which is why expert explanations so often skip the step you're actually stuck on. The person three weeks ahead of you is sometimes a better teacher than the person thirty years ahead.

Here's a concrete version. Imagine two people writing about learning to cook a particular dish. The chef writes a flawless recipe that assumes you already know how to deglaze a pan and why the order of ingredients matters. The amateur writes, "I burned the garlic twice before I realized I was supposed to lower the heat the second the pan smelled good, here's what that actually looks like." For a true beginner, the second one is more useful, more honest, and more likely to be read all the way through.

So the move is to share while you learn, not after you've mastered something. Document the questions you're chasing right now. The gap in your knowledge is the most relatable thing about you, and narrating how you close it is a gift to everyone one step behind. You're not claiming to be the authority. You're saying, here's the trail I'm cutting, walk it with me.

Think Process, Not Just Product

There's a reason the bloopers reel sometimes gets more love than the movie. People are wired to care about how things get made. The finished product is a wall; the process is a door. Show Your Work! leans hard on this, and it's the difference between sharing that connects and sharing that just announces.

A polished result invites admiration and not much else. You see a beautiful thing, you nod, you scroll on. But show the rough sketch next to the final piece, the version you scrapped, the constraint you wrestled with, and suddenly the viewer is inside the work with you. They have something to think about, react to, maybe argue with. Process is what turns an audience of spectators into a group of people who feel involved.

Process is also where the teaching lives. The product shows what's possible; the process shows how. If you want your work to actually help someone, the polished version is almost useless on its own. They need to see the choices, the tradeoffs, the moment you went left instead of right and why. That's the stuff a beginner can use, and it's the stuff you can only share if you've been documenting along the way rather than swooping in at the end with a finished thing.

The practical instruction is to get comfortable showing the middle. Not just the launch, but the draft. Not just the answer, but the wrong turns that got you there. This feels exposing at first, because we're trained to present only the polished face. But the messy middle is the most human and the most useful part of anything you make, and it's the part nobody else is showing.

Turn Your Reading Into Public Artifacts

Here's where the book speaks directly to anyone who learns by reading, and where it stops being only about people who paint or code or build furniture. Kleon argues that before you've made anything of your own, you can share your taste. What you read, what you quote, what you react to, all of it is a form of showing your work.

This is the part people miss. They think "showing your work" requires output, some original thing you've produced. But the influences you collect are themselves a body of work. The passages that stop you cold, the lines you'd want to remember, the ideas you find yourself arguing with: that collection is a portrait of a mind in motion. Long before you've written your own book, you can show the marginalia.

This is exactly what a public highlighting practice is. When you highlight a passage with Glasp's web highlighter, you're documenting a decision, this sentence and not that one mattered to me. Add a note about why, and you've turned passive reading into a visible artifact of your thinking. Do it consistently and your highlights become a running record of what you've been learning and how your taste is shaped, which is showing your work in the most literal sense, no original creation required.

It also taps into something old. Sharing what you read has always been how knowledge spreads, a history we trace in reading was always social. The modern version is that your reading lives in the open by default, where others chasing the same questions can find it through the community feed, and you can find theirs. The same act builds a digital commonplace book, a personal collection of what struck you, except this one is searchable, shareable, and discoverable by people on the same path.

Share Something Small Every Day

One of the book's most freeing instructions is about size and frequency. You don't owe anyone a masterpiece. You owe them, and yourself, a small honest update on a regular basis. Kleon's framing is to find one small thing you can share each day: something you learned, something you noticed, something you're working on.

The logic is the same compounding logic behind any steady practice. A single big post is a bet that might not pay off, and the pressure to make it perfect is exactly what keeps it forever unfinished in your drafts. A daily small thing has no such weight. It's allowed to be minor. It's allowed to be a single highlight with a one-line reaction, a screenshot of what you're stuck on, a half-formed thought. Because the bar is low, you actually clear it, and clearing it daily is what builds the habit and the body of work.

Picture two people over a year. One is saving up for the definitive thread that will establish them as a thinker, and posts it roughly never. The other shares one small thing they learned most days: a quote, a question, a tiny realization. At the end of the year the first person has a great idea and no evidence of it. The second has three hundred artifacts, a visible trajectory, and a small group of people who've been watching them grow. The compounding isn't in any single post. It's in the accumulation.

The trick to sustaining it is to lower the friction until daily is genuinely easy. This is where a reading-and-highlighting habit carries the load for you. If you're already marking what strikes you as you read, you're already generating shareable small things; you just have to leave them public and add the occasional sentence. The day's update isn't a separate chore. It's the residue of a normal day's reading, which is the whole "document, don't create" idea pointed at your most consistent activity.

Tell Good Stories About What You Learn

A pile of artifacts isn't enough on its own. Kleon is clear that the work needs a story around it, because people don't connect with objects, they connect with narratives. The same highlight, the same project, the same lesson lands completely differently depending on whether you frame it well.

The core skill is learning to talk about your work in a way that invites people in rather than shutting them out. That doesn't mean inflating it or pretending it's more important than it is. It means giving it context: where it came from, what problem it's solving, what you were confused about, what changed your mind. A study you highlighted is just a fact until you say "this reframed how I think about X, here's why," at which point it becomes a story someone can carry.

Two ideas from the book are worth pulling out here. First, give credit generously. When you share what influenced you, name the source, link to the person, point upstream. This isn't just etiquette; it's how you become a trustworthy node in a network instead of someone who launders other people's ideas. Crediting your influences is part of showing your work honestly, and it's how the people you admire come to know you exist. Second, the story arc matters more than polish. A clumsy sentence with a real arc beats a beautiful sentence about nothing.

For a reader, the story is usually the connection. The interesting move is rarely "here's a fact I found." It's "here's how this fact rubs against that other thing I read last month." That friction is your contribution. When you can articulate why a passage matters to the larger question you're chasing, you're building what we call a curiosity graph, a web of connected ideas that's far more compelling than any single quote. If you want help finding the thread, you can ask Glasp's AI chat what your saved highlights have in common, then tell the story in your own words.

Build a Body of Work That Compounds

Zoom out far enough and the daily small things become something much larger. This is the quiet, almost philosophical payoff of the book: do this for long enough and you accumulate a body of work, a record of a mind that thought and learned and changed over years. Kleon's final movements are about playing the long game and "sticking around," staying in the conversation long after most people drift off.

The compounding is real and underrated. Any single post is forgettable. But a thousand of them, accumulated over years, become a map of how you got from there to here. You can look back and see how your thinking evolved. Other people can trace your path. The collection becomes a thing in its own right, often more valuable than any individual piece in it, the way a single tree ring is meaningless but the whole pattern tells a story of decades.

There's a legacy dimension to this that's easy to overlook when you're posting about a book you read on a Tuesday. The record you leave of what you cared about and how you thought is, in a real sense, what survives you. We make this argument fully in your greatest legacy, and it changes how the small daily act feels. You're not just sharing for today's three readers. You're building an archive that outlasts the moment, a public profile that says, here is what one curious person paid attention to.

This is exactly what a public highlighting profile becomes over time. Every passage you mark, every note you leave, every connection you draw accretes into a living record of your intellectual life. It's discoverable, so people find you through the ideas you've cared about rather than through self-promotion. And it's durable, so it keeps working long after you've moved on to the next thing. The body of work isn't a project you start. It's the byproduct of showing up and showing your work, day after day, and letting the collection grow.

When NOT to Show Your Work

A book this enthusiastic about sharing needs an honest counterweight, and intellectual fairness demands we supply it. Showing your work is genuinely good advice, but taken as an absolute it has real failure modes, and Kleon's cheerful tone can undersell them.

The first is that some work needs privacy to survive. Early ideas are fragile. Share a half-formed thought too soon and the feedback, even kind feedback, can collapse it before it's strong enough to stand. There's also a documented risk that announcing a goal can give you the social reward of having pursued it without the work, which quietly drains your motivation to actually do it. Not everything benefits from an audience. Some things need a closed door until they're ready, and knowing which is which is a skill the book doesn't dwell on.

The second is that "sharing" can rot into performance. When you start documenting your work for an audience, there's a pull to do the work that documents well rather than the work that matters. You begin choosing the photogenic project over the important one, narrating the struggle instead of struggling. The byproduct becomes the product. At that point you're not learning in public anymore; you're performing learning, which is a different and emptier thing.

Then there are the myths the book is too upbeat to flag clearly. Sharing consistently does not guarantee an audience; survivorship bias makes the wins loud and the silence invisible. For every person who built a following by showing their work, many did the same and were never seen, and that's mostly luck and timing, not a failure of effort. There's also the simple matter of noise. A world where everyone shares everything is a world where most sharing goes unread, and adding to the pile isn't automatically valuable. And privacy is a real cost; a permanent public record of your half-baked opinions can age badly.

None of this kills the advice. It sharpens it. Show your work, but keep a private workshop for the fragile stuff. Share the process, but make sure the work, not the sharing, stays the point. Expect the upside to be smaller and slower than the success stories suggest, and do it anyway, because the real reward is the practice and the body of work, not the audience.

Frequently Asked Questions

What is Show Your Work by Austin Kleon about?

It's a 2014 book, the companion to Steal Like an Artist, arguing that you shouldn't wait until your work is finished and perfect to share it. Instead you should document your process as you go, share what you're learning while you're still an amateur, and let people see how things get made. The core idea is "document, don't create": you're already doing the work, so just leave a public trail of it rather than manufacturing extra content.

What does "document, don't create" mean?

It's Kleon's relief valve for the pressure to produce content. You don't need to invent something new to share. The byproducts of your normal work, the notes, sketches, false starts, and things you've highlighted, are already worth sharing. Documenting means capturing that residue with a photo, a screenshot, or a sentence, instead of treating sharing as a separate, exhausting second job.

Do I need to be an expert before I learn in public?

No, and Kleon argues the opposite. Sharing as an amateur, while you're still learning, is an advantage. You're close enough to the confusion that beginners feel, so your notes and explanations are often more useful and more honest than an expert's, because the expert has forgotten what it's like not to know. The person a few steps ahead is frequently a better teacher than the master far ahead.

How is showing your work different from self-promotion?

Self-promotion pushes a finished product and asks for attention. Showing your work shares the process and gives something useful away: how you made a thing, what you're learning, who influenced you. It builds connection and trust because people get to be inside the work with you, and because you credit your sources generously rather than positioning yourself as the lone genius. One announces; the other invites people in.

Should I really share everything I'm working on?

No. Some early ideas are too fragile and need privacy until they're strong enough to survive feedback. Sharing can also slide into performing for an audience, where you start doing photogenic work instead of important work, and a permanent public record can age badly. The honest version of the advice is to show most of your work while keeping a private workshop for the delicate parts, and to keep the work, not the sharing, as the real point.

Conclusion

Show Your Work! is a small book with one large permission slip inside it: you can start sharing now, before you're an expert, before the work is finished, before you feel ready. The case is that documenting what you already do, learning out loud as an amateur, and showing the messy middle is not only easier than manufacturing impressive content, it's more useful and more human. Do it daily in small pieces, tell honest stories about what you find, give credit upstream, and stick around long enough for it to add up.

The honest caveats keep it grounded. Keep a private workshop for fragile ideas, watch that sharing doesn't quietly replace the work, and expect the audience to be smaller and slower than the success stories promise. The real reward was never the audience anyway. It's the practice and the body of work that accumulates whether anyone is watching or not.

If you're a reader, the easiest place to start is the thing you're already doing. Read something today, highlight the two or three passages that move you with Glasp, add a sentence on why they mattered, and leave it public. That's showing your work, the document-don't-create version, pointed at your most consistent habit. Do it most days for a year and you won't have a masterpiece. You'll have something better: a living record of a curious mind, discoverable by the people walking the same path. Then read Kleon's book, because the full thing, illustrations and all, is worth twenty minutes of your afternoon.