Design as Craft and Simplicity

A synthesis of highlights on design as a way of thinking — subtraction over addition, fast software as engineering honesty, tools that embody values, and the quiet discipline of getting small things right.

Design here is not decoration laid over a finished object; it is a way of thinking that starts with what something should be and works backward. The highlights collected below circle a few stubborn convictions: that the best solutions come from subtraction rather than addition, that speed and simplicity are moral properties of software, that a well-made tool can carry a culture's values, and that caring about details nobody will ever notice is the whole game. Running underneath is a suspicion of ego, style, and the loud designer "wagging their tail" in your face.

Design is how it works, not how it looks

The load-bearing idea is Steve Jobs's, quoted in Kahney's biography of Jony Ive: "Most people make the mistake of thinking design is what it looks like... People think it's this veneer... That's not what we think design is. It's not just what it looks like and feels like. Design is how it works."¹ For Ive, the starting point was never appearance. "What something should be was always the starting point for his designs,"¹ and he approached each project "in an almost chameleon-like way, adapting himself to the product," so that his early works had "no signature style."¹ Style, in this reading, is a corrosive agenda: "a lot of people see design primarily as a means to differentiate their product competitively... I really detest that. That is just a corporate agenda, not a customer or people agenda."¹

Ive's origin story is one of care: "I came to realize that what was really important was the care that was put into it. What I really despise is when I sense some carelessness in a product."¹ The emotive, unmeasurable attributes are exactly the ones industry ignores — "care was taken even on details, hard and soft, that people may never discover."¹ And the goal is self-effacement: he "disdains decoration — every tiny screw is there for a reason — and his goal is to make design disappear,"¹ happiest "when the user doesn't notice his work at all."¹

mindmap
  root((Design as<br/>craft))
    Intent
      What should it be?
      Design is how it works
      No signature style
    Subtraction
      Nothing left to take away
      Prune the cruft
      Take something away
    Invisible
      Make design disappear
      Essential is invisible
      Care nobody sees
    Speed
      Fast = engineering honesty
      Unbloat over time
      Tactile means no latency
    Values
      Kodawari
      Wabi-sabi and iki
      Tools that embody culture
    Discipline
      Chase the product
      Pride in small jobs
      Don't talk too loud

Perfection is subtraction

The clearest statement of the aesthetic is Saint-Exupéry's, flagged in The Little Prince: "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away."² The same book supplies the companion line about why the essential resists measurement — "what is essential is invisible to the eye"² — which pairs naturally with Ive's ambition to make design vanish.

Yet the highlights are honest that subtraction runs against human instinct. Collaborative Fund's essay on the pedal-less Strider Bike names the bias directly: "people are biased towards solving problems through addition rather than subtraction," because "adding something makes you feel like you are advancing, while taking something away makes you feel like you are retreating."³ Companies compound the problem, "incentivized to sell us endless solutions" — the case study being Starbucks' app with "over 170,000 ways to customize" an order.³ Steph Ango frames the same law as system entropy: "Our bias is to always add more... Interdependencies proliferate, and gradually strangle us. Systems want to grow and grow, but without pruning, they collapse. Slowly, then spectacularly."⁴ His prescription is structural — "A good system is designed to be periodically cleared of cruft. It has a built-in counterbalance"⁴ — and his diagnosis of why we hoard is psychological: "we attach our identity to what is visible."⁴ Even Ive's Apple lived this: Jobs "erased the whiteboard and drew a very simple two-by-two grid," collapsing the product line to four machines,¹ and the design team mantra was "We are not interested in design statements. We do everything we can to simplify design."¹

Fast software is honest software

Craig Mod's essay turns speed into a proxy for integrity: "Speed can be a good proxy for general engineering quality. If an application slows down on simple tasks, then it can mean the engineers aren't obsessive detail sticklers... I want all my craftspeople to stickle."⁵ Speed builds trust; slowness leaks doubt. His ideal is software that improves by shedding weight: "I love software that does this: Software that unbloats over time... The longer it's around, the more elegant it should become. Smooth over like a river stone."⁵ The cautionary tale is Google Maps "dying a tragic, public death by a thousand cuts of slowness" — animations that are "nice individually, but in aggregate very slow."⁵ Even wording can slow you down: the macOS shift from "Don't Save" to "Delete" — "Pressing delete feels violent."⁵ And the physical stakes are tactile: "on a screen, to feel tactile is to move without latency."⁵

Simon Willison's rules for single-file HTML tools are subtraction applied to code: "Avoid React, or anything with a build step... I prompt 'no react' and skip that whole rabbit hole entirely,"⁶ loading dependencies from a CDN only when necessary and favoring simple paste/transform/copy flows. Jason Fried supplies the counterweight to the fantasy that everyone should build their own tools: "A powerful excavator doesn't turn a homeowner into a contractor. Most people just want the hole dug."⁷

