The Creative Act: attention before output

My reading includes books such as The Design of Everyday Things, Lean UX, About Face & Thinking in Systems. Rick Rubin’s book feels different from the design books I usually read. It brings a different kind of conversation to that shelf. His book considers creativity as a relationship with the world, with room for people beyond professional artists. & here is how I would bring that conversation into digital product work. There is value in looking before generating. With tools like Codex & Claude Design in my work, producing another version is increasingly accessible. The question worth protecting is what makes one version worth pursuing. Imagine a founder asking for a website with more personality. A useful starting exercise would be to gather references from the business itself: the way the founder explains the work, something a customer kept, the typography on an old invoice, a photograph of the place where the work happens. These are prompts for exploration, not instructions to put every object on the homepage. A specific detail can suggest a direction that a collection of similar agency websites never will. The designer still has to choose what belongs. For a small studio, that might mean one distinctive typographic gesture, a quieter navigation, or language that sounds like an actual conversation. Character does not require every part of the interface to perform.

Make room for a version you would not immediately ship. An early idea can be useful without being ready for a client presentation. Try an intentionally sparse page. Try a layout led by a single image. Try telling the story without the headline you have become attached to. Give each exploration a question. Does this ordering explain the service sooner? Does the image contribute something the copy cannot? Is the unusual interaction helping someone understand the offer, or is it asking for attention on its own behalf? This is an exercise I would suggest to a founder & designer working together. Set aside a contained period for exploration, then make a decision. Endless variations can become a way of avoiding the uncomfortable part: choosing what the product should be.

A digital product asks other people to get something done. That creates obligations beyond the designer's preference. Someone needs to read the text, find a price, recover from a mistake, or use the interface with a keyboard. I would read a book about creativity alongside those obligations. An unusual navigation might make a portfolio memorable & still be a poor choice for a time-sensitive customer task. A visually quiet error message might look elegant & fail to help someone recover. The useful conversation is specific: what does this choice add, what effort does it ask of the user & what have we observed? That leaves room for personality while making the tradeoffs discussable. Choose one screen that feels competent but anonymous. Before asking AI for alternatives, write down three details that are particular to the company. Then select one to explore in the design. Compare the original & the new version using the same realistic content & task. Invite someone unfamiliar with the work to try both. Notice whether they understand the offer & can act on it, as well as what they remember. Treat the session as input for the next iteration, not a vote that settles the design forever.

The Creative Act is a book I am happy to recommend to people who make things. For founders, I would pair it with direct contact with customers. Leave room for the unexpected idea, then do the work to see whether it belongs in the product.