What Leaders/Managers Can Learn from Steal Like an Artist
Leaders often present decisions and strategies as if they arrived fully formed, hiding the borrowed frameworks, other managers' advice, and earlier failed attempts that actually shaped them. That performance of total originality makes leaders seem less trustworthy, not more, and it teaches a team that only finished, confident-sounding plans are allowed to be shown.
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 4 selected
The core lessons, applied to you
Openly study and build on the work of people you admire
For a manager, this means telling your team where a process or framework actually came from — a book, a mentor, another team's playbook — instead of presenting it as your own invention.
A manager rolls out a new planning process lifted almost entirely from a previous employer and presents it as something they designed from scratch. When a team member later recognizes the format from a public source, the manager's credibility takes a hit that has nothing to do with whether the process actually works.
The next time you introduce a process or framework, spend thirty seconds naming where it came from and what you adapted.
Start making things now, before you feel ready or fully know your own style
A leader's management style develops through practice, not through waiting until you feel like a "finished" leader before making real decisions.
A newly promoted manager delays giving any real feedback for months, waiting to feel confident in their own leadership approach. The team is left without direction in the meantime, and small problems that early feedback could have caught grow larger.
Pick one decision you've been sitting on and make a call this week, even a reversible one, rather than waiting for full confidence.
Share your work and process regularly, not just the finished result
Teams trust leaders more when they see the reasoning behind a decision, not just the decision itself announced after the fact.
A leader announces a reorg with a tidy final slide and no visible reasoning trail. Without seeing the tradeoffs that were weighed, the team assumes the worst about what got left out and trust erodes even if the decision itself was sound.
When you announce a decision, include one paragraph on what you considered and rejected, not just what you chose.
Protect focused, unglamorous work time and treat limits as useful for finishing
Leaders' calendars fill instantly with meetings, leaving little room for the quieter work of actually thinking through a plan or coaching a direct report. Protecting even small blocks of unscheduled time, and treating a tight budget or headcount limit as a forcing function that clarifies priorities rather than only a constraint to complain about, is often what separates a functioning team from a constantly reactive one.
Sharing unfinished reasoning can feel risky when a team expects steady confidence from its leader. The practical answer is to separate tone from content: you can share genuine uncertainty about a decision while still being clear and calm about how you'll decide and by when.
Name one thing, honestly
Where in your leadership have you been performing certainty you don't actually feel, and what would it cost to be more honest about it?
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
When you announce a decision, include one paragraph on what you considered and rejected, not just what you chose.