The Wisdom of Charles Eames
Austin Kleon mentioned Corita Kent's fantastic "Learning by Heart" in a recent blog post. I thoroughly enjoyed the book (thanks, Austin!), and will likely revisit many of her techniques and observations in the future.
One quote that really struck me came when she was describing her admiration for her collaborator, legendary designer, Charles Eames: "Charles said that the first step in designing a lamp (or anything) was NOT to ask how it should look -- but whether it should even be."
I thought that was a beautiful way of describing the purpose of prototyping: determining whether something should be. As we say at Stanford, the first question to be answered is not "can I make it?" but rather, "should I make it?"
This is not an indictment of the frivolous; quite the contrary, the frivolous is often the prelude to the fabulous; rather, it's an indictment on spending resources in the wrong direction. Many times, it's much easier to answer the question "should I..." (ie does performing some envisioned function for another human being accomplish the impact i'm hoping to achieve?), than it is to answer the question "can I..." (which can involve much expense in terms of time, etc).
Click here to subscribe to Paint & Pipette, the weekly digest of these daily posts.
I'm best known for my work on innovation, creativity, and entrepreneurship. My “shift” toward AI might seem like a radical departure. But it's not a shift—it's an evolution. Having taught and spoken to tens of thousands from ~100 countries in the last two years, I’m more convinced than ever that AI isn't separate from innovation; it's the most profound innovation platform of our lifetime.
AI isn't coming for your job. But someone using AI almost certainly is. So why not take your own job before someone else does? It’s time to prioritize and systematize disrupting ourselves.
When organizations think about AI transformation, they immediately focus on technical roles: data scientists, developers, prompt engineers. But what if the most important AI role in your organization requires zero technical expertise?
Enjoy this guest post from Eric Porres, Head of Global AI at Logitech. It’s a fantastic personal story of how one business leader got a much-needed turbo boost by augmenting his own intelligence with AI.
Behold the great AI measurement delusion: Organizations tracking usage metrics are missing the only thing that matters—impact.
More use isn't better use. Better use is better use.
Last week a CEO asked me the same question I hear from every executive: 'How do I get my team to use AI?'
My answer shocked him.
In the AI age, love is more important than ever. Because now anyone can generate “good enough” solutions with a few prompts. But people want more than good enough. When average is free, only above-average passion will stand out.
Deeply practical guest post by former NCAA and NFL punter, now tech executive, Zoltán Meskó. I met Zoltán at Stanford’s annual Campbell Trophy Summit last summer, and he stayed in touch, telling me all the cool stuff he was trying - check out how AI is changing the way he works.
"I don't really have any pain points to automate," a CEO told me during an AI workshop last week. "I don't do repetitive work like other people in the company do."
Then he mentioned how he spends six hours manually editing every report his team sends him… I had to stop him right there.
Last week, Shopify CEO Tobi Lütke released an internal memo that's been making waves. My take: this isn't just another tech CEO jumping on the AI bandwagon. It's the clearest articulation I've seen of a principle I've been exploring the past 18 months: the greatest risk with AI isn't failure—it's inaction.