"There's a consistency to physical objects that somehow reads all the way through, so that when you make a physical object, if it lacks the proper amount of weight or if it lacks a certain density...I mean, if its outside says, 'I weigh so much and I have such-and-such a density,' and when you pick it up, you discover an inconsistency there, then you can sense that, you can see it, even without picking it up. It's absolutely essential that everything be done all the way through."
There was a language in the world that everyone understood, a language the boy had used throughout the time he was trying to improve things at the shop. It was the language of enthusiasm, of things accomplished with love and purpose, and as part of a search for something believed in and desired.
What’s important to you in the development of a product?
One of the things that really hurt Apple was that after I left John Sculley got a very serious disease. And that disease — I’ve seen other people get it too — it’s the disease of thinking that a really great idea is 90% of the work, and if you just tell all these other people “here’s this great idea,” then of course they can just go off and make it happen.
The problem with that is that there’s just a tremendous amount of craftsmanship in between a great idea and a great product. And as you evolve that great idea it changes and grows. It never comes out like it starts, because you learn a lot more as you get into the subtleties of it, and you also find there are tremendous tradeoffs you have to make, there are just certain things you can’t make electrons do, there are certain things you can’t make plastic, or glass, or factories, or robots do. And as you get into all these things, you find that designing a product is keeping 5,000 things in your brain, these concepts, and just fitting them all together and continuing to push to fit them together in new and different ways to get what you want. And every day you discover a new problem or a new opportunity to do it a little differently. And it’s that process that is the magic.
Aristotle’s 18 qualities of homoeomerous bodies that he chose to explain in detail in his Meteorologica, are just those fine points of behavior that would be noticed in a workshop. They are:
solidifiable
meltable
softenable by heat
softenable by water
flexible
breakable
fragmentable
capable of taking an impression
plastic
squeezable
ductile
malleable
fissile
curable
viscous
compressible
combustible
capable of giving off fumes
This redundant list of properties is not the neat classification of a philosopher. It reads more as if it were based on a conversation with a workman whose eyes had seen and whose fingers had felt the intricacies of the behavior of materials.
The Sukiya consists of the tea room proper, designed to accommodate not more than five persons, a number suggestive of the saying "more than the Graces and less than the Muses..."
The tea room is unimpressive in appearance. It is smaller than the smallest of Japanese houses, while the materials used in its construction are intended to give the suggestion of refined poverty. Yet we must remember that all this is the result of profound artistic forethought, and that the details have been worked out with care perhaps even greater than that expended on the building of the richest palaces and temples. A good tea room is more costly than an ordinary mansion, for the selection of its materials, as well as its workmanship, requires immense care and precision. Indeed, the carpenters employed by the tea masters form a distinct and highly honored class among artisans, their work being no less delicate than that of the makers of lacquer cabinets.
As they work, the experience of the material under the artist's fingers subtly interacts with the idea in their mind to give the finished work some quality that was rarely fully anticipated. A few artists seem to have such a feeling for their materials that the prevision needs little modification; most say that the idea grows as they work experimentally.
I sought to design [my first book] so as to make it self-exemplifying – that is, the physical object itself would reflect the intellectual principles advanced in the book. Publishers seemed appalled at the prospect that an author might govern design. Consequently I decided to self-publish the book.
...[Howard Gralla and I] spent the summer in his studio laying out the book, page by page. We integrated graphics into the text, sometimes in the middle of sentences, eliminating the usual segregation of text and image – one of the ideas Visual Display advocated.
My view on self-publishing was to go all out, to make the best and most elegant and wonderful book possible, without compromise. Otherwise, why do it? The next 4 books were financed by the previous books. I have never written a grant application.
"Quality is only there," Irwin explained, "if you pursue it all the way to the last bolt." Consequently, how joints are finished must be specified in the contract. "And believe me," he added ruefully from experience, "there is a real discrepancy here. The difference [in] how we interpret the word finish or this word quality is really disparate."
"When you bring them in and get them to be part of it," he noted, "the workmen themselves start to take pride in it. And when they start taking that pride in this idea of quality, ...it starts becoming theirs, something important to them, that they in fact do know what we are talking about."
macOS software that adheres to craft — Things or Carbon Copy Cloner or BBEdit or Sublime Text (which, despite not being “native native” feels so solid and so responsive you’re willing to overlook its quirks) or Bear or Alfred or iA Writer or Keynote (arguably one of the best pieces of macOS software of all time) or anything by Panic, heck, even Terminal or Quicken (which, against all rational expectations is just a joy to use)5 — exists in troves, the existence of such proves to the Slacks or Twitters or Adobes of the world that it’s not impossible nor rare to produce craft-oriented software in service to user fluency, and still make a profit.
In fact, there’s a business case to be made for being craft- and fluency-focused. We’ve seen entire companies with business models that could be summarized as “Bloat-Free X” emerge in recent years. Affinity is bloat-free Adobe. Install Adobe Creative Cloud on your laptop and marvel at the no fewer than a dozen processes whirling around in the background for unknown purposes. It’s no surprise Affinity Photo and Publisher and Designer have taken off. Sketch’s main feature for many years was simply: Not Adobe.
And the web! When you care — when you really give a shit — the web is awe inspiring. I still can’t believe Figma is web-native (also born from the Not Adobe camp). That an application can feel so powerful, so fast, so well-crafted and be fully web-based should be a kind of lighthouse-archetype for all other sites lost in a sea of complexity and muck and unnecessary frameworks.
"Those stretcher bars were finished on the inside in ways no one will ever know; I spent days, weeks, months finishing things no one is ever going to see. But it had much more to do with the fact that I couldn't leave them unfinished. I just had this conviction that in the sense of tactile awareness, if all those things were consistent, then the sum total would be greater, even though that might not be definable in any causal, connected way."
When a space resonates with our humanity, when it feels really pleasant or splendid and beautiful—when you place yourself in such an environment, I've always believed that people will be drawn in. So I guess you could say it's this sense that I try to reflect in the plans; I believe that this will lead in the right direction, to an honest lifestyle.
If you consider the inheritance of skills, we can keep this heritage by having young people do the work properly, as they did in the past. If you don't do this, or you become too practical, you'd only make simple things. It's very low tech, this inheritance of skills—using carpentry tools to do manual work. We deliberately put effort into these things, completing work properly in unseen areas.
Here there is no mastery of unnameable creative processes, only the patience of a craftsman, chipping away slowly; the mastery of what is made does not lie in the depths of some impenetrable ego; it lies, instead, in the simple mastery of the steps in the process, and in the definition of these steps.
'Craftsmanship' may suggest a way of life that waned with the advent of industrial society—but this is misleading. Craftsmanship names an enduring, basic human impulse, the desire to do a job well for its own sake.
It is true that [the artist], like everybody else, derives remuneration from his work (though not, strictly speaking, profit in the financial sense, of the word, since what he invests in his work is not money but time and skill, whose returns cannot be calculated in percentages). The remuneration is frequently beyond the amount necessary to enable him to go on working. What is remarkable about him is the way in which he commonly employs the escape-from-work which the extra remuneration allows him. If he is genuinely an artist, you will find him using his escape-from-work in order to do what he calls “my own work”, and nine times out of ten, this means the same work (i.e. the exercise of his art) that he does for money. The peculiar charm of his escape is that he is relieved, not from the work but from the money.
What distinguishes him here from the man who works to live is, I think, his desire to see the fulfilment of the work.
Something strange is happening in the world of software: It’s slowly getting worse. Not all software, but a lot of it. It’s becoming more sluggish, less responsive, and subtly less reliable than it was a few years ago.
In some ways this is hyperbole. Objectively, we’ve never been able to do so much, so easily with our smartphones and laptops and tablets. We’ve never pushed more data between more places more readily. But while the insidious “worseness” I mention falls only in part on the engineering side of things, it falls harder on the more subjective, craft side of things, making it all the more worrisome.
Why should we care about this? Because the majority of our waking hours take place within the confines of applications. A truth recently amplified by the covid pandemic.
And I believe software used by millions (if not billions) has a moral duty to elevate the emotional and intellectual qualities of its users. That elevation begins with craft.
Jobs's father had once taught him that a drive for perfection meant caring about the craftsmanship even of the parts unseen. Jobs applied that to the layout of the circuit board inside the Apple II. He rejected the initial design because the lines were not straight enough.
In an interview a few years later, after the Macintosh came out, Jobs again reiterated that lesson from his father: "When you're a carpenter making a beautiful chest of drawers, you're not going to use a piece of plywood on the back, even though it faces the wall and nobody will ever see it. You'll know it's there, so you're going to use a beautiful piece of wood on the back. For you to sleep well at night, the aesthetic, the quality, has to be carried all the way through."
Care brings the worlds of action and meaning back together, and reconnects the necessary work of maintenance with the forms of attachment that so often (but invisibly, at least to analysts) sustain it.
...What if we care about our technologies, and do so in more than a trivial way? This feature or property has sometimes been extended to technologies in the past, but usually only ones that come out of deep folk or craft traditions, and rarely the products of a modern industrial culture.
...Is it possible to love, and love deeply, a world of things?
Every work of literature is the result of thousands and thousands of decisions.
Intricate, minute decisions—this word or that, here or where, now or later, again and again.
It's the living tissue of a writer's choices,
Not the fossil record of an ancient, inspired race.
All folk artisans, regardless of their lack of academic knowledge concerning their craft, are still capable of producing works of merit. They work as if this were the natural thing to do; they create as if this were the natural thing to do; they give birth to beauty as if this were the natural thing to do. They have entered the way of salvation through unconscious faith. It is a path open to all.
Slack embodied the belief, so common in Silicon Valley, that the best product would win in the end. “Building a product that allows for significant improvements in how people communicate requires a degree of thoughtfulness and craftsmanship that is not common in the development of enterprise software,” the company wrote in its open letter to Microsoft. “How far you go in helping companies truly transform to take advantage of this shift in working is even more important than the individual software features you are duplicating.”
And yet, if there’s a lesson of the past four years, it’s that thoughtfulness and craftsmanship only got the company about 10 percent as far as Microsoft did by copy-pasting Slack’s basic design. In its open letter, Slack famously told Microsoft: “You’ve got to do this with love.” In 2020, looking at Slack’s size, the idea seems laughable. What’s love got to do with it?
First, and most importantly, it’s not the features that matter. You’re not going to create something people really love by making a big list of Slack’s features and simply checking those boxes. The revolution that has led to millions of people flocking to Slack has been, and continues to be, driven by something much deeper.
Building a product that allows for significant improvements in how people communicate requires a degree of thoughtfulness and craftsmanship that is not common in the development of enterprise software. How far you go in helping companies truly transform to take advantage of this shift in working is even more important than the individual software features you are duplicating.
Saying that taste is just personal preference is a good way to prevent disputes. The trouble is, it's not true. You feel this when you start to design things.
As in any job, as you continue to design things, you'll get better at it. Your tastes will change. And, like anyone who gets better at their job, you'll know you're getting better. If so, your old tastes were not merely different, but worse. Poof goes the axiom that taste can't be wrong.
With the loss of tactility, measures and details crafted for the human body – and particularly for the hand – architectural structures become repulsively flat, sharp-edged, immaterial and unreal. The detachment of construction from the realities of matter and craft further turns architecture into stage sets for the eye, into a scenography devoid of the authenticity of matter and construction. The sense of 'aura', the authority of presence, that Walter Benjamin regards as a necessary quality for an authentic piece of art, has been lost.
Good software comes from a vision, combined with conversations not commandments. In a craft-focused environment, care for efficiency, simplicity, and details really do matter. I didn’t leave my last job just because I wanted to make something new. I left because I wanted to make it in a way I could be proud of.
This sounds like a paradox, but a great painting has to be better than it has to be. For example, when Leonardo painted the portrait of Ginevra de Benci in the National Gallery, he put a juniper bush behind her head. In it he carefully painted each individual leaf. Many painters might have thought, this is just something to put in the background to frame her head. No one will look that closely at it.
Not Leonardo. How hard he worked on part of a painting didn't depend at all on how closely he expected anyone to look at it. He was like Michael Jordan. Relentless.
Relentlessness wins because, in the aggregate, unseen details become visible. When people walk by the portrait of Ginevra de Benci, their attention is often immediately arrested by it, even before they look at the label and notice that it says Leonardo da Vinci. All those unseen details combine to produce something that's just stunning, like a thousand barely audible voices all singing in tune.
Great software, likewise, requires a fanatical devotion to beauty. If you look inside good software, you find that parts no one is ever supposed to see are beautiful too.
Interestingly, just as software people were talking about how we need to kind of follow this very Taylorist notion as the future of software development, the manufacturing world was moving away from it. The whole notion of what was going on in a lot in manufacturing places was the people doing the work need to have much more of a say in this because they actually see what's happening.
Holistic technologies are normally associated with the notion of craft. Artisans, be they potters, weavers, metal-smiths, or cooks, control the process of their own work from beginning to finish. Using holistic technologies does not mean that people do not work together, but the way in which they work together leaves the individual worker in control of a particular process of creating or doing something.
The opposite is specialization by process; this I call prescriptive technology. Here, the making or doing of something is broken down into clearly identifiable steps. Each step is carried out by a separate worker, or group or workers, who need to be familiar only with the skills of performing that one step. This is what is normally meant by "division of labor".
Methodically noting and filing resources is a sign of a mature and deliberate craftsman—it is an investment into future learning and projects. Before long, you will begin to reach the point where this collection generates projects and ideas with minimal effort; previously isolated ideas are consolidated and curiousity spurred on.
Repair is a neglected, poorly understood, but all-important aspect of technical craftsmanship. The sociologist Douglas Harper believes that making and repairing form a single whole; he writes of those who do both that they possess the "knowledge that allows them to see beyond the elements of a technique to its overall purpose and coherence. This knowledge is the 'live intelligence, fallibly attuned to the actual circumstances' of life. It is the knowledge in which making and fixing are parts of a continuum."
Put simply, it is by fixing things that we often get to understand how they work.
...understands the importance of the sketch—that is, not knowing quite what you are about when you begin.
...places positive value on contingency and constraint.
...needs to avoid pursuing a problem relentlessly to the point that is becomes perfectly self-contained.
...avoids perfectionism that can degrade into a self-conscious demonstration.
...learns when it is time to stop.
The clock has no finished design and it has been made without any careful drawings or mathematical calculations. The pieces are only made if I can hold their details in my head as I make them, without reference to any set of external measures. I do make rough sketches of some parts as a path to understanding them, but never use these during the making of the parts. The clock gradually grows through trial and error and lots of physical work with metal, but out of this has come a set of principles of making that were not clear to me before doing the clock. I have finally realized that what I am actually making is a pattern of understandings of the process of making rather than the things that are actually being made. — Richard Benson
The resonances arising in workmanship are often very subtle. The fact that the material itself guides the tool differently in different processes of working introduces changes in the overall relationship of curvatures. The smooth curves of surfaces approaching the edge of a jade axe that come about from innumerable abrasive particles moving against a slightly yielding and mechanically unconstrained backing would seem incongruous if other surfaces or outlines were present that had come from cleavage or from the geometric motions of a machine. These could be produced easily enough, but the eye would not establish larger resonances among them.
The best of all examples of a satisfactory art form based upon the inner nature of a metal is provided by Japanese swords.
Our perception of beauty seems to involve the interaction of several patterns having origin and significance at many different levels of space, time, matter, and spirit. In the Japanese sword blade there is heterogeneity in both the macrostructure and the microstructure. The manner of forging, the heat treatment, and the final polishing operation are all uniquely Japanese techniques, and all make necessary contributions to the final quality of the blades. The shape along would be simplistic form; the forged texture of the steel without heat treatment would at best faintly echo the beauty of grained wood; the outlines of the quench-hardened zone at the edge would be sharp and uninteresting if it depended only on the control of cooling rate during quenching; and the polish would be uniform glitter if the metal were homogeneous. With true artistry all these are made to interact.
By craftsmanship I refer to a style of work and a way of life having the following characteristics:
In craftsmanship there is no ulterior motive for work other than the product being made and the processes of its creation.
In craftsmanship, plan and performance are unified, and in both, the craftsman is master of the activity and of himself in the process. The craftsman is free to begin his working according to his own plan, and during the work he is free to modify its shape and the manner of its shaping.
Since he works freely, the craftsman is able to learn from his work, to develop as well as use his capacities.
The craftsman’s way of livelihood determines and infuses his entire mode of living. For him there is no split of work and play, of work and culture. His work is the mainspring of his life; he does not flee from work into a separate sphere of leisure; he brings to his non-working hours the values and qualities developed and employed in his working time.
What I am suggesting to you is that designers ought to take the value of craftsmanship as the central value for which they stand; that in accordance with it they ought to do their work; and that they ought to use its norms in their social and economic and political visions of what society ought to become.
As makers of buildings, we architects must start now,
with a fundamental change of direction.
For the last hundred years or so, we have understood
building to be an art in which an architect draws a building,
and a contractor then builds that building from the
architect's plans.
But a living environment cannot be built
successfully this way.
To achieve a successful building — one that has life — we
must focus our attention on all the crafts and processes,
and then, as architects, ourselves take direct charge
of the making.
We must take full responsibility
for the entire building process, ourselves.
Visionary designers have lost their conceptual integrity to an industrial complex optimized for consensus, predictability, and short-term business gain. The rise of customer-obsession mantra and data-driven culture cultivated a generation of designers who only take risk-free and success-guaranteed steps towards the inevitable local maxima of design monotony.
…in so many of the best product companies there is an additional dimension that goes beyond individual empowered product teams, and even goes beyond achieving business results.
It has to do with ensuring a level of what I’ll refer to here as “excellence” although that is clearly a very ambiguous term.
Over the years, this concept has been referred to by many different names, always necessarily vague, but all striving to convey the same thing: “desirability,” “aha moments,” “wow factor,” “magic experiences,” or “customer delight,” to list just a few.
The concept is that an effective product that achieves results is critical, but sometimes we want to go even beyond that, to provide something special.
Maybe it’s because we believe this is needed to achieve the necessary value. Maybe it’s because the company has built its brand on inspiring customers.
Often this dimension shows up most clearly in product design, where functional, usable but uninspiring designs can often achieve our business results, but great design can propel us into this realm of the inspiring.
And what is delight? For me, delight is born from a tool’s intuitiveness. Things just working without much thought or fiddling. Delight is a simple menu system you almost never have to use. Delight is a well-balanced weight on the shoulder, in the hand. Delight is the just-right tension on the aperture ring between stops. Delight is a single battery lasting all day. Delight is being able to knock out a 10,000 iso image and know it'll be usable. Delight is extracting gorgeous details from the cloak of shadows. Delight is firing off a number of shots without having to wait for the buffer to catch up. Delight is constraints, joyfully embraced.
The decreasingly tangible product of code, i.e. that all we have are files on a hard-drive, may make it easy to forget that writing software produces a thing. If you produce a wonky chair or an overly long fork, it’s easy to see the quality of work was not great. By calling for a perception of software as a craft, we fight against that ability to forget or not notice the final quality of the product. You could watch two software engineers with different levels of experience, or in different domains, and it wouldn’t necessarily be so easy to guess which is which, at least from a distance.
So maybe there is something to be said for the value of software as a craft, for sometimes focusing on the practice of making better, or at least different, software just for the sake of it.
Maybe the internet is due for a wave of things that don’t scale at all. In that light, I’ve been fascinated by ‘Morioka Shoten’ in Tokyo - a bookshop that sells only one book at a time. This is retail as anti-logistics - as a reaction against the firehose, and the infinite replication of Amazon. Before the internet that would only work in a very dense city, but, again, the internet is the densest city on earth, so how far do we scale the unscalable?
I'm Jacob — a designer and coder who creates things with computers (Fig 1) 'Digital Craftsman' best describes my skill set.
Digital projects thrive when designers understand how they will be built. Just as an architect understands how a structure is created, the same should be true on the web.
Should we really demand that the guy who checks ticket stubs at the movie theater hones his craft?
Well, yes. No job is too low to not warrant care, because no job exists in isolation. Carelessness ripples. It adds friction to the working of the world. To phone it in or run out the clock, regardless of how alone and impotent you might feel in your work, is to commit an especially tragic—for being so preventable—brand of public sin.
Bob [the driving instructor] oozes concern; he wants to infect the state of New Jersey with good driving habits. He respects his public role, the fact that the minute he's done with these kids they head straight for their parents' car keys and out onto the roads we share. When I asked him what he likes to do outside of work, he laughed: "This is my life."
My approach to what I do in my job — and it might even be the approach to my life — is that everything I do is the most important thing I do. Whether it’s a play or the next film. It is the most important thing. I know it’s not going to be the most important thing, and it might not be close to being the best, but I have to make it the most important thing. That means I will be ambitious with my job and not with my career. That’s a very big difference, because if I’m ambitious with my career, everything I do now is just stepping-stones leading to something — a goal I might never reach, and so everything will be disappointing. But if I make everything important, then eventually it will become a career. Big or small, we don’t know. But at least everything was important.
Universities are often too large, dulling the student-educator relationship. Internships are often transitory and involve large volumes of work without context or learning: building web pages or presentations from pre-built components to meet a deadline, for example. It’s work that people need to do, but it doesn’t require learning or understanding the client or the project. Thankfully, there is a middle ground that we seem to have forgotten about in tech: the apprenticeship.
The thing that you’re talking about though, which I’ve never seen a mature company really have a sustainable space for, is the “senior craftsperson.” They’re not pivoting at some point in their career to saying “I’m going to take what I know and leverage it through other people.” They’re saying “I want to get better infinitely at the thing that I do.” I believe that that’s possible.
You see it more in pure-art kind of careers. Like “I’m an illustrator” or “I’m a concept artist” or something, and there’s a need for that person being really fucking good at that one thing, and continuing to do that one thing. I think a lot of people can intuitively understand why that would be really satisfying for someone as a career path.
Let me be more precise: The Pareto distribution is a useful model of power law effects in real life. But people are using it poorly, primarily as an excuse to be lazy.
...People forget that the devil is in the details. The first 20% everyone knows to say on Twitter. The remaining 80% is the ugly, nasty, hacky, unglamorous shit nobody talks about unless you've got time to sweat the details.
In the television show Masterchef there was an episode where the judges did a test on what they call “basic skills”. One of the judges often says that in order to be a “true chef”, you must know how to quickly and finely cut onions.
...This was really bothering me and I am stubborn so I wanted to win this fake argument really badly so I looked up why the way one cuts onions is important: as it turns out, the shape and even the surface area affect the end flavour. I thought the whole “chop chop chop” was about performance in the kitchen. Cut quickly to serve quickly! I was wrong.
Building structure requires serious listening, serious reflection, and serious imagination. All this requires experience, and no matter how experienced you are, it costs you. We spend our time and nerves to save users their time and nerves. Well-designed things give us the invaluable present of time. Well-designed products do not just save us time, they make us enjoy the time we spend with them. They make us feel that someone has been thinking about us, that a nice person took care of the little things for us. This is mainly why we perceive well-designed things as more beautiful the longer we use them, and the more used they become.
Craftsmanship is about thoughtfulness and care in the work we do. It means being deliberate about what we build and how possible it will be to maintain and extend in the future. A solution that will require revisiting in a month — because it’s not scaling, because it has a ton of bugs, because it doesn’t support all the use cases it needs to — is not useful to us and ultimately will generate pain for our users.
What we trade off by living this value is (sometimes) day-to-day speed. It’s easy to imagine an engineering team that emphasizes moving fast over keeping things stable and bug-free -- like a team building a product that isn’t responsible for important user data and doesn’t support anyone’s livelihood. But given the role the Figma product plays in the lives of our users, we feel it’s worth it to ensure we hold a high quality bar for them. And in the long run, being thoughtful about how we build often reduces the complexity of ongoing development and new features regardless.
Too often, a popular consumer app unexpectedly gets worse: Some combination of harder to use, missing features, and slower. At a time in history where software is significantly eating the world, this is nonsensical. It’s also damaging to the lives of the people who depend on these products.
...Maybe we ought to start promoting PMs who are willing to stand pat for an occasional release or three. Maybe we ought to fire all the consumer-product PMs. Maybe we ought to start including realistic customer-retraining-cost estimates in our product planning process.
We need to stop breaking the software people use. Everyone deserves better.