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.
Back to the Drawing Board
The lost art of drawing for engineers and architects.
- You can almost tell which software they were designed in
- Conversational drawing
- The effort heuristic
- Tablets have caught up
You can almost tell which software they were designed in
Tatiana von Preussen, cofounder of London practice vPPR Architects, says that certain software comes with constraints that encourage a particular style:
“Something I’ve noticed with new buildings is that you can almost tell which software they were designed in. For instance, if you take Revit, it’s very hard to freely create non-orthogonal, non-linear geometries, and it’s very easy to create repetitive elements, so it lends itself to a particular way of building.”
Conversational drawing
A skilled draughtsman guides design conversations by selecting and emphasizing details in a way that computer programmes cannot. Ron Slade, author of Sketching for Engineers and Architects and a structural director at WSP in London, calls it “conversational drawing”. He notes how botany field guides are always based on detailed drawings rather than photographs — as much for what they leave out as for what they show. “Extraneous material that might exist in a photograph is eliminated. It may be important to pick out and illustrate particular areas and leave other parts in sketchy or broad outline.”
The effort heuristic
Psychologists have noted that people tend to place greater artistic value on images when they can see the work that has gone into them — a tendency known as the “effort heuristic”. They are also more likely to connect emotionally with the work if they can detect the human hand, says Goldsmiths’ Chamberlain. “There’s an argument that if we see a brush stroke, we almost recreate it, and that’s part of the connection we feel with the artist — you can feel the intention.”
Perhaps to capitalize on this, some architects now show presentation drawings that look hand-drawn but are actually generated entirely by computer. “It’s totally fake,” says Brillhart. “They just take a computer image into Photoshop and put filters over it to make it look like it’s drawn by hand. It’s kind of amusing — instead of just sitting down and drawing for an hour, they spend eight hours making it look like a hand drawing.”
Tablets have caught up
But in the past couple of years, Brennan believes that tablets have caught up, with apps such as Apple’s ProCreate and Morpholio’s Trace becoming far more responsive to the user’s marks. “Tablets didn’t used to have that immediate response, from brain to eye to hand to pen to paper. A half-second delay has a huge impact on how you think — it causes you to stumble. But now that lag’s gone, it’s almost the same as drawing with pen on paper. You don’t need to engage with the airbrushes or other features — just use it in its purest form.” The stylus, too, far more convincingly apes a manual pen: “You’re able to tune it to almost replicate your favourite pen — and it doesn’t run out of ink.
Chetwood is an iPad devotee, using it to produce fantastical urban artworks as well as architecture. Far from hindering the drawing process, he believes tablets will give rise to a new era of creative drawing. “A lot of people say technology and computers are taking away the true art of drawing. That’s rubbish, it releases sketching. You can move so much quicker and change things much more quickly, and it keeps a record of what you’re doing. The control is just brilliant.” The polished glass surface is the only flaw, but textured acetates applied to the screen can make it feel more like paper.