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.
Thinking in terms of outputs
In our use of digital and analogue filing tools, we classify information through folders. An article about railway construction gets filed under ‘infrastructure’ or ‘transport’. In Evernote we tag it with ‘rail’ or ‘construction’. This is thinking like a librarian and not like a writer. We are classifying the information as an input. The reason you take notes as a writer is to produce content. It makes sense, then, to take notes in line with this goal.
Traditional filing like this tends to fail when you attempt to write your content. You are stuck trying to figure out which categories will be relevant for your proposal, paper or blog post. Interesting writing often comes from connecting separate fields through a common idea. By revealing the common denominator. By unifying two seemingly-contradictory ideas. How can you possibly achieve this if you’re looking in the same category for your information? The categories simply do not fulfil the function required by the writer.
The notes you take and indeed, the way you process information, should be with a specific project or idea in mind. You must classify information in terms of its outputs. When you take notes on a book, think about how this could apply to a specific idea you had or how it argues against a paper you read last week. The premise is that you should be organising by context and always trying to connect the dots between the content you're consuming.