Leading with Meaning – Chapter 2 – Unity, not Duality

CHAPTER TWO

Leading with Meaning – Unity, Not Duality

The Vortex Automotive plant in Monterrey ran on rhythm. Hydraulic presses fired in sequence. Conveyor belts moved at a pace calibrated to the second. Robotic arms swung, welded, retracted. And in between the machines, people moved too, glossed with sweat, focused, precise.

Carlos Mendoza had spent eleven years inside this rhythm. He’d started on the line at twenty-two, a mechanic who could diagnose a failing actuator by sound alone. Promotions followed, not because he sought them but because people trusted him. When something went wrong, you went to Carlos. He spoke the language of the plant like a native.

Now, at thirty-three, he was a floor supervisor. On paper, a step up. In practice, it felt like exile. His days had narrowed to shift rotation charts, disciplinary paperwork, emails from corporate requesting productivity metrics and employee morale data in the same sentence, as if the two were interchangeable. He barely touched the machines anymore. He barely talked to his team, either, not in the way that mattered.

On the morning everything changed, he was staring at the roster. Twelve names. Three no-shows. Two hearings pending. And one resignation letter, unopened, sitting at the bottom of his inbox. “I’m a mechanic in a suit,” he said to nobody.

* * *

The breaking point came during a routine recalibration of the assembly line.

A new hire named Luis, three weeks on the job, bypassed a safety lockout procedure while adjusting a station sensor. The result was a line-wide shutdown, several thousand dollars in damage, and a thirteen-hour backlog that cascaded through the night shift. Two departments blamed each other. Corporate demanded answers.

Carlos was called into a meeting with the plant director, HR, and two department heads. The question landed cold: “Why aren’t your people following processes?”

He wanted to say a lot of things. What came out was this: “They don’t see them as their processes. They see them as yours.”

The room went quiet. Not the quiet of agreement. The quiet of people deciding whether to be offended.

Carlos walked out knowing he’d said the wrong thing in the right way. Luis hadn’t bypassed the procedure out of recklessness. He’d done it because nobody had explained why the procedure existed, what it protected, or why it mattered beyond the compliance manual. He’d been handed a checklist, not a reason.

And that, Carlos started to realize, was the same problem running through everything. Not just the safety incident. The no-shows. The resignation letter. The flatness in people’s eyes at the start of each shift. They were doing their jobs. They just weren’t invested in them.

* * *

The cost of splitting things in two

Carlos had always believed, without questioning it, that leadership and management were two different activities performed by two different kinds of people. Leaders were visionaries. Managers were executors. Leaders sat in boardrooms and set direction. Managers made sure the direction was followed. He was a manager. Leadership was someone else’s department.

This belief is extraordinarily common, and it is also deeply unhelpful.

The habit of dividing leadership from management has a long history in business thinking, and it has done real damage. It created a class system inside organizations: the thinkers and the doers, the people with vision and the people with clipboards. It told millions of mid-level managers, team leads, and supervisors that their job was to execute, not to inspire. And it told their teams that the person standing next to them on the floor was just a conduit for decisions made elsewhere.

Peter Drucker cut through this decades ago. “Management is about human beings,” he wrote. “Its task is to make people capable of joint performance. Management is the critical, determining factor.”

The secret of management and the secret of leadership are the same secret: both are about people. Both are about making it possible for a group of individuals to do something together that none of them could do alone. Trying to separate the two is like trying to separate breathing in from breathing out. They are two phases of the same essential act.

For Carlos, the separation had a specific cost. Because he saw himself as “just a manager,” he treated his role as a buffer between corporate directives and the shop floor. He relayed information downward and reported problems upward. He kept the line moving. But he never asked himself the questions that leadership demands: What do these people need from me beyond task assignments? What kind of environment am I creating by my presence, or my absence? What am I building here beyond output numbers?

The moment he told the leadership meeting that his people didn’t feel ownership, he crossed a line. Not a line of insubordination. A line inside himself. He’d stopped being a relay and started being a voice.

* * *

Everyone has a leadership role

Here is an idea that sounds obvious when you say it out loud but that most organizations still fail to practice: in any endeavour, every person has a leadership-related role.

Regardless of official title, we all lead and we are all led. The receptionist who shapes a visitor’s first impression of the company is leading. The engineer who decides to flag a concern rather than stay silent is leading. The janitor who notices that a hallway layout is causing a bottleneck and mentions it to the facilities team is leading. Leadership is not a position in the hierarchy. It is a behaviour that can come from anywhere.

The Versatile Leadership framework takes this principle seriously. The leadership we need, it argues, is one that involves and engages everybody, each according to their needs and according to what the organization and its environment demand. This is not a feel-good platitude. It is a structural claim about how effective organizations work. When leadership is concentrated at the top, the organization becomes brittle. When it is distributed, the organization becomes adaptive.

Carlos didn’t have the language for this yet. But he had the instinct.

* * *

The folding table experiment

The day after the meeting, Carlos did something he’d never done before. He didn’t send a memo. He didn’t schedule a training session. He didn’t call anyone into his office.

Instead, he carried a folding table into the breakroom during the lunch shift. On it, he put a large sheet of paper and a handful of markers. At the top of the sheet, he’d written a single question in his own handwriting: “What does good leadership look like to you?”

He didn’t make a speech. He told people the paper was there, that he was curious, and that he’d read whatever they wrote. Then he left.

For two days, nothing happened. The paper sat there, blank, while people ate their lunches around it. Carlos started to feel foolish.

