It’s now been 5 months since I left the big corporate ‘world of KUKA’. I was a little bit more absent than I wanted to be here on Substack, so you might wonder: What’s she up to?

One thing that bothered me throughout my career is the money wasted because the people who actually KNOW the shop floor are not listened to. If you’ve been reading my articles here on The Unseen Obstacles, you know this is a drum I beat often. We’ve explored how “Innovators” design systems using explicit knowledge, completely ignoring the vital tacit knowledge of the “Stewards” who actually run the line.

Because of this disconnect, we all know the horror stories of robots sitting in boxes, robotic cells pushed into the corner, and pilot projects that never scaled. So I started to ask myself: WHY is that happening over and over?

While there are different reasons, you can find one big common theme: Underestimating THE HUMAN SIDE OF AUTOMATION.

Black & Decker had to close a whole plant in 2023 because of it—after investing $90 million in automation. And no, I’m not talking about better HMI design or easier-to-program robots. While those improvements are undeniably important, they don’t solve the underlying problem.

We design perfect systems on sterile engineering whiteboards using a framework of “Work-as-Imagined,” but drop them onto a chaotic, messy shop-floor reality where “Work-as-Done” takes over. And then we wonder why veteran operators resist using them. We buy the machines, but we completely forget to build the “Social Operating System” required to actually run them.

Bridging that gap between technological enthusiasm and the gritty reality of the shop floor is exactly what I am doing next. I am focused on being REALISTIC about automation without discarding its importance—hence why I’m calling myself the “Automation Realist.”

Let’s do a Reality Check

Want to get a first impression of what ‘being realistic’ about automation actually looks like?

On June 4th, I’m hosting my first live session: the Automation Reality Check webinar. It’s a free, 45-minute interactive session where we will look past the ROI spreadsheets and figure out how to actually escape “pilot purgatory.”

If you are evaluating a major robotics proposal, trying to get one adopted on the floor, or just curious to learn more about the human side of automation, I’d love for you to join the conversation.

Click here to register for the Automation Reality Check

I’m excited to be back, and I’ll see you on June 4th.

— Denise

The semi-truck pulls up to the loading dock at 7:00 AM.

The guys on the floor stop what they’re doing. They watch as the forklift maneuvers a massive, plastic-wrapped crate onto the concrete. It’s a multi-million dollar robotic cell—shiny, high-tech, and “efficient.” The VP of Operations stands there with a clipboard and a smile that says, “I just saved us 20% on labor.”

But the guys in the stained Carhartt’s? They’re looking at it like a meteor just crashed into their living room.

The implicit message from the front office is simple: “Here it is. Figure out how to live with it.” It’s a feeling of pure inevitability. We’ve been taught to view technological progress as a force of nature, like a thunderstorm. You can’t stop it; you can only buy an umbrella and hope for the best.

In reality, we aren’t passive recipients of “progress.” We’re just victims of bad timing. A lot of manufacturers fail to scale their automation beyond the initial pilot phase.

Why? Because we keep trying to fix the machine after it’s already bolted to the floor.

The “Too Late” Problem

In the world of big-ticket tech, there’s a trap called the Collingridge Dilemma. Don’t let the academic name fool you; it’s basically just the “Bad Tattoo Rule.”

When a new technology is just a drawing on a whiteboard, it’s easy to change. But because it’s not built yet, we don’t really know how it will screw up our lives. By the time the machine is delivered and the software is locked, we finally see the problems. But by then, the technology is so entrenched that change is nearly impossible.

We are “locked in.”

Think of it like building a house and forgetting to put in a bathroom. You only realize it’s a problem once you move in. By then, tearing out the walls to fix it costs more than the house is worth. You’re stuck using a bucket in the backyard.

We wait until the “finished” machine arrives to train the workers—the people I call the Stewards. But waiting until the machine is finished means the technology is already locked in. We expect the humans to adapt to the machine’s requirements. We should be designing the machine to adapt to them.

The Gap Between “Imagined” and “Done”

Most automation is designed by people sitting in quiet offices using a framework called Work-as-Imagined. This is the perfect, clean version of the job that exists in manuals and slideshows.

But on the floor, we have Work-as-Done. This is the actual physical activity, full of trade-offs, heat, noise, and equipment malfunctions. Research in high-risk industries reveals a startling gap: many of the steps required to do a task involve a discrepancy between how the boss thinks it’s done and how it actually gets done.

Operators use “shadow work”—informal workarounds and “tricks”—to keep the line running when formal procedures fail. When we buy automation that only follows the “official” rules, we “lock in” a system that removes the worker’s ability to perform these essential workarounds.

When the machine gets confused because the real world isn’t perfect, it stops. And because we didn’t include the operator in the design, they can’t help it. They become “Machine Janitors” instead of “Pilots”.

Subscribe now

The Machine is Never Actually Finished

A robot, by itself, is useless. It is an unfinished artifact. It is intrinsically incomplete until a human hand touches the controls and adds their “tacit knowledge”—the unwritten expertise developed over years of practice.

There is an “Irony of Automation” here: the more reliable an automated system becomes, the more crucial the human operator becomes for managing the rare, high-stakes failures the system can’t diagnose itself.

If we don’t capture this “tribal knowledge” before our most experienced workers retire in the upcoming “silver wave,” we lose the very thing that makes the automation work. We end up with expensive systems that no one knows how to truly “tame” when things go sideways.

The Upstream Revolution

To fix this, we have to move the decision-making Upstream. We have to bring the operators—the people who know where the grease hits the floor—into the room before the first line of code is written.

This isn’t just about “consulting” them; it’s about Co-Creation. It’s about bringing the worker’s knowledge and values into the earliest stages of R&D. When we unite the front office and the shop floor around a shared mission, we stop buying “stuff” and start solving problems.

To help you start this process, I’ve developed the “Upstream” Automation Audit. It’s a simple diagnostic tool meant to be used by a manager, an engineer, and an operator sitting in the same room. It forces you to get honest about whether your goals are clear, if you’ve actually mapped how the work is done, and if you’re building a system that your own team can maintain.

If you can’t get a “Yes” from all three people on these points, you have an unseen obstacle that needs your attention before you bolt another machine to the floor.

Organiksol Upstream Automation Audit

395KB ∙ PDF file

Download

A collaborative diagnostic tool for managers, engineers, and operators. Use this 5-point checklist to identify "Unseen Obstacles" and ensure your technology serves your people—not the other way around.

Download

Automation shouldn’t feel like an invasion. It should feel like getting a better pair of boots—something that supports you, fits your stride, and makes the long day a little easier to manage. The revolution isn’t about the robots; it’s about who gets to hold the pen when the robots are being imagined.

Let’s Bridge the Gap

Building a human-centric organization isn’t something you have to do in a vacuum. At Organiksol, we specialize in the “mechanics” of this transition—providing the Industry 5.0 roadmaps and workshops needed to transform your employees from passive operators into active fans and co-creators.

If you’re ready to stop being a “firefighter” and start being the architect of a resilient system, I’d love to have a conversation about how we can support your team’s next move

Explore Organiksol's Changemaker's Hub

I started my career as a car mechanic. In a garage, you learn the difference between two types of “hard” very quickly.

There is the “hard” of a rusted, seized-up bolt that won’t budge. That’s friction. It’s draining, it doesn’t require skill, and it’s basically just a traffic jam for your productivity. Then there is the “hard” of perfectly timing a torque wrench or feeling a part click into place. That’s effort. That second kind of hard is why people actually like working with their hands. It’s the “bite” of the job.

When I moved into business development for industrial robotics, I noticed a common theme in planning meetings and strategy sessions. The goal was almost always “frictionless.” We wanted to automate every step, remove every hurdle, and make the job so easy that anyone—or anything—could do it.

But there’s a massive problem with that strategy. When you remove all the friction, you don’t get a perfect worker. You get a bored one. And if you want a team that is actually “in the zone,” you don’t design for the least amount of effort. You design for Flow.

The Sweet Spot of Flow

“Flow” is that mental state where you’re so deep in the zone that time disappears. You aren’t thinking about your mortgage; you’re just doing. Most people think Flow happens when a task is easy. It’s actually the opposite.

