QM Management Depth (30) | Cross-Departmental Quality Drive: How to Get Others to Cooperate Without Management Authority

1. Three Rectification Orders, Zero Responses

A manufacturing company with annual revenue just over 400 million has 11 people in the Quality Department. At the management review in March 2026, the quality manager received six cross-departmental rectification tasks:

1. Increase the SMT process pass rate from 91% to 96%, responsible department: Production Department.
2. Complete DFM reviews before the trial production of new projects, responsible department: R&D Department.
3. Re-evaluate the list of A-class materials for exemption from inspection, responsible department: Purchasing Department. The other three tasks were assigned to Equipment, Warehouse, and HR, respectively.

A month later, during the re-inspection, none of the six tasks were completed, and the progress column uniformly read: "Pending cooperation."

He went to talk to each person and received three types of responses. The Production Department manager said, "Orders are booked until June, the production line can't stop for a day, who has time to do experiments with you?" The R&D Department said, "The client is pressing for the drawings, you handle the review yourself, and we can make changes after the drawings are done." The Purchasing Department said, "Who will sign off if there's a problem with the exempted materials? If your Quality Department provides a commitment letter, I'll exempt them on the spot." He reported this progress to the boss, who replied with a single sentence: "You need to coordinate."

The issue is that he has no authority to evaluate, appoint, or manage the budget of any of these three people. He only has the power to sign "disagree" on the release forms. However, once he really signs "disagree," the fire of delayed delivery will burn back to the Quality Department. This is the most typical deadlock in cross-departmental promotion: having veto power but no driving force.

2. Correct Three Misjudgments

Misjudgment One: Treating "no authority" as "no way," thus automatically switching to a begging mode. The characteristic of begging mode is: frequent communication, inefficient commitments, and relying on personal connections to get things done. The real difference is not in authority but in whether you can get the other party to include this task in their own risk list or evaluation form. A person can refuse a request, but it's hard to refuse a task that is already written into the meeting minutes with a date and their name.

Misjudgment Two: Attributing the problem to "poor quality awareness." Awareness is a result, not a cause. The Production Department manager is not unaware of quality; rather, in his evaluation function, "reducing downtime today" has a much higher weight than "reducing defect rate in three months." To change his behavior, you need to change the numbers in his equation, not just repeat the importance of quality.

Misjudgment Three: Relying on personal relationships to initiate actions. Relationship-based influence is a lubricant, not an engine. It can help you get your message across, but it can't complete the task for you. Moreover, it has a fatal flaw: it resets to zero with any personnel change, and all the rapport you've built up has to be rebuilt.

Once these misjudgments are clear, you can see that there are actually four sources of influence, ranked from most reliable to least.

Rule-based: System documents, inspection specifications, quality agreements, and customer CSR. These are things the company has signed off on, and using them doesn't require additional authorization because they are the authorization themselves. Customer CSR is especially strong—it's external pressure, and it's hard for cross-departmental teams to resist.

Data-based: Convert quality issues into the language of the other department. For production, it's downtime and rework hours; for R&D, it's the cost of later design changes; for purchasing, it's the claim amount and the premium for emergency purchases. The same issue, when explained in terms of money, has a much greater impact than when explained in terms of defect rates.

Political-based: Bring the issue to a meeting with decision-making authority, making the boss the arbitrator rather than the mediator. Many people are hesitant to do this, fearing it will be seen as complaining, thus getting stuck in the "you need to coordinate" loop.

Relationship-based: Daily reciprocal accounts. If you help the other party with something that is important to them but unrelated to quality, they owe you a favor. This is a bonus, not the main focus.

3. Four Actionable Steps

Step One: Translate "Please Cooperate" into "Three Sentences for the Other Party."

Before pushing any cross-departmental task, clearly write down three things: what the other party will gain, what they will have to pay, and what will happen if they don't act. Write these three sentences on an A4 sheet, not exceeding 200 words.

• Who does it: The quality manager himself, filling out each item individually, not delegating to a quality engineer.
• Standard: The other party can repeat these three sentences after hearing them, without asking, "What does this have to do with us?" If they start asking, it means you haven't calculated their costs and benefits clearly enough.

