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.
Letters to the Future
The lapse of many years
At this point I wish to emphasize what I believe will ultimately prove to be the greatest purpose of our museum. This value will not, however, be realized until the lapse of many years, possibly a century, assuming that our material is safely preserved. And this is that the student of the future will have access to the original record of faunal conditions in California and the west, wherever we now work. He will know the proportional constituency of our faunae by species, the relative numbers of each species and the extent of the ranges of species as they exist today.
— Joseph Grinnell, 1910
The Grinnell System
The recording of field notes was common practice for biological surveyors and naturalists generations before Grinnell. His system continues this tradition but is distinguished by its distinctive standardized format. It consists of three sections:
- The journal contains a narrative account describing the study site and summarizing each day’s activities and observations, including a list of species encountered. This section is often peppered with sketches, photographs, or maps.
- The catalog is a sequential record of all voucher specimens collected, each with a unique field number and the information needed for the specimen’s museum tag, such as its sex, mass, breeding status, and standard body measurements.
- Species accounts are species-specific summaries of information and observations, gradually accumulated over multiple days at a site or across multiple sites, that eventually grow to detailed summaries of physical description, seasonal behaviors, microhabitat associations, and other characteristics.
Separating the notebook in this fashion allows each section to have its own context-specific structure and format.
Jim's system
From the earliest days of my fieldwork until now, throughout a given day I jotted notes, typically in pencil, into a small, spiral-bound pocket notebook, remembering the admonition not to trust one’s memory but to record observations as continually as possible. I then transcribes these notes into my handwritten journal in the evenings on the best of days or every few days when an intense field effort allowed.
From 2000 onward, I would still takes pencil notes in a small pocket notebook in the field, but I transcribes these into a word-processor document with margins set for the size of our field note pages. I combined this document with my field catalog for a particular trip and eventually both would be bound in the same manner as standard, handwritten field notes.
This approach had the advantage of producing both an archival paper copy as well as an electronic copy. It was also easy to intersperse specialized maps and digital photographs, which had become the norm by this time, throughout the journal text.
John's system
I have two field notebooks: a “raw" notebook and my formal Grinnellian notebook.
In the field, I take all my raw notes in a waterproof notebook using a fine-point permanent pen (or pencil when its raining). The entries have virtually no structure other than the date at the top of (almost) every page.
At the end of the day, I transcribe the notes into my Grinnellian journal as if I were writing a latter to a colleague.
Record them all
You can’t tell often in advance which observations will prove valuable. Do record them all!
— Joseph Grinnell, 1908
Recommendations for field notes
Being an end-user of someone else’s field notes certainly gives you insight into the benefits of good note-taking skills. Our experiences as end-users and creators of archival field notes lead us to a few specific recommendations:
(1) Don’t get bogged down in the details of format or style.
Rules are counterproductive if they prevent a researcher from taking field notes in the first place.
You will get more return by focusing on your content than by refining your formatting.
(2) Compose your notes as if you were writing a letter to someone a century in the future.
Writing for an external audience requires you to be more explicit in your descriptions and to take less knowledge for granted. Avoid the use of abbreviations, symbols, and other shortcuts that only you will understand.
Ask yourself: How would you describe this to someone over the phone?
(3) It is better to spend five minutes writing the important details than twenty minutes writing the trivial ones.
Field notes
Field notes example.
Camp's notes
Grinnell-era field notes example, Charles L. Camp.