Flow is like riding a bike. If you’re coasting down a hill with a tailwind, you aren’t in Flow. You’re just a passenger. You only hit Flow when you’re on a slight incline—where the resistance of the road meets the strength of your legs in a perfect 1:1 match.

In other words, Flow requires a certain amount of resistance. If there’s no “effort” required, the brain checks out.

Subscribe now

The Woodshop Lesson: Why “Easy” Kills Engagement

A few years ago, a study looked at this exact dynamic in a wood workshop. Researchers had people drill holes into wood while collaborating with a lightweight robot.

In the first group—the “High Automation“ group—the robot did almost everything. It moved the drill into position and handled the pressure. The human was basically just a supervisor. On paper, this was the “perfect” system. It was fast and error-free.

In the second group—the “Medium Automation“ group—the robot only supported the weight of the drill. The human had to guide the drill to the exact spot and decide when to push.

The results were a wake-up call. The people in the “High” group—the ones with the “easy” job—lost their sense of being the “boss” of the work. But the people in the “Medium” group hit a much higher state of Flow. Because they had to provide the “fine-tuning” effort, they felt like the tool was an extension of their own body.

But the most telling part was a physical measurement: Grip force. The researchers found that when the robot took over too much, the workers physically loosened their grip on the tool. Their hands went limp because their brains had stopped caring. They weren’t “in the zone” anymore; they were just waiting for the bell to ring.

The Missing Seat at the Table

This is where automation projects usually go off the rails. It isn’t just a “top-floor” problem; it happens in engineering bays and project management offices where people design tools without actually asking the shop floor how the work “feels.”

If you want an optimal result, the worker cannot be treated as just the “end-user.” They have to be a co-creator.

Think about a professional chef. If you want to design a better knife, you don’t just hand them a finished product. You sit them down during the planning phase. You ask them where the balance point should be. You ask them how the handle should feel when their hands are wet or greasy.

The person doing the work is the only one who knows where the “good friction” lives. The same applies to a factory floor or a small business. The worker knows which parts of the job are “rusted bolts” (Bad Friction) and which parts are “the bite of the tool” (Good Effort).

When you give the worker a seat at the table, you ensure technical accuracy. An engineer might see a “manual alignment” step as a waste of time. The worker knows that the alignment step is where they catch the 1% of defects that a robot would miss. By including them as a co-creator, you ensure you are removing the friction—not the expertise.

Share

Building “With,” Not “For”

To get the best shot at an optimal result, we have to change the strategy. We need to stop designing automation for people and start building it with them.

When the worker is a co-creator, the technology becomes a “power-up” rather than a replacement. It’s the difference between being a passenger in a self-driving car and being a pilot in a high-performance jet. One is a chore; the other is a craft.

If you take the “win” away from the worker by making the task effortless, they will stop giving you their best. They will loosen their grip. But if you build a tool that supports their weight while letting them lead the dance, you get a level of precision and engagement that no “High Automation” system can match.

The Audit: How to Start

If you’re looking at a new process or tool, ask these three questions:

1. Who helped design this? Was it just people in offices, or did the people who will actually hold the tool have a say in how it works?

2. Does it remove the “Bite”? Are you removing the skilled part of the job that gives the worker a sense of control?

3. Is the worker a co-creator? Are there parts of the system the worker can influence based on their expertise, or is it a “black box” they can’t touch?

   Subscribe now

The Bottom Line

The goal shouldn’t be to make work easy. It should be to make work meaningful.

Remove the rusted bolts. Kill the bad interfaces. Delete the pointless steps. But keep the fight. Keep the challenge. And make sure the person doing the work is helping you decide which is which.

Don’t just automate. Collaborate. That’s how you find the Flow.

Explore Organiksol Changemaker's Hub

I spent three years as a car mechanic apprentice, leaning over fenders and fighting rusted bolts. I spent the next twenty-five years in the world of industrial automation. I’ve lived on both sides of the glass—the hot, loud reality of the floor and the quiet, climate-controlled world of strategy.

In those decades, I’ve seen one myth cause more expensive failures than a snapped drive belt: the idea that the person who designs a system is naturally more “knowledgeable” than the person who runs it.

We call the designer the “Innovator.” We call the person on the floor the “Steward.” In many companies, there’s an unspoken ladder where the Innovator sits at the top, handing down instructions like they’re the only ones who understand the logic. We assume that because someone can model a robotic cell in CAD software, they understand how that cell will behave on a humid Tuesday in a Detroit plant when the power fluctuates and the lubricant is running thin.

This is the Cookbook Fallacy. You can read a recipe for Beef Wellington a hundred times (explicit knowledge), but that doesn’t mean you know how the meat feels when it’s perfectly seared (tacit wisdom). My three years in the grease were my foundation. Without them, the next twenty-five years of automation strategy would have been built on sand.

The Hard Truth: Data is “Noise,” Wisdom is “Nuance”

Automation projects don’t usually fail because the engineering is bad. They fail because of a clash between two types of knowledge.

The Innovator relies on Explicit Knowledge. This is the stuff you can put in a spreadsheet: cycle times, motor torque, and ROI projections. It’s clean. It’s logical. It’s also incomplete.

The Steward—the person who has worked that line for a decade—possesses Tacit Knowledge. This is “wisdom in the hands.” It’s the “muscle memory” that knows a machine is about to blow a seal because the hum sounds a half-octave too high. You can’t download that into a training manual.

When we ignore the Steward, we fall into the ROI Trap. We build a “perfect” system on paper that is incredibly brittle in the real world. It’s like a bad marriage where one person decides how the house will be run without ever asking the other person if they prefer the thermostat at 68 or 72. It looks good on the “to-do” list, but the friction will eventually burn the whole thing down.

The Method: Anthropology, Not Just Engineering

If you want to build automation that actually sticks, you have to flip the script. We need Mentorship in Reverse. This means the Innovator—the person with the title and the software—needs to become an apprentice to the Steward.

In the trade, we call this a “Go-and-See.” But don’t just go and stand there with a clipboard like a narc. You need to perform Sensory Mapping. You have to ask questions that aren’t in the technical specs:

• “What are you feeling for when you seat that part?”

• “What sound tells you the machine is struggling?”

• “What’s the one ‘workaround’ you have to do every hour just to keep this thing running?”

This isn’t just about being “nice”; it’s functional requirements gathering. You are translating invisible human intuition into the logic of the machine. If you don’t capture the “nuance” of the human, your machine will only ever be “noise.”

Subscribe now

The Mindset: Check Your Ego at the Time-Clock

The biggest obstacle to this isn’t technology—it’s ego.

Too many people in professional roles have a “Power Over” mindset. They think their value is tied to having all the answers. If they admit they don’t know why a specific sensor keeps tripping, they feel like they’re losing their professional edge.

That’s a trap. Real innovation is Humble Inquiry. It’s entering a conversation with curiosity rather than a lecture. It’s being more interested in being right (finding the truth) than being validated (being the smartest person in the room). You have to detach from your “perfect” plan and engage in a collective search for what actually works on the floor.

When you do this, the dynamic shifts from “Buy-In” to Co-Creation.

“Buy-In” is a sales pitch. It’s what you ask for when the project is already finished and you’re trying to convince the workers not to hate it. Co-Creation is building the solution together from the start. When a Steward sees their own “gut feeling” built into the logic of a robot, they don’t see a threat—they see a partner.

The Audit: Are You Actually Listening?

If you are a designer, a consultant, or a project lead, take a look in the mirror. Use this checklist as a guide for your next project:

• The Proximity Test: Have your designers spent meaningful time watching or performing the job they are “optimizing”? Try to focus on the flow of the work before reaching for the notepad.

• The Language Check: Are you using big words to hide the fact that you don’t understand the floor reality? If you can’t explain the “why” to a smart twelve-year-old, you don’t understand it yet.

• The Source vs. Resource Rule: Do you view your workers as “resources” (units of labor to be managed) or “sources” (the primary source of wisdom for the system)?

Share

The Bottom Line

