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
Product vs. Feature Teams An Article by Marty Cagan svpg.com This article is certain to upset many people. Empowered product teamsViability, usablity, feasibilityWhat went wrong? featuressoftwareagile
Empowered product teams When I wrote about the virtues of empowered product teams, I was referring to what I’ll continue to call here as product teams. Specifically, they are cross-functional (product, design and engineering); they are focused on and measured by outcomes (rather than output); and they are empowered to figure out the best way to solve the problems they’ve been asked to solve.
Viability, usablity, feasibility In an empowered product team, the product manager is explicitly responsible for ensuring value and viability; the designer is responsible for ensuring usability; and the tech lead is responsible for ensuring feasibility. The team does this by truly collaborating in an intense, give and take, in order to discover a solution that work for all of us. However, in a feature team, you still (hopefully) have a designer to ensure usability, and you have engineers to ensure feasibility, but, and this is critical to understand: the value and business viability are the responsibility of the stakeholder or executive that requested the feature on the roadmap. What went wrong? teamwork
What went wrong? If something ships from one of the companies I advise, and it is virtually unusable because of poor design (which as we all know occasionally does happen), you can bet I go directly to the designer and ask how this happened? It is absolutely on the designer to ensure this does not happen, so something went wrong. Similarly, if the product ships and performance is terrible you can bet I go directly to the tech lead with the same question. And most frequently of all, if something ships and the analytics show that it’s either not being bought or not being used, or it turns out that it violates some business constraint like compliance or privacy, you can bet I go right to the product manager with that question. Viability, usablity, feasibility