feedback
Control and Correlation
The fastest way to learn something is to do something
An Article by David R. MacIverSuppose you have a problem to solve. What do you do?
Well, you sit down and think real hard, and after extensive and careful planning you try the well thought out and rigorous solution that you have thought up. Right?
No, wrong! Bad.
The correct thing to do when you have a problem is:
- Think for a short amount of time.
- Make sure it is safe to try things.
- Try something you think will work.
- Observe the result. If you succeeded, yay you solved the problem! If it didn't work, think about what that means for the nature of the problem and try again.
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.
When Customer Journeys Don’t Work: Arcs, Loops, & Terrain
An Article by Stephen P. AndersonThinking [in terms of loops and arcs] allows us to let go of a specific journey or sequence, and imagine dozens of scenarios and possible sequences in which these skills can be learned. This doesn’t mean there aren’t more fundamental skills that other skills build upon, but we can let go the tyranny of how, precisely, a person will move through a system. We’re free to zoom in and obsess on these loops, which does two things for us:
- Approach the design of a system as the design of these as small but significant moments of learning.
- Consider the many ways these loops might be sequenced, with the exact order being less important.
Asynchronous Design Critique: Getting Feedback
An Article by Erin CasaliGetting feedback can be thought of as a form of design research. In the same way that we wouldn’t do any research without the right questions to get the insights that we need, the best way to ask for feedback is also to craft sharp questions.
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.