We need to stop treating the shop floor like a laboratory and start treating it like a classroom. The machine should handle the “noise”—the repetitive, data-heavy, soul-crushing tasks—so the human can focus on the “nuance”—the judgment and creativity that no algorithm can touch.

That symbiosis only happens when we respect the wisdom in the grease as much as the logic in the code.

The Challenge: At the start of your next project, pause the design meetings. Send your lead innovator to the floor for a shift. No laptops, no agendas—just eyes, ears, and a humble heart.

Let’s see what they learn when they finally shut up and listen.

Explore Organiksol's Changemaker's Hub

In the industrial world, a “resource” is something you use up.

Oil is a resource. You burn it to create energy. A drill bit is a resource. You use it until it dulls, and then you throw it in the scrap bin. It is a finite asset with a depreciable value.

For over a century, our economic models have applied this same logic to people. We created departments dedicated to “Human Resources.” We calculated “labor costs” on the same ledger as “material costs.” We built systems designed to extract maximum output from a human unit until that unit was depleted or replaced by a cheaper one.

But in the transition to Industry 5.0, this model isn’t just morally wrong; it is operationally obsolete.

The foundational error of the modern factory is the belief that a human being is a battery to be drained. A necessary Ethical Framework of Industry 5.0 has to propose a radical correction: A human is not a resource; they are a Source. People are seen as having latent energies and capacities that are infinite, not finite.

If you want to build a resilient organization, you have to stop managing resources and start releasing potential.

Subscribe now

The “Amoral” Trap of Efficiency

We like to pretend that business and technology are morally neutral—that they are just math. We tell ourselves that an ROI spreadsheet has no ethics.

But technology is not neutral; it is a reflection of the values of the people who design it.

When we design a factory line that requires a human to move like a robot for eight hours a day, we are making a moral statement. We are saying that the speed of the part is more important than the well-being and happiness of all people. We are saying that the purpose of economic life is merely the generation of material wealth, rather than a contribution to the betterment of the world.

This approach worked (arguably) when we only needed hands to pull levers. But today, in the complexity of modern manufacturing, we need minds. We need judgment, creativity, and wisdom.

You cannot extract wisdom from a person you are treating like a spare part.

The Hard Value of “Soft” Virtues

This is where the conversation usually gets uncomfortable for traditional managers. We have to talk about virtues.

In the boardroom, words like truthfulness, trustworthiness, and sincerity are often dismissed as “soft skills” or “nice-to-haves.” We view them as personal traits, irrelevant to the hard mechanics of production.

But a holistic Industry 5.0 framework needs to reframes these qualities and see them as a prerequisite for all to progress.

Think about the “Silence” we discussed in previous articles. Why do projects fail? Because someone wasn’t honest about a delay. Why do supply chains break? Because a vendor wasn’t trustworthy.

These aren’t “soft” problems. They are structural failures caused by a lack of ethical infrastructure. A system without truthfulness is a system without accurate data. A system without trustworthiness is a system with high friction. In this light, ethical conduct isn’t just about being “good”; it is about operational viability.

The Mechanism of Change: From “Power Over” to “True Consultation”

So, how do we operationalize this shift? We cannot just put up a poster that says “Be Virtuous.” We have to change the mechanics of how we make decisions.

In a “Resource” mindset (Power Over), the boss thinks and the worker acts. Dissent is seen as resistance.

In a “Source” mindset (Power With), we engage in True Consultation.

This is more than just a brainstorming session or a polite request for feedback. In a holistic Ethical Framework, True Consultation is a collective investigation of reality. It requires a rigorous discipline where participants must:

1. Detach from their own opinions: You are not there to win the argument; you are there to find the truth.

2. Weigh views without attachment: A technician’s view on a machine is weighed equally with an engineer’s view, input has to be based on its merit, not the rank of the speaker.

3. Unite behind the decision: Once a decision is made, the team supports it fully, even if they initially disagreed.

This process produces decisions that are robust, unified, and grounded in reality. It is an operating expression of justice in human affairs.

Technology as a Human Right

Finally, we must rethink who owns the future.

For too long, scientific and technological activity has been decided only by a fractional segment of the population. We have allowed a tiny elite of engineers and executives to dictate how technology is used, often creating tools that serve the market but harm the worker and society at a large.

Industry 5.0 challenges us to rethink and reorganize this. It argues that knowledge is a human right.

This means we must stop designing “black box” automation that alienates the worker. We must design transparent, explainable systems that invite the operator to participate in the generation and application of knowledge. When a worker understands the machine—and helps improve it—they are no longer a cog in the wheel. They are a protagonist in the story.

The Shift

We are living through a time of global turmoil, a time of transition where humanity is struggling to come of age. The old models of “growth at all costs” and “extreme riches alongside extreme poverty” are breaking down.

The leaders of the future will not be the ones who extract the most value from their people. They will be the ones who generate the most value through their people.

They will realize that wealth is not an end in itself, but a tool that must serve humanity as a whole. They will understand that you cannot have a healthy economy on a sick planet, and that our industrial systems must respect the cultivation of the earth as a sacred duty as it’s a prerequisite for a peaceful, resilient and livable world.

Next time you look at your org chart, try a mental shift.

Stop seeing “Human Resources” (a cost to be minimized).

Start seeing “Human Sources” (a potential to be developed).

When you recognize that every person on your floor has potential talents waiting to be developed, you stop trying to control them and start asking them: “What can you see that I can’t?”

That is the moment the “Unseen Obstacle” disappears. That is the moment the organization comes alive.

Explore Organiksol's Changemaker's Hub

Recommended Readings

If you missed last week’s deep dive into why “Smart Factories” are failing financially

Audit your own leadership style—are you practicing “Power Over” or “Power With”?

Learn how to create the “True Consultation” environment where truthfulness can thrive.

If you look at the balance sheets of many manufacturers today, you will find a troubling paradox. Over the last decade, capital investment in automation—robots, sensors, digital twins—has skyrocketed. We have built the “Smart Factories” we were promised. Yet, operational productivity in many sectors remains stagnant, and labor costs continue to rise.

We bought the hardware. We installed the software. Why aren’t we seeing the returns?

The answer does not lie in the code; it lies in the culture. We have spent billions optimizing the “Technical Subsystem” of our organizations while allowing the “Social Subsystem” to decay. We have built systems that are technologically advanced but psychologically fragile.

To fix this, leaders must stop viewing Industry 5.0 as a “soft” ethical add-on and start treating it as a hard strategic necessity. We need to apply a rigorous Problem-Solution Framework to identify where our current industrial model is failing and how a human-centric approach provides the pragmatic remedy.

The Problem: The High Cost of Silence

The most dangerous byproduct of the Industry 4.0 era was not job displacement; it was the systemic disengagement of the workforce.

In our drive for efficiency, many organizations inadvertently created a culture characterized by a self-defeating cycle: the “punishment of the innocent” and the “rewards for the uninvolved.”.

When a complex automation project fails or a timeline slips, the traditional management reflex is to find a specific person to blame—often the most visible person rather than the one truly responsible. This teaches employees a rational, survivalist lesson: remain silent and uninvolved to avoid blame.

This culture of silence is not a neutral act; it is an active contributor to organizational decline. The data on this is stark. Research indicates that when known problems go undiscussed due to fear:

• 86% of projects miss their deadlines.

• 78% exceed their budgets.

• 54% of the time, the morale of the team is permanently damaged.

Silence is the sound of capital evaporating. You cannot build a resilient supply chain on a foundation of frightened people.

The Solution: An Architecture of Empowerment

The remedy to this dysfunction is not more training or better incentives. It is a fundamental shift in the power dynamic of the organization—from “Power Over” (control, hierarchy, compliance) to “Power With” (shared capacity, collaboration, commitment).

This is one of the key elements of the Industry 5.0 Solution. It proposes that the only way to break the cycle of silence is to build an architecture of empowerment based on consultative decision-making.

This is not a philosophical preference; it is a strategic imperative for building high-autonomy organizations.

How to Execute the Shift

Leaders must replace the metric of “compliance” with the metric of “agency.” A successful system is one that workers want to use because it genuinely improves their work-life. To achieve this, we must change the fundamental question we ask our teams.

