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.
You’re probably getting fat on AI content: bingeing podcasts, hoarding newsletter tips, saving Twitter threads... While it feels productive, all that consumption is just giving you a knowledge sugar high. And like any sugar high, it’ll crash—leaving you with exactly zero new capabilities.
The most inventive folks I’ve studied are disciplined about seeking inspiration. If you don’t make time to get out of the box, you will not be able to think out of the box, either. It’s not that complicated, but it requires you obliterate clean compartmentalization in favor of messy meandering.
While the winding road to innovation often only makes sense in retrospect, that doesn’t mean you can’t bend the odds. One of my favorite prospective strategies an organization can employ is the classic science fair... but you must approach it correctly.
NYU Chief AI Architect Conor Grennan makes a strong case for why GenAI shouldn't be an IT capability, but rather, championed by HR. He argues that the folks responsible for human behavior change need to be leading the charge.
In this special guest post, Mo Bunnell, Author of Give to Get, makes a compelling case for a counterintuitive strategy: giving gifts of your expertise as a way to build relationship and give clients a taste for your unique value proposition.
Sprints are a fantastic tool to drive innovation with efficiency. But sometimes you’ve got to be inefficient in order to create effectively. A few reflections on a troubling trend I'm seeing emerge among would-be innovation practitioners.
Undisputed "Beyond the Prompt" fan favorite Jenny Nicholson drops by to share some insights from her adventures helping folks innovate with AI. Important lessons for any leader looking to unleash their teams with this transformative technology.
Last week, I found myself in the bizarre position of attending a conference for YouTube creators. Talk about a fish out of water. Even though I didn't "belong" there, it sparked a bunch of fresh connections and insights... which is exactly the point of this post.
In the past year, I've witnessed a fascinating phenomenon across organizations embracing GenAI. Two "identical twins" in the AI race, similar in their approach to AI adoption -- engaged senior leadership, extensive training, numerous opportunities for AI integration -- whose outcomes couldn't be more different.
One of the defining contributions the d.school is helping teams ask themselves, “What kind of thinking is appropriate, when?” We call such clarity being “Mindful of Process.” And it can seem like semantics until you realize we need to show up in different ways.