Personal Productivity
The Problem Isn’t You. It’s Your System
AUTHOR: María Sáez
In 1982, General Motors closed its plant in Fremont, California. It was GM’s worst factory: absenteeism routinely exceeded 20%, there were more than 800 pending union complaints, and wildcat strikes were almost routine. The cars coming out of that plant were of the lowest quality in the system. Toyota reopened it two years later as NUMMI, rehiring almost all of the same workers, including the former strike leaders. It used the same machinery. It manufactured similar cars. And in less than a year, the plant went on to have the best quality in GM. Absenteeism dropped to 2%.
Nothing changed for the workers. Nothing changed for the machines. The only thing that changed was the management system: the processes, the roles, the protocols, the routines. The wiring.
The three layers of any production system
In their book Wiring the Winning Organization, Gene Kim and Steven J. Spear argue that in any organization, work takes place across three distinct layers:
- Layer 1 is the work itself: the technical product being created or modified. The code being written, the report being drafted, the client being served. It’s the “what.”
- Layer 2 consists of tools and infrastructure: the IDE, the compiler, a hospital scanner, kitchen knives. It’s the “how.” Culturally, mastering this layer is considered the sign of a good professional.
- Layer 3 is the wiring: the processes, protocols, standards, and routines that integrate individual efforts toward a common goal. It’s the least visible part, but the most critical. It defines who talks to whom, about what, when, in what format, and under what rules. It’s what set NUMMI apart from the old Fremont plant.
According to Kim and Spear, most organizations focus their efforts on layers 1 and 2 (hiring more talent, acquiring better tools) and ignore layer 3. And it’s layer 3 where the game is won or lost.
The individual also has three layers
This framework was originally designed for organizations, but its principles apply perfectly to personal organization as well. You, too, have three layers.
Your layer 1 is your work: the project you’re developing, the article you’re writing, the call you’re preparing for. Your layer 2 is your tools: your laptop, your apps, your task manager. And your layer 3 is your personal wiring:
The system of habits, routines, and protocols you use to process what comes into your life, decide what to do with it, and stay focused on what really matters.
Most people who feel overwhelmed try to fix the problem at the wrong levels. They work longer hours (level 1) or look for the ultimate app (level 2). But the problem almost always lies at level 3: not in the amount of work or the tools, but in the wiring that connects both of those to your goals.
GTD is a redesign of your Layer 3
Kim and Spear describe three mechanisms through which a well-organized system transforms organizations. All three have a direct counterpart in GTD.
- Slowification: shifting problem-solving away from the context of frenetic execution to slower, more controllable spaces (planning, reflection) where you can think without the pressure of the moment. In GTD, this mechanism has its own name: the Weekly Review. David Allen calls it “the critical success factor” of the entire system, and that’s no accident. It’s the act of pausing, stepping out of execution mode, and regaining perspective. Just as NUMMI would halt the production line at the first sign of a problem (rather than letting the defect spread), you halt your “line” once a week to review, reorganize, and ensure that the system continues to reflect reality.
- Simplification: breaking down large, complex problems into smaller, more manageable parts. The central mechanism here is clarification. When something enters your system, GTD forces you to ask a specific question: Is it actionable? And if so, what is the desired outcome? What is the next physical action? A vague commitment like “the trip thing” becomes “book the hotel in Rome by Thursday.” Vagueness is the main source of psychological resistance; clarifying is simplifying. The two-minute rule is the extreme case of this logic: if the action takes less time than the effort to log it, do it now.
- Amplification: making problems visible early on, before they become systemic. At NUMMI, this mechanism was the andon cord: any worker could stop the line upon detecting a defect. The equivalent in GTD is universal capture. When you have a trusted inbox where you jot down everything that demands your attention, without filtering, without deciding just yet, you’re making problems visible before they turn into crises. What isn’t captured keeps circling in your head, consuming cognitive resources in the background and popping up at the worst possible moment.
The result of all this is what Allen describes as a mind like water: a mind that responds to every situation with exactly the energy it requires, without the underlying tension of unacknowledged commitments or the anxiety of not knowing whether you’re doing the right thing. It’s not a state of passive relaxation; it’s a sign that your layer 3 is properly wired.
The app is not the system
Here it’s important to make a distinction that Kim and Spear’s framework illustrates particularly well. An app like FacileThings is layer 2: a tool. What sets a GTD framework apart from a simple task manager is that it’s not just a place to store things, but is built to support the infrastructure of layer 3. It integrates the workflow (capture, clarify, organize, review, engage) so that the tool and the system are both mutually reinforcing.
But the “cargo cult” trap is very real. Kim and Spear recount the case of two plants that installed identical andon cords: at one, no one pulled the cord, and the quality was terrible. Copying the visible practice without understanding the underlying principle doesn’t work. The same goes for GTD: having the app doesn’t mean you have the system. The system is the wiring that lives in your habits, in your Weekly Review, in the discipline of clarifying stuff rather than accumulating.
Conclusion
The lesson from NUMMI wasn’t that the workers were bad or the machines were inadequate. It was that the system connecting the two was broken. When Toyota changed that system, the same workers and the same machines produced radically different results.
If your productivity isn’t where you’d like it to be, ask yourself honestly where the problem lies. You probably don’t need to work harder or use a new app. You probably need to rethink your approach.
No comments