Instead of asking, “How do we get you to use this machine?”, we must ask: “What does a ‘good day’ look like for you in this role? And how can this technology help create more of those days?”.

When you anchor technology to human well-being, you transform the worker from a passive user into an active partner.

The Problem: Technological Alienation and the Skills Gap

The second major deficiency of the current model is the widening gap between human capability and machine complexity.

A purely technology-centric approach—one that seeks only to replace human labor—creates a critical operational bottleneck. It generates a workforce that suffers from “technological alienation.” Workers face a lack of trust in automated systems, anxiety about physical safety in shared workspaces, and a fear of displacement.

We are seeing a trade-off where physical injuries may decrease with automation, but “mentally unhealthy days” reported by workers are increasing. We have traded backaches for headaches, creating a workforce that is physically safe but cognitively overloaded.

The Solution: Collaborative Technology (Augmentation)

Industry 5.0 offers a distinct solution: Augmentation over Substitution.

The goal of technologies like collaborative robots (cobots) is not to replace the worker but to create a synergistic system. We must combine the accuracy and repeatability of the robot with the dexterity, critical thinking, and “tacit knowledge” of the human.

How to Execute the Shift

This requires treating workforce development not as a one-time cost, but as a core organizational capability. We must adopt a culture of “continual learning,” where the capacity to learn and adapt is valued as highly as the ability to produce.

Practical application means moving away from “Black Box” automation—where the machine is opaque and controlling—toward transparent, explainable systems where the human remains the pilot. When a worker understands why a machine makes a decision, trust is established. When trust is established, efficiency follows.

The Leadership Imperative: From Smart to Wise

The transition from Industry 4.0 to Industry 5.0 is not a software upgrade. It is a maturity test for leadership.

We are moving from an era where we measured success by the speed of the part to an era where we must measure the health of the system. The leaders who win in the next decade will not be the ones who buy the most robots. They will be the ones who understand that a factory is a socio-technical ecosystem.

They will realize that economic efficiency and human flourishing are not opposing goals. They are inextricably linked. You cannot have one without the other.

To survive the volatility of the modern market, we must stop trying to engineer humans out of the loop and start designing the loop around the human. It is time to stop building “smart” factories and start building wise ones.

Explore Organiksol's Changemaker's Hub

Related Article

In case you’re now asking yourself ‘How do I measure this if not by efficiency?’ you might be interested in reading

In case you’re now asking yourself ‘Am I running a Smart Factory or a Wise one?’ you might be interested in reading

In case you’re now asking yourself ‘How do I break the silence?’ you might be interested in reading

It’s 2:00 PM on a Tuesday.

On a factory floor somewhere in Michigan, an operator ignores a warning light on his console.

He doesn’t ignore it because he’s lazy. He ignores it because he is tired. He ignores it because the last time he pointed out a glitch, his manager told him to “stop slowing down the line.” He ignores it because the interface is confusing, the font is too small, and his brain is fried from six hours of “monitoring” a machine that does the work for him.

He clears the error. The line keeps moving.

In the old way of thinking (Industry 4.0), this is a “personnel issue.” You write him up. Maybe you retrain him.

But in the new reality (Industry 5.0), this isn’t an isolated mistake. It is a structural crack in the foundation of the global economy.

That single moment of “cognitive fatigue” travels upwards. It becomes a batch of defective parts. That batch becomes a recall. That recall becomes a supply chain bottleneck. And that bottleneck contributes to the fragility of an entire industry.

We often treat “worker burnout” as an HR problem and “supply chain failure” as a logistics problem.

They are the same problem. You cannot have a resilient supply chain if you have fragile people.

Here is how the stress on the factory floor ripples out to break the world—and how we can fix it.

Level 1: The Individual
(Trading Backaches for Headaches)

For a hundred years, we designed factories to save the human body. We invented hoists, conveyors, and eventually, robots to do the heavy lifting.

We succeeded. But we replaced one pain with another.

Recent data reveals a disturbing trade-off: While the introduction of industrial robots significantly reduces physical injuries, it is correlated with an increase in “mentally unhealthy days” for workers.

We traded backaches for headaches.

We fixed the physical load, but we ignored the Cognitive Load. We put humans in environments where they have to supervise complex, opaque machines without having any real control.

When a worker feels like a “passive observer” rather than an active participant, their brain rebels. Research in neuroscience suggests that intrinsic motivation—the drive to do good work—isn’t just a “nice to have.” It is connected to the neural machinery that regulates our biological drive to stay alive.

When we design systems that bore, confuse, or silence workers, we aren’t just making them unhappy. We are shutting down their biological capacity to care.

Level 2: The Organization
(The Quiet Crisis)

Zoom out to the company level. Right now, small manufacturers are in a vice grip.

Take the Small Manufacturing and Assembly Businesses (SMABs) here in Michigan. They are facing a brutal reality: labor costs are rising (up 3.7%), but productivity is flat (up only 0.3%).

The instinctive reaction is to buy more robots. “If people are expensive and slow,” the logic goes, “let’s automate them.”

But this fails because of the Culture of Silence.

When an organization runs on fear—what I call “Power Over” leadership—employees learn a rational lesson: keep your head down. If you point out a flaw, you get blamed.

This silence is expensive. Research shows that when known problems go undiscussed, 78% of projects exceed their budgets and 54% damage team morale.

A factory filled with silent, scared employees is not efficient. It is a ticking time bomb. The companies that will survive aren’t the ones with the most robots; they are the ones with the most Psychological Safety. They are the ones where a worker can say, “This isn’t working,” without fear.

Level 3: The Society
(The Broken Ladder)

Now, zoom out one last time. Look at the country.

For decades, manufacturing was the engine of the American Dream. It was the ladder to the middle class.

That ladder is losing its rungs. Absolute income mobility has fallen starkly. In 1940, 92% of children grew up to earn more than their parents. For children born in 1984, that number dropped to 50%.

This is where the “technical” becomes “societal.”

If we use automation only to replace human skill (de-skilling), we remove the last remaining pathways for economic advancement. We create a permanent underclass of “button pushers” and a tiny elite of engineers.

But if we use automation to augment human skill (Industry 5.0), we create “Super-Operators.” We use the robot to take the drudgery, allowing the human to become a problem-solver, a strategist, and a craftsman.

This isn’t just about factory efficiency. It’s about civilizational stability.

The Crown of Maturity

We are living through a time of global turmoil. It feels chaotic. But I believe this turmoil is actually the “fits and starts” of humanity coming of age.

We are moving from an era of “growth at all costs” to an era of maturity.

Industry 5.0 is simply the industrial expression of that maturity. It is the realization that a system is only as strong as its smallest part.

If you are a leader, you might feel helpless watching the global news. You can’t fix the stock market. You can’t fix geopolitics.

But you can fix Tuesday at 2:00 PM.

You can walk out to the floor, find that operator, and ask: “What is the most frustrating thing about this machine?”

And then—this is the most important part—you can fix it.

That small act of listening repairs the trust. It lowers the cognitive load. It prevents the error. It saves the batch.

It is a small flap of a butterfly’s wing. But it is the only way to fix the storm.

Visit Organiksol's Changemaker's Hub

Related posts

We’ve all been there. You buy a fancy new gadget—maybe a smart home device or a high-end coffee maker—promising to make your life easier. But a week later, you’re shouting at it because it won’t connect to the Wi-Fi.

Now, imagine that frustration on a factory scale.

Companies are currently pouring billions into the “Technical Subsystem” of Industry 5.0. They are buying collaborative robots (cobots), installing Digital Twins, and deploying Generative AI models. The assumption is linear: Better Hardware = Higher Efficiency.

But the data tells a different story. Automation projects frequently stall, data lakes turn into data swamps, and expensive robots sit unused in corners.

Why? Because we bought the hardware, but we forgot to install the Operating System.

In every organization, there is an invisible layer of code that dictates how work actually gets done. It isn’t written in Python or C++; it is written in trust, culture, and cognitive design. In academic terms, this is the “Social Subsystem” . I call it the Social Operating System.

If you try to run Industry 5.0 hardware on an Industry 2.0 social operating system (one based on fear and control), the system will crash.

If you aren’t sure which one you have, check my Leadership Checklist from last week:

