FIT: Fatigue, Interloper, Thrive

Most people experience technology change as a blur: a new gadget appears, a job changes, something feels harder or less secure, and we move on. My career in computing, which began in 1968, taught me to see these shifts as part of a repeatable pattern. I call that pattern FIT: Fatigue – Interloper – Thrive.

FIT is a simple way to understand how systems change—people, organizations, technologies, even our daily habits. It describes how something new crosses a boundary, exhausts what used to work, and forces us either to adapt or decline.

In this article, I’ll explain the FIT pattern, show how it appeared in real industrial transitions I lived through, and then broaden it to everyday life.

The FIT Pattern

FIT stands for:

·       Fatigue – The system is under strain. The old way still operates, but it is costly, brittle, or falling behind.

·       Interloper – Something crosses a boundary and takes over part of the system’s work: a technology, a process, a rule, a habit, even a person.

·       Thrive – The system either reorganizes around the interloper and becomes stronger, or fails to adapt and loses its ability to thrive.

The key move in FIT is the interloper. Interlopers are boundary‑crossers. They insert themselves where some group once had exclusive competence, control, or identity. The result is fatigue on the old side of the boundary and a chance—though not a guarantee—to reorganize and thrive in a new way.

Case 1: Wang and the Legal Secretaries

In the 1970s, law firms needed exact, flawless copies of contracts. That work belonged to highly skilled legal secretaries using IBM typewriters and carbon paper. Legal secretary was a professional occupation, with real expertise and predictable job security.

Then came dedicated word processors such as the Wang systems installed in many legal offices.

·       Fatigue – As firms demanded more documents, revisions, and speed, the traditional typing workflow became a bottleneck. The labor and time cost were high, and the market was pushing for more throughput and flexibility.

·       Interloper – The word processor entered the office as a “tool,” but it didn’t just assist the secretaries; it replaced the core skill: precise creation and duplication of contracts. The system, not the person, now held the authority over formatting, correction, and storage.

·       Thrive (or not) – The business thrived: faster documents, easier revisions, new possibilities. But the labor segment built around the old craft fatigued and, for many, failed to thrive. The interloper didn’t just help them; it hollowed out the economic value of their particular skill.

In FIT terms, the interloper was the replacement. The secretaries didn’t simply gain a new tool; the core of their work migrated into silicon.

Case 2: GM, Saturn, and Robotics

In the 1980s, General Motors faced fierce competition from Japanese automakers who offered reliable, high‑quality small cars. The traditional GM plants were struggling to match that quality and efficiency under existing processes and labor relations.

GM’s answer included the Saturn project: a new car line, a new plant, and a new manufacturing philosophy built around robotics and rethought labor agreements. In 1984, IBM hired me to work with GM research to help design the robotics data networks for this new environment.

Seen through FIT:

·       Fatigue – The existing plants and labor models were under pressure. Quality and productivity were lagging, and the global market was making that pain visible.

·       Interloper – Robotics and tightly integrated automated systems were introduced as the new core of production. They crossed into work that had long been the domain of line workers and traditional job classifications.

·       Thrive (contested) – The Saturn idea was to pair automation with new forms of cooperation and skill, so workers and machines together could thrive. The longer history is complicated, but the pattern is clear: robotics acted as an interloper into a protected domain of human work. Some roles were upgraded, many were displaced, and the system never fully stabilized in the “thrive” state that had been promised.

Again, the interloper was not a person but a system—a coordinated technology and process that claimed core productive functions.

Interloper Phenomena

These stories led me to what I call the Interloper Phenomenon: the recurring way an external system crosses into a human domain, exhausts the old pattern, and forces a choice between adaptation and decline.

In the Wang story, the interloper is word processing.
In the Saturn story, the interloper is robotics.

In both, the interloper:

·       Crossed a boundary (from “tool at the edge” to “center of production”).

·       Took over the core value‑producing activity.

·       Reshaped or erased existing skill‑based roles.

Once you see this structure, you can see FIT everywhere.

When FIT Enables Thriving

Not every interloper destroys a role. Many interlopers arrive as repair technicians of a sort: they fix fatigue and restore thrive.

Consider two common examples:

·       Doctors treating injuries
The interloper is the injury or disease—a disruption of the body’s normal homeostasis. The doctor’s job is to detect the interloper, manage the fatigue (pain, functional loss, risk), and help the patient’s system reorganize so they can thrive again. The interloper never stops existing as a possibility, but the person becomes more knowledgeable and sometimes more resilient.

·       Auto mechanics fixing brake problems
Here the interlopers are wear, heat, contamination, and misuse. Mechanics diagnose these interlopers, remove or mitigate them, and tune the braking system so the car can thrive—stop safely, predictably, and with less stress on components.

In these cases, technicians are specialists in FIT: they understand what “thrive” looks like, they know how fatigue shows up in their domain, and they are trained to spot and neutralize interlopers.

Research and Engineering as FIT Disciplines

The FIT pattern also illuminates how research and engineering behave.

·       Research often begins with a puzzle: Why is this system fatigued? What keeps it from thriving? Research hunts for hidden interlopers—viruses, misalignments, feedback loops, stressors—and documents how they operate. Good research enhances thrive by revealing the interlopers that cause or prevent fatigue.

·       Engineering usually begins with a use case: What do we want this system to do, reliably, under stress? Engineering anticipates interlopers (load, wear, noise, mistakes), designs how they will be handled, and tunes the system so it can maintain or regain thrive. A robust design assumes interlopers are inevitable and arranges for fatigue to be monitored and managed.

Seen this way, research maps the landscape of interlopers; engineering designs paths through that landscape that keep systems in a thriving region rather than a failing one.

Daily Life as FIT Practice

Most daily life skills are quiet FIT routines.

·       Time management: noticing task overload (fatigue), spotting the interlopers (distractions, unrealistic commitments), and restructuring your schedule to reclaim the ability to thrive.

·       Relationships: recognizing emotional fatigue, identifying interlopers (resentment, miscommunication, third‑party pressure), and practicing repair to restore trust and joy.

·       Health habits: detecting early signs of fatigue (sleep, mood, energy), identifying interlopers (diet, stress, inactivity), and making adjustments that restore vitality.

We typically call this “coping,” “maintenance,” or “self‑improvement,” but structurally it is the same FIT loop: detect interlopers, manage fatigue, cultivate thrive.

Why FIT Matters Now

We are living through a period of dense interlopers: AI systems, automation, platform economics, and social changes that repeatedly cross boundaries once guarded by human skills and institutions. The Wang and Saturn stories were early signals of something much larger.

The FIT model gives a language for asking sharper questions:

·       Where is fatigue showing up in this system?

·       What, exactly, is the interloper? A technology? A policy? A habit?

·       Who or what gets to thrive after the interloper arrives? Who doesn’t?

·       How can we design roles, tools, and institutions so that people, not just technologies, are able to thrive?

I developed FIT out of lived experience—the feeling of watching tools I helped build “hack” jobs and reorganize lives. It is not an abstract theory; it’s a way to make sense of the trade‑speak, shop‑floor stories, and personal histories that surround technological change.