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.
Gods of the Word
Imagine that we had no voice and no tongue
Socrates: Imagine that we have no voice and no tongue, but want to communicate with one another. Wouldn’t we like the deaf and the dumb make signs with the hands and the head and the rest of the body?
Hermogenes: There would be no choice, Socrates.
Socrates: We would imitate the nature of the thing: lifting the hands to heaven would mean lightness and upwardness. Heaviness and downwardness would be expressed by letting them drop toward the ground...
Hermogenes: I don’t see that we could do anything else.
Socrates: And when we want to express ourselves with the voice or tongue or mouth, the expression is simply their imitation of what we want to express?
Hermogenes: I think, it must be so.My name
“I am the utterance of my name.”
— Thunder, Perfect Mind, The Nag Hammadi Library
Reference and Is-ness
There are at least two aspects to what we have traditionally called the meaning of a word. One aspect is reference, and the other is something I will call ‘inherent meaning’ following Ullman (1963). Inherent meaning is ‘Is-ness’ meaning. Inherent meaning is a word’s identity, and reference merely its resumé, where it has gone and what it has done, an itemization of its contexts. ‘Is-ness’ is unifying. Each word has a single pronunciation, a single inherent meaning. But reference is divisive. It makes what was one thing – the word – appear to be many things – its senses. It is inherent meaning which gives all those multifarious senses the power of being a single word.
It flows out and fills
This deeper meaning of a word isn’t confined to what we think of as a dictionary definition. Rather it flows out and fills all the space available to it. Although a basic sense does affect the dynamics of a word, it has no power over its essence. Like the captain of a ship, it can control the crew’s actions, but not their minds. Each word has an aspect of meaning which lies deeper than any of its senses, and it is fundamentally on this meaning that all the senses depend.
No less than a Zeus
I too am a true believer in the autonomy of the archetype. A
/t/
or an/h/
is no less than a Zeus. The consonants are not essentially physical, but they live, evolve and influence human affairs. We overlook something essential if we deny that they can get up and walk around. This is not to say that their existence is independent of the human psyche. But then everything depends on everything.Like a prism
When you look at phonemes, you look through the perspective of morphemes, which are one linguistic level higher. The higher level is like a prism that splits the light in two. What was one thing, like ‘length’ at the phoneme level, looks like two opposite things ‘long’ and ‘short’ from the perspective of the morphemes. In practice, when you find both a word and its opposite, then the phoneme is not about either of these two things, but about what is common to them.
Fracturing
If we step back and view from afar this process of One-ness and Is-ness to fracturing and interpretation – of inherent meaning to reference, it follows that what lies at the foundation of language is simply what it is – sound – free of reference and interpretation. What makes what we know as language from its sound is fracturing and interpretation or using a word for a function other than what it simply is.
To evolve the language itself
So in the process of talking, we might say we are putting words in slightly new contexts, and then testing them against our peers to see if our experiment in juxtaposition had ‘meaning. If we succeed, we have introduced new contexts for the words we use. These contexts will be taken up by our listeners, and will gradually become clearly enough defined to be thought of as referents. Once our words gain new referents, they start affecting the underlying phonosemantic structure of the language, the clustering patterns, the network of semantic relations. That is, the purpose of talking in the long run is to evolve the language itself.
Scooting over
There is at this point no evidence that acquired characteristics can be inherited. It is held that all changes to a genome are random, and cannot be subject to any higher principle. However, when a word is used in a new context, as it is whenever we say something new, a new sense is permitted. This does affect the phonosemantic structure, the linguistic DNA. Words in the vicinity of this word ‘scoot over’ to make room and allow themselves to be influenced by its philosophy. The language itself is now different.
The element becomes a sign
Each unit can be seen purely as form, as what it is. Or it can be viewed as having a function. Its function is only understandable within the next higher level of organization. And in every case, function must succumb to the constraints of form. Once this worldly function is assigned, the element becomes a ‘sign’. It falls into the realm of concept. There is a mapping from one thought system to another.
The demand of a new word
Why are these phonosemantic classes enough, and we need neither more nor less? Why are these consonants enough, and we need neither more nor less? What determines the need for a new word? How is this demand ‘felt’ by a language? How did the metabolic pathways of American English recognize that ‘jerk’ and ‘twerp’ and ‘punk’ and ‘nitwit’ and ‘dork’ and ‘ass’ and ‘goon’ and ‘twit’ and ‘dodo’ and ‘bum’ and ‘nerd’ and ‘dunce’ and ‘turd’ and ‘boob’ and ‘chump’ and ‘bitch’ and ‘bastard’ and ‘prude’ and so on and so forth simply were not equal to the task? We had to add ‘turkey’ and ‘squirrel’ as well?