To fix this, we need to stop designing just the machine, and start designing the relationship.

The “Hardware” of the Human Mind: Cognitive Ergonomics

In traditional manufacturing, we are obsessed with physical limits. We know exactly how many Newtons of force a robotic arm can lift before it fails. We know the thermal limits of a server rack.

But we rarely measure the “Cognitive Load” of the human operator standing next to them.

In Industry 5.0, the goal is not to “dumb down” the work. It is the exact opposite. We want to clear away the mental clutter so the human mind can do what it does best: solve complex problems.

When a worker is forced to constantly translate abstract data from a screen into physical actions, they experience “high cognitive friction.” This isn’t deep thinking; it’s just mental noise. And when the noise gets too loud, safety drops and quality suffers.

The “Operator 5.0” Solution
The goal is to create what researchers call the “Operator 5.0”—a worker who is not replaced by automation but is made “self-resilient” through it. This requires designing systems that induce a state of “Flow”—where the technology removes the friction, allowing the worker to be completely immersed in the craft of their work.

Case Study: The “Zero-Error” Hangar at Lockheed Martin
Consider the assembly of the Orion spacecraft at Lockheed Martin. This is an environment with zero margin for error. Traditionally, technicians had to interpret thousands of pages of complex, 2D technical drawings to build a 3D spacecraft .

This process was a massive tax on human attention. Technicians had to constantly shift focus from the hardware to the paperwork, breaking their “flow” hundreds of times a day.

Lockheed didn’t solve this by hiring faster workers. They solved it by fixing the socio-technical interface. Using Microsoft HoloLens 2 headsets, they overlaid holographic instructions directly onto the physical spacecraft .

• The Shift: The technology didn’t replace the human mind; it liberated it. The headset handled the “minutia” of data retrieval, allowing the human to focus entirely on the tactile quality of the installation .

• The Result: Tasks that previously took 8 hours were completed in just 45 minutes.

• The Metric that Matters: The new system achieved a zero-error rate.

This proves a fundamental law of Industry 5.0: When you remove the cognitive drudgery, you unlock the cognitive potential.

The Architecture of Trust: Extended Virtual Control

If you ask an engineer about “trust,” they might roll their eyes. But in your Social Operating System, trust is a hard constraint.

In a human-machine system, trust functions as “Extended Virtual Control”.

Think of it this way:

• Low Trust: If you don’t trust the machine, you micromanage it. You watch every move. You gain zero efficiency.

• High Trust: If you trust the machine, you relax. You let it handle the volume while you focus on the strategy.

But trust doesn’t appear by magic. It is built through Control. Humans only trust automation when they know they are still the ultimate authority .

Case Study: Symbiosis at Siemens At the Siemens Electronics Works in Amberg, the challenge was quality control. The plant produces 17 million components annually, creating a massive bottleneck at the x-ray inspection station.

Siemens installed an AI model to predict defects. But crucially, they designed the system to be collaborative, not substitutive.

The AI acts as a filter. It handles the clear-cut data, but it flags “suspicious” or ambiguous cases and hands them over to a human expert for the final decision.

• The Outcome: The system reduced x-ray volume by 30%.

• The Lesson: The human operators trust the AI because the AI knows its place. It handles the noise (the data), but it defers to the human for the nuance (the judgment).

Redefining “Collaboration”

When we talk about human-robot interaction, we often rely on a spatial spectrum :

• Coexistence: The robot is fenced off; the human is safe outside.

• Cooperation: They work sequentially (handoffs).

• Collaboration: They work simultaneously in shared space.

There is a common misconception that moving to “Level 3” (removing the fence) is always the goal. It isn’t. In many cases—dealing with toxic materials, heavy payloads, or extreme speeds—Coexistence is the most human-centric choice because it prioritizes safety.

Human-Centric is the first pillar we discussed in Industry 5.0 Demystified:

But this reveals a deeper truth: Collaboration is not defined by proximity; it is defined by agency.

You can take down the physical cage, but if the operator feels forced to work with a machine they don’t understand or want, you haven’t created a partner; you’ve created a nuisance.

True collaboration starts long before the robot hits the factory floor. It begins with Participatory Design . It means actively involving workers—from operators to maintenance staff—in the decision of which problems to automate.

If you bring a robot into a factory without asking the person who will stand next to it, you haven’t collaborated. You’ve just installed an obstacle.

Subscribe now

The Takeaway: Audit the Connection, Not Just the Code

If you are looking at a piece of technology that isn’t working the way the brochure promised, stop looking at the code for a moment.

Audit your Social Operating System.

• Audit the Cognitive Load: Are you using technology to dumb down the job, or to clear the clutter? (Remember Lockheed: Remove the friction, keep the craft).

• Audit the Trust: Is the system opaque, or explainable? (Remember Siemens: Keep the human in the loop).

• Audit the Process: Did the people using the tech help choose the tech?

The future of industry isn’t about automating the human out. It’s about augmenting the human in. And that starts with respecting the human operating system as much as the digital one.

If you found this breakdown helpful, share it with a colleague or reply and let me know:

Explore Organiksol's Changemaker's Hub

Related Article:

We talk a lot about the “Future of Work.” It can sound complicated, full of buzzwords about “smart factories” and “digital transformation.” But you don’t need an engineering degree to spot the difference between the old way of working and the new one. You just need to look at how you make decisions on a Tuesday morning.

To translate these concepts into action, leaders must learn to distinguish between the old and new paradigms. It is often easy to agree with the idea of human-centricity in principle, but much harder to spot where we are falling short in our daily execution.

To help you see those blind spots, I’ve outlined a simple comparison below. Think of this not as a comprehensive analysis, but as a quick diagnostic mirror—a tool to help you observe the gap between your intentions and your reality.

1. The Goal of Technology

Every automation project starts with a “why.” When you sign off on a new initiative, what is the driving force behind it?

🔴 The Industry 4.0 Approach (Efficiency-Driven)
The primary goal is to automate processes to replace human labor and reduce costs. The machine is viewed as the priority, and the human is a cost line item to be minimized.

🟢 The Industry 5.0 Approach (Value-Driven)
The goal is to augment human capabilities, creating a synergy between humans and machines. The objective is to make the worker stronger, safer, and more capable, not obsolete.

💡How to Shift
To move to the new paradigm, you must make the process inclusive from day one. The most critical shift is letting the operators decide what gets automated. Instead of asking, “How can we replace this person?”, ask your team: “What are the most frustrating, draining, or repetitive parts of your day?”. When you use technology to remove the drudgery they hate, you build trust instead of fear.

2. The Worker’s Role

When you bring a new machine onto the floor, how do you view the person standing next to it? This view dictates the entire design process.

🔴 The Industry 4.0 Approach (Efficiency-Driven)
The worker is seen as an operator, supervised by technology, or a component to be phased out. They are expected to comply with the machine’s rules and are rarely consulted on its design.

🟢 The Industry 5.0 Approach (Value-Driven)
The worker is a central, empowered collaborator whose creativity and expertise are essential. You recognize that they hold “tacit knowledge”—the wisdom in their hands that isn’t in any manual.

💡How to Shift
Give operators a say in how the solution is built. Don’t just hand them a manual; bring them into the design process early so their expertise shapes the solution. A powerful way to do this is through “Go-and-See” apprenticeships, where engineers watch and learn from operators before writing a single line of code. Treat them as co-creators, not just users.

3. The Key Metric of Success

You get what you measure. If your metrics only care about the machine’s speed, you will eventually break the people running it.

🔴 The Industry 4.0 Approach (Efficiency-Driven)
Success is measured by productivity, output speed, and cost reduction. If the numbers look good on a spreadsheet, the project is considered a win, regardless of the human toll.

🟢 The Industry 5.0 Approach (Value-Driven)
Success is measured by human well-being, resilience of the value chain, and sustainable, long-term prosperity. You measure the health of the system, not just the speed of the part.

💡How to Shift
You must balance your spreadsheet. If you track a machine metric (like throughput), you must also track a human metric (like satisfaction or stress). Ask the team: “Has this new tool reduced your physical strain? Has it freed up time for more creative work?”. If efficiency goes up but satisfaction goes down, you are building a fragile system.

