Over the years, I’ve met many mechanical design engineers with vastly different mindsets. Some see themselves simply as executors—professionals who design exactly what they’re told, no more, no less. If the product manager asks for a small green apple, they design a small green apple. And if it turns out that a green apple isn’t what the market needed? That’s someone else’s problem—“I just did what I was told.”
But I’ve also worked with engineers who take a very different approach. When asked for a small green apple, they respond with questions: Why an apple? Why green? Why small? What’s the customer’s actual situation? Are they even hungry—or just thirsty and in need of water instead? They go beyond the immediate request to understand the deeper need, examine market alternatives, consider new technologies, and suggest tweaks to improve cost or functionality.
Sometimes, this attitude upsets the product owner. “I’m the product owner—how dare you question my decision? Just build what I asked for!” And so, many engineers are left wondering: What is the right thing to do?
The Engineer’s Role: More Than Execution
There’s a famous saying, often attributed to Napoleon: “Every private in the French army carries a field marshal’s baton in his knapsack.”
To me, this doesn’t mean every soldier aspires to command, but that every individual should think from a higher level. A private following an order to advance should understand that the real goal isn’t movement—it’s to capture the hilltop, set up artillery, and change the course of battle.
Likewise, a mechanical engineer must understand the purpose behind the product, not just its surface-level specifications.
A Framework for Thoughtful Engineering
1. Understand the Purpose Start by interpreting the product definition through the lens of the customer’s situation. Why was this product specified this way? What essential need is it meant to fulfil?
2. Translate into Engineering Terms Once the purpose is clear, translate it into engineering language. Ask:
- Are the specs too high or too low for the use case?
- Is there a better alternative to meet the need?
- Is there a more cost-effective solution?
- Is there a newer technology with better performance?
- Is this practical to manufacture and reliable over the product’s lifecycle?
3. Align with the Product Owner Go back to the product owner with your insights. Confirm the product definition and share constructive feedback. Offer data-driven suggestions to improve the outcome without undermining the product owner’s role.
4. Implement with Clarity Once alignment is achieved, implement the design confidently. This phase becomes far more efficient when the first three steps are followed.
Unfortunately, in many organisations, engineers jump straight to step four—implementing without truly understanding the context. This often leads to confusion, misalignment, and products that fail to hit their mark.
Don’t Overstep—Respect the Product Owner’s Role
It’s essential not to overdo it. Respect the expertise and responsibility of the product owner. Often, a great deal of research and validation has gone into defining the product, even if it’s not immediately visible to the engineer. Constructive input should be delivered with humility and emotional intelligence. The goal is to collaborate, not confront.
Three Levels of Mechanical Design Engineers
Level 1 – The Executor: Designs the product exactly as defined, with minimal questioning or feedback.
Level 2 – The Inquirer: Seeks to understand the logic behind the product definition and offers some feedback.
Level 3 – The Partner: Fully understands the customer’s essential needs, proactively collaborates with the product owner, and contributes to product definition, technical strategy, and practical implementation—all while ensuring the design is manufacturable and cost-effective.
The higher you go, the more impact you make—not only on the product, but also on your growth as an engineer. Great design comes from asking the right questions, not just drawing the right lines.