Reading the landscape As we walk about a site and talk to people, we can note our observations. At this stage, we try to store the information we gain in some accurate way, carry a notebook, or a camera and tape-recorder, and make small sketches. The notes we end up with can later be used to devise design strategies. We do not just see and hear, smell and taste, but we sense heat and cold, pressure, stress from efforts of hill-climbing or prickly plants, and find compatible or incompatible sites in the landscape. We note good views, outlooks, soil colours and textures. In face, we use (consciously) all our many senses and become aware of our bodies and responses. Beyond this, we can sit for a time and notice patterns and processes: how some trees prefer to grow in rocks, some in valleys, others in grasslands or clumps. We see how water flows on the site, where fires have left scars, winds have bent branches or deformed the shape of trees, how the sun and shadows move, and where we find signs of animals resting, moving, or feeding. The site is full of information on every natural subject, and we must learn to read it well. Bill Mollison, Introduction to Permaculture The Battle for the Life and Beauty of the Earth ethnography
The observer effect In biology, when researchers want to observe animals in their natural habitat, it is paramount that they find a way to do so without disturbing those animals. Otherwise, the behavior they see is unlikely to be natural, because most animals (including humans) change their behavior when they are being observed. Farnam Street fs.blog The Spoken and the Unspoken uxethnography
Two kinds of usability An Article by Ryan Singer world.hey.com I 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. uxethnography
The heart of systems engineering While the client has some knowledge of his symptoms, he may not understand the real causes of them, and it is foolish to try to cure the symptoms only. Thus while the systems engineers must listen to the client, they should also try to extract from the client a deeper understanding of the phenomena. Therefore, part of the job of a systems engineer is to define, in a deeper sense, what the problem is and to pass from the symptoms to the causes. Just as there is no definite system within which the solution is to be found, and the boundaries of the problem are elastic and tend to expand with each round of solution, so too there is often no final solution, yet each cycle of input and solution is worth the effort. A solution which does not prepare for the next round with some increased insight is hardly a solution at all. I suppose the heart of systems engineering is the acceptance that there is neither a definite fixed problem nor a final solution, rather evolution is the natural state of affairs. This is, of course, not what you learn in school, where you are given definite problems which have definite solutions. Richard Hamming, The Art of Doing Science and Engineering: Learning to Learn What the problem isComplete and consistent requirements