The Day I Stopped Chasing My Team

At 8:50 on Monday morning, Zhou Ming posted the week's to-do list on the whiteboard. Seventeen items. He circled three in red and wrote, "Must do today." At 9:10, the first person came in and asked, "Which one first?" He pointed to the first. At 9:40, the second person came in and asked, "The client changed the requirements. Do we still follow the original plan?" He froze. At 10:00, the third person posted in the group chat: "Done, please check." He opened the file and saw it was not what he wanted. He called the three of them into the meeting room. Seventeen items on the whiteboard, like seventeen forks in the road. He realized he was not managing a project. He was plugging holes.

This is a familiar day for many managers. The phone cannot be on silent. Messages get answered in seconds. Meetings follow one another. The progress sheet gets revised late into the night. It looks like managing people, managing tasks, managing stability. But when he gets home, his head is still a mess. After a whole day of being busy, nothing moved forward on its own. Everything depended on him pushing.

Only after managing for a long time does a person slowly see one thing clearly: management works through people. You get things to happen by influencing them. You do not get them to happen by holding everyone in your hand. One step further: you make the right things happen continuously, without depending on any single person.

Managing people, managing tasks, and stability are outward forms of this work. Task management gives the work a frame. People management keeps effort flowing. Stability keeps the team from falling apart when conditions change. If any one is missing, management becomes a one-man show.

1. Managing tasks: not chasing, but closing the loop

Many managers understand "managing tasks" as assigning work, chasing progress, holding meetings, and dividing jobs. Today they ask, "Where is it?" Tomorrow they ask, "Why is it not done yet?" The day after, they call everyone together for another meeting. It looks busy. In fact, it only creates anxiety.

Real task management is building a closed loop.

From the beginning to the end of a piece of work, at least four questions must be answered.

First, what is the goal? Why are we doing this? What counts as completion? Employees are not afraid of being busy. They are afraid of being busy for a long time without knowing what "good enough" means. If you tell them, "Just do it well," they can only guess. If they guess right, it is luck. If they guess wrong, it is "poor execution."

Second, what is the standard? What counts as done? What counts as good? Is "roughly right" acceptable, or must it be error-free? Is it a three-day delivery or a two-week polish? If the standard is unclear, there will be an argument at acceptance. You say, "This is not what I wanted." They say, "You did not say that." Both sides feel wronged.

Third, who is responsible? Who pushes it forward? Who supports? Who has decision rights? Who do we go to when something goes wrong? If everyone thinks, "This is not my job," it will not get done. Responsibility is not a name on the wall. It is the person who is called into the meeting room first when something breaks.

Fourth, how is feedback given? Where is the progress? Is there deviation? How do we correct it? What do we review afterward? Without feedback, a task is thrown into a black hole. Employees do not know whether they did well. Managers do not know where the risk is.

Later, Zhou Ming learned to write four lines: goal, standard, owner, feedback time. After that, things no longer depended on him chasing them again and again. Chasing progress only creates anxiety. A closed loop lets things move on their own.

He also stopped asking, "Have you done it?" He asked, "Where are you stuck?" The first question makes people cope. The second makes people solve. The first gets "Almost." The second gets "The client has not confirmed yet. I will follow up again before two." Two answers, two kinds of management.

Managing tasks means giving every task a direction, a standard, an owner, and feedback. Holding every task in your own hand is not management. Then things can move forward on their own.

2. Managing people: clocking in does not mean engagement

Some people clock in on time every day, sit at their desks, and are not really there. You ask why they are doing this task. They say, "Because you told me to." You ask how it relates to the team goal. They cannot say. You gave them a task but not meaning. They deliver. You accept. Even.

But management is not about being even. Power can buy cooperation. It cannot buy engagement. A position can make people listen to you. It cannot make them treat the work as their own when no one is watching.

Zhou Ming once managed an employee named Xiaolin. Xiaolin arrived first and left last. For a while, Zhou Ming thought he was reliable. Then a project had a problem and someone needed to watch the data over the weekend. Xiaolin said he had family matters. Zhou Ming said nothing. The next week, another project needed overtime. Xiaolin said he did not feel well. Zhou Ming checked his work record and found that everything he delivered was correct, but only correct to the passing line. He did not do one extra step. He did not ask one extra question.