On the third day, Luis wrote something. The same Luis who’d caused the shutdown. His handwriting was small, pressed hard into the paper: “Someone who asks, not just tells.”

After that, others followed. By the end of the week, the sheet was full. The entries were short, mostly one line each. “Listens when something’s not working.” “Teaches instead of yelling.” “Knows my name.” “Trusts me to fix it.”

Carlos stood in front of the sheet after everyone had gone home on Friday. He read each line slowly. What struck him wasn’t any single response. It was the pattern. Nobody had written anything about strategy, or KPIs, or market positioning. Nobody had asked for a charismatic figure to rally behind. They were asking for something far simpler and far harder to deliver: presence. The feeling that someone with authority actually saw them, heard them, and believed they were capable.

That weekend, Carlos sat at his kitchen table and opened a notebook. At the top of the first page, he crossed out “Floor Supervisor” and wrote “Connector of Purpose.” It was a private gesture, a little dramatic, maybe. But it marked something real. He was redefining his own role, not waiting for anyone else to do it for him.

* * *

From pyramids to networks

What Carlos did with a folding table and a sheet of paper was, without knowing it, a small act of organizational redesign.

Traditional leadership models are shaped like pyramids. A few people at the top make decisions. Many people at the bottom carry them out. Information flows up, commands flow down. This structure works well enough when the environment is stable and the work is predictable. It breaks down when the environment is volatile, the problems are complex, and the people doing the work are the ones closest to the information that matters.

Modern organizations are increasingly shaped like networks. Influence moves laterally as much as vertically. Teams form and reform around problems. Authority shifts depending on context and expertise. In a network, the role of a formal leader changes. Instead of being the single point where all decisions converge, the leader becomes a node, one connection among many, whose job is to strengthen the links between people rather than to direct traffic.

Carlos began practising this without calling it a theory. He stopped delivering morning directives and started asking questions instead. “What’s slowing you down today?” “Where can we improve this station?” “Who has an idea that hasn’t been heard yet?” Small questions, but they changed the dynamic. They signalled that information was supposed to flow in more than one direction.

He also did something subtler. He started spending the first twenty minutes of each shift walking the floor, not inspecting, just being present. Asking how people’s weekends were. Noticing when someone looked tired. Learning the names of people he’d only known by station number. It wasn’t efficient in the traditional sense. But it was effective in a way that no directive could have been.

* * *

What changed, and why it matters

Three weeks after the folding table experiment, the numbers moved. Productivity was up twelve percent. Safety incidents dropped. But the more telling changes were harder to measure. People greeted each other by name. They stayed a few minutes after their shifts to help colleagues at neighbouring stations. Luis, the new hire who had caused the shutdown, stayed late one evening to reconfigure part of a station he didn’t even work on.

“I never thought I’d say this,” Luis told Carlos, “but this job feels like it means something now.”

Carlos didn’t take credit. He knew better. What had happened wasn’t the result of one person’s brilliance. It was the result of removing a barrier, the false belief that leadership belonged to someone else, and letting people step into a role they’d always been capable of filling.

This is what distributed leadership looks like in practice. It does not mean that hierarchy disappears, or that everyone becomes a manager, or that accountability becomes diffuse. It means that the capacity to lead, to see a problem, to take initiative, to support a colleague, to speak up when something isn’t working, is recognized as belonging to everyone. The formal leader’s job is to create the conditions in which that capacity can emerge.

Carlos didn’t create a leadership programme. He didn’t redesign the org chart. He just stopped treating leadership as something that happened above him and started treating it as something that happened through him and around him. That shift, from pyramid to network, from title to behaviour, from separation to unity, is the core of this chapter’s argument.

* * *

Closing the divide

Carlos Mendoza didn’t become a CEO. He didn’t publish a management theory. But he changed the culture of his corner of the plant by doing something deceptively simple: he stopped drawing lines between leaders and non-leaders, between management and leadership, between his authority and his team’s agency.

The unity that the Versatile Leadership framework calls for is not about eliminating roles or flattening structure. It is about recognizing that the work of leading, truly leading, happens at every level. That management without human connection is just administration. That leadership without operational grounding is just talk. And that every person in an organization, from the executive suite to the shop floor, is capable of both.

A few questions worth carrying with you:

Where in your work have you drawn an artificial line between “leading” and “managing”? What has that division cost you or your team?

Who around you is already leading, without the title, without the recognition, without the formal authority? What would change if you acknowledged that out loud?

And what would your version of the folding table look like? What is the simplest thing you could do this week to invite the people around you into a leadership conversation they’ve been excluded from?

The answers to these questions are the beginning of unity. And unity, as we’ll see in the chapters ahead, is the foundation on which everything else in the Versatile Leadership framework is built.

Bouns Tips

Leaders can enhance their understanding of meaning by engaging in the following practices:

• Reflective Journaling: Dedicate time each week to reflect on your experiences, decisions, and feelings. Journaling can help clarify your thoughts and identify recurring themes related to your purpose.
• Peer Conversations: Facilitate discussions with trusted colleagues or mentors about their leadership journeys. Sharing stories can inspire insights and highlight different perspectives on meaning.
• Learning Workshops: Participate in workshops focused on values exploration and purpose alignment. These settings can provide tools and frameworks to help articulate and refine your leadership meaning.
• Feedback Loops: Actively seek feedback from your team and peers. Understanding how others perceive your leadership can unveil blind spots and inform your development journey.