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 Blue Cliff Record
Mountains are mountains
Before attaining enlightenment,
mountains are mountains, rivers are rivers.At the moment of enlightenment,
mountains are no longer mountains,
nor are rivers rivers.After attaining enlightenment,
mountains are mountains, rivers are rivers.No door at which to knock
Penetrating the Blue Cliff, you will open
the eye within eyes
and realizing life through the Blue Cliff,
you yourself will become a torch,
the light beyond light.Being so, you will find no door at which to knock, nor any door to be opened.
The miraculous bones of the ancients
A Ch'an master once wrote that the wise enshrine the miraculous bones of the ancients within themselves; that is, they do not regard teachings of ways to enlightenment as an external body of knowledge or information to be possessed as an acquisition or believed or revered as inflexible dogma, but rather apply it as far as possible to themselves and their situations, vivifying the way of enlightenment with their own bodies and lives, not just in their thoughts. It is therefore a matter of course that new Buddhist literature has been produced; for the Buddhist canon is not closed, as long as people continue the search for enlightenment.
Ch'an was referred to by its followers as the "school of the patriarchs" because it was transmitted by a living succession of human exemplars; not a school of doctrine, or philosophical or scholastic interpretation, it was not based on any particular scripture, but on the direct experience of the enlightened mind, by whatever means currently necessary.
What did you see when you were there?
Ch'an masters tell us to look right where we stand and step: they ask what is there, is there anything, who are you and where do you come from, what did you see and hear when you were there?—in a hundred ways they try to make us wake up, clear our minds, and face reality directly.
I have pacified your mind
Bodhidharma, the first Patriarch of Ch'an in China, was asked by Hui K'e, the future Second Patriarch, so pacify his mind for him; Bodhidharma said, "Bring me your mind and I will pacify it for you." Hui K'e said, "When I search for my mind, I cannot find it." Bodhidharma said, "I have pacified your mind for you." At this Hui K'e was enlightened.
In one there are many; in two, one
The ultimate path is without difficulty;
Speech is to the point, words are to the point.
In one there are many kinds;
In two there is no duality.It's dark outside
As soon as Te Shan crossed the threshold he said, "Long have I heard of Lung T'an (Dragon Pond), but now that I've arrived here, there's no pond to see and no dragon appears." Master Lung T'an came out from behind a screen and said, "You have really arrived at Lung T'an." Te Shan bowed and withdrew.
During the night, Te Shan entered Lung T'an's room and stood in attendance till late at night. Lung T'an said, "Why don't you go?" Te Shan bade farewell, lifted up the curtain, and went out; he saw that it was dark outside, so he turned around and said, "It's dark outside." Lung T'an lit a paper lantern and handed it to Te Shan; as soon as Te Shan took it, Lung T'an blew it out. Te Shan was vastly and greatly enlightened.