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.
Questions to ask on a new job search
The role and expectations
- What does this job entail?
- What's driving the hire?
- What are the biggest challenges?
- What scope is there to do x, y, z?
- How/when/why would you consider hiring me to be successful?
- What does progression from here look like?
- What's the biggest mistake I could make?
The wider business
- Can you tell me a bit about the company?
- What about the culture?
- How does diversity, equity, and inclusion play into this?
- What's the most exciting thing on the company horizon?
- What's been the impact of COVID-19 on company finances/strategy?
- What are the best and worst things about working here?
Day to day
- What's the size/structure of the team I'd be around/have reporting to me?
- Which other people would I work most closely with?
- What technologies/tools would I work with?
- What could I do that would make your life easier?
The practical bits
- What salary are you offering for this role?
- Additional package/benefits
- How do you approach distributed working, and is there scope for this?
- What timescales are you hoping for?
- Holiday
- Job title
Give yourself an extra shot: Is there anything I've said today that makes you hesitate?