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 Image of the City
- To become completely lost
- Apparency
- On the edge of something else
- Nothing there, after all
- Paths, edges, districts, nodes, landmarks
To become completely lost
To become completely lost is perhaps a rather rare experience for most people in the modern city. We are supported by the presence of others and by special way-finding devices: maps, street numbers, route signs, bus placards. But let the mishap of disorientation once occur, and the sense of anxiety and even terror that accompanies it reveals to us how closely it is linked to our sense of balance and well-being. The very word "lost" in our language means much more than simple geographical uncertainty; it carries overtones of utter disaster.
Apparency
Half a century ago, Stern discussed this attribute of an artistic object and called it apparency. While art is not limited to this single end, he felt that one of its two basic functions was "to create images which by clarity and harmony of form fulfill the need for vividly comprehensible appearance." In his mind, this was an essential first step toward the expression of inner meaning.
On the edge of something else
The most common response to the question of symbolism was nothing in the city at all, but rather the sight of the New York City skyline across the river. Much of the characteristic feeling for Jersey City seemed to be that it was a place on the edge of something else.
Nothing there, after all
When asked to describe or symbolize the city as a whole, the subjects used certain standard words: "spread out", "spacious", "formless", "without centers". Los Angeles seemed to be hard to envision or conceptualize as a whole. Said one subject:
It's as if you were going somewhere for a long time, and when you got there you discovered there was nothing there, after all.
Paths, edges, districts, nodes, landmarks
The contents of the city's images which are referable to physical forms can conveniently be classified into five types of elements: paths, edges, districts, nodes, and landmarks.
- Paths are the channels along which the observer customarily, occasionally, or potentially moved.
- Edges are the linear elements not used or considered as paths by the observer. They are the boundaries.
- Districts are the medium-to-large sections of the city, conceived of as having two-dimensional extent.
- Nodes are points, the strategic spots in a city into which an observer can enter, and which are the intensive foci to and from which they are traveling.
- Landmarks are another type of point-reference, but in this case the observer does not enter within them, they are external. They are usually a rather simply defined physical object: building, sign, store, or mountain.
A directional quality
Paths may not only be identifiable and continuous, but have directional quality as well: one direction along the line can easily be distinguished from the reverse. This can be done by a gradient, a regular change in some quality which is cumulative in one direction.
Introverts and extroverts
Some regions are introvert, turned in upon themselves with little reference to the city outside them, such as Boston's North End or Chinatown. Others may be extrovert, turned outward and connected to surrounding elements. The common visibly touches neighboring regions, despite its inner path confusions.
Junctions
The junction, or place of a break in transportation, has compelling importance for the city observer. Because decisions must be made at junctions, people heighten their attention at such place and perceive elements with more than normal clarity. This tendency was confirmed so repeatedly that elements located at junctions may automatically be assumed to derive special prominence from their location.
What we are accustomed to call beautiful
Most objects which we are accustomed to call beautiful, such as a painting or a tree, are single-purpose things, in which, through long development or the impress of one will, there is an intimate, visible linkage from fine detail to total structure.
A certain plasticity
There are dangers in a highly specialized visible form; there is a need for a certain plasticity in the perceptual environment. If there is only one dominant path to a destination, a few sacred focal points, or an ironclad set of rigidly separated regions, then there is only one way to image the city without considerable strain. This one may suit neither the needs of all people, nor even the needs of one person as they vary from time to time. An unusual trip becomes awkward or dangerous; interpersonal relations may tend to compartmentalize themselves; the scene becomes monotonous or restrictive.
As plain as day
The personal experience of most of us will testify to this persistence of an illusory image long after its inadequacy is conceptually realized. We stare into the jungle and see only the sunlight on the green leaves, but a warning noise tells us that an animal is hidden there. The observer then learns to interpret the scene by singling out "give-away" clues and by reweighting previous signals. The camouflaged animal may now be picked up by the reflection of its eyes. Finally by repeated experience the entire pattern of perception is changed, and the observer need no longer consciously search for give-aways, or add new data to an old framework. They have achieved an image which will operate successfully in the new situation, seeming natural and right. Quite suddenly the hidden animal appears among the leaves, "as plain as day."