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.
A Burglar's Guide to the City
To commune with the space
...having realized long ago that the best way to commune with an architectural space was by breaking into it.
Every building is infinite
For the burglar, every building is infinite.
Putting the streets to use
Tad Friend writes, if you build “nine hundred miles of sinuous highway and twenty-one thousand miles of tangled surface streets” in one city alone, then you’re going to find at least a few people who want to put those streets to use. This suggests that every city blooms with the kinds of crime most appropriate to its form.
Topology by other means
The burglar is a three-dimensional actor amid the two-dimensional surfaces and objects of the city. This means operating with a fundamentally different spatial sense of how architecture should work, and how one room could be connected to another. It means seeing how a building can be stented: engineering short-circuits where mere civilians, altogether less aggressive users of the city, would never expect to find them. Burglary is topology pursued by other means: a new science of the city, proceeding by way of shortcuts, splices, and wormholes.
Burglary's White Whale
If all cities already contain the crimes that will occur there, then, taken to its logical conclusion, this suggests there might be a kind of Moby-Dick of crime, a White Whale of urban burglary: a town or city so badly designed that the entire place can be robbed in one go.
Tarzan of the concrete jungle
Weissmuller was most famous for playing Tarzan, and swinging into his apartment from a ledge outside had a wild irony, like some new Tarzan of the concrete jungle updating the character for an urban age.
The source code for SimCity
Local Code was Sorkin’s attempt to design a whole city from scratch—with one big twist. The whole thing had been written as if it were the byzantine, nearly impossible to follow codes and regulations for an entire, hypothetical metropolis. The effect is like stumbling upon the source code for SimCity. Sorkin’s exhaustively made point was that, if you know everything about a given metropolis, from its plumbing standards to its parking requirements, its sewer capacity to the borders of its school districts, then you could more or less accurately imagine the future form of that city from the ground up.
Architectural dark matter
Every building had its rhythms. These service corridors were the internal hinterlands—the architectural dark matter—so beloved by Bill Mason.
Vamburglars
Burglary was originally only possible in a household or dwelling; the very word contains an etymological variant on the Latin burgus, for “castle” or “fortified home” (from which other words, such as burgher and even borough, also derive). Common law definitions of burglary also originally required the person to break into a house or dwelling at night. Giving historical burglary an oddly vampiric dimension, you could not, legally speaking, be a burglar while the sun was still out.
The close
Think of it as an invisible geometric shape perceptible only to lawyers—a conceptual pane of glass that might not have kept the rain out but could, for legal purposes, be used to define the original limits of the car’s interior. This is the close, and defining it is ultimately just a form of connecting the dots: drawing an imaginary line from the corner of an open window to the edge of a nearby wall to the front gate of a home garden, and so on.
Breaking the close thus constitutes entry into a “protected interior” or “specified enclosure".
To deter crime
“To deter crime,” Cisneros explains, “spaces should convey to would-be intruders a strong sense that if they enter they are very likely to be observed, to be identified as intruders, and to have difficulty escaping.”
Architectural sequences
Noted designer and architectural theorist Bernard Tschumi would call the predictable repetition of events inside an architectural space a sequence: a linear series of actions and behaviors that are at least partially determined by the design of the space itself.
Architectural screenplays
Tschumi began to explore this notion through what he called screenplays: each “screenplay” was a black-and-white diagram breaking down a range of events that might occur inside an architectural space. Tschumi drew them in a way that resembled dance notation or the spatial analysis of a film scene.
The City of Light
Streetlights were one of many new patrol tools implemented by Louis XIV’s lieutenant general of police, Gabriel Nicolas de la Reynie. De la Reynie’s plan ordered that lanterns be hung over the streets every sixty feet—with the unintended side effect that Paris soon gained its popular moniker, the City of Light. The world’s most romantic city takes its nickname from a police operation.
Spatial expectations
Loya, who served seven years in prison for multiple bank heists before becoming a writer, explained to me that it was during the getaway that he often had the best chance of thwarting people’s spatial expectations. In his case, this meant that what he did immediately after leaving the bank was often the most important decision of all.
The getaway to end all getaways
Any attempt to track down the perfect getaway is made all the more complex because almost everything we know about burglary—including how they did (or did not) get away—comes from the burglars we’ve caught. As sociologist R. I. Mawby pithily phrases this dilemma, “Known burglars are unrepresentative of burglars in general.” Great methodological despair is hidden in such a comment. Studying burglary is thus a strangely Heisenbergian undertaking, riddled with uncertainty and distorted by moving data points. The getaway to end all getaways—the one that leaves us all scratching our heads—to no small extent remains impossible to study.
Every heist is a counterdesign
Heists obsess people because of what they reveal about architecture’s peculiar power: the design of new ways of moving through the world. Every heist is thus just a counterdesign—a response to the original architect.
All the things we want to do
This is precisely where “burglary” becomes a myth, a symbol, a metaphor: it stands in for all the things people really want to do with the built environment, what they really want to do to sidestep the obstacles of their lives.