The Pawn Sees the Board: Leadership, Authority, and the Cost of Centralization

I have come to believe that authority and responsibility have to travel together.

What can a pawn see from the floor?

I have been thinking about leadership lately through the image of a chessboard. I do not see myself as the king, queen, knight, bishop, or rook. In a frontline technical role, I am closer to the pawn. That is not an insult to myself. A pawn is still part of the game. It occupies space, protects other pieces, changes what moves are available, and can eventually earn a different position. What it cannot do is pretend that it already has authority the board has not given it.

That distinction matters to me because I can see problems without owning every decision attached to them. I can gather information. I can document what happened. I can provide photographs, measurements, prior examples, and a recommendation. I can explain what I believe should happen next. But if the organization has not given me the authority to make the final call, then I should not manufacture that authority for myself.

There is a temptation in organizations to reward the person who keeps solving problems outside the boundaries of the role. At first it looks like initiative. Sometimes it is. But it can also hide a structural weakness. If I make decisions that belong to someone else simply because they are unavailable, leadership may never feel the pressure created by its own structure. The process appears to work because someone underneath it keeps carrying weight that was never formally delegated.

If leadership wants to retain the decision, leadership also retains responsibility for the decision and the delay that may come with it. My responsibility is to make the problem visible, provide enough information for a sound decision, and follow the legitimate chain. Respecting the chain of command does not mean surrendering judgment. It means knowing where my judgment ends and where someone else’s authority begins.

What happens when leadership is too far from the work?

Distance by itself is not the problem. Modern organizations operate across buildings, states, countries, and time zones. The problem begins when decision-making remains centralized while the work becomes increasingly distributed.

Imagine several production locations, a distribution operation, different customers, and another facility being added. Each location has its own daily problems, quality questions, staffing needs, production interruptions, and customer requirements. If too many routine decisions still have to travel back through one leadership group, the leadership structure can become a bottleneck. Expansion adds capacity to the operation, but it also adds communication paths and decisions. If leadership capacity and delegation do not expand with it, the organization can stretch itself thin without realizing how much friction it has created.

The difficult part is that the numbers may look good for a while. A leaner management structure can reduce visible payroll costs. Fewer people on salary can make the operation look efficient on paper. But those savings can reappear somewhere else as sorting, rework, expedited freight, downtime, missed shipments, customer complaints, repeated inspections, turnover, or supervisors spending time answering questions that should have been resolved locally.

Sometimes an organization becomes so focused on saving a dollar that it spends ten correcting what the dollar was supposed to prevent. I have said it another way before: chasing a dime can cost a dollar. The exact numbers will change from one organization to another, but the operational principle does not. Apparent savings are not always actual savings. Efficiency has to include the cost of the system around the labor, not only the cost of the labor itself.

Why should quality build an organizational memory?

One of the simplest improvements I see in quality is also one of the easiest to overlook. When an unusual condition appears, the organization should preserve more than the final disposition. It should preserve the evidence that led to the decision.

If a technician finds a questionable weld, surface condition, dimension, or cosmetic defect, take a clear photograph. Record what the issue was. Record what decision was made. If the customer approved the condition, preserve that approval with the example. If the condition was rejected, preserve that too. Build a visual history that another technician can use later.

A picture can say a thousand words, but only if someone saved the picture.

This is more than recordkeeping. It is organizational memory. It turns experience that currently lives inside one person’s head into knowledge that belongs to the organization. A new technician should not have to ask the same question that five other technicians already asked six months earlier. Leadership should not have to rely on perfect memory every time a similar condition appears. The organization already paid for the learning the first time. It should not keep paying for the same lesson.

That kind of system also develops competence without creating dependence. A technician can compare the current condition with previous examples, understand how similar decisions were made, and know when the current problem is different enough to escalate. The goal is not to eliminate judgment. The goal is to give judgment something to work with.

What does communication actually change?

I have also had to correct myself. I have been critical of communication in workplaces when questions seemed to disappear or decisions came back without enough explanation. Then I watched a leader handle an issue differently. My questions were answered. I was kept in the communication loop. Other people who needed to be involved were brought into the conversation. I was given enough information to understand what was happening.

That mattered.