Step Two: Turn Verbal Requests into Responsibility Mechanisms.

Choose the most painful and quantifiable issue and create a simplified responsibility matrix: who executes, who reviews, who is notified, completion date, and escalation path. The key is to clearly define the escalation path—automatically escalate after a certain number of days, rather than relying on the quality manager to repeatedly follow up.

• Who does it: The quality manager drafts it, and the responsible department manager confirms and signs it.
• Standard: At least three tasks are included in the system documents or meeting minutes, each with a clear completion date and escalation trigger. Tasks without dates and escalation paths are not tasks but wishes.

Step Three: Borrow Power from Above, Once and Correctly.

When reporting to higher-ups, use an options format rather than a complaint format: present two options, A and B, list the required resources and potential consequences for each, and ask the boss to choose. The implicit goal is to push back the phrase "you need to coordinate"—coordination requires authorization, so please give the authorization or abandon one of the tasks.

• Who does it: The quality manager formally proposes this at the monthly business meeting or a special meeting.
• Standard: The boss clearly writes in the minutes, "Cooperation from a certain department is required, to be completed by a certain date." This line of text carries more weight than all your previous private communications.

Step Four: Build Small Wins in Horizontal Collaboration.

Proactively help the other party solve a problem that is important to them but unrelated to quality; co-sign the project results and share the credit.

• Who does it: The quality manager and quality engineers divide the work, each maintaining reciprocal accounts with two to three key departments.
• Standard: The other party is willing to co-sign the joint project and speak up for you at the next cross-departmental meeting. This is a sign that your influence has taken root.

4. What He Did Later, and the Cost

The quality manager reduced the six tasks to two, voluntarily giving up four less critical rectifications, and focused on improving the SMT pass rate and DFM reviews for trial production. This was a necessary tuition fee: pushing all six tasks at once meant none of them would move forward.

For the SMT task, he stopped talking about defect rates and instead created a cost conversion table: a 91% pass rate means approximately 18,000 defective units per month and about 2,300 rework hours, equivalent to an annual cash expenditure of 4.6 million yuan, with 70% of this cost attributed to the Production Department's manufacturing expenses. The Production Department manager asked for the first time in a meeting, "How many experiments do we need to run? I'll schedule the production." He had been waiting for this for two months.

The DFM task was even more challenging. He set DFM reviews as a prerequisite for trial production release—no review record, no release form. The R&D Department opposed this for two rounds; in the third round, he stopped discussing the process and instead presented the cost of later design changes for the past four projects: an average of 3.7 million yuan per project, accounting for 18% of the project's R&D costs, with 70% occurring after trial production. The R&D director himself proposed the solution of "moving the review to the A-sample stage."

There was a cost. The entire process took four months, two months longer than his initial plan. During this period, the Production Department complained to him twice about "interfering with delivery," one of which was escalated directly to the boss. When he first used the options format to report, the boss felt he was forcing a decision and did not respond for nearly three weeks. In his post-mortem analysis, he realized that if he had acknowledged a month earlier that the four less critical rectifications were not worth doing, the saved energy would have been enough to complete the first two tasks a month earlier.

5. Self-Inspection Checklist

• Can I clearly explain the "benefits, costs, and consequences of non-action" for each cross-departmental task on a single A4 sheet?
• How many of these tasks have been included in the system documents or meeting minutes with clear completion dates and escalation paths? (Fewer than three indicates reliance on personal connections)
• In my most recent report to the boss, did I use a complaint format or an options format? Did the boss provide clear authorization or a clear choice?
• Do I maintain reciprocal accounts with at least two to three key departments, or do I only appear when cooperation is needed?
• Do I have the courage to proactively cut those "non-painful" rectifications? Is the length of my task list exceeding my driving force limit?

When you have no management authority, rely on rules, data, and superiors to get tasks on the other party's list

Knowledge code: 13.1.2

Version: v20261013

Author: QTank QTank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.