Introduction
After years in mechanical design, certain ways of working become second nature — not because they were taught, but because trial and error in real projects made them indispensable. This article records seven principles I have carried through my career as a design engineer. They are not rules. They are what has consistently worked.
1. Write in a Notebook Every Day
I have kept a daily work notebook from early in my career. It started as a way to not forget things. Over time it became the place where I structured my thinking about the day and looked back at how problems were solved.
Looking back at old notebooks, I can trace every time I was stuck and how I got unstuck. That record is why I do not make the same mistake twice. No special system is needed — date, task reference, status, and next action. That is enough.
2. Ask “Why” Consistently
When given an instruction or inheriting a design decision, I ask why. “Because it has always been this way” is not a design rationale — it is a gap in understanding. The ability to explain the reason behind every dimension, material choice, and configuration in your own words is what separates an engineer who can defend a design from one who can only execute instructions.
When the answer is not known, that is information too. Ask, research, and build the understanding — it compounds over a career.
3. Report Mistakes Quickly
When a design error is discovered, I report it promptly. The temptation to delay — hoping to have a solution before telling anyone — makes the situation consistently worse. The damage from a mistake discovered at manufacturing is far larger than the discomfort of reporting it early.
Prompt, honest reporting of problems is not a sign of incompetence. Over time, it builds a reputation for reliability that has more value than any individual technical achievement.
4. Design for the Person Who Will Build It
When drawing, I think about the machinist receiving the drawing. Not “does this drawing make sense to me?” but “can a machinist I have never met build this correctly from this drawing alone?”
This shift — from designer perspective to manufacturer perspective — changes the way you annotate dimensions, place notes, and specify tolerances. It is the single habit most consistently praised by manufacturing teams I have worked with.
5. Keep Records
Calculation sheets, meeting notes, design decisions, change history — I document them. Not comprehensively, but consistently. The practical benefit: when a design needs to change six months later, the reasoning behind the original decision is still accessible. Without records, every change starts from reconstruction instead of improvement.
6. Accept Change as Normal
CAD tools change. Standards are revised. Client requirements shift. The engineers who struggle most are those who are most attached to how things were done before. Adapting to new tools and new requirements quickly — while maintaining the core engineering judgment that does not change — is what keeps a career useful and interesting over decades.
7. Bring Your Best Work Today, Not Perfect Work Tomorrow
Not every day produces excellent work. Fatigue, complexity, and distraction are part of the job. The standard I hold is: bring the best work available to me today. Consistently adequate is more valuable than occasionally excellent. The notebook records prove that good and bad days accumulate into a body of work that is larger than any individual day’s output.
Closing
These principles were not handed to me. They developed through mistakes, corrections, and the slow accumulation of field experience. Your principles will be different — formed by your specific work, your industry, your team. The process of forming them, through deliberate reflection on what works and what does not, is itself the career development that no course or certification can replace.
FAQ
Q. How do you maintain motivation through long, difficult projects?
A. Focus on today’s output, not the project’s end state. The notebook habit helps here — when you can see the week’s progress concretely, the distance to completion feels less abstract. Difficult projects also produce the most growth; the hardest periods are usually the most valuable retrospectively.
Q. Why is “why” such an important question in engineering?
A. Because design judgment — the ability to make good decisions when the situation does not match any textbook case — develops through understanding reasons, not memorizing procedures. An engineer who understands why a safety factor of 3 is used can adapt appropriately when conditions change; one who only knows “use 3” cannot.
Q. How do you build a habit of keeping records?
A. Start with three categories: calculation notes, meeting summaries, and design change rationale. Write them immediately after the event, not from memory hours later. When you first need to retrieve a record you wrote three months ago and it is there, the habit reinforces itself.
コメント