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.
Cubed
A dry, husky business
Despite the furor over their aggressive unmanliness, clerks, and with them the office, crept silently into the world of nineteenth-century America. Moral philosophers were mostly preoccupied with the clang of industrialization and its satanic mills, and most regarded as negligible the barely audible scratch of pens across ledgers and receipts that characterized the new world of clerical work. It was only a “dry, husky business,” as the narrator of Bartleby had it.
A segment of the enormous file
As office buildings grew taller, and flammability became a problem, steel file cabinets replaced wooden ones – the tall cabinets mimicking the shape of the skyscraper, such that the “file” seemed to be a metaphorical stand-in for the office itself. “Each office within the skyscraper,” C. Wright Mills would argue some years later, “is a segment of the enormous file, a part of the symbolic factory that produces the billion slips of paper that gear modern society into its daily shape.” Aldous Huxley, in his dystopian novel Brave New World, could imagine no more powerful symbol of a totally bureaucratized world than the idea of each person having his or her name on a file.
Taylorism
“In the past the man has been first. In the future the system must be first.” — Fred W. Taylor
Taylorism was a way of thinking that came at the expense of the workers’ own knowledge of their system. Taylor summed up his philosophy thus:
“It is only through enforced standardization of methods, enforced adoption of the best implements and working conditions, and enforced cooperation that this faster work can be assured. And the duty of enforcing the adoption of standard and enforcing this cooperation rests with the management alone.”
The unscripted practices of the old offices would remain, but as a kind of subterfuge: in the future, a leisurely pace wouldn’t be the norm; time would not be given, but stolen.
Divided against itself
By separating knowledge from the basic work process (“the separation of conception from execution,” as Harry Braverman once put it), in the factory as well as the office, the ideology of Taylorism all but ensured a workplace divided against itself, both in space and in practice, with a group of managers controlling how work was done and their workers merely performing that work.
Somewhat more dangerously, this division put into serious doubt the notion that office workers were, as a whole, on the way up. It became increasingly clear from the shape of the offices themselves, and from the distance between the top and the bottom rungs of the “ladder”, that some workers were never going to join the upper layers of management. For some, work was always, frankly, going to suck.
Form follows finance
The formula that Sullivan coined to explain this individualist-conformist principle has become a commonplace of architectural history: “Form follows function.” The envelope of the building was to reflect no particular style, no empty ideal, but rather, with as pure a transparency as possible, the shape and feel of the interior. It was the office that determined the skyscraper – a fact that might have had a beneficial effect on the form of the office itself.
But the result was the opposite: few conceptions of the office have had a more deleterious effect on the human work environment. The title of an influential work by the architectural historian Carol Willis gives us a better, if less palatable, explanation: Form follows Finance. For by and large, making an office “functional” had less to do with making it serve the needs of a particular corporation and much more with serving any corporation. The point was not to make an office building per specification of a given company, but rather to build for an economy in which an organization could move in and out of a space without any difficulty. The space had to be eminently rentable.
Serendipity
This was not meant to be like Bell Labs; there were no expectations that the clerical workers would run into their managers in a “serendipitous encounter” and produce a new innovation. The ideas was rather to create a workplace in which status barriers seemed to dissolve, in which participation and friendliness all around made the work environment look less like the white-collar factory it was.
Office survival
“The caveman was undoubtedly very pleased to find a good cave but he also undoubtedly positioned himself at the entrance looking out. Protect your back but know what is going on outside is a very good rule for survival. It is also a good survival rule for life in offices.” — Robert Propst, The Office: A Facility Based on Chicago
The office landscape
An organic, almost forest-like office layout.
There is an affinity with certain planned “landscapes” of the natural world – namely, the classic Italian Baroque garden. In the sample plans the Schnelle brothers devised, the arrangement of desks seems utterly chaotic, totally unplanned – a mess, like a forest of refrigerator magnets. But, as with the seemingly “wild” overgrowth of a “natural” garden, the office landscape is more thoroughly planned than any symmetrical and orderly arrangement of desks. Imaginary lines wend their way around every cluster, delineating common pools of activity; between and through the undergrowth of clusters are invisible, sinuous paths of work flow.
Open-plan the world
In the end, noise would always be a problem, when quiet was not placed at a premium. Interaction and communication were conceived of as norms in the landscaped office; introspection and concentration were sidelines. In the rush to open-plan the world, some crucial values for the performance of work were lost.
The cubicle
The cubicle had the effect of putting people close enough to each other to create serious social annoyances, but dividing them so that they didn’t actually feel that they were working together. It had all the hazards of privacy and sociability but the benefits of neither. It got so bad that nobody wanted them taken away; even those three walls offered some kind of psychological home, a place one could call one’s own. All these factors could deepen the frenzied solitude of an office worker.
Chilled-out anxiety
Working in the typical dot-com office was an admixture of frenetic pace and a relaxed overall atmosphere, exemplifying that chilled-out anxiety which was the general mood of the 1990’s.
A resource
The office, Chiat argued, had become the site of a turf war, not a place to do work. Changing the office “means focusing on doing great work instead of focusing on agency politics,” he argued. “You come to work because the office is a resource.”