Steal Like an Artist

I think this addresses a problem that almost everyone doing creative or technical work eventually run into:

How do i create original work when almost everything has already been done?

it's a short, illustrated book built around 10 principles for creative work it's a quick read

The Central Idea

The title sounds provocative:
"Steal Like an Artist."
Kleon isn't advocating plagiarism.

He's arguing that creative work is cumulative.

Almost nobody creates in a vacuum.
Artists, Designers, Programmers, Writers, Filmmaker, & Musicians
Absorb influence and then transform them.

The productive cycle is:

Observe
   ↓
Collect influences
   ↓
Understand them
   ↓
Combine ideas
   ↓
Modify them
   ↓
Make something of your own

That's much more closer to how creativity actually works.

The Distinction Between Copying and Stealing

This is probably the mot important concept in the book.

Copying says:

"I want to reproduce what this person made."

Stealing says:

"I want to understand what makes this work effective and incorporate the underlying idea into something different."

For example,
while attempting to design the learning application (HoneyGuide)
I am gonna study:

Duolingo's progression system
Pokémon's character attachment
Animal Crossing's warmth
Apple's interaction design
Nintendo's onboarding I don't intend to reproduce their interfaces.

I ask:

What mechanisms make their system work?

Then i reinterpret those mechanisms into my own context.

This is essentially Kleon's philosophy.

Nothing is completely original

This is one of the book's healthiest ideas for creative work.
New work usually looks more like:

A + B + C + personal experience
            ↓
         New work

rather than:

Nothing
  ↓
Pure originality
  ↓
New work

For example,
a strong product design might emerge from combining:

Duolingo's learning loops

Pokémon's collection psychology
South African cultural context
your own product decisions

The result can be genuinely distinctive even though its ingredients aren't unprecedented.

That's an important distinction between originality and novelty.

The book is particularly good for people who feel like impostors

One of Kleon's recurring messages is:

You don't have to feel like an expert before you start making things.

This matters because beginners often wait for:

permission
expertise
inspiration
confidence
the perfect idea

before producing anything.

Kleon's approach is essentially:

Make something
    ↓
Learn from it
    ↓
Make another thing
    ↓
Get better
    ↓
Develop a voice

Your "voice" emerges through volume and iteration,
rather than appearing before you begin.

One of the best ideas: become good at collecting

Kleon recommends deliberately collecting things that interest you.

Not because you necessarily need to use them immediately.

You build an idea library.

That could be:

screenshots
books
quotes
illustrations
interfaces
photographs
songs
websites
conversations
observations
interesting pieces of code

Then, over time, these inputs start interacting.

This is essentially building your own creative corpus.

For a developer/designer, something like:

~/inspiration/
    ui/
    typography/
    animation/
    branding/
    games/
    education/
    copywriting/
    architecture/

isn't a bad idea.

The important part isn't the folder structure.
It's deliberately paying attention.

"Write the book you want to read"

This is another excellent principle.

Instead of asking:

"What will people want?"

ask:

"What do I wish already existed?"

That is a much more powerful starting point for creative projects.

It can lead to:

better side projects
better writing
better products
better tools
better open-source projects

E.g. for the learning platform i'm tryna develop
Rather than starting with "what educational app should I build?",
the more interesting question is:

What kind of South African learning experience do I wish existed?

That's exactly the kind of framing Kleon encourages.

Another important principle: work with your hands

Kleon is skeptical of living entirely inside the digital world.

One of his recommendations is essentially to maintain a separation between:

analog thinking

and

digital execution.

For example:

Notebook
   ↓
Sketch
   ↓
Think
   ↓
Computer
   ↓
Build

rather than immediately opening an IDE, Figma, or AI tool every time you have an idea.

That doesn't mean analog is inherently superior.

The underlying idea is:

Changing the medium can change the way you think.

That's quite useful.

One thing I'd change about the philosophy

I'd add a principle that Kleon's book only partially addresses:

Steal, but develop taste.

The real differentiator isn't how many influences you collect.

It's your ability to determine:

What is worth taking?

Two people can look at the same ten products, films, books, and interfaces and produce completely different work.

The difference is often taste.

And taste develops through:

Exposure
+
Analysis
+
Experimentation
+
Failure
+
Iteration

That's the part I'd emphasize most.

The book's biggest weakness

It's very simple.

Some of the ideas will feel obvious once you've been doing creative work for a while.

You might read a page and think:

"Yes, obviously."

And that's fair.

This is more like a creative operating manual than a major philosophical work.

Don't spend hours dissecting every chapter.

Its value comes from actually applying the principles.

Bottom line

The central lesson is worth keeping:

You don't need to invent everything. Learn broadly, collect intelligently, make connections, and transform what you've learned into something that becomes yours.

For someone building software, designing products, creating a brand, writing, or making art, that's a very practical philosophy.

Search reads