4. The Leadership Style

Ultimately, your technology strategy is a reflection of your power dynamic. Are you hoarding control, or sharing it?

🔴 The Industry 4.0 Approach (Efficiency-Driven)
The style is top-down, command-and-control, focused on process compliance. Information flows one way, and questions are often seen as resistance.

🟢 The Industry 5.0 Approach (Value-Driven)
The style is collaborative, trust-based, focused on empowering workers and fostering innovation. Leaders use their authority to remove obstacles, not to enforce rigid rules.

💡How to Shift
Move from “Power Over” to “Power With”. A great way to practice this is by inviting healthy conflict. Use a “Red Team” approach where you ask your most experienced operators to find flaws in a plan early. Reward them for finding problems before you build them. This turns disagreement into a valuable contribution rather than resistance.

Subscribe now

The “Hybrid” Trap

If you looked at this list and felt like you were stuck somewhere in the middle, you aren’t alone.

The most dangerous place to be is in the “Hybrid Trap.” This happens when you tell your team, “We want you to be creative partners!” (Green Column), but you measure them strictly on speed and cost (Red Column). You can’t demand innovation while managing for compliance.

Moving from the red list to the green list isn’t about buying more expensive software. It is a choice about respect. It means believing that the people doing the work know more about it than the people managing it.

Where did you land? If you realized your strategy is leaning heavily on the Industry 4.0 side, don’t worry. Simply spotting the gap is the first step toward closing it.

The goal of this newsletter is to explore practical ways we can make that shift, one small decision at a time.

If you found this checklist helpful, share it with a colleague or reply and let me know:

Explore Organiksol's Changemaker's Hub

Related articles

For decades, the promise of automation was pure efficiency. But this approach has hit a wall. The most common cause of project failure isn’t technical; it’s human. We face an “Unseen Obstacle”: a gap between our technology and our team’s willingness to adopt it.

Industry 5.0 could provide the solution—a profound value-shift that places people, resilience, and sustainability at the center of our strategy. This article demystifies the three pillars of Industry 5.0 and provides a practical roadmap for leaders who want to build the resilient, human-centric organizations of the future.

Table of content

1. The Challenge of Automation: When Technology Meets Human Resistance

2. From Mass Production to Human-Centric Collaboration

3. The Three Foundational Pillars of Industry 5.0

   1. Pillar 1: Human-Centricity (Prioritizing People)

   2. Pillar 2: Resilience (Building Adaptive Systems)

   3. Pillar 3: Sustainability (Purpose Beyond Profit)

4. A Roadmap for Changemakers

   1. A Working Definition of Industry 5.0

5. Conclusion: The Leadership Imperative

1. The Challenge of Automation: When Technology Meets Human Resistance

For decades, the promise of technology in the workplace was singular: maximum efficiency. Companies invested billions in advanced automation—from complex software to sophisticated machinery—to reduce costs and increase output. Yet, many organizations still face a frustrating paradox: despite owning cutting-edge systems, they struggle with high employee turnover, persistent skills gaps, and a workforce often wary of change.

This gap—between technological capability and human acceptance—is what I call the Unseen Obstacle.

When new technology is implemented, employees frequently perceive it not as a helpful tool, but as a direct threat to their jobs or a source of overwhelming complexity. Automation, when conceived solely as substitution, often fails to capitalize on the unique and irreplaceable assets that humans bring to the table: creativity, intuition, critical judgment, and strategic problem-solving.

To navigate the increasing volatility of the global economy, every organization must understand a fundamental shift: the next wave of industrial evolution is not about more technology; it is about purposeful technology, directed by human values.

2. From Mass Production to Human-Centric Collaboration

To understand Industry 5.0, it helps to briefly trace the path of previous industrial revolutions:

• Industry 1.0 (18th Century): Defined by mechanization, using water and steam power to replace animal and human labor.

• Industry 2.0 (19th Century): Introduced electrical energy, the assembly line, and the concept of mass production.

• Industry 3.0 (20th Century): Leveraged electronics and early Information Technology (IT), field-level computers like PLCs to introduce programmed automation.

• Industry 4.0 (Early 21st Century): This is the era of the “Smart Factory” and “Digital Transformation,” integrating the Internet of Things (IoT), Big Data, Artificial Intelligence (AI), and Cyber-Physical Systems to connect machines seamlessly. The goal was high efficiency and data-driven decision-making.

However, the rapid and relentless drive for efficiency in Industry 4.0 often ignored the social, environmental, and ethical consequences. This led to systems that are brittle when faced with crises (like the recent pandemic) and organizations that struggled with cultural adoption that comes with the technological change.

Industry 5.0 (I5.0) emerges as a vital course correction. It is not a technology shift, but a value shift. I5.0 expands upon the digital foundations of Industry 4.0 by emphasizing the idea of putting people at the center of industrial production processes. Its ultimate aim is to resolve the socioeconomic and environmental problems that Industry 4.0 either fails to address or makes worse.

3. The Three Foundational Pillars of Industry 5.0

Academic and institutional policy across the world—including the European Union’s influential framework—defines Industry 5.0 not by the tools it uses, but by the purpose it serves. This framework is built on three inseparable pillars:

3.1. Pillar 1: Human-Centricity (Prioritizing People)

Human-Centricity is the paramount idea of placing humans at the core of the manufacturing process. It acknowledges that the workforce is not merely a collection of passive participants, or an asset, but an active protagonist, contributing to the overall success and innovative capacity of the system.

• Augmentation, Not Replacement: The core mandate is to move beyond automation as substitution and use technology to “amplify human capacities”.

• Focus on High-Value Skills: Technology takes over the dull, dirty, and dangerous work, freeing humans to focus on high-demand skills like critical thinking, collaboration, communication, and creative problem-solving. Technology is assisting workers so that value is added, not to simply replace human workers.

• Well-being and Engagement: A human-centric workplace prioritizes worker well-being, fostering a working environment tailored to human needs. This focus on psychological and social needs ensures that technological progress aligns with the well-being and growth of the human workforce and makes sure that everyone has an opportunity to contribute to an ever-advancing civilization.

3.2. Pillar 2: Resilience (Building Adaptive Systems)

Resilience is the capacity of a system to quickly adapt, withstand disruptions, and recover its stability after experiencing significant changes or shocks. The fragility of global supply chains exposed during the COVID-19 pandemic highlighted the urgent need for this attribute in industrial planning.

• Viability-Based Integration: In I5.0, resilience is not just a function of backup technology; it is achieved through the integration of all three core principles. A system is more resilient when its people are upskilled and empowered to manage complexity, rather than strictly following rigid, unchangeable rules.

• Preparing for Change: Resilience demands organizational flexibility to adapt to profound industry shifts, such as the transition to new power technologies or major supply chain reconfigurations. Organizations must adopt reconfigurable processes and foster a culture of continuous learning to stay competitive during rapid change.

3.3. Pillar 3: Sustainability (Purpose Beyond Profit)

Sustainability in Industry 5.0 broadens the traditional concept of profit to include social and ecological responsibility. It mandates that production respects the ecological limits of our planet while generating positive societal impacts.

• Holistic Value: This commitment involves reducing environmental impact (e.g., integrating circular economy principles, green manufacturing) but also ensuring social sustainability—fair labor practices, ethical governance, and equal opportunities.

• Ethical Technology: I5.0 requires ethical automation and Value-Oriented Engineering. This means actively addressing technological complexity, such as high system integration costs, troubleshooting difficulties, and the challenge of recruiting personnel capable of operating complex equipment, especially in smaller enterprises.

4. A Roadmap for Changemakers

For any leader or changemaker, adopting the vision of Industry 5.0 is only the first step. The true difficulty lies in translating these abstract values into practical, day-to-day organizational change. Leaders often perceive I5.0 as overly complex or expensive, particularly because practical adoption is often in its early stages due to resource constraints and a lack of specialized in-house expertise.

What is needed is a framework for worker-inclusive automation that maximizes human potential and organizational health. Such a framework has to be guided by the philosophy of transforming leadership dynamics from “Power Over” (based on control, compliance, and micromanagement) to “Power With” (based on consultation, shared capacity, and empowerment).