Zhou Ming talked to him. Xiaolin said, "I get paid this much, so I do this much. I did everything you assigned." Zhou Ming wanted to get angry, but held back. He asked himself: Did I ever tell him why this matters? Did I ever let him know what happens if it is done well? Did I ever give him a chance to take part in deciding how to do it?

No. He was only assigning work. Xiaolin was only receiving work. The two were like two gears, meshed together but producing no heat.

Managing people means making them willing to put their minds into the work. Turning them into obedient hands is not the goal.

This requires several conditions.

First, a sense of direction. They know why they are doing this and how it connects to the team goal and the company goal. People are not most afraid of being busy. They are most afraid of being busy without meaning. You tell them, "This report is important." They nod. You tell them, "This report is for the client. After reading it, the client decides whether to renew. If the renewal goes through, we keep this line next year." They will read the data twice more.

Second, a sense of growth. Can they learn something here? Can they become stronger? Can they see their own progress? If a person is no different three years later, they will leave sooner or later, or stay and stop engaging. Later, Zhou Ming took half an hour each week to go over Xiaolin's work with him, telling him what could be better and why. Not criticism. Breakdown. Xiaolin began asking questions. Later, he proactively proposed an optimization plan. Zhou Ming let him try. It worked. Xiaolin did not work overtime that day, but he took his laptop with him when he left.

Third, a sense of fairness. Is good work seen? Is poor work addressed? Do responsibility and reward match? If doing more or less makes no difference, if doing well or badly makes no difference, then what remains will be silence and perfunctoriness. Zhou Ming started posting project results at the weekly meeting: who did what, where it was stuck, how it was solved. No public criticism, but people who did the work were seen. People began to care about that whiteboard.

Fourth, a sense of participation. They are not a screw. They are not only there to execute passively. They have a chance to offer ideas, join decisions, and take responsibility for their own work. People only truly care about what they helped create. Later, when making plans, Zhou Ming would first ask, "What do you think would be smoother?" Sometimes the answers were not mature, but they contained information. He listened, then decided. Employees knew their words were heard. When they executed, it was different.

Management creates conditions that make people willing to engage. It does not remake human nature. You cannot force someone to love their work, but you can let them know why they are doing it, what meaning it has, that good work will be seen, and that poor work will get feedback. Then they may move from "I have to do it" to "I want to do it."

3. Stability: when the boss is away, the team can still run

In some small companies, everything is normal when the boss is there. The moment the boss leaves, everything falls apart.

Because usually the boss pushes everything forward. There is no process for how to do it. There is no standard for what counts as qualified. There is no clarity on who manages a problem when it appears. The team depends heavily on the boss.

Zhou Ming once went on a three-day business trip. Before leaving, he arranged everything and sent a long message to the group. The first day was fine. On the second day, the client suddenly changed requirements. The team asked around in the group, but no one dared to decide. By the time Zhou Ming landed, six hours had passed. The client was unhappy. The team felt wronged. After returning, Zhou Ming did not yell. He sat in the meeting room and took the incident apart. The problem was not that employees dared not decide. The problem was that no one had told them what they could decide on their own and what had to be reported.

Stability does not mean the team never changes. It does not mean no one leaves, no conflict, no surprises. Stability means: when you are not there, things still have someone pushing them. When a new person joins, they can get started by following the process. When an old employee hits a problem, they know whom to ask. When something deviates, there is a mechanism to fix it.

Process, standard, and responsibility look dry. But for a team to keep running, it depends on these dry things.

Process answers "how to do it." What is step one, step two, who signs, what template to use. This saves new people from asking about everything. It does not turn people into machines.

Standard answers "to what degree." What counts as qualified, excellent, or rework. If the standard is unclear, ten people produce ten versions, and in the end the manager judges with one mouth.

Responsibility answers "who is responsible when something goes wrong." Responsibility lets everyone know their boundaries. It is not blame. When boundaries are clear, collaboration no longer depends on guessing.

When the system comes alive, people do not have to keep fighting fires. When the boss is away, the team can still run. This does not weaken the manager's power. It lets the manager spend time on what is more worth spending time on.