If I am willing to notice poor communication, then I also have an obligation to notice when communication improves. Otherwise, I am not evaluating behavior anymore. I am protecting my own conclusion about the person. That would be hypocritical to the leadership philosophy I claim to follow.

Recognition does not need to arrive wrapped in criticism. If I want a culture of better communication, then I should reinforce the behavior I want to see when it appears.

I have watched small changes like that spread. One person starts finishing an email with a simple ‘thank you, team’ or ‘best regards.’ Someone else starts doing the same. People begin acknowledging who contributed information. The language changes first. Then sometimes the tone of the team changes with it. Culture is often discussed as if it is something leadership announces. In small groups, culture can begin with one person repeatedly demonstrating a behavior that others decide is worth copying.

Can expertise become another bottleneck?

Organizations often spend money to acquire expertise. They hire experienced managers, consultants, auditors, engineers, and specialists. That can be valuable. But hiring knowledge and using knowledge are two different things.

I have seen organizations gather employees together to talk about Lean, 5S, participation, and continuous improvement. People were encouraged to contribute ideas. The language sounded right. Then the physical process became harder. Material moved farther from the work. Visibility declined. Some people responsible for frontline coordination did not have ready access to the information needed to understand what resources were available.

That is where improvement language becomes decoration. A company can hire excellent talent and still waste the investment if the advice is never translated into the operating system. Consultants can recommend. Auditors can identify. Employees can contribute. None of that matters if the organization does not implement what it learns.

This is one reason I am careful when people assume experience automatically means competence. I have worked around different welding systems and different quality environments. That gives me a foundation. It does not mean I know every process in another plant. Procedures change. Equipment changes. Customer expectations change. A person can bring twenty years of experience into a job and still need to learn how this organization actually works. Experience should create a starting point, not permission to stop learning.

What does a family culture mean when the structure does not support it?

Organizations sometimes talk about being a family. I understand what they are trying to communicate. They are usually talking about closeness, loyalty, continuity, and a workplace where people know one another. Those things can be real. But a corporation does not have emotions. People do. The organization still has customers, expenses, deadlines, contracts, equipment, payroll, and a need to remain financially viable.

Calling an organization a family cannot substitute for structure. A close organizational culture can become an advantage when leaders use that trust and flexibility to reinvest in people, systems, training, and operational capacity. But that flexibility only becomes an advantage if the organization uses it.

Reinvestment is not simply spending more money. It is putting resources where the operation is creating avoidable friction. Sometimes that means another leader. Sometimes it means training. Sometimes it means a better document-control system, local decision authority, maintenance support, staffing, technology, or a clearer escalation process. It takes money to make money, but it also takes judgment to know where the money should go.

The most expensive decision is not always the one with the largest immediate price tag. Sometimes the expensive decision is the cheaper option repeated every day.

Why does the chessboard still matter?

The chessboard metaphor helps me because every piece has limits. The pawn does not move like the bishop. The bishop does not move like the rook. The queen has enormous range, but even the queen cannot ignore the rules of the board. Authority changes what a piece can do, but position does not eliminate consequences.

I am comfortable being the pawn when that is the position I was hired to occupy. I can contribute what I know. I can share information. I can support the team. I can ask questions. I can document problems. I can recommend a move. What I will not do is pretend to be another piece because leadership has not decided who should move next.

That does not mean passivity. A pawn still moves. It still changes the board. It still protects other pieces. And if it keeps moving successfully, it can eventually earn promotion. But it earns that position by moving within the rules, not by declaring itself something else halfway across the board.

That is where I see leadership, followership, and organizational development meeting. The organization has to decide which decisions belong where. Leaders have to communicate enough for people to understand the purpose behind the work. Employees have to use judgment without manufacturing authority. Knowledge has to be preserved so the next person does not start from zero. And when someone improves, we should be willing to acknowledge the improvement instead of protecting an old opinion about them.

Every move changes what becomes possible next.

That is true in chess, and I think it is true in organizations. The real question is whether leadership understands the board well enough to know which moves should remain centralized, which should be delegated, and which problems keep returning because nobody has changed the game around them.

---

Related reading: The Work Came Before the Theory

For organizations: Request Leadership Training