Creativity, Inc. by Ed Catmull and Amy Wallace - A Summary

You’re receiving this because you signed up on our website. Want to unsubscribe? Just reply to this email with the words “no thanks.”

First-time reader? Join other business leaders for free.

Listen to this post here.

Sponsored by

Want to sell more?

Instead of paying salaries, many companies hire commission-only reps—experienced sellers who get paid only when they produce.

Post your opportunity on CommissionOnly.com.

Thousands of motivated reps are actively looking for performance-based roles.

Author: Ed Catmull and Amy Wallace

Ed Catmull is a cofounder of Pixar and former president of Pixar and Walt Disney Animation Studios, while Amy Wallace is a journalist and author who writes about leadership, culture, and creative work.

In Creativity, Inc., the central idea is that creative success doesn’t come from finding one brilliant idea and protecting it from criticism. It comes from building a culture where talented people can speak honestly, expose problems early, and improve weak ideas without fear.

The book’s argument is practical: leaders can’t remove uncertainty from creative work, but they can create conditions where people take smart risks, share unfinished thinking, learn from failure, and solve problems together.

Great ideas usually begin as weak, incomplete ideas.

That means companies shouldn’t judge every early concept as though it were a finished product. They should give promising ideas enough support, honest feedback, and time to become stronger. Creative work improves through many rounds of testing, criticism, revision, and problem-solving.

This matters because employees often hide problems when they fear embarrassment, punishment, or office politics. Leaders may then discover those problems after too much time and money have been spent. A healthy creative culture makes it safer to tell the truth while there’s still time to improve the work.

If this idea resonated with you, share it with your network using the social sharing buttons at the top of this post.

Start by making unfinished work easier to share. Employees often wait too long because they believe every idea must look polished before anyone sees it. Create regular checkpoints where teams can show drafts, rough concepts, early prototypes, or incomplete plans without pretending the work is finished.

Next, separate feedback from authority. A review group should help the owner of the work see problems more clearly, but it shouldn’t automatically take control. The person responsible for the project should remain responsible for deciding what to change unless the business faces a serious legal, financial, or safety risk.

Create a small Braintrust for important projects. Choose people with relevant experience, good judgment, and the ability to speak honestly without turning the meeting into a performance. Include different viewpoints, but don’t make the group so large that useful discussion becomes slow or political.

Set rules for useful criticism. Feedback should focus on the work, explain the concern, and give enough detail to be useful. “I don’t like it” isn’t helpful. “The customer problem isn’t clear until the third page, so the opening may lose attention” gives the team something it can examine.

Teach employees to identify problems without demanding their preferred solution. People sometimes weaken feedback by insisting that their fix is the only answer. A reviewer may correctly see that a proposal is confusing but suggest the wrong repair. Separate the diagnosis from the solution so the project owner can consider several options.

Ask leaders to speak last. When the highest-ranking person gives an opinion first, others often adjust their comments to match it. Let the people closest to the work speak before executives do. This increases the chance that leaders will hear what the team actually thinks.

Protect early ideas from premature judgment. Don’t compare a rough first version with a competitor’s finished product. Decide whether the idea solves a worthwhile problem, contains something promising, and deserves another round of development. Judge its direction before judging its polish.

At the same time, don’t protect weak ideas forever. Set review points where the team must show what it has learned, what has improved, and what remains uncertain. Support should help an idea develop, not allow a project to continue without evidence or discipline.

Make it safe to raise bad news early. Reward employees who identify risks before they become expensive. When someone reveals a problem, begin with curiosity instead of blame. Ask what happened, what the team knows, what it still needs to learn, and what decision must be made next.

Review failures based on how they happened. A failed test that produced useful knowledge is different from a missed deadline caused by poor communication. Use different responses. Useful experiments should lead to learning, while preventable failures should lead to clearer standards, better preparation, or stronger accountability.

Build short learning loops. Don’t wait until the end of a large project to discover whether the idea works. Use prototypes, customer interviews, pilot programs, draft reviews, and small tests. Faster feedback reduces the cost of being wrong.

Watch for meeting behavior that weakens candor. If the same people dominate every discussion, junior employees stop contributing, or leaders punish disagreement, honest feedback will disappear. Use direct invitations, smaller groups, anonymous input, or written comments when necessary.

Give people permission to challenge the process. A company can become attached to systems that once worked but now slow the team down. Ask employees which rules, approvals, reports, or meetings are reducing quality without protecting anything important.

Hire for collaboration as well as skill. A brilliant employee who refuses feedback or damages trust can weaken the entire group. Look for people who can defend an idea, reconsider it, improve someone else’s work, and separate their identity from the success of one proposal.

Protect ownership. Creative people need to feel responsible for the work, not merely assigned to execute someone else’s opinion. Give teams clear goals and limits, then let them make meaningful decisions within those boundaries.

Reduce fear through leader behavior. Employees study how leaders react when a project struggles. If leaders become angry, look for someone to blame, or hide mistakes from senior management, the team will learn to protect itself. If leaders remain honest, curious, and focused on solving the problem, employees are more likely to do the same.

Make post-project reviews normal. After a launch, campaign, product, or major decision, review what worked, what failed, what surprised the team, and what should change. Record the lessons so they improve future work instead of disappearing when the team moves on.

Finally, remember that culture requires maintenance. Candor can weaken as companies grow, new managers arrive, and successful teams become protective of their methods. Leaders need to keep asking where people feel unable to speak, which problems are being hidden, and what success may be preventing the company from seeing clearly.

Share the insights below on LinkedIn or X/Twitter and we’ll feature your business in the newsletter. Just use the hashtag #BizBookDaily. It’s as simple as that.

INGINES — Strategic IT leadership, project leadership, and help aligning technology with business goals.

We’ve been collecting standout business insights from experienced operators—short, practical ideas that hold up in the real world. Take a look at our Top Insights here.

Catmull and Wallace provide a whole lot more useful info in Creativity, Inc.. Here are three reasons you might want to read the full book:

Consider skipping this book if you want a step-by-step technical guide to generating ideas rather than a leadership book about creative culture.

Hidden gems most people miss. One powerful idea from each.

BOOK 1: On Board by Jonathan Foster
THE INSIGHT: Strong onboarding shapes long-term employees success.

BOOK 2: One Venture, Ten MBAs by Ksenia Yudina
THE INSIGHT: Building a startup teaches more than degrees.

BOOK 3: Own the Shift by Eric Hudspith
THE INSIGHT: Adapt fast or get left behind.

Sponsored by

Many of the best business books begin as ideas leaders have been refining for years—frameworks, philosophies, or lessons learned the hard way. Writing the book forces those ideas into clear form, and once they’re on the page, they can travel far beyond a single conversation or presentation.

At MemoirGhostwriting.com we write memoirs and business books for entrepreneurs, founders, executives, and industry experts. Most of our clients have been meaning to write their book for years—they just don’t have the time to sit down and do it properly. We help them speak more frequently on stages, scale consulting practices, attract more leads and move them deeper down their marketing funnels, increase conversion rates in complex sales cycles, and position them for for-profit boards.

We don’t just help you write, we take the whole project off your plate and see it through to a finished, publishable book.

Our team handles the entire process:

If you’ve ever thought about what a best-selling business book could do for you, let's talk.

Learn more:

Know someone who likes smart business ideas?

Forward this email to one colleague or friend who would enjoy today’s lessons.

Or send them here:
BusinessBookDaily.com