People making Tools for thought often say they’re trying to help people do math, or make art, or whatever. But in reality, the people making these tools are rarely connected very deeply with the actual creative practices they’re trying to amplify. The work is often more of a tech demo or a toy or a “sandbox.” As we wrote in How can we develop transformative tools for thought?: “Tools for writing that aren’t used by actual writers. Tools for mathematics that aren’t used by actual mathematicians.” Deep down, such system designers are generally developing a system for its own sake—not because there’s some creative problem they’re desperately trying to solve.
Such tools might look mathematical (or whatever) on their surface, but they’re not seriously trying to answer hard problems in those domains—often because the creators don’t actually know what those problems are or understand how to solve them. Effective system design requires insights drawn from serious contexts of use
Startups and technologists often fool themselves by working with and talking to early adopters who are mostly interested in playing with new technologies. But it’s not just a “tech industry” problem: academic tool-makers generally evaluate their systems in artificial settings with artificial data, against artificial validation criteria.
It’s hard to resolve this issue: Great tool-makers are often not great tool-users, and vice-versa
Matuschak, A., & Nielsen, M. (2019, October 0). How can we develop transformative tools for thought? https://numinous.productions/ttft
Interface matters to me more than anything else, and it always has. I just never realized that. I’ve spent a lot of time over the years desperately trying to think of a “thing” to change the world. I now know why the search was fruitless — things don’t change the world. People change the world by using things. The focus must be on the “using”, not the “thing”. Now that I’m looking through the right end of the binoculars, I can see a lot more clearly, and there are projects and possibilities that genuinely interest me deeply.
The Apollo program was an incredibly powerful Enabling environment, but it did not emerge from a project aiming to give scientists lots of great opportunities for personal growth. Rather, it was about putting people on the moon (and, er, saving the world from the Soviets). The enabling environment was a byproduct of that deeply meaningful effort.
Likewise, when Pixar created its revolutionary animation tools, many teams had been working on computer graphics for years, but Pixar’s systems emerged from a zealous pursuit of a storytelling dream: Pixar’s movies and technology development act as coupled flywheels.
Cathedrals! University research labs! Mathematica! They all follow this pattern.
Practically speaking, such contexts provide deeply meaningful feedback: Effective system design requires insights drawn from serious contexts of use. They also avoid the issues described in Authored environments are significantly colored by authors’ motivations. But perhaps most importantly, these projects also provide the intense personal connection which makes great work possible.
Some implications:
Is it possible to make the tail wag the dog? To initiate a project pursuing some intrinsically meaningful purpose in order to reap the enabling environments which emerge in that context? It’s not clear. The most likely failure mode is that the resulting project wouldn’t really create the intense personal connection required. But this is what we’re trying for with Ladder.
Building on Seymour Papert. (2005). You Can’t Think About Thinking Without Thinking About Thinking About Something. Contemporary Issues in Technology and Teacher Education, 5(3), 366–367.: you can’t teach children “logical thinking” in a vacuum, in an abstract sense; in the same way, you can’t make “tools for thought” in an abstract sense. You have to make a tool for thinking about something in particular; likewise, you have to understand logical thinking about something in particular.
https://github.com/mnielsen/tpft/blob/master/big_picture.md
The most powerful tools are not developed in isolation. Rather, they arise as part of projects done for their own, intrinsic reasons. Think of the art of stained glass windows, developed in service of God in the great cathedrals. Or of the development of computer animation in service of story by Pixar. These larger goals orient the development of the tools, ensuring they can be used seriously. This sounds like a platitude, but is often violated. “Tools” for mathematics or art or etc are often developed by people who are not deeply active in the area themselves. Unless they do extremely intensive user research—effectively, a collaboration with serious users—it’s extremely difficult for them to build anything other than plausible-seeming toys.
To this end, we will develop a series of ambitious media projects. These will—indeed, must!—be intrinsically worth doing in their own right. But they will also serve as a vehicle for the development of tools for thought.
Bret Victor’s 2021-06-14 reply to my email about research-context fit
DNA origami is a powerful emerging tool; it didn’t come out of a field centered on tool-making, but rather Paul Rothemund invented it as a means to the end of making self-assembling computers. The Scanning Tunneling Microscope didn’t come out of the field of microscopy, but rather Heinrich Rohrer wanted to help his colleagues fabricate Josephson junctions and needed a better spectrometer.
(see also Shawn Douglas on DNA origami)
Quote from Alan Kay in that same email:
==I don’t think you can start with “text” or “programming” and get very far==. I think it’s always better to have something important and big you want to do better with — eventually this provides clues to various kinds of media (including “languages”) that need to be invented to help. This is what people miss. McCarthy wasn’t trying to invent Lisp, he was trying to create ways to make an “Advice Taker”. Doug wasn’t trying to do hypertext, he was trying to synergize human effort for good.