process
On Process
People get confused, companies get confused. When they start getting bigger, they want to replicate their initial success, and a lot of them think that somehow there’s some magic in the process that they’ve created. And so they start to institutionalize process across the company. And before very long people get very confused that the process is the content.
In my career I’ve found that the best people are the ones who really understand the content. And they’re a pain in the butt to manage. But you put up with it because they’re so great at the content. And that’s what makes great products. It’s not process, it’s content.
Just-in-time manufacturing
Get embedded in the team. Designers should use sprint planning, grooming, standup, and retro as opportunities to provide design to — and receive feedback from — the rest of the team. Designs can take the form of written or verbal descriptions, not just wireframes and high-fidelity mockups.
Only design what’s needed. Use constant communication between engineering and product partners to understand what your collaborators will need next. Then, plan on delivering only what is needed, and nothing more. Use the agile process — grooming, planning, and retro — to find any shortfalls or excesses.
Avoid creating a backlog of designs. Designs don’t age well. In the time between finishing design and shipping code, it’s likely that you’ll learn something new that changes your understanding. If you’re producing more design than can be implemented, focus more on the quality of each design.
How beautiful the world would be if there were a procedure for moving through labyrinths
Design skirmishes
it is apparent that the unfolding of the design process assumed a distinctly episodic structure, which we might characterize as a series of related skirmishes with various aspects of the problem at hand.
As the scope of the problem became more determined and finite for the designer, the episodic character of the process seems to have become less pronounced. During this period a systematic working out of issues and conditions took hold within the framework that had been established. This phenomenon is not at all surprising when we consider the fundamental difference between moments of problem solving when matters are poorly defined and those with clarity and sufficiency of structure.
Within the episodic structure of the process, the problem, as perceived by the designer, tends to fluctuate from being rather nebulous to being more specific and well-defined. Furthermore, moments of "blinding" followed by periods of backtracking take place, where blinding refers to conditions in which obvious connections between various considerations of importance go unrecognized by a designer.
How we can do better
It actually doesn't matter whether you actually have a formal retrospective. It doesn't matter whether you have four or five labels of things on your retro board, or exactly how you do the retro. What does matter is the notion of thinking about what we're doing and how we can do better, and it is the team that's doing the work that does this, that is the central thing.
Holistic and prescriptive technologies
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".
That which requires caring
Today's real world of technology is characterized by the dominance of prescriptive technologies.
The temptation to design more or less everything according to prescriptive and broken-up technologies is so strong that it is even applied to those tasks that should be conducted in a holistic way. Any tasks that require caring, whether for people or nature, any tasks that require immediate feedback and adjustment, are best done holistically. Such tasks cannot be planed, coordinated, and controlled the way prescriptive tasks must be.
Prescriptive technologies eliminate the occasions for decision-making and judgment in general and especially for the making of principled decisions. Any goal of the technology is incorporated a priori in the design and is not negotiable.
Direct management
Direct Management does not include or permit the concept of profit to occur. The management is fee-based, or based as a fixed salary, and all construction costs are fixed ahead of time, and the building design is modified during construction, to make up any over-runs. The manager is not able to move money around at will, or put it in their pocket. At the same time, the design is approximately fixed, but with the understanding that it may be changed, during the evolution of the building, so that subtle adaptations can be included in the emerging building. In the Direct Management method it is the architect themselves and the direct manager who together manage the building works and all on-site construction for the owner.
Manifesto for Agile Software Development
A DefinitionWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
That is, while there is value in the items on the right, we value the items on the left more.
Deadlines are bullshit
An ArticleIn software development deadlines are a necessary evil. It is important to understand when they are necessary, and it is important to understand why they are evil.
- External vs. internal deadlines
- Why are internal deadlines evil?
- Engineers who love their work
The Design Diagram
An Idea by Charles Eames & Ray EamesThis Eames drawing, often referred to as the Design Diagram, was created for a 1969 exhibition at the Louvre entitled, What is Design? Charles and Ray mailed it to the exhibition curator to augment their answers to a series of questions she had posed.
In Defence of Intuition
An Essay by Boris MüllerDesign, it seems, is not only becoming more methodical but also more scientific. This is not surprising. Design as a discipline has moved from “product beautification” to being a central part of product development. It has incorporated methodologies from human-computer interaction, sociology, and anthropology as well as advertising and management. And with the rise of design thinking, a wider range of professional disciplines are using creative methods.
I don’t want to criticize design methodologies. But against the backdrop of an overly structured design process, it is important to remind our community that there is one fundamental aspect to design that cannot be formalized in a methodology. And that is intuition.
Why we need to stop over-complicating UX
An Article by Hugo FroesMany have become so focused on the process and methodologies that they’ve forgotten the fundamentals of why we started focusing on the user and what we hope to achieve with that focus.
Beyond Artboards
An Essay by Chuánqí SunThe Pursuit of Lossless Design-Development Handoffs.
Just-in-time Design
An Article by Matthew StrömThere is a disconnect between product design and product engineering.
The Hot Potato Process
An Article by Dan MallThe big misconception I’ve seen designers and developers often fall victim to is believing that handoff goes one way. Designers hand off comps to developers and think their work is done. That puts a lot of pressure on the designer to get everything perfect in one pass.
Instead, great collaboration follows what Brad Frost and I call “The Hot Potato Process,” where ideas are passed quickly back and forth from designer to developer and back to designer then back to developer for the entirety of a product creation cycle.
Building Momentum
An Article by Dan MallFight the Waterfall
Start all of the pieces of work a little bit earlier. The key to starting work early is not succumbing to the pressure of having to finish the work. Don’t worry about finishing. If you’re a developer, you can start doing things while your design or information architect are working because a lot of your work actually isn’t dependent on their work. Some of it is, so you probably won’t be able to finish, but that shouldn’t stop you from starting.
Share Work-in-Progress Early and Often
When you share work-in-progress, share it with the caveat that no feedback is needed at this point. You’re simply sharing it to let people know where you are. For example, if you have to make 12 wireframes, share it when you finish 2 or 3. Rather than spending a whole week to drop 12 wireframes, share 2 – 3 wireframes every 2 days. The more often you do this, you start to build rhythm, and rhythm builds momentum.
The care and feeding of software engineers (or, why engineers are grumpy)
An Article by Nicholas ZakasWe do say “no” very quickly, not just to designs, but to everything. That led me into thinking about the psychology of software engineers and what makes us the way we are.
The art of taking
A Quote"By making it possible for the photographer to observe his work and his subject simultaneously, and by removing most of the manipulative barriers between the photographer and the photograph, it is hoped that many of the satisfactions of working in the early arts can be brought to a new group of photographers. The process must be concealed from—non-existent for—the photographer, who by definition need think of the art in taking and not in making photographs. In short, all that should be necessary to get a good picture is to take a good picture, and our task is to make that possible."
— Edwin H. Land, co-founder of Polaroid
Painting With the Web
An Article by Matthias OttSo much about [Gerhard Richter's painting process] reminds me of designing and building for the Web: The unpredictability, the peculiarities of the material, the improvisation, the bugs, the happy accidents. There is one crucial difference, though. By using static wireframes and static layouts, by separating design and development, we are often limiting our ability to have that creative dialogue with the Web and its materials. We are limiting our potential for playful exploration and for creating surprising and novel solutions. And, most importantly, we are limiting our ability to make conscious, well-informed decisions going forward. By adding more and more layers of abstraction, we are breaking the feedback loop of the creative process.
Technical debt as a lack of understanding
An Article by Dave Rupert"If you develop a program for a long period of time by only adding features but never reorganizing it to reflect your understanding of those features, then eventually that program simply does not contain any understanding and all efforts to work on it take longer and longer.” — Ward Cunningham
Steve Jobs
You'll know it's there
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."
The Apple Marketing Philosophy
Markkula wrote his principles in a one-page paper titled "The Apple Marketing Philosophy" that stressed three points.
The first was empathy, an intimate connection with the feelings of the customer: "We will truly understand their needs better than any other company."
The second was focus: "In order to do a good job of those things that we decide to do, we must eliminate all of the unimportant opportunities."
The third and equally important principle, awkwardly named, was impute. It emphasized that people form an opinion about a company or product based on the signals that it conveys. "People DO just a book by its cover," he wrote. "We may have the best product, the highest quality, the most useful software etc.; if we present them in a slipshod manner, they will be perceived as slipshod; if we present them in a creative, professional manner, we will impute the desired qualities."
Not just in the details
There falls a shadow, as T.S. Eliot noted, between the conception and the creation. In the annals of innovation, new ideas are only part of the equation. Execution is just as important.
The improvements [over Xerox] were in not just the details but the entire concept. The mouse at Xerox PARC could not be used to drag a window around the screen. Apple's engineers devised an interface so you could not only drag windows and files around, you could even drop them into folders. The Xerox system required you to select a command in order to do anything...the Apple system transformed the desktop metaphor into virtual reality by allowing you to directly touch, manipulate, drag, and relocate things. And Apple's engineers worked in tandem with its designers to improve the desktop concept by adding delightful icons and menus that pulled down from a bar atop each window and the capability to open files and folders with a double click.
An icon is a symbol equally incomprehensible in all human languages
An icon is a symbol equally incomprehensible in all human languages. There's a reason why humans invented phonetic languages.
If it could save a person's life, would you find a way to make it faster?
"If it could save a person's life, would you find a way to shave ten seconds off the boot time?" [Jobs] asked. Kenyon allowed that he probably could. Jobs went to a whiteboard and showed that if there were five million people using the Max, and it took ten seconds extra to turn it on every day, that added up to three hundred million or so hours per year that people would save, which was the equivalent of at least one hundred lifetimes saved per year. "Larry was suitably impressed, and a few weeks later he came back and it booted up twenty-eight seconds faster," Atkinson recalled. "Steve had a way of motivating by looking at the bigger picture."
We might as well make them beautiful
The Macintosh team came to share Jobs's passion for making a great product, not just a profitable one. "Jobs thought of himself as an artist, and he encouraged the design team to think of ourselves that way too," said Hertzfeld. "The goal was never to beat the competition, or even to make a lot of money. It was the do the greatest thing possible, or even a little greater." He once took the team to see an exhibit of Tiffany glass at the Metropolitan Museum in Manhattan because he believed they could learn from Louis Tiffany's example of creating great art that could be mass-produced. Recalled Bud Tribble, "We said to ourselves, 'Hey, if we're going to make things in our lives, we might as well make them beautiful.'"
Models and iterations
Every month or so, Manock and Oyama would present a new iteration based on Jobs's previous criticisms. The latest plaster model would be dramatically unveiled, and all the previous attempts would be lined up next to it. That not only helped them gauge the design's evolution, but it prevented Jobs from insisting that one of his suggestions had been ignored.
For a computer to be friendly
Even though Steve didn't draw any of the lines, his ideas and inspiration made the design what it is. To be honest, we didn't know what it meant for a computer to be 'friendly' until Steve told us.
It's not just a little thing
At one point Kare and Atkinson complained that he was making them spend too much time on tiny little tweaks to the title bar when they had bigger things to do. Jobs erupted. "Can you imagine looking at that every day?" he shouted. "It's not just a little thing, it's something we have to do right."
Real artists sign their work
When the design was finally locked in, Jobs called the Macintosh team together for a ceremony. "Real artists sign their work," he said. So he got out a sheet of drafting paper and a Sharpie pen and had all of them sign their names. The signatures were engraved inside each Macintosh.
Whole widgets
Jobs believed that for a computer to be truly great, its hardware and its software had to be tightly linked. When a computer was open to running software that also worked on other computers, it would end up sacrificing some functionality. The best products, he believed, were "whole widgets" that were designed end-to-end, with the software closely tailored to the hardware and vice versa.
A ripple through the universe
As every day passes, the work fifty people are doing here is going to send a giant ripple through the universe. I know I might be a little hard to get along with, but this is the most fun thing I've done in my life.
Customers don't know what they want
At the end of the presentation someone asked whether he thought they should do some market research to see what customers wanted. "No," he replied, "because customers don't know what they want until we've shown them." Then he pulled out a device that was about the size of a desk diary. "Do you want to see something neat?" When he flipped it open, it turned out to be a mock-up of a computer that could fit in your lap, with a keyboard and a screen hinged together like a notebook. "This is my dream of what we will be making in the mid- to late eighties," he said. They were building a company that would invent the future.
All sorts of ways to use the machine
Jobs wanted to sell Pixar's computers to a mass market, so he had the Pixar folks open up sales offices—for which he approved the design—in major cities, on the theory that creative people would soon come up with all sorts of ways to use the machine. "My view is that people are creative animals and will figure out clever new ways to use tools that the inventor never imagined."
One keyboard at a time
His frustration with Apple was evident when he gave a talk to a Stanford Business School club at the home of a student, who asked him to sign a Macintosh keyboard. Jobs agreed to do so if he could remove the keys that had been added to the Mac after he left. He pulled out his car keys and pried off the four arrow cursor keys, which he had once banned, as well as the top row of F1, F2, F3 ... function keys. "I'm changing the world one keyboard at a time," he deadpanned. Then he signed the mutilated keyboard.
Think Different.
They debated the grammatical issue: If "different" was supposed to modify the verb "think," it should be an adverb, as in "think differently." But Jobs insisted that he wanted "different" to be used as a noun, as in "think victory" or "think beauty." Also, it echoed colloquial use, as in "think big." Jobs later explained, "We discussed whether it was correct before we ran it. It's grammatical, if you think about what we're trying to say. It's not think the same, it's think different. Think a little different, think a lot different, think different. 'Think differently' wouldn't hit the meaning for me"
Ban PowerPoints
One of the first things Jobs did during the product review process was ban PowerPoints. "I hate the way people use slide presentations instead of thinking," Jobs later recalled. "People would confront a problem by creating a presentation. I wanted them to engage, to hash things out at the table, rather than show a bunch of slides. People who know what they're talking about don't need PowerPoint."
Which ones do I tell my friends to buy?
The product review revealed how unfocused Apple had become. The company was churning out multiple versions of each product because of bureaucratic momentum and to satisfy the whims of retailers..."I had people explaining this to me for three weeks," Jobs said. "I couldn't figure it out." He finally began asking simple questions, like, "Which ones do I tell my friends to buy?"
When he couldn't get simple answers, he began slashing away at models and products. Soon he had cut 70% of them..."I came out of the meeting with people who had just gotten their products canceled and they were three feet off the ground with excitement because they finally understood where in the heck we were going."
After a few weeks Jobs finally had enough. "Stop!" he shouted at one big product strategy session. "This is crazy." He grabbed a magic marker, padded to a whiteboard, and drew a horizontal and vertical line to make a four-squared chart. "Here's what we need," he continued. Atop the two columns he wrote "Consumer" and "Pro"; he labeled the two rows "Desktop" and "Portable." Their job, he said, was to make four great products, one for each quadrant. "The room was in dumb silence," Schiller recalled.
That feeling of putting care into a product
I always understood the beauty of things made by hand. 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.
Unlike some designers, [Ive] didn't just make beautiful sketches; he also focused on how the engineering and inner components would work.
He became head of [the design department at Apple] in 1996, the year before jobs returned, but wasn't happy. Amelio had little appreciation for design.
There wasn't that feeling of putting care into a product, because we were trying to maximize the money we made. All they wanted from us designers was a model of what something was supposed to look like on the outside, and then engineers would make it as cheap as possible. I was about to quit.
To be truly simple
Why do we assume that simple is good? Because with physical products, we have to feel we can dominate them. As you bring order to complexity, you find a way to make the product defer to you. Simplicity isn't just a visual style. It's not just minimalism or the absence of clutter. It involves digging through the depth of the complexity. To be truly simple, you have to go really deep. For example, to have no screws on something you can end up having a product that is so convoluted and so complex. The better way is to go deeper with the simplicity, to understand everything about it and how it's manufactured. You have to deeply understand the essence of a product in order to be able to get rid of the parts that are not essential.
Total collaboration
The process of designing a product at Apple was integrally related to how it would be engineered and manufactured. Ive described one of Apple's Power Macs. "We wanted to get rid of anything other than what was absolutely essential," he said. "To do so required total collaboration between the designers, the product developers, the engineers, and the manufacturing team. We kept going back to the beginning, again and again. Do we need that part? Can we get it to perform the function of the other four parts?"
Pure and seamless
The connection between the design of a product, its essence, and its manufacturing was illustrated for Jobs and Ive when they were traveling in France and went into a kitchen supply store. Ive picked up a knife he admired, but then put it down in disappointment. Jobs did the same. "We both noticed a tiny bit of glue between the handle and the blade," Ive recalled. They talked about how the knife's good design had been ruined by the way it was manufactured. "We don't like to think of our knives as being glued together," Ive said. "Steve and I care about things like that, which ruin the purity and detract from the essence of something like a utensil, and we think alike about how products should be made to look pure and seamless."
When we make a model and realize it's rubbish
Much of the design process is a conversation, a back-and-forth as we walk around the tables and play with the models. He doesn't like to read complex drawings. He wants to see and feel a model. He's right. I get surprised when we make a model and then realize it's rubbish, even though based on the CAD renderings it looked great.
He loves coming in here because it's calm and gentle. It's a paradise if you're a visual person. There are no formal design reviews, so there are no huge decision points. Instead we can make the presentations fluid. Since we iterate every day and never have dumb-ass presentations, we don't run into major disagreements.
A ritual of unpacking
I love the process of unpacking something. You design a ritual of unpacking to make the product feel special. Packaging can be theater, it can create a story.
The iMac
Ive and his team worked with Apple's Korean manufacturers to perfect the process of making the cases, and they even went to a jelly bean factory to study how to make translucent colors look enticing. The cost of each case was more than $60 per unit, three times that of a regular computer case. Other companies would probably have demanded presentations and studies to show whether the translucent case would increase sales enough to justify the extra cost. Jobs asked for no such analysis.
Topping off the design was the handle nestled into the iMac. It was more playful and semiotic than it was functional. This was a desktop computer; not many people were really going to carry it it around. But as Ive later explained:
Back then, people weren't comfortable with technology. If you're scared of something, then you won't touch it. I could see my mum being scared to touch it. So I thought, if there's this handle on it, it makes a relationship possible. It's approachable. It's intuitive. It gives you permission to touch. It gives a sense of deference to you.
We'll slap a little color on this piece of junk
"The one thing Apple's providing now is leadership in colors," Gates said as he pointed to a Windows-based PC that he jokingly had painted red. "It won't take long for us to catch up with that, I don't think."
Jobs was furious, and he told a reporter that Gates, the man he had publicly decried for being completely devoid of taste, was clueless about what made the iMac so much more appealing than other computers. "The thing that our competitors are missing is they think it's about fashion, and they think it's about surface appearance," he said. "They said, We'll slap a little color on this piece of junk computer, and we'll have one, too."
The Apple Store
"Ron [Johnson] thinks we've got it all wrong. He thinks [the Apple store] should be organized not around products but instead around what people do." There was a pause, then Jobs continued. "And you know, he's right." He said they would redo the layout, even though it would likely delay the planned January rollout by three or four months. "We've only got one chance to get it right."
Jobs liked to tell the story—and he did so to his team that day—about how everything he had done correctly had required a moment when he hit the rewind button. In each case he had to rework something that he discovered was not perfect.
The iPod
Suddenly everything had fallen into place: a drive that would hold a thousand songs; and interface and scroll wheel that would let you navigate a thousand songs; a FireWire connection that could sync a thousand songs in under ten minutes; and a battery that would last through a thousand songs.
"We suddenly were looking at one another and saying, 'This is going to be so cool,'" Jobs recalled. "We knew how cool it was, because we knew how badly we each wanted one personally."
Cannibalize yourself
Like many companies, Sony worried about cannibalization. If it built a music player and service that made it easy for people to share digital songs, that might hurt sales of its record division. One of Jobs's business rules was to never be afraid of cannibalizing yourself. "If you don't cannibalize yourself, someone else will."
The job of art is to chase ugliness away
Bono later explained that not all corporate sponsorships were deals with the devil.
The 'devil' here is a bunch of creative minds, more creative than a lot of people in rock bands. The lead singer is Steve Jobs. These men have helped design the most beautiful art object in music culture since the electric guitar. That's the iPod. The job of art is to chase ugliness away.
The right kind of building can do great things for a culture
"Steve had this firm belief that the right kind of building can do great things for a culture," said Pixar's president Ed Catmull.
Despite being a denizen of the digital world, or maybe because he knew all too well its isolating potential, Jobs was a strong believer in face-to-face meetings. "There's a temptation in our networked age to think that ideas can be developed by email and iChat," he said. "That's crazy. Creativity comes from spontaneous meetings, from random discussions. You run into someone, you ask what they're doing, you said 'Wow,' and soon you're cooking up all sorts of ideas."
When our tools are broken, we feel broken
In his piece [for Time] Lev Grossman correctly noted that the iPhone did not really invent many new features, it just made those features a lot more usable. "But that's important. When our tools don't work, we tend to blame ourselves, for being too stupid or not reading the manual or having too-fat fingers...When our tools are broken, we feel broken. And when somebody fixes one, we feel a tiny bit more whole."
Scoop it up and whisk it away
At one point Jobs looked at the model [for the first iPad] and was slightly dissatisfied. It didn't feel casual and friendly enough, so that you would naturally scoop it up and whisk it away. Ive put his finger, so to speak, on the problem: They needed to signal that you could grab it with one hand, on impulse. The bottom edge needed to be slightly rounded, so that you'd feel comfortable just scooping it up rather than lifting it carefully.
A pedestrian cloak
Even before the iPad went on sale, Jobs was thinking about what should be in the iPad 2...there was a peripheral issue that he focused on that most people hadn't thought about: The cases that people used covered the beautiful lines of the iPad and detracted from the screen. They made fatter what should be thinner. They put a pedestrian cloak on a device that should be magical in all of its aspects.
To read things that are not yet on the page
My passion has been to build an enduring company where people were motivated the make great products. Everything else was secondary...the products, not the profits, were the motivation.
Some people say, "Give the customers what they want." But that's not my approach. Our job is to figure out what they're going to want before they do. I think Henry Ford once said, "If I'd asked customers what they wanted, they would have told me, 'A faster horse!'" People don't know what they want until you show it to them. That's why I never rely on market research. Our task is to read things that are not yet on the page.
Click
I'm about fifty-fifty on believing in God. For most of my life, I've felt that there must be more to our existence than meets the eye.
I like to think that something survives after you die. It's strange to think that you accumulate all this experience, and maybe a little wisdom, and that it just goes away. So I really want to believe that something survives, that maybe your consciousness endures.
But on the other hand, perhaps it's like an on-off switch. Click! And you're gone.
...Maybe that's why I never liked to put on-off switches on Apple devices.