- Introduction
- Wall 1: Too Many Part Numbersu2014Can’t Track the Whole
- Wall 2: The Design Change Process Is a Black Box
- Wall 3: Drawing Review Without a Checklist
- Wall 4: No Ability to Estimate How Long Things Take
- Wall 5: Getting Stuck Because You Don’t Know What to Ask
- Summary: Year-One Walls Are Future Assets
- FAQ
- Related Articles
Introduction
The first six months of working as a mechanical engineer are, honestly, one obstacle after another. The gap between what you learned and what the job demands. Being handed a drawing and having no idea where to start. Watching senior engineers do things “automatically” that you can’t even see yet.
I started my career as a mechanical designer employed at an engineering firm, assigned on-site at a large manufacturer. It was an unusual starting position, but the “year-one walls” I hit were essentially the same as any new engineer faces.
Looking back at the TODO notebooks I kept at the time, I can see clearly where I got stuck. This article draws from those notes to name five walls that first-year mechanical engineers almost universally hitu2014and what actually works to get past each one.
Wall 1: Too Many Part Numbersu2014Can’t Track the Whole
Why It Happens
Mechanical design environments involve dozens or hundreds of part numbers for a single product. In year one, you drown in this. My notebooks from that time are filled with part numbersu2014tasks I wrote in the morning that had become a tangle by the end of the day. I was trying to track the status of multiple part numbers in my head simultaneously. That was the problem.
How to Get Past It
Build your own status-tracking table for part numbers. What I eventually landed on was a simple handwritten list:
Part# | Task | Status | Deadline | Notes ------|------|--------|----------|------ XXX | Drawing review | Done ✓ | Dec 15 | YYY | Change request | Awaiting reply | Dec 18 | → sent to Engineer A ZZZ | New drawing | In progress | Dec 20 |
The key is always writing the status—not just whether something is done, but whether it’s pending someone else’s action, actively in progress, or on hold. Once you make the invisible visible, the workload stops feeling uncontrollable.
Wall 2: The Design Change Process Is a Black Box
Why It Happens
Every mechanical design organization has a “design change flow”—a sequence of steps that must be followed when a drawing is revised. In year one, this process is completely opaque. My notebooks had traces like: “alignment check → drawing A check → content check → drawing B check → final check.” But I had no idea who did each step, what each document was, or where in the sequence I needed to act. Missing a step means reworku2014and you only find out you missed it when someone asks why things are stuck.
How to Get Past It
Draw the flow as a diagram and write it in your own words. When a senior explains the process, don’t write bullet pointsu2014draw a box-and-arrow flowchart on the spot. Then annotate each step with “what do I do here specifically?” Having a visual flow lets you always answer: “where in this process am I right now?”
Wall 3: Drawing Review Without a Checklist
Why It Happens
When someone hands you a drawing and says “check this,” year-one engineers are lost. Senior reviewers glance at a drawing and immediately spot problems. That pattern-matching comes from experience. What it’s built onu2014the specific things being looked foru2014is invisible to the new engineer. You scan the drawing, nothing jumps out, you say “looks fine,” and later get told “why didn’t you catch this?”
How to Get Past It
Build your own checklist incrementally. Start with five or ten items. Every time you receive a comment on something you missed, reflect on why you missed it and add it to the list. My personal early review categories:
- Dimension gaps and contradictions: Are all dimensions present? Do the numbers add up?
- Machinability: Can this shape actually be cut with available equipment?
- Assembly sequence: Can the part physically be assembled in the order shown?
- Tolerance-function alignment: Does this tolerance serve an actual functional requirement?
- Standardization: Does a similar part already exist that could be reused?
A checklist built from your own mistakes is worth more than any generic one. The habit of building it is what matters mostu2014the three-year version of you will thank the first-year version.
Wall 4: No Ability to Estimate How Long Things Take
Why It Happens
When told “have this drawing checked today,” a first-year engineer has no idea whether that’s realistic. How long does reviewing three A3 drawings take? How much time does processing a design change for one part number require? With no reference points, you either overcommit and exhaust yourself, or you hedge everything and seem slow.
How to Get Past It
Record how long tasks actually take. I started tracking actuals in my notebook:
Drawing review (3x A3): 1.5 hrs Part number list organization (20 items): 0.5 hrs Design change processing (1 case): 2 hrs
After two or three months of this, you accumulate your own personal time data. Once you can estimate, scheduling becomes dramatically easieru2014and you become someone who can reliably commit to deadlines.
Wall 5: Getting Stuck Because You Don’t Know What to Ask
Why It Happens
This may be the hardest year-one wall. You’re stuck, but you’re afraid asking will make you look incompetent. Or worse, you’re not even sure what your question is. So time passes and nothing moves. (I felt this even more acutely as an external engineer at a client siteu2014asking the “wrong” thing felt higher-stakes when I was an outsider.)
The reality: almost no senior engineer minds being asked by a first-year engineer. The actual problem isn’t the askingu2014it’s not knowing how to formulate the question.
How to Get Past It
Lead with your hypothesis: “I was thinking of approaching this with method Y because of reason Zu2014does that create any issues?”
Instead of asking “how do I do X?”, you’re asking “is my proposed approach to X correct?” This signals that you’re thinking. It also makes you far easier to answeru2014the other person just needs to confirm or redirect, rather than explain from scratch. You reduce their effort and build your reputation simultaneously.
Another useful technique: write out your question in your notebook before asking. The act of writing often resolves the problemu2014you realize mid-sentence what was actually confusing you.
Summary: Year-One Walls Are Future Assets
| Wall | Core of the Solution |
|---|---|
| 1: Too many part numbers | Build a personal status-tracking table |
| 2: Design change flow is opaque | Draw it as a diagram; know where you are at all times |
| 3: No drawing review framework | Build and incrementally grow a personal checklist |
| 4: Can’t estimate task duration | Track actual time on every task type |
| 5: Don’t know what to ask | Lead with a hypothesis before asking |
The walls you hit in year one are a record of what you didn’t know yet. That record is the foundation your second and third year are built on. Every frustrating moment you log becomes a data point that makes the next version of you faster and more capable.
FAQ
Q: What are the most important things to learn in the first year of mechanical design?
A: Three fundamentals: how to read engineering drawings, basic JIS symbols, and CAD fundamentals. In terms of behavior, the most important thing is building the habit of asking questions immediately when something is unclearu2014not sitting on confusion.
Q: I’m getting criticized constantly in my first year and it’s demoralizing. What should I do?
A: Getting criticized in year one is completely normal in design environments. Three habits change this quickly: take notes during feedback, read them back aloud to confirm understanding, and never make the same mistake twice. Senior engineers notice these behaviors and their perception shifts.
Q: What skills should I develop before the end of my first year?
A: Drawing creation, design change processing, and solid CAD operation are the top three. Beyond that, establishing a personal system for TODO management and reliable communication habits will accelerate everything that comes after.
コメント