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.
Stealth Architecture: The Rooms of Light and Space
To absorb it or build your own
Robert Smithson and other so-called land artists simply disengaged from architecture, placing their works in America's open landscape, leaving behind the museums and galleries Smithson referred to as "tombs". A new "expanded field" allowed artists to contextualize their work beyond the institutional frame of the museum or the commercial structure of a gallery. Richard Serra, who also began to move outdoors, at times chose to "attack" architecture, creating structures that disrupted or overwhelmed the buildings around them.
The artists of the Light and Space movement took another tack. Rather than fight or flee the architecture, they explored and manipulated it, approaching architecture as a kind of found object, creating a series of rooms that incorporated architecture and architectural structures directly into their art. Bruce Nauman summarized it well: "When you work in a gallery or museum, the architecture is a given. If you wanted to have a show, you didn't have a choice, except to deal with it. You had to find a way to either absorb architecture into the piece of build your own."
A stealth architect
By the 1970s, Irwin was in effect a stealth architect. We often talk about the ephemeral qualities of light and space in Irwin's installations, but what make those qualities palpable to our perception are practical structures—windows, walls, corridors, doorways, and skylights—in other words, architecture. And Irwin was keenly aware of how best to use all of those structures. One of his greatest talents has been to engage bad or benign architectural situations, disappearing into their details, changing them, and creating and entirely new quality of space.
The measuring unit of all space
The piece was titled The Portal, referring to a large opening in the center of the wall. Whether you want to call it art or architecture, it was a testament to the amazing presence that can be shown by a simple wall, which [Tadao Ando] has referred to as "the measuring unit of all space."
The walls are reserved for the sun
Maria Nordman always insisted, "Nothing should hang on a wall. The walls are reserved for the sun." It was like being inside a large cardboard box that had been gently slit open with an X-Acto knife, allowing thin planes of light to emerge. It is well known that Nordman avoided using the camera to document her installations, feeling that it abstracted and framed various aspects of the experience, which is best absorbed more holistically. It is ironic that Nordman's rooms often took the form of a kind of architectural camera in which slits in walls and corners created mysterious apertures that allowed light to leak into a room at a glacial pace. Being inside one of Nordman's spaces is like being inside a camera operating in exceedingly slow motion.
A little too something
As Irwin had chosen a stairwell for his UCLA installation because it was curious in its banality and innocuousness, Bruce Nauman became interested in corridors and shafts as overlooked and slightly eccentric spaces. He was particularly interested in those that had "a kind of constriction that wasn't natural or was a little too long or a little too something—like the architect just hadn't really thought it out."
Various titles of Bruce Nauman artworks
- Sound Breaking Wall
- Get Out of My Mind, Get Out of This Room
- False Silence
- Flayed Earth Flayed Self (Skin/Sink)
- Room with My Soul Left Out, Room That Does Not Care