Ryan Singer
Two kinds of usability
An Article by Ryan SingerI divide usability problems into two kinds:
- Perceptual: "They couldn't figure out what to do next", "they couldn't find the feature", "they didn't know they could click that button..." etc.
- Domain-specific: "We need a way to jump back here because in their workflow this happens..."
In general, usability testing only catches type 1 perceptual problems. Because in those tests you take people out of the real world and assign them tasks. Usability testing doesn't catch domain-specific problems because they only come up in real life use.
How I Wrote Shape Up
An Article by Ryan SingerHere’s a little behind-the-scenes look at the development of our newest book, Shape Up: Stop Running in Circles and Ship Work that Matters.
Keep digging
An Article by Ryan SingerThe hardest thing about customer interviews is knowing where to dig. An effective interview is more like a friendly interrogation. We don’t want to learn what customers think about the product, or what they like or dislike — we want to know what happened and how they chose... To get those answers we can’t just ask surface questions, we have to keep digging back behind the answers to find out what really happened.
Domain-specific vs. Domain-independent UX
An Article by Ryan SingerDomain specific UX means understanding how the supply should fit the demand considering a specific situation and use case.
On the other hand, many aspects of UX don’t require knowledge about a particular situation. They‘re based on the common constraints of human sense faculties, memory and cognition or the net of ergonomic factors around the device and the setting where it’s used. These domain independent elements of the UX are important too.
Domain independent UX should absolutely pervade the organization. It belongs to the general skill and knowledge of each supplier at their link in the chain. It’s part of learning to be a good designer, programmer, marketer, salesperson etc.
The Fidelity Curve
An Article by Ryan SingerHow do we choose which level of fidelity is appropriate for a project?
I think about it like this: The purpose of making sketches and mockups before coding is to gain confidence in what we plan to do. I’m trying to remove risk from the decision to build something by somehow “previewing” it in a cheaper form. There’s a trade-off here. The higher the fidelity of the mockup, the more confidence it gives me. But the longer it takes to create that mockup, the more time I’ve wasted on an intermediate step before building the real thing.
I like to look at that trade-off economically. Each method reduces risk by letting me preview the outcome at lower fidelity, at the cost of time spent on it. The cost/benefit of each type of mockup is going to vary depending on the fidelity of the simulation and the work involved in building the real thing.
Time-based analytics
An Article by Ryan SingerAnalytics apps don't tell you much about usage behavior. You might be able to see how many users performed an event, or how many times they did it. But none of the analytics packages out there are good at showing you how often people do things. Are they using to-dos once a week? Every day? Only signing into the app once a month but happily paying for years?
Time matters. You can't understand usage without time.
UI and Capability
An Article by Ryan SingerI’m very conscious of whether I am affording a feature or styling it. It’s important to distinguish because they look the same from a distance.
...Affording a capability and styling it are both important. But it’s essential to know which one you are doing at a given time. Style is a matter of taste. Capability and clarity are not. They are more objective. That person standing at the edge of the chasm cares more about accomplishing their task than the details of the decor.
What happens to user experience in a minimum viable product?
An Article by Ryan Singer"Feature complexity is like surface area and quality of execution is like height. I want a base level of quality execution across all features. Whenever I commit to building or expanding a feature, I'm committing to a baseline of effort on the user experience."
There’s a distinction to make: The set of features you choose to build is one thing. The level you choose to execute at is another. You can decide whether or not to include a feature like ‘reset password’. But if you decide to do it, you should live up to a basic standard of execution on the experience side.
Features can be different sizes with more or less complexity, but quality of experience should be constant across all features. That constant quality of experience is what gives your customers trust. It demonstrates to them that whatever you build, you build well.
What UI really is (and how UX confuses matters)
An Article by Ryan SingerPeople mix the terms UI and UX together. UX is tricky because it doesn’t refer to any one thing. Interface design, visual styling, code performance, uptime, and feature set all contribute to the user’s “experience.” Books on UX further complicate matters by including research methods and development methodologies. All of this makes the field confusing for people who want to understand the fundamentals.
That’s why I avoid teaching the term ’UX.’ It means too many things to too many different people. Instead I focus on individual skills. Once you understand the individual skills, you can assemble them into a composite system without blurring them together. For software design, the core skill among all user-facing concerns is user interface design.
The Shape of Design
Near and far
The creative process, in essence, is an individual in dialogue with themselves and the work. The painter, when at a distance from the easel, can assess and analyze the whole of the work from this vantage. He scrutinizes and listens, chooses the next stroke to make, then approaches the canvas to do it. Then, he steps back again to see what he’s done in relation to the whole. It is a dance of switching contexts, a pitter-patter pacing across the studio floor that produces a tight feedback loop between mark-making and mark-assessing. The artist, when near, is concerned with production; when far, he enters a mode of criticism where he judges the degree of benefit (or detriment) the previous choice has had on the full arrangement.
Painting’s near and far states are akin to How and Why: the artist, when close to the canvas, is asking How questions related to craft; when he steps back, he raises Why questions concerned with the whole of the work and its purpose. Near and Far may be rephrased as Craft and Analysis, which describe the kinds of questions the artist asks while in each mode. This relationship can be restated in many different ways, each addressing a necessary balance:
- How and Why
- Near and Far
- Making and Thinking
- Execution and Strategy
- Craft and Analysis
Why we should read
Unfortunately, the program met its end because the show’s approach opposed the contemporary standard format of children’s television: teaching kids how to read, rather than Reading Rainbow’s objective, which was to teach kids about why they should read.
Reading Rainbow had a long run, lasting twenty-three years, but its cancellation feels like a symbolic blow. Education, just like climbing the ladder, must be balanced between How and Why. We so quickly forget that people, especially children, will not willingly do what we teach them unless they are shown the joys of doing so. The things we don’t do out of necessity or responsibility we do for pleasure or love; if we wish children to read, they must know why.
We hear a voice whisper
The Shakers have a proverb that says, “Do not make something unless it is both necessary and useful; but if it is both, do not hesitate to make it beautiful.” We all believe that design’s primary job is to be useful. Our minds say that so long as the design works well, the work’s appearance does not necessarily matter. And yet, our hearts say otherwise. No matter how rational our thinking, we hear a voice whisper that beauty has an important role to play.
Needs more love
He held the phone to his chest, looked at me, and simply said, “Needs more love.” He pushed the portfolio back across his desk, smiled warmly, and shooed me out of his office.
I still think about this advice, and what exactly he might have meant when he said my work needed more love. At the time, I took it to mean that I should improve my craft, but I’ve come to realize that he was speaking of something more fundamental and vital. My work was flat, because it was missing the spark that comes from creating something you believe in for someone you care about. This is the source of the highest craft, because an affection for the audience produces the care necessary to make the work well.
One candle can light another
Lighting one candle
with another candle—
spring evening.Buson is saying that we accept the light contained in the work of others without darkening their efforts. One candle can light another, and the light may spread without its source being diminished.
A great leap of lightness
The first step of any process should be to define the objectives of the work with Why-based questions. The second step, however, should be to put those objectives in a drawer. Objectives guide the process toward an effective end, but they don’t do much to help one get going. In fact, the weight of the objectives can crush the seeds of thought necessary to begin down an adventurous path.
The creative process, like a good story, needs to start with a great leap of lightness, and that is only attainable through a suspension of disbelief. The objectives shouldn’t be ignored forever, but they should be defined ahead of time, set aside, and then deployed at the appropriate moment so that we may be audacious with our ideas.
Going evil
To begin, we must build momentum and then reintroduce the objectives to steer the motion. I find the best way to gain momentum is to think of the worst possible way to tackle the project. Quality may be elusive, but stupidity is always easily accessible; absurdity is fine, maybe even desired. If the project is a business card for an optician, perhaps you imagine it is illegible. (This is in the spirit, but you can do better.) If it is a brochure for an insurance agency, imagine otters on the cover and deranged handwriting on the inside for the copy. (Further!) If it is design for an exhibition of Ming Dynasty vases, brand it as an interactive show for kids, and put the vases on precariously balanced pedestals made of a shiny metal that asks to be touched. (Yes!)
The important realization to have from this fun—though fruitless–exercise is that every idea you have after these will be better. Your ideas must improve, because there is no conceivable way that you could come up with anything worse.
The momentum of making
Limitations narrow a big process into a smaller, more understandable space to explore. It’s the difference between swimming in a pool and being dropped off in the middle of the ocean with no land in sight. Those limitations also become the basis for the crucial first steps in improvisation. After those, the momentum of making accelerates as ideas are quickly generated without judgment.
Let the body wander
If the mind needs to wander, best let the body do the same. A short walk is more effective in coming up with an idea than pouring all the coffee in the world down your gullet.
Message, tone, format
All design work seems to have three common traits: there is a message to the work, the tone of that message, and the format that the work takes. Successful design has all three elements working in co-dependence to achieve a whole greater than the sum of the individual parts.
Asking why
Most inventions are recombinations of existing things, but where do the sparks for those combinations come from? What instigates that magic to make hybrids, to use them for unimagined purposes, and to inspire new settings for the three levers? Certain advancements seem logical and inevitable—smaller cellphones, faster computers, more reliable medical technology—while others seem to come out of nowhere. Turning avocado into caviar, for example, is not a logical conclusion in the kitchen. That choice is an inspired one. You can always spot these brilliant inventions as instances of magic, because our reaction, much like Achatz’s first meal at elBulli, is always disbelief.
Henry Ford famously said that if he had asked his customers what they wanted, they would have said a faster horse. Of course, we know that the faster horse is a testament to the limited imagination of customers, but I’d suggest that it’s more representational of not reassessing the objectives of the work in light of new opportunities. The faster horse is a recombination of the three levers in a predictable way: the customer’s answer is staunchly loyal to the horse, the already established format of transportation. They are inside of the adjacent possible, and ask a How question: How can horses be better?
Asking a Why question leads us to a different conclusion: Why are horses important? Because they quickly and reliably get us from one place to another. A Why question defines our need and uses an objective to create a satisfactory outcome for the work. This type of question is specific enough to be observable, but flexible enough to be approached in a variety of different ways. It’s easy to think that the way to improve life is to iterate on the things that we already have, but that is a trap of limited imagination. We should be iterating on how we answer our needs, and not necessarily on the way our old solutions have taken shape. The root of our practice is located in the usefulness of the work, not the form that it takes.
Outcomes and consequences
The primary purpose of the design is to have it do something particular, not be any particular thing. All of this implies that design is a field of outcomes and consequences more than one of artifacts. The forms that designers produce are flexible, so long as the results serve the need.
The source of delight
Design doesn’t need to be delightful for it to work, but that’s like saying food doesn’t need to be tasty to keep us alive. The pedigree of great design isn’t solely based on aesthetics or utility, but also the sensation it creates when it is seen or used. It’s a bit like food: plating a dish adds beauty to the experience, but the testament to the quality of the cooking is in its taste. It’s the same for design, in that the source of a delightful experience comes from the design’s use.
Every exit is an entrance somewhere
At the Ace Hotel in New York, a required exit sign over a door was an eyesore, and a stark contrast from the considered, detailed wall where it was mounted. Rather than accept the wart as it was, the sign was embraced as a chance to create an experience for the hotel’s guests by integrating the exit sign into the space. Now, surrounding the sign are other letters painted on the wall in a similar condensed style.
Every requirement is an opportunity for delight, even the ugly ones. Sometimes the creative treatment of these warts are the most enjoyable parts of a design.