Tools that embody values

The Sigma BF camera is the purest artifact of craft-as-values. Its unibody is CNC-machined so slowly that "each five-axis machine takes seven hours to carve a single unibody" and "only 9 cameras come off the production line" per day — a process embodying kodawari, "the uncompromising commitment to perfection."⁸ The essay closes with Okakura Kakuzo: "A single masterpiece can teach us more than any number of the mediocre products of a given period or school," and the BF "has a lot to teach us about creating tools that embody cultural values rather than merely technical capabilities."⁸

That Japanese vocabulary of taste recurs. A Geek in Japan supplies the grammar: wabi-sabi "represents imperfection and incompletion... emphasizes the simplicity and sobriety of things,"⁹ while iki describes things that are "original, calm, refined, and sophisticated without being perfect or complicated."⁹ The same discipline of "repetition without thinking," done "in a strict, systematic, and perfectionist way," permeates Japanese work — slow to decide, but "when things are done, they usually work to perfection."⁹ It is worth noting the user's parallel interest in craft that is not Western: Derek Guy's thread insists "quality workmanship speaks for itself regardless of where it's done," profiling India's hand-block printing and khadi, whose hand-production gives "subtle variations, which gives the cloth character," and the shirtmaker 100 Hands whose Gold Line "surpasses anything I've seen in Europe."¹⁰

Chase the product, not the data

Robin Rendle's warning is against outsourcing judgment to metrics: "You can only build a great product if you care more for the vibes than for the data."¹¹ Research, done right, is not amplification of the loudest — "The value of research doesn't come from elevating people who are already shouting. It comes from finding the people who are not being heard."¹¹ This is the same taste-first instinct behind Josh Puckett calling a Basecamp page "a masterclass in IA, copywriting, and positioning,"¹² and behind the micro-craft of Ludvig Rask rebuilding a button "using only: 1x Stroke, 1x Inner shadow, 1x Drop shadow, and 1x Gradient."¹³ Akshay Verma's note that Figma is "a sovereign app... optimised for intermediate users, rather than first timers"¹⁴ is the reminder that good design serves a specific posture rather than a generic everyone.

Craft is friction, attention, and small things

The counterintuitive theme is that friction is not the enemy of craft — it is often its precondition. Craig Mod defends shooting film precisely because it hurts: "I like the strange pain of the shots, that each one counts and costs and in that way causes me to look more closely." He values "artificial friction" because "humans are quirky and sometimes we need artificial friction to do The Thing," the slow feedback loop that is "terrible when you're young" but "unexpectedly valuable later," and above all "a physical archive... Durable evidence of life and work done."¹⁵

Making small things well is disproportionately hard. Jerry Seinfeld: "The smaller something is, the harder it is to make, because there's less room for error," his ideal being "solitude and precision, refining a tiny thing for the sake of it."¹⁶ James Hoffmann finds the reward of great coffee in its very transience — "It's beautiful because it ends... Great coffee's worth chasing."¹⁷ The path to bigger work runs through small work done with pride: "if you take pride in the little jobs, people will think you worthy of the bigger jobs."¹⁸ And the whole enterprise resists tidy rulebooks — as one writer put it, "there are many rules and also no rules at all,"¹⁹ echoing Susan Sontag's aphorism that the interesting is "what has not previously been thought beautiful."²⁰

Considered objects and the cost of enough

Craft on the buying side is discernment. Steph Ango's cost-per-use heuristic — "How much will it cost me if I divide the price by its expected number of uses?" — favors durability, notes that "the best things to splurge on are the things you use the most," and lands on the ascetic limit: "the ideal cost per use trends to $0. The most cost-effective choice is to not buy something you don't need."²¹ Derek Sivers gives the same logic an equation: WEALTH = HAVE ÷ NEED, where "the easiest way to increase your wealth is to decrease your needs" — an inner game, "entirely under your control."²² Craft, on this view, ends where consumption's addition-bias began: the most designed object is often the one you chose not to add.

The discipline of critique

The last thread is self-suspicion. Ive treats over-advocacy as a warning light: "if I'm trying to talk a little too loud about something... I'm trying to convince myself that something's good."¹ The designer's curse, he says, is a permanent interrogation — "you are constantly looking at something and thinking, Why? Why is it like that and not like this?"¹ Good design, then, is less a flourish added at the end than a discipline of refusal maintained throughout: refusing style, refusing cruft, refusing to talk too loud, refusing to add when the honest move is to take something away.

Related

• UI/UX and Visual Design Craft
• Creativity, Craft, and Deliberate Practice
• Reading, Analog, and the Physical World
• Desire, Status, and the Psychology of Enough
• Steve Jobs
• Jason Fried & 37signals
• Craig Mod
• Derek Sivers
• Robin Rendle
• Japan
• Overview