4. Direction: let people know why they are doing it

An employee works hard every day but does not know the company goal, nor how the work in their hands relates to that goal. Their effort will burn away. It is not that they do not want to do well. They do not know what "well" is for.

Managers cannot only assign work. Assigning work is step one. Step two is letting everyone know why we are doing this.

For a period, Zhou Ming was in charge of a growth project. The team made posters, wrote copy, and ran channels every day. After a month of busy work, the data did not move. Zhou Ming called everyone into the meeting room and asked, "Do you know why we are doing this project?" Someone said to acquire new customers. Someone said to hit KPI. Someone said the boss wanted it. Zhou Ming said, "None of those. It is because last month we found that old customer renewals were falling. New customers were not making up for it. Next year, this line is gone. Every poster we make is looking for people who can fill that gap."

After that day, the copy changed. Before, it said, "Limited-time discount." Later, it said, "The feature old customers already use. New customers get the first month free." It was not that copywriting techniques changed. The team knew why they were writing.

Direction is the basis for decisions when people encounter problems. It is not a poster on the wall. When direction is clear, they know how to choose. When direction is unclear, no amount of process can do more than spin empty.

5. Empowerment: do not steal your employees' work

An employee makes a mistake. You think they are slow. You take the work over and do it yourself. Short term, it is efficient. Long term, the team cannot leave you. The more capable you are, the less the team moves. In the end, every problem waits for you to solve it. You become the bottleneck.

Zhou Ming once managed an intern who was slow at making spreadsheets. The first time Zhou Ming watched him do it, he got anxious and took it over to fix himself. The second time, he fixed it again. The third time, the intern simply sent him the raw data and said, "Zhou, you fix it faster." Zhou Ming froze. He realized he was not leading people. He was doing their work for them.

Later he changed his approach. When the intern finished, he did not edit it. He first asked, "Where do you think it could be better?" The intern could not say. He pointed to one place: "If you sort by date here, would it be clearer?" The intern tried. The next time he made a sheet, he sorted on his own. The time after, he added filters. The progress was slow, but Zhou Ming did not do it for him.

Whether a manager is strong cannot be judged only by how many problems he solves himself. It must also be judged by whether the people he develops can solve problems themselves. When ten people work together and produce more than the sum of ten people working separately, management has a multiplying effect. If a group of excellent people come together and spend all their energy consuming one another, that is not a team. That is internal friction.

Empowerment gives tools, methods, feedback, and room to make mistakes. It is not laissez-faire. It moves people from "waiting for your assignment" to "I can solve it."

6. Rules: reduce coordination costs

Rules reduce coordination costs. They are not meant to bind people.

Without rules, everything depends on chasing, arguing, and guessing. With rules, everyone knows where the boundary is, what can be done, what cannot be done, and what counts as good enough.

Zhou Ming's team later set a few small rules. Requirement changes had to be posted in the group, not discussed privately. Any task over two hours had to have a clear deadline. At the weekly meeting, each person had three minutes: first blockers, then plans. Retrospectives did not assign blame, only causes.

These rules looked small, but they saved a lot. Before, when a client changed requirements, sales privately went to design. Design finished, but product did not know, testing did not know, and something went wrong at launch. Now requirement changes went into the group, and everyone relevant could see them. Before, the weekly meeting took two hours. Now it took forty minutes.

Process answers "how to do it." Standard answers "to what degree." Responsibility answers "who is responsible when something goes wrong." When these three are clear, the team no longer depends on one person to hold it up.

When rules stand up, the manager's mouth can say less. When the mouth says less, the ears can listen more.

7. Balance: too much control and too much freedom both cause problems

Too much control grinds away creativity. Everything needs approval. Everything needs reporting. Everything must be done your way. Over time, the team becomes a group of people waiting for your instructions. If you do not speak, they do not move. If you ask, they say, "Waiting for you to decide."

Too much freedom also loses direction. No goals, no standards, no feedback. Everyone does their own thing. It looks free, but it is actually loose sand. At the end of the month, everyone was busy, but together there was no result.

The balance must be found by the manager. Things move forward in an orderly way, and the people on the team are still willing to think and act. That is good management.

