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.
What Good Means
The center of the way
The advice I’ve received from those who are close to the center of this timeless way of building is to start small. Like with a piece of tile, or a tea tray. And to then imagine along with Christopher Alexander:
What it would be like
to live in a mental world
where one’s reasons
for making something
functionally
and one’s reasons
for making something
a certain shape,
or in a certain
ornamental way
are coming
from precisely
the same place
in you
.Seduction
“The classic pervasive seduction to designers is finding a solution instead of the truth.” — Richard Saul Wurman
What the material wants to be
Part of how Lou Kahn made things be good was to ask the material what it wanted to do and be. He asked brick what it liked, and would get a different answer depending on the context for the building. In Dacca, the capital of Bangladesh, brick said it liked an arch. For the Korman House in Philadelphia, brick said it liked two giant fireplaces with a lintel between them for a doorway beneath and a balcony above.
Asking yourself some questions
All of the moves that we make in space will tend toward being in accord with this phenomenon of wholeness / beauty / life if we’re willing to bring the requisite level of care to the doing of our work.
Alexander says that each of us possess the means for accessing this order within ourselves and — here’s where he loses most other architects and many in the so-called sciences in academia — he contends that what we’re connecting with inside of ourselves is an objective criterion for what good means.
Applying the criterion is easy: you ask yourself some questions:
With any action you might take with regard to placement, and with regard to the situatedness of things in space you ask yourself: does this move increase wholeness / beauty / life?
Does the intervention you’re taking intensify the feelings of wholeness in you as the maker when you are performing the work?
How does your work on this one part enhance what’s going on among wholes at the system level?
Losing meaning
The people who’ve proven that they can make very good individual products with the radical focus of a spotlight seem to be pushed ever further from making good ecosystems.
Products are being made “consistent” with the application of so-called “design patterns,” and rather than bringing coherence to these various touch-points, the painting-on of interface standards and interaction patterns did something far less valuable.
Rote consistency, in the way many seem to be going about it (Material Design being just one example), is at odds with making things be good. It simplifies what needs to remain complex.
Always, when simplification is underway, meaning is being lost.
Two coffee trays
We speculate that the shop owners designed and built an initial quantity of these remarkable coffee trays, replete with what Alexander considers to be the fifteen geometric properties that correlate with wholeness / beauty / life.
Then they got busy. And then they got successful. They needed more coffee trays, and our hypothesis is that somebody decided to simplify the trays to ensure they could be produced in the quantities and at the price that worked for their budget, within an urgent food-service timeline.
The simplified tray fulfills every function the more complex tray does, with less fuss in manufacturing on account of having standardized its geometry. The simplified tray works, but isn’t alive. It lacks the gradients, local symmetries, levels of scale, contrast, and boundaries that are all present and accounted for in the tray that’s got wholeness / beauty / life. The tray with wholeness isn’t necessarily better than the simpler one. But it is good.