There is plenty to learn, experience and consult about how to transition from I4.0 to I5.0. Let’s start with:

A Working Definition of Industry 5.0

Industry 5.0 is a holistic ‘co-creation’ framework, based on collaboration and true consultation between all stakeholders, moving beyond individual productivity to focus on collective well-being and resilience. It’s an intentional partnership between human ingenuity and intelligent automation, designed to augment our shared potential and contribute to long-term, equitable societal advancement.

By focusing on cultural change (e.g., fostering psychological safety), skill development (reskilling the workforce for Human-Machine Collaboration), and ethical governance (addressing bias in AI), this methodology directly targets the “human element as a bottleneck”. It makes the principles of I5.0 actionable, providing a pathway for increasing productivity, lowering employee turnover, and fostering the innovation necessary to compete in a rapidly changing world.

5. Conclusion: The Leadership Imperative

The research on Industry 5.0 signals a clear turning point for organizational management across all sectors. The deepest challenge facing leaders today is not technical; it is the cultural and ethical decision of how to deploy technology.

Leaders must move away from the outdated assumption that automation leads solely to downsizing, and instead embrace the knowledge that a deliberate investment in human capability and well-being directly enhances system resilience and organizational viability. The future belongs to those who successfully merge human intelligence with machine precision, creating organizations that are not just smart, but wise—guided by principles of justice, collaboration, and shared purpose.

More Resources on the Changemaker's Hub

Related articles

While working through it all, I thought I’d give the new video feature in NotebookLM a chance. I fed it my research and asked it to create a video.

Here is the result, completely uncut.

It’s an interesting take. It’s definitely not how I would (or will) present the topic myself, but I do think it’s worth sharing as one way of introducing this complex and important conversation.

Picture a massive, top-down automation project—the kind with a multi-year roadmap and a seven-figure budget. It looks perfect on paper, a flawless blueprint for the future. But when it finally rolls out, it fails in practice. It hits a dozen small, human realities that the blueprint never accounted for, realities that everyone on the floor could have predicted but were never asked.

Now, picture a small, worker-suggested tweak to an existing process—a clever workaround, a simple script. It costs almost nothing and takes a week to implement. And it ends up having a disproportionately huge positive impact on both productivity and morale.

This is the power of learning from the edges.

The Myth: Big Transformation Requires a Big, Top-Down Strategy

We are taught to believe that major transformation must be a “big bang” initiative, driven by executive vision and rolled out from the top down. We assume that the best ideas are born in the boardroom and that the frontline’s job is simply to execute the plan. We see innovation as a mandate, not a conversation.

But this approach is built on a flawed and dangerous assumption: that all the important knowledge resides at the top of the organizational chart.

The Truth: The Unseen Obstacle is a Centralized Mindset

The most resilient and effective automation strategies don’t come from top-down mandates; they emerge from the “edges” of the organization, from the people who live with the process every day. The unseen obstacle is a centralized mindset that believes all intelligence resides at the center.

This mindset fails because it ignores the most valuable dataset you have: the tacit knowledge of your people. As I explored in my article on “Innovators vs. Stewards,” the people on the floor—the Stewards—are the keepers of your organization’s real-world wisdom. They know every hum and rattle of the machine. They know the subtle workarounds that keep the system running when the official process breaks down.

As I wrote in my Organiksol series, “The Art of Human-Centric Automation,” any strategy that ignores this deep well of human expertise is destined to create brittle, ineffective systems that people resent and are forced to work around.

True innovation isn’t about imposing a single, perfect solution. It’s about creating a system that allows the best ideas to surface and be scaled, wherever they come from. The goal is not to have the best strategy; it’s to have the most intelligent organization.

The Playbook: A Guide to Cultivating Grassroots Innovation

Here are three disciplines to help you shift from a top-down mandate culture to a bottom-up innovation ecosystem.

Discipline 1: Make Automation an Open Conversation, Not a Command.

The language we use shapes the outcome. A leader who asks, “How can we automate this process?” is asking a technical question that invites a top-down solution. A leader who asks, “What are the most frustrating, draining, or repetitive parts of your day?” is asking a human question that invites a grassroots solution. Start by mapping the drudgery, not just the process. This simple shift in framing opens the door for your frontline experts to identify the opportunities for automation that will have the most meaningful impact on their daily work.

Discipline 2: Equip, Don’t Dictate.

Instead of investing all your resources in one massive, centrally-planned project, distribute them. Provide your teams with the tools, training, and—most importantly—the autonomy to experiment with small-scale automation solutions for their own problems. This “Power With” approach turns your team from passive end-users into active co-creators of their own more effective workplace. It signals that you trust their expertise and are willing to invest in their capacity to solve their own problems.

Discipline 3: Amplify the Small Wins.

Create a formal system for identifying, celebrating, and scaling the successful micro-innovations that emerge from the frontline. When one team’s clever workaround saves five hours a week, that’s not just a small win; it’s a successful pilot program. Your job as a leader is to recognize its potential, provide the resources to refine it, and then share it across the organization. This creates a virtuous cycle where small, successful experiments build momentum for larger, sustainable change, proving the value of grassroots innovation one win at a time.

The Inspiring Conclusion

The future of work isn’t being written by a few brilliant people in a boardroom. It’s being co-created every day by the people on the front lines who are finding smarter, more human ways to get things done. When we learn to listen to the edges, we don’t just build better automation; we build a more intelligent, resilient, and empowered organization.

More resources on The Changemaker's Hub

The project kickoff meeting is a celebration. The initial ROI calculation looks flawless: projected labor savings are significant, and the new automation system was delivered on time and on budget. On paper, it’s the very definition of a successful project. Management is thrilled.

But a year later, the real story emerges. Two of your most experienced supervisors—the operational experts who knew every hum and rattle of the old machines—have quit, citing burnout from trying to manage the new, brittle system. The “labor savings” on the spreadsheet have been completely erased by the high cost of recruiting and retraining their replacements. Maintenance costs have doubled because the new system, without the team’s tacit knowledge to guide it, requires constant, expensive expert intervention.

The initial financial win has become a long-term operational and financial drain. What went wrong?

The Unseen Obstacle not Covered in Your ROI Spreadsheet

Let’s be clear: a project has to make financial sense. An ROI calculation is a necessary and non-negotiable tool for any serious business decision. The spreadsheet is an essential instrument for fiscal discipline.

But a tool can be essential and still give you a dangerously incomplete picture.

The classic ROI model is already failing a critical real-world test: it’s calculating savings on workers we can’t even find or retain in the first place. In today’s tight labor market, automation is often not about cutting costs, but about ensuring survival and enabling growth with the team we have.

This reveals the spreadsheet’s quiet lie. The problem isn’t that the initial numbers were wrong; it’s that they were incomplete. It measures the projected efficiency of the machine but is blind to the expertise, creativity, and well-being of the very people who will make it succeed. This partial truth creates an unseen obstacle—a false sense of security that leads to disastrous long-term consequences.

The Real ROI is Our Collective Capacity

The goal, then, is not to replace the financial ROI, but to balance it. A truly successful project is one that is both profitable and sustainable. Sustainability doesn’t come from a machine; it comes from the partnership between technology and the people who operate, maintain, and improve it.

The long-term success of any technology is not how efficiently it replaces a task, but how effectively it augments our collective capacity. A system that hits its initial financial targets but alienates our most valuable partners is not a success; it’s a long-term liability that creates a fragile, brittle organization.

The Playbook: The Co-Creative Framework

The solution is to build a more complete picture from the very beginning. Think of the financial ROI as the first filter for a project. This “Co-Creative Framework” is the second—a set of guiding principles to ensure our project is not just profitable, but sustainable and successful in the real world.

Principle #1
Treat Your Team as Co-Creative Partners, Not End-Users.

We must move past the idea of designing a system for a group of users. The operational experts on the floor are our most valuable partners in the process, holding the tacit knowledge that will make or break the project.

• Let’s Ask Together: “What are the most frustrating, draining, or repetitive parts of your current work? How can we design a system that solves for that first?”

Principle #2
Solve Their Problems, Not Just Our Own.