Zhou Ming's method was: direction, standard, and responsibility, which he set. How to do it, who does it, when to do it, the team decided. After deciding, they told him. He did not nod, but he could ask questions. If after the questions the team still insisted, they tried. If they failed, they reviewed. If they succeeded, they spread it.

This lets the team run inside boundaries. It is not delegating power. The clearer the boundaries, the more confidently they run.

8. Role shift: from doing things yourself to leading people who do things

Before, when you did your own work well and solved problems when they appeared, everyone thought you were capable. In a management role, the standard changes. People also look at whether you can raise the people around you and help them become capable of doing things well.

In the past, many problems were solved because you had the ability. Later, when the team encounters a problem, the people you developed can catch it. Only then has the shift from doing things yourself to leading a group of people been completed.

Once, Zhou Ming got sick and took three days off. On the first day, he still replied in the group. On the second day, he forced himself not to look. On the third day, he opened the group and found the project moving forward as usual. Someone had changed the schedule. Someone had confirmed requirements with the client. Someone had written risks into the weekly report. He scrolled down and saw Xiaolin say in the group, "I will decide this one. If something goes wrong, I am responsible."

Zhou Ming put down his phone and took a sip of water. The water was cold. He did not reply.

There is more power, but also more responsibility. The people who follow you, whether their goals are clear, whether they can grow here, whether they still trust you, are all things you must care about. You cannot only care whether the work is done. You must care whether people are being consumed. You cannot only care whether the result is good. You must care how the result came about. You cannot only care whether you have authority. You must care whether the team has ability.

A manager's success comes from letting the team stand on the stage, not from standing alone in the spotlight.

9. Behind poor execution, management often failed to do the earlier work

Many bosses like to say, "The employees just cannot execute."

But execution is never an isolated thing. It is more like a result: execution = clarity × willingness × ability × mechanism.

If clarity is missing, employees do not know what to do, why to do it, or to what degree. They can only guess. If they guess right, it is luck. If they guess wrong, it is poor execution.

If willingness is missing, employees do not recognize the goal, do not agree with the method, and do not trust the manager. They only cope. After coping for a long time, they become cynical and slick.

If ability is missing, employees want to do well but do not know how, while the manager assumes they should know. There is no training, no coaching, no feedback. In the end, it can only fail.

If the mechanism is missing, doing well or badly makes no difference. When something goes wrong, no one can be found. When something is achieved, no one sees it. Over time, even excellent people become mediocre.

So when a team has poor execution, the manager must first ask:

Did I explain clearly?
Did I give resources?
Did I build feedback?
Did I put the right people on the right things?
Did I let employees know how this relates to them?

If these questions have no answers, then "poor execution" is only an excuse the manager gives himself.

10. How to judge whether management is real

You can ask yourself a few questions:

When you are not there, can the team still run normally?
Do employees know why they are doing something and to what degree it counts as good?
When something goes wrong, do people look for someone to blame, or can the system expose and correct it?
Have the people who follow you become stronger?
Is the goal achieved through pressure and luck, or through consensus, mechanism, and ability?

If the answer is no, it does not necessarily mean the employees are incapable. It may mean management has not arrived yet.

Good management makes everyone know where to go. It does not make everyone fear you. It makes the team able to win even when you are gone. It does not make you the center.

11. Management is about making people able

Management is the work of making people able. Control is only a small part of it. Making the goal able to move. Making people able to act. Making the work able to continue. Making the people who do the work able to carry it.

Because you are there, everyone is clearer about direction. Because you are not there, the team can still move forward.

Later, Zhou Ming replaced the whiteboard. Before, it was covered with to-dos. Now it had only three lines: goal, owner, deadline. The rest was blank. Someone asked, "Is it a waste to leave it empty?" He said, "I am leaving it for you to write on."

The next morning, a few lines appeared on the whiteboard. They were not written by him. He stood there and looked for a while, then took his cup to get water. The water dispenser gurgled. Outside, someone was moving boxes, cardboard scraping against the ground. He returned to his desk, opened his computer, and a message popped up in the group: progress normal today. He marked it read, turned the phone over, and put it face down on the desk.