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.
A Q&A with Figma's VP of Product
Since we launched FigJam back in April, teams having been using it to grow all kinds of ideas into great designs. We recently caught up with Figma's VP of Product, Yuhki Yamashita, to hear what it was like to build FigJam and how things have changed since then. Here, he reflects on the evolving role of design and product management, what it means to welcome “non-designers” into the process, and the future of FigJam.
Stretching the product
When we’re thinking about where to take our product next, we actually take a lot of inspiration from our customers and the Figma Community, to see how they’re stretching our product in interesting or unexpected ways. We saw this happening in the early days of the pandemic. Our users were starting to use Figma for everything from brainstorming ideas to running team warm-up activities, to even putting on social events for people to get to know each other. We saw a lot of use cases that got us thinking.
Engineering, design, and product management
The boundary between engineering, design, and product management is blurring. Some of us used to have a mental model in which roles and responsibilities dictated how things work—that designers do one thing and engineers do another, for example. Increasingly, more people are crossing team lines to problem solve together...Now, it’s not about who “owns” what—it’s more of a collective endeavor. And the roles have become more interlocked, and I think that’s fundamentally a good thing.
Embracing the mess
Design is non-linear. At Figma, we often talk about “embracing the mess,” and that really means leaning into the chaos and complexity that makes the design process what it is. Even once you have the seedling of an idea, you need to explore and iterate, then pull back and evaluate to see what’s working and what’s not. Sometimes you’ll scrap an idea after a brainstorm session, and other times you’ll get pretty far with a concept, but still need different perspectives and input to move forward.