2025-08-23

Reason #9: Seventy-Two Percent of Your Week Is Not Engineering

You pictured yourself at a whiteboard, sketching mechanisms, sizing shafts, running simulations until something elegant fell out. Then you got the job. In the only peer-reviewed time-use study of practicing engineers in a complex product environment, researchers tracked thirty engineers through their actual workweeks and found that problem-solving and design occupied 28 percent of their time (Crabtree, Baid, & Fox, 1993). Documentation alone took 23 percent. Meetings, planning, information gathering, and negotiating requirements consumed the rest. For every hour you spend doing what you trained for, you spend roughly two and a half hours on the work that surrounds it. See Reason #26.

That study was conducted in 1993. The ratio has not improved. A 2023 survey of over 150 engineering managers at manufacturing companies found that approximately 45 percent of engineering time now goes to feeding data into PLM, ERP, and ECO platforms (Techconsult, 2023). The systems multiplied. The design share did not.

The reason is not culture. It is physics. Mechanical engineering produces physical objects, and physical objects require physical verification. When you change a wall thickness, you do not push a code commit and watch an automated test suite return green in four minutes. You initiate an ECO. You revise the drawing. You update the BOM in ERP. You notify the supplier. You wait for new samples. You update the test fixture if the geometry changed. You write a test protocol. You run the test on calibrated equipment traceable to NIST standards. You write the test report. You route the deviation if the result is borderline. You update the DFMEA. You trigger a PPAP revision if the part is production-bound. Then you pass a gate review before the change is released. That is not bureaucracy. That is matter. Matter must be verified in a physical medium, and every verification generates a document. See Reason #36.

Software engineers face overhead too. A 2025 survey of 1,200 software engineers found that only 16 percent of their time goes to writing code and building new features (Chainguard, 2026). But the character of their overhead is categorically different. Their version control is automated. Their changelogs are auto-generated. Their deployment pipelines run continuous integration that catches regressions in minutes. A software fix can go from idea to production in hours. An ME design fix goes from ECO to gate review in weeks, sometimes months. The documentation is not a management preference you can optimize away. It is a structural consequence of working in the physical world, where a test requires a chamber, a chamber requires a calibration, a calibration requires a certificate, and a certificate requires a signature. See Reason #51.

In automotive, a single component launch under APQP runs through five formal gate phases, each requiring completed deliverables before the project advances (AIAG, 2024). A single PPAP submission requires eighteen distinct mandatory elements, from DFMEA to process flow diagram to control plan to dimensional results to the Part Submission Warrant (AIAG, 2020). Each element is a document you prepare, review, revise, or sign. Eighteen documents for one part. Your program has dozens of parts. The third edition of APQP, released in 2024, added a gated management appendix with documentation checklists and a new requirement to review sub-tier supplier APQP activity, which means you now document your supplier's documentation. See Reason #37.

This does not get better with seniority. Senior MEs own more gates, which means they prepare more gate review packages, not fewer. The ASME study found documentation frustration was universal across tenure levels. The 28 percent does not become 50 percent at year ten. It becomes 28 percent with higher stakes and a longer signature chain. You trained for the 28 percent. The market hired you for the 72. See Reason #33.


References:

AIAG. (2020). Production Part Approval Process (PPAP) manual (4th ed.). Automotive Industry Action Group. https://www.inspectionxpert.com/ppap

AIAG. (2024). Advanced Product Quality Planning (APQP) manual (3rd ed.). Automotive Industry Action Group. https://www.aiag.org/docs/default-source/quality-/new-aiag-apqp-cp-what-you-need-to-know-to-be-ready.pdf

Chainguard. (2026). Engineering reality report 2026. https://byteiota.com/engineers-spend-84-of-time-on-non-coding-tasks-crisis/

Crabtree, R. A., Baid, N. K., & Fox, M. S. (1993). Design engineering: Problems in coordination. Proceedings of the JSME/ASME Design Theory Workshop, Tokyo. http://www.eil.utoronto.ca/wp-content/uploads/public/papers/jsme.pdf

Techconsult/Zuken. (2023, May 11). Design time vs. admin overheads: How to win the battle by closing the gaps. https://www.zuken.com/en/blog/design-time-vs-admin-overheads-win-war-closing-gaps/


An empty ancient amphitheater with rows of stone and wooden seating curving around a bare central stage.




No comments:

Post a Comment

Reason #75: It's a Vocation Wearing a Profession's Suit

You took the same calculus sequence as the pre-med students. You took the same physics as the future physicists. You survived thermodynamics...