Technical Excellence Is Not Enough
A mechanical engineer who produces technically excellent designs but cannot communicate them effectively to manufacturing, quality, and sales will consistently see those designs fail to reach their potential. Manufacturing will interpret ambiguous drawings in ways the designer did not intend. Quality will flag issues that the designer could have prevented with a brief conversation. Sales will make commitments based on incomplete understanding of design constraints, creating customer expectations that engineering cannot meet.
Cross-functional communication is not a soft skill that is secondary to technical competence — it is a force multiplier that determines how much of your technical work actually results in a good product reaching a customer. This article covers the communication approaches that work in practice with each of the three major engineering counterparts: manufacturing, quality, and sales.
Working with Manufacturing: The Communication That Prevents Rework
The most costly failures in design-manufacturing communication are discovered after fabrication has started. A machinist who encounters an ambiguous drawing will either stop and ask (causing a delay) or make a reasonable assumption and continue (potentially creating a nonconformance). Neither outcome is acceptable — both were preventable.
Communicating Design Intent, Not Just Specifications
Manufacturing engineers and machinists need to understand not just what dimensions are specified, but why certain dimensions are critical and what the function of each feature is. This knowledge allows them to make intelligent decisions when unexpected situations arise during production.
- When releasing a drawing with an unusually tight tolerance, include a brief note explaining the function: "Ø32H7 bore — clearance fit with bearing OD per bearing manufacturer specification. Tolerance is critical for bearing function." This is not standard drawing practice, but a brief conversation or fabrication note achieves the same result.
- When a part has features that interact functionally (mating surfaces, seal grooves, locating pins), communicate the assembly sequence and how features are used. Manufacturing engineers who understand assembly can often identify producibility issues before they become problems.
- Walk through new drawings with manufacturing engineers before release, not after. A 30-minute conversation before fabrication begins costs far less than a nonconformance and rework cycle.
The Right Way to Request Manufacturing Input
Manufacturing engineers respond well to specific questions and poorly to vague requests for review. "Can you check this drawing?" results in a superficial check. "I need to hold ±0.02 mm on this bore diameter — is that achievable with your standard turning process, or do we need to discuss an alternative approach?" results in a substantive technical conversation. Specific questions show respect for the manufacturing engineer’s expertise and get useful answers.
Working with Quality: Building a Partnership, Not an Adversarial Dynamic
The relationship between design and quality is frequently adversarial in practice and collaborative in principle. Design engineers sometimes perceive quality as a function that slows things down and finds problems that were not problems. Quality engineers sometimes perceive design as a function that creates unverifiable specifications and resists inspection feedback.
Both perceptions are addressable through communication.
Involving Quality in Design, Not Just Inspection
- Include quality engineers in design reviews for complex new products. They will identify inspection access issues (features that cannot be measured without special fixtures) and tolerance requirements that do not match inspection capability before the design is released, not after.
- When specifying tolerances, ask quality: "Do you have the gauging for this measurement?" A Ø50H7 bore tolerance of ±0.013 mm requires a calibrated bore gauge or CMM measurement. If that capability doesn’t exist in your facility, either the tolerance must be changed or the measurement capability must be acquired.
- When a quality escape occurs (a defect that reached the customer), engage quality proactively rather than defensively. Treat the investigation as a collaborative problem-solving exercise. Designers who are defensive during quality investigations damage the relationship and reduce the quality of the root cause analysis.
How to Handle Quality Feedback on Design
Quality engineers sometimes provide feedback on design issues that designers believe are within acceptable tolerance. The productive response is to evaluate the feedback technically before accepting or rejecting it. If the quality engineer’s concern is valid, acknowledge it and address it. If it is not valid, explain the technical reasoning clearly: "The surface roughness on this bore is intentional — the specification requires Ra 3.2 μm to retain lubrication. Smoother would actually reduce component life." Clear technical explanation is more effective than dismissal.
Working with Sales: Translating Technical Reality into Customer Communication
The design-sales communication gap creates some of the most expensive product problems. Sales engineers who do not understand design constraints make commitments that engineering cannot fulfill. Design engineers who do not understand customer requirements create products that technically meet specifications but fail to satisfy the customer’s actual need.
| Communication Scenario | Engineering Approach | Expected Outcome |
|---|---|---|
| Sales requests faster delivery than engineering schedule allows | Explain what is driving the schedule; offer specific options (reduced scope, parallel work) with trade-offs | Informed decision with realistic expectations |
| Customer requests a technical modification mid-project | Assess impact (cost, schedule, performance) and provide a clear written summary before committing | Change is managed with full stakeholder awareness |
| Sales promises a feature engineering hasn’t designed yet | Clarify technical feasibility immediately; document the commitment and the engineering response in writing | Problem surfaced early rather than at delivery |
| Customer reports a field problem through sales | Request the original equipment ID and detailed symptom description; avoid second-hand technical diagnosis | Accurate problem definition for root cause analysis |
Making Technical Communication Accessible to Sales
Sales engineers are typically not trained in mechanical design. Communicating technical constraints in a way they can use and convey to customers requires translation, not simplification. The constraint "the frame cannot support a load greater than 500 kg at 1.0 m from the mounting face" is a technical statement. "If the customer needs to place a 600 kg load at that distance, we need to redesign the frame — here is what that would cost and how long it would take" is a business statement that sales can use. Both are accurate; only the second is actionable for a non-technical audience.
Written Communication: The Engineering Record
In cross-functional engineering work, the written record is as important as the conversation. Verbal agreements about technical requirements, change approvals, and scope decisions are consistently the source of later disputes. Build the habit of following up significant verbal decisions with a brief written summary — an email or message that confirms what was agreed and assigns actions.
This is not about distrust. It is about the fact that people remember conversations differently, especially when there is time pressure and multiple topics were discussed. A written summary ensures alignment and creates a record that can be referenced when questions arise weeks later.
FAQ
Q: How do I handle a situation where a manufacturing engineer insists a tolerance is not achievable, but my analysis shows it is required?
Start by verifying your analysis is correct and that the tolerance is genuinely required for function. If it is, engage collaboratively: share the analysis, explain the functional requirement, and ask the manufacturing engineer to propose an alternative if one exists. Sometimes the answer is a process change (grinding instead of turning), a fixture investment, or a design modification that achieves the function with a more producible tolerance. If the tolerance is truly required and not achievable, the right answer is to escalate to a joint engineering decision, not to override the manufacturing engineer’s assessment unilaterally.
Q: What is the best communication approach when delivering bad news to sales or management about a design problem?
Lead with the problem statement and the proposed path forward, not with a lengthy explanation of what went wrong. "We have found a design issue that will require a two-week schedule extension. Here is what we know, here is what we are doing to fix it, and here is the revised timeline." This framing is more effective than a narrative that starts with the history of the problem. Management and sales need to understand the impact and the plan — the technical details come after, for those who want them.
Q: How do I build better working relationships with departments that have historically been adversarial with engineering?
Start with small acts of genuine collaboration. Ask for manufacturing or quality input on a design before it is finalized. Acknowledge valid feedback publicly and credit the person who provided it. Show up to manufacturing or quality problems as a partner looking for solutions rather than a defender of the original design. These behaviors change the dynamic over time better than any formal process or team-building exercise. Trust between functions is built in individual interactions, not in meeting rooms.
コメント