Research & Ethnography
What is unspoken
A nested classificatory hierarchy
Unfinished
Record them all
Recommendations for field notes
In Defense of Browsing
The illustrated guide to a Ph.D.
When users never use the features they asked for
An Article by Austin Z. HenleyWe deployed our tool. Almost no one used it.
The handful that did use it, used it once or twice and barely interacted with it. After a few days, zero people were using it.
Why did they tell me they wanted these features?
Why Most Published Research Findings Are False
A Research Paper by John P.A. IoannidisThere is increasing concern that most current published research findings are false. The probability that a research claim is true may depend on study power and bias, the number of other studies on the same question, and, importantly, the ratio of true to no relationships among the relationships probed in each scientific field. In this framework, a research finding is less likely to be true when the studies conducted in a field are smaller; when effect sizes are smaller; when there is a greater number and lesser preselection of tested relationships; where there is greater flexibility in designs, definitions, outcomes, and analytical modes; when there is greater financial and other interest and prejudice; and when more teams are involved in a scientific field in chase of statistical significance.
How can we develop transformative tools for thought?
A Research Paper by Andy Matuschak & Michael NielsenConventional tech industry product practice will not produce deep enough subject matter insights to create transformative tools for thought.
...The aspiration is for any team serious about making transformative tools for thought. It’s to create a culture that combines the best parts of modern product practice with the best parts of the (very different) modern research culture. You need the insight-through-making loop to operate, whereby deep, original insights about the subject feed back to change and improve the system, and changes to the system result in deep, original insights about the subject.
A hypothesis is a liability
A Research Paper by Itai Yanai & Martin LercherThere is a hidden cost to having a hypothesis. It arises from the relationship between night science and day science, the two very distinct modes of activity in which scientific ideas are generated and tested, respectively [1, 2]. With a hypothesis in hand, the impressive strengths of day science are unleashed, guiding us in designing tests, estimating parameters, and throwing out the hypothesis if it fails the tests. But when we analyze the results of an experiment, our mental focus on a specific hypothesis can prevent us from exploring other aspects of the data, effectively blinding us to new ideas.
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.
Fast Path to a Great UX – Increased Exposure Hours
An Article by Jared SpoolAs we’ve been researching what design teams need to do to create great user experiences, we’ve stumbled across an interesting finding. It’s the closest thing we’ve found to a silver bullet when it comes to reliably improving the designs teams produce.
The solution? Exposure hours. The number of hours each team member is exposed directly to real users interacting with the team’s designs or the team’s competitor’s designs. There is a direct correlation between this exposure and the improvements we see in the designs that team produces.
Weighing up UX
An Article by Jeremy KeithMetrics come up when we’re talking about A/B testing, growth design, and all of the practices that help designers get their seat at the table (to use the well-worn cliché). But while metrics are very useful for measuring design’s benefit to the business, they’re not really cut out for measuring user experience.
Monkeys testing random designs
A Tweet by Jared SpoolA/B testing is an effective approach to use science to design and deliver deeply-frustrating user experiences.
A/B testing without upfront research is just random monkeys testing random designs to see which of those designs do “best” against random criteria.
If drug testing was actually implemented like most A/B tests, you’d give 2 drugs to 2 groups of people and pick the “winner” by whichever group had fewer deaths.
You and Your Research
A Speech by Richard HammingThis talk centered on Hamming's observations and research on the question "Why do so few scientists make significant contributions and so many are forgotten in the long run?"
Rethinking Repair
This chapter is an exercise in broken world thinking. It asks what happens when we take erosion, breakdown, and decay, rather than novelty, growth, and progress, as our starting points in thinking through the nature, use, and effects of information technology and new media.
The modern infrastructural ideal
The form and possibility of the "modern infrastructural ideal" is increasingly under threat, as cracks (sometimes literal ones) show up in our bridges, our highways, our airports, and the nets of our social welfare systems. For these and other reasons, broken world thinking asserts that breakdown, dissolution, and change, rather than innovation, development, or design as conventionally practices and thought about are the key themes and problems facing new media and technology scholarship today.
Attached to this, however, comes a second and more hopeful approach: namely, a deep wonder and appreciation for the ongoing activities by which stability (such as it is) is maintained, the subtle arts of repair by which rich and robust lives are sustained against the weight of centrifugal odds, and how sociotechnical forms and infrastructures, large and small, get not only broken but restored, one not-so-metaphoric brick at a time.
The fulcrum of these two worlds
Here, then, are two radically different forces and realities. On one hand, a fractal world, a centrifugal world, and always-almost-falling-apart world. On the other, a world in constant process of fixing and reinvention, reconfiguring and reassembling into new combinations and new possibilities...the fulcrum of these two worlds is repair.
A creature of bones, not words
In building connections, [articulation work] builds meaning and identity, sorting out ontologies on the fly rather than mixing and matching between fixed and stable entities. Articulation lives first and foremost in practice, not representation; as its proper etymology suggests, it's a creature of bones, not words. When articulation fails, systems seize up, and our sociotechnical worlds become stuff, arthritic, unworkable.
The world is always breaking
So the world is always breaking; it's in its nature to break.
A side that goes unrecognized
Edward Burtynsky, Shipbreaking #4.
Burtynsky's [shipbreaking] photos tell us important things about the themes of breakdown, maintenance, and repair raised here. The first is the extent to which such work is rendered invisible under our normal modes of picturing and theorizing technology. Burtynsky's photos share, in exquisite detail, a side or moment of technological life that goes for the most part unrecognized.
If we are to understand maintenance, repair, and technology more broadly, scenes such as Burtynsky's must be made empirically and conceptually familiar, even normal.
Turned into other things
Ask yourself this: for all the representations of great ships in history you've encountered, at what times and in what forms have you seen such vessels? In almost every instance it will be at moments of birth, or at the heights of strength and glory: the christening before the maiden voyage, rounding the cape, facing down the Spanish fleet, and so on. But what happens (or happened) to these ships? Save for the special cases of hostile sinking, shipwreck, or honorable retirement and preservation, it was this: they were disassembled, repurposed, stripped, and turned into other things.
An engine of technological difference
Whether at the level of national "technological styles" that shape and differentiate the nature of "same" technologies in different national contexts, or the simple but consequential variations by which industrial commodities are brought into, enlivened, and sustained within the circumstances of individual homes and lives, repair may constitute an important engine by which technological difference is produced and fit is accomplished.
The internet grew by breaking
The Internet grew by breaking, bumping up against the limits of existing protocols and practices and working around them, leaving behind almost by accident some of the properties that we now enumerate as key and distinctive virtues of the Internet as infrastructural form. Far from being a generalized cultural tendency or a property of individual minds, innovation in the technology space, as in culture more generally, is therefore organized around problems. This makes innovation simultaneously specific and in some measure collective in nature. And its engine is breakdown and repair.
What the fixer knows
Can repair sites and repair actors claim special insight or knowledge, by virtue of their positioning vis-à-vis the worlds of technology they engage? Can the fixer know and see different things—indeed, different worlds—than the better-known figures of "designer" or "user"?
Tool-being
Take Heidegger's notion of "tool-being", built around the central distinction between tools that are "ready-to-hand" versus "present-at-hand".
In the former state, technologies function as anticipated, do and stay where they're supposed to, and therefore sink below the level of conscious reflection. In the latter, the material world resists, obstructs, or frustrates action, and therefore calls attention to itself (precisely because we must now work to figure out and overcome barriers in our no-longer seamless world).
An ethics of mutual care
Foregrounding maintenance and repair as an aspect of technological work invites not only new functional but also moral relations to the world of technology. It references what is in fact a very old but routinely forgotten relationship of humans to things in the world: namely, an ethics of mutual care and responsibility.
To love deeply a world of things
Care brings the worlds of action and meaning back together, and reconnects the necessary work of maintenance with the forms of attachment that so often (but invisibly, at least to analysts) sustain it.
...What if we care about our technologies, and do so in more than a trivial way? This feature or property has sometimes been extended to technologies in the past, but usually only ones that come out of deep folk or craft traditions, and rarely the products of a modern industrial culture.
...Is it possible to love, and love deeply, a world of things?
We live in the aftermath
So do we live in later modernity, postmodernity, alternative modernity, or liquid modernity? Knowledge societies, information societies, network societies, or risk societies? New media, old media, dead media, or hypermedia? The world of information, the world of search, the world of networks, or the or the world of big data?
The answer is simple: like every generation before, we live in the aftermath.