A successful system is one that our partners want to use because it genuinely makes their work-life better. This means our primary goal must be to solve their real-world frustrations, not just to impose a solution that looks good on a spreadsheet.

• Let’s Ask Together: “What does a ‘good day’ look like for you in this role? How can this technology help create more of those days?”

Principle #3
Prioritize Growth and Capability.

The best technology doesn’t just replace human skill; it creates an opportunity for us all to learn and grow. A successful project should make the entire organization more capable and adaptable.

• Let’s Ask Together: “What new skills are you interested in learning? How can this project become a platform for developing those capabilities together?”

Principle #4
Anchor Everything to the Mission.

The co-creative process is the method, not the goal. The ultimate objective is still to solve the original business problem that prompted the project. This principle ensures our human-centric approach remains rigorously focused on achieving mission-critical outcomes—whether that’s improving quality, increasing throughput, or ensuring safety.

• Let’s Ask Together: “How does this solution help us achieve our primary business objective? How can we track both our human-centric metrics and our core operational KPIs together?”

A More Complete Truth

The most successful changemakers don’t choose between the spreadsheet and the people; they understand that both are essential for a complete picture of reality. This Co-Creative Framework doesn’t replace our ROI calculation; it stress-tests it. It ensures our projected financial returns are sustainable by building a stronger, more capable, and more unified team for the future.

It’s how we build automation that doesn’t just look good on paper, but works for your people—and your bottom line—in the real world.

Read more about human-centric automation

The project kickoff meeting feels like a huge success. The engineering team presents a polished, data-driven plan for the new automation line. The operations team, including the veteran supervisors you were most worried about, nods along. When you ask for questions, you're met with silence. You leave the room feeling relieved—everyone is on board. The rollout will be flawless.

Fast forward three months, and the line is plagued by constant failures. Your best people are stuck doing manual overrides, and the promised efficiency gains are nowhere to be seen. What went wrong? The answer lies in that silent, "perfect" kickoff meeting.

This is the illusion of the flawless rollout. We are taught to see a smooth, conflict-free process as a sign of success. We assume that if the frontline users aren't raising objections, they must be aligned with the plan. Any potential friction is viewed as "resistance to change" that needs to be managed, rather than valuable data that needs to be incorporated.

But in an automation project, this polite silence is the most dangerous sound you can hear. It's not a sign of alignment; it's a sign of low psychological safety. The people on the floor—the operators and supervisors with the invaluable tacit knowledge of how things actually work—can already see a dozen ways the "perfect" plan will fail in the real world. But they stay silent because past experience has taught them that their practical concerns will be dismissed as "not understanding the technology" or "being resistant."

This "flawless rollout" is a mirage that leads directly to brittle, ineffective automation that people resent and work around. The lack of healthy, task-focused conflict during the design phase is the single biggest predictor of project failure upon implementation.

Suggestions for Engineering Healthy Conflict

To build automation that actually works, we can intentionally design a process that makes it safe—and even necessary—to disagree. The goal is to surface the critical conflicts during the planning stage, not after the system is built.

1. Frame the Plan as a "Version 0.1 Hypothesis." Consider framing your plan not as a finished solution, but as a "Version 0.1 Hypothesis." A project lead can set the stage for true consultation by saying, "Here is our best guess based on the data we have. We guarantee it has flaws. Your job is not to approve it; your job is to help us find the flaws with your real-world experience." This simple reframing transforms the operations team from passive recipients into active, expert critics whose input is essential.

2. Build Mutual Respect with "Go-and-See" Apprenticeships. Mutual respect starts with shared experience. A powerful practice is the "Go-and-See" apprenticeship. Before a single line of code is written or a robot is ordered, the engineering team should spend significant time on the floor, observing the manual process with the frontline operators. This is not just about watching; it's about asking questions like, "What are you feeling for right now?" or "What sound tells you that's right?" This process builds empathy and ensures the designers truly understand the invaluable tacit knowledge they are trying to augment.

3. "Red Team" the Solution to Make Disagreement Safe. To make disagreement feel safe, it can be helpful to formalize the process. Create a "Red Team" composed of your most experienced supervisors and skeptical operators. Their sole, official job is to find every potential failure point in the proposed automation plan. Crucially, you must publicly reward them for the problems they find. This directly counters the fear of speaking up and transforms critique from an act of resistance into a valued, essential contribution to the project's success.

Building technology that serves people is one of the most difficult, and most rewarding, challenges a changemaker can undertake. It requires us to abandon the illusion of the flawless, top-down plan and embrace a messier, more human process of co-creation. When you have the courage to invite disagreement, you don't just build better robots; you build a more resilient, intelligent, and empowered organization.

Visit the Organiksol Blog

The meeting is on your calendar: ‘Project Upgrade: Line 4.’ On one side, your 15-year veteran supervisor—the Steward—who knows every hum and rattle of the machine. On the other, the brilliant young engineer you just hired—the Innovator—armed with schematics for collaborative robots and AI-powered vision systems.

You can already feel the tension. This isn't just a project meeting; it's a collision of two worlds. But this friction isn't just a people problem; it’s a symptom of a flawed approach to technology. The mistake most leaders make is focusing on the ROI of the machine. Great leaders know the real goal is to unlock the potential of their people through the machine.

The ROI Trap: Why Most Automation Fails

When an automation project creates friction, it's rarely about the technology itself. It’s about a clash between two essential, yet fundamentally different, types of knowledge.

The Innovator operates on explicit knowledge. It's the world of blueprints, data sheets, and processing speeds—the measurable data that fills a spreadsheet and justifies a project's ROI.

The Steward, however, is the keeper of your organization's tacit knowledge. It’s the wisdom that lives in their hands and their gut. It’s knowing the subtle change in sound before a machine fails, or the exact amount of pressure a component needs. This knowledge rarely makes it into a technical manual, yet it’s the invisible force that keeps your operation running.

The ROI trap is believing that the Innovator’s explicit data is the only thing that matters. This leads to brittle, inefficient systems that fail the moment they encounter a real-world variable the Steward would have handled instinctively. The most successful automation projects don't see tacit knowledge as a barrier to overcome; they see it as the most valuable dataset they have.

The Playbook for Human-Centric Automation

To get this right, you must shift your team’s focus from simply replacing human tasks to genuinely augmenting human skill. This requires a disciplined, human-first approach to design and implementation.

1. Start with Anthropology, Not Engineering. Before a single robot is proposed, the Innovator’s first job is to become an apprentice to the Steward. They must map the human workflow with obsessive detail. Ask questions not just about the steps, but about the senses: What are you looking for? What do you feel for? What sound tells you it's right? This process translates invaluable tacit knowledge into functional requirements for the system.

2. Move from Consultation to Co-Creation. Don't just ask the Steward for feedback on a finished plan. Make them a co-creator of the solution. The Innovator brings the menu of technological possibilities; the Steward provides the real-world context to know which ones will actually work. This partnership turns the Steward from a potential resistor into your project's greatest champion.

3. Aim to Augment, Not Annihilate. The goal is not always to remove the human from the loop. The best solutions automate the dull, repetitive, and dangerous parts of a job to free up the Steward for what they do best: problem-solving, quality control, and handling complex exceptions. The question isn't "Can a robot do this job?" but "How can technology make our most skilled person even better at their job?"

4. Redefine Success Beyond the Spreadsheet. An automation project's success shouldn't just be measured in throughput or uptime. Implement human-centric metrics: Has this reduced physical strain? Has it increased employee satisfaction? Has it freed up time for more creative work? Success is a system that your people willingly and effectively adopt because it makes their work, and their work-life, better.

Technology That Serves, Not Replaces

Three months later, the air in the factory feels different. There's a new, quieter hum from the line—a blend of robotic precision and human oversight. You see the Steward and the Innovator standing side-by-side, pointing at a monitor. They aren’t just colleagues; they're co-creators. The young engineer is acknowledging a small calibration tweak the Steward suggested—a detail that saved the project from a major setback.

This is the promise of human-centric automation: systems that are not only more efficient, but more resilient and adaptable, built with and for the people they are meant to serve.

Visit the Organiksol Blog