When a Non-Standard Automation Project in China Goes Off the Rails: A Crisis Recovery from the Inside

I was on holiday with my girlfriend when the call came.

Ten o’clock at night. My boss asked where I was. I told him I was on vacation, not in Suzhou. He asked if I could come back that night — there was a flight to Shanghai in the morning. A project had gone completely out of control, and the site manager had asked for me by name.

I was head of the project department. I said yes.

I drove back to Suzhou in the early hours. My boss and I flew out together at dawn. We went straight to the site without stopping to eat.

When we arrived, my boss looked at me and said: “This is yours now. I’m flying back to Suzhou tomorrow morning.”

Then he left.

The Project: A National-Level Factory Logistics System in China

This was 2019. A full factory logistics and conveying system — a national-level project, awarded after competitive tender. The client’s team had been assembled from specialists selected across China and internationally. The scale of the project, and the caliber of the people on the client side, told you everything about how seriously they were taking it.

Our side was a different picture.

My boss had set up a subsidiary company specifically to handle this scope. The general manager of that subsidiary — Director Liu — was a former colleague of mine. He was the one who had asked for me by name.

Because this was a subsidiary operation, I hadn’t been involved. I didn’t know the project. I didn’t know the site. I didn’t know what had gone wrong or how far behind they were.

Director Liu called the entire team together and told them clearly: everyone on site, including himself, would take direction from me. Then he sat down and walked me through the project from the beginning.

What I heard was not good.

Five Things That Had Gone Wrong Before I Arrived

The work couldn’t be pre-assembled at the factory.

Everything had to be assembled on site. On a project of this scale, that meant every mistake, every rework, every delay happened in front of the client.

The labor estimate was wrong — badly wrong.

Director Liu and the subcontractor’s lead, Director Wang, had both underestimated the manpower required. Neither side had enough installation staff on the ground. Director Wang had tried to hire local workers near the client’s site, but the area had a low industrial base. The workers available didn’t have the skills the work required. Jobs done incorrectly had to be redone. The rework cost time and money that hadn’t been budgeted for.

Emergency materials couldn’t be sourced locally.

When components were missing or damaged, there was nowhere nearby to buy them. Everything had to be purchased in Suzhou and flown in. And when I arrived, nobody had been formally assigned to manage that process.

The on-site technical lead wasn’t a project manager.

The person running day-to-day operations was a technical specialist doing their best in a role they hadn’t been prepared for. When the client raised issues — and they raised many — the answers were vague, the timelines were unreliable, and the client’s patience had run out. They needed someone who could give a straight answer and then actually deliver on it.

The client had lost confidence.

This is the one that matters most. Everything else is recoverable if the client still believes you’re going to get there. When they don’t, every conversation becomes a confrontation, every delay becomes a crisis, and the team spends more energy managing the relationship than doing the work.

What Happened in the First 24 Hours

The first thing I did was listen.

Director Liu walked me through everything — the scope, the status, the gaps, the people. I needed to understand exactly what was unfinished before I could say anything useful to anyone.

Then I made a list. Not a plan yet — a list. Every piece of work not done. Every resource missing. People, materials, money, information. Everything blocking progress, written down in one place.

Once I had the list, the plan followed. I knew what we needed, who could provide it, and in what order things had to happen.

I called Director Wang and told him to bring skilled assembly and commissioning technicians from his headquarters in Suzhou. I made the same request to our own company. We needed qualified people on the ground, and we needed them fast. Local labor wasn’t going to work for the technical scope that remained.

Then I went to see the client.

Rebuilding Trust With the Client

This couldn’t wait.

The client’s project lead was experienced, demanding, and had been dealing with weeks of vague answers and missed commitments. The first thing I had to change was what they expected from a conversation with our team.

I didn’t make promises I couldn’t keep. I told them what I knew, what I didn’t know yet, and when I would have a clear answer on the things I didn’t know. I told them what I needed from their side to move faster. I gave them a completion plan — specific, with dates, with named responsible parties — and I committed to updating it every day.

The client didn’t immediately trust us. That trust had to be rebuilt one day at a time, by doing what we said we would do.

One Month. Every Day Until Three in the Morning.

For the next month, the working day started at eight and ended at three in the morning.

Every evening, everything planned for that day was either completed or had a clear explanation and a revised date. Nothing carried over without accountability. Every morning, the team knew exactly what the day required.

This rhythm — plan, execute, account for what happened, adjust, repeat — is not complicated. But it requires someone at the center of it who doesn’t let the day end without closing the loop. On a project in crisis, that person is the difference between recovery and continued deterioration.

The team needed more than a plan. They needed to believe the plan was real. Part of my job for that month was making sure that belief held — being honest about where we were, acknowledging the difficulty, and making sure every person on site understood that we were going to finish this.

We finished it in a month.

The Part the Client Never Saw

The project was accepted. On time. To specification.

From the client’s side, it was a successful delivery. The acceptance report was signed. The system went into operation.

What they didn’t see was any of what I’ve described above.

They didn’t see the phone call at ten o’clock at night, or the drive back to Suzhou before dawn. They didn’t see the workers whose work had to be torn out and redone. They didn’t see components being flown in from Suzhou because there was nowhere local to buy them. They didn’t see the team working until three in the morning, or the conversations that kept people going when the work felt impossible.

They saw a completed project. That’s what the acceptance report reflects.

This is not unusual. It is how almost every large non-standard automation project in China works, from the client’s perspective. The supplier’s internal world — the staffing problems, the rework, the near-misses, the improvised solutions under pressure — is invisible. What’s visible is the outcome.

When the outcome is good, that invisibility feels like efficiency. When the outcome is poor, it becomes the reason the client has no idea what went wrong or who is responsible.

What This Means for Foreign Manufacturers Procuring Equipment in China

The gap between what a foreign manufacturer sees and what is actually happening inside a project in China is not a communication problem. It is structural.

It exists because no one on the project has both the access to the supplier’s internal world and the obligation to report honestly to the client.

Foreign buyers evaluating a Chinese supplier see the factory, the certifications, the sample quality, and the commercial proposal. They don’t see how the project will actually be staffed once it’s awarded. They don’t see whether the labor estimate is realistic, whether emergency procurement has been planned for, or whether the on-site team has the project management experience the work requires.

On this project, the client got a successful outcome. They also got lucky. Those two things are not always the same.

Independent oversight doesn’t guarantee a smooth project. Nothing does. But it provides something the acceptance report never can — a clear account of what is actually happening at each stage, reported to the person who needs to know, while there is still time to act on it.

I have spent over a decade managing non-standard automation and logistics projects in China — projects that ran well, and projects that did not. I know what the difference looks like from the inside, because I have been inside both.

Now I work exclusively for the buyer, providing independent technical risk advisory for foreign manufacturers procuring custom equipment and systems in China.

If your company is planning a large-scale equipment project in China, the right time to understand what’s on the other side of your contract is before the work begins — not when someone calls you at ten o’clock at night to tell you it has gone wrong.

Honzer Industrial & Independent Risk Consulting Suzhou, China

#NonStandardAutomation #ProjectManagement #ManufacturinginChina #RiskManagement #ForeignManufacturers #EquipmentProcurement #LogisticsSystems #IndependentRiskAdvisory #ChinaManufacturing #FactoryAutomation