As a teenager in early-1980s Japan, Yoky Matsuoka was expected to pick one subject and build a career around it. She couldn't — physics and math pulled her one way, biology and physiology another, competitive tennis a third (until injury ended that path), and beneath all of it a straightforward love of building things with her hands.1
At UC Berkeley, and later in MIT's robotics master's program, she finally found a field wide enough to hold all of it: robotics, and within it, the specific problem of designing a robotic hand.
The other students working on the same lab's robot were almost entirely male engineers who treated the problem as pure mechanics — pack in as many actuators as possible, treat the whole assembly as a moving computer approximating human-like motion.2
Matsuoka wanted something categorically different: a hand as anatomically faithful to the real thing as she could build, which meant treating questions of evolution, physiology, and neuroscience as equally central to the design process as the engineering itself.3 Building toward genuine biological accuracy forced her to actually understand why the human hand is shaped the way it is — a bump at the base of the index finger's knuckle, for instance, turned out to exist specifically to add grip power at the center of the palm, most likely a mutation that stuck because of how central the hand became to human development.4
The clearest single design decision showing the difference between the two approaches: standard engineering practice packed all of a robotic hand's motors and cables into the palm, for convenience, which made the palm rigid — and a rigid palm meant the thumb could never touch the pinky, a permanent, unfixable limitation software engineers were then handed afterward and asked to work around.5
Matsuoka reasoned from the opposite direction. Starting from the question of what actually makes a hand dexterous, she identified a flexible, curved palm as the real requirement — which meant the motors had to go somewhere else entirely. And once she was thinking at that level, it became clear the thumb, not general across-the-board mobility, was the actual key to grasping, so that's where she concentrated the mechanical power.6 Other engineers dismissed her biological approach as a waste of time — until her "anatomically correct test-bed hand" became the industry's actual model, reshaping the field of prosthetic design.
Rather than stop at a working design, Matsuoka went back to MIT for a PhD in neuroscience specifically to understand the hand-brain connection at a deeper level, pursuing a prosthetic hand that could connect directly to the nervous system and genuinely feel, not just move. Her lab work extended into studying how people explore ambiguous objects by touch with their eyes closed, hunting for overlap between that physical exploration and abstract problem-solving more generally — and finding that the more a subject's brain treats a virtual-reality hand as genuinely part of the body, the more control they have over it.7
Greene diagnoses a specific failure mode Matsuoka's method exists to counter, naming it directly: technical lock. Learning any complex field requires immersion in its standard techniques and procedures — but that immersion, left unchecked, locks a mind into seeing every new problem through the same techniques, imprinted so deeply that the bigger picture — the actual purpose behind the work — quietly disappears from view. What's left is tunnel vision dressed up as expertise.8
Matsuoka's actual defense against technical lock wasn't more discipline within the existing engineering frame — it was deliberately operating one level above it, holding large governing questions (what makes the human hand work the way it does, how touch and thought connect) in constant view rather than letting the engineering details become an end in themselves.9 Held at that altitude, the smaller technical paths she needed to investigate multiplied rather than narrowed — a bigger question generates more useful sub-questions than a narrow one does, not fewer.
Greene's generalized prescription: connect whatever you're working on to something larger — an overarching question the immediate task serves — and return to that larger question specifically whenever the work starts to feel stale or overly fixated on technique for its own sake.
Worth being precise about what Greene means by a "higher level," since it's easy to mistake for simply thinking more abstractly or generally. Matsuoka's governing questions — what makes the hand dexterous, how touch and cognition connect — were not vaguer than the engineering details she was working on. They were more specific about purpose while staying agnostic about method. A vague question ("how can robotics help people") wouldn't have generated the palm-flexibility insight. A precise question about function, asked one level above the immediate technical habit, did.
You're deep in a technical problem and notice you keep reaching for the same handful of standard solutions regardless of what the specific problem actually needs. That's technical lock's signature. Step back and reconnect to the larger question your technique is supposed to be serving.
You're designing something and facing an apparent constraint everyone in your field treats as fixed. Ask, the way Matsuoka did with the rigid palm, whether the constraint is actually structural or just a byproduct of an unexamined default choice (motors in the palm because that's convenient, not because it's necessary).
You've mastered a field's standard techniques and colleagues are starting to treat your unconventional approach as a waste of time. Consider that dismissal itself as potentially informative rather than simply discouraging — Matsuoka's biological approach drew the same reaction before it became the industry standard.
Matsuoka's robotics career and her anatomically-driven hand design are documented, verifiable biography, and Greene's account is accurate on the major technical points.
Open question: Greene presents technical lock as avoidable through deliberately holding a "bigger question" in mind, but doesn't address how a practitioner without Matsuoka's unusually broad prior training (physics, biology, engineering, competitive athletics) identifies which bigger question is actually the right one to hold — the prescription may implicitly require a breadth of background the strategy itself doesn't supply.
This page converges closely with Occupy the Perfect Niche — The Darwinian Strategy, built earlier in the book from this same figure's path from tennis to neurobotics — that page documents how Matsuoka's wide-ranging early interests eventually converged on one niche; this page shows what she did once inside it, refusing to let the niche's standard techniques narrow her thinking the way they narrowed her engineering peers'.
Alter Your Perspective — technical lock is a field-specific instance of the Conventional Mind's general shorthand-seeking behavior described in that earlier strategy: expertise, in both cases, produces fast pattern-matching that's efficient precisely because it stops examining its own assumptions. The insight the pairing produces: technical lock isn't a special professional hazard unique to engineering — it's the general cognitive shorthand problem, showing up in a field where the stakes of getting stuck inside an unexamined frame (a permanently rigid prosthetic palm) are unusually visible and costly.
Weak Traits Are Self-Maintaining — this Laws of Human Nature page argues strengths decay without active practice while weaknesses need no maintenance to persist. Technical lock describes a related asymmetry: an engineer's technical strength (deep procedural fluency) actively degrades their weaker, less-practiced capacity for reframing a problem from first principles, simply through repeated use. The insight the pairing produces: expertise isn't neutral with respect to flexibility — the more a specific technical strength gets exercised, the more its shadow cost (rigidity in exactly that domain) compounds, unless something deliberately counteracts it.
Sharpest implication. If deep technical fluency and susceptibility to technical lock are the same asset viewed from two angles, then the most technically accomplished people in any field are, structurally, also the most at-risk for exactly the tunnel vision this page describes — meaning seniority and technical lock risk may correlate positively rather than an experienced practitioner being safely past the danger.
Generative questions.