To continue the conversation, ASCE Plot Points, a podcast that tells the robust story of civil engineering one civil engineer at a time, is in Season 2 and just yesterday posted an episode on the topic of making mistakes. You can listen to this episode here: https://news.asce.org/asce-plot-points-season-2-episode-6-the-art-of-making-mistakes/
Excited to hear what you all think of the episode (or even Season 2 of the podcast so far)!
------------------------------
Danielle Schroeder EIT, A.M.ASCE
Associate Engineer
Pennoni Associates
Philadelphia PA
------------------------------
Original Message:
Sent: 10-09-2019 13:24
From: Danielle Schroeder
Subject: Failure on Paper
@James Smith @Richard Lenz @Irfan Alvi these are all great answers and examples! Along the same topic, mistakes are also part of the design process that are bound to happen due to human nature. Thanks to our internal QAQC process and always having someone more senior checking my work, any mistakes I have made are picked up before submissions are due.
ASCE Plot Points, a podcast that tells the robust story of civil engineering one civil engineer at a time, is in Season 2 and is looking for answers on the following question: "What is the biggest mistake you've ever made on the job?"
If interested, email your answer as a voice memo to <maskemail>ASCENEWS@...</maskemail> for a chance to be featured in the next episode. I submitted an answer to one of the featured questions last season, so feel free to respond here or message me with any questions.
Also, thank you @Chad Morrison for starting this important discussion!
------------------------------
Danielle Schroeder EIT, A.M.ASCE
Associate Engineer
Pennoni Associates
Philadelphia PA
Original Message:
Sent: 09-30-2019 08:51
From: Chad Morrison
Subject: Failure on Paper
More great answers! Support from outside the profession is so important! Too often we find ourselves thinking inside a box. Sometimes, it takes someone outside to help us get out!
A well conceived final product is the ultimate goal. Recognizing pitfalls that were avoided along the way should be part of celebrating any success. It is so important that these obstacles are shared with all team members so that everyone in the office or professional community can learn and develop best practices.
------------------------------
Chad Morrison P.E., M.ASCE
Professional Engineer
Greenville RI
Original Message:
Sent: 09-18-2019 09:49
From: Richard Lenz
Subject: Failure on Paper
I have been retired now for more than 10 years. Ever since I started in the engineering business, working mostly on industrial and general building projects, the design effort has always included iterations and changes as it proceeded, mostly resulting from the necessary coordination with the other design disciplines and the client changing their mind or adjusting scope. Doing the design in phases with interim approvals is a big help, but "fast-tracking" the work, which now seems to be the "norm", makes this difficult, indeed. All of this perceived "inefficiency" has always been part of the work and will likely remain so. One can derive satisfaction from playing a significant role in controlling or managing all of this.
Also, the cost and unpaid effort to prepare proposals and negotiate for the work needs to be built into one's fee structure to remain profitable. In the firms I worked for, a 70% chargeable or billable labor ratio was normal. Maybe one day engineers and architects will be taught the business aspects of practicing as well as the technical. I was fortunate to learn a lot of this as a co-op student in the 60's. I got my BSCE and MS in school and my "MBA" on the job.
------------------------------
Richard Lenz
LM, ASCE, Retired
West Chester OH
Original Message:
Sent: 09-17-2019 17:48
From: James Smith
Subject: Failure on Paper
Chad,
Great topic! This is something that's a big part of Civil Engineering that no one really likes to talk about. From putting together proposals and bids that aren't accepted, to efforts that require tedious trial and error, to plan changes (for any myriad of reasons), disputes with sub-consultants or contractors or even clients, to projects like Design Build that involve the work of numerous individuals putting in countless hours of work that at don't pan out. Not succeeding is a big part of the job that every engineer will face on a weekly basis over their career.
I think the most important thing is to not focus on "failure". To college and high school students I focus on the fact that these should all be learning experiences. It may not make it less frustrating, but going forward hopefully you learn something. That some how next time you can avoid these pitfalls, be more efficient at your process, or save time and energy in the future on similar endeavors.
Another thing I try to stress to those in college and high school is that at least you're still getting paid. These problems arise there as well, just usually a much smaller scales. Of course this isn't always true. Not winning a proposal was time you may still be compensated for writing but it cost your company money without any return. Some disputes can end up costing money as well, at loss for you or other parties involved. But, in general, this "learning experience" shouldn't cost you your job provided you actually learn from it and as much as possible avoid it in the future.
Sometime though, you hit a rough patch where it all seems to hit at once. I've had this a few times in my career where things just don't seem to go well no matter what for days, weeks, or even months. When it hits like this, it really takes a toll on you. I know my wife noticed the change in my mood when it's happened. Not taking it home with you can be hard, but it's really important. Sometimes problems at home may be part of the issue as well. As much as possible focus on getting things right at home and if you can take some time for yourself. A long weekend can go a long ways to "recharge" yourself.
Don't be afraid to ask for help. Whether it's the insight of a mentor, spouse, parent, or close friend get their insight. Maybe you need to change your approach or maybe you need to rethink things altogether. I don't recommend changing jobs just because your having a rough time, but that doesn't mean you shouldn't consider it. One way or another it will pass. Just keep working hard and doing your best, that's all you can.
"When you reach the end of your rope, tie a knot in it and hang on" - Franklin D Roosevelt
------------------------------
James Smith P.E., M.ASCE
Design Engineer
Grand Rapids MI
Original Message:
Sent: 09-17-2019 11:10
From: Irfan Alvi
Subject: Failure on Paper
Chad,
Thanks for your response as well.
In my office, we generally don't release preliminary or unchecked calculations to clients, we only release final and checked calculations when asked to do so.
For concept study and preliminary design submissions, we usually provide reports, drawings, and cost estimates, but the drawings may only be prepared for a recommended alternative or a few top alternatives, with other alternatives described mainly in writing.
------------------------------
Irfan A. Alvi, P.E., M.ASCE
President & Chief Engineer
Alvi Associates, Inc.
Towson, Maryland
www.alviassociates.com
<maskemail>ialvi@...</maskemail>
Original Message:
Sent: 09-17-2019 10:27
From: Chad Morrison
Subject: Failure on Paper
Irfan, thank you for your response. I agree with all of your points. It is not my intention to portray a negative assesment, but rather invite a realistic discussion of what practice entails. It has taken me years to become comfortable with marking calcs and drawings as preliminary and releasing them outside of the office. As an EIT it is best to keep those which may contain engineering errors in house. As a senior engineer, releasing preliminary concepts to the whole team is necessary to provide the needed coordination. It was this solution that I successfully implemented recently that spurred these questions. It takes confidence to release something as preliminary and conceptual... rather than something that might be perceived by others as incomplete.
------------------------------
Chad Morrison P.E., M.ASCE
Professional Engineer
Greenville RI
Original Message:
Sent: 09-13-2019 16:16
From: Irfan Alvi
Subject: Failure on Paper
This assessment of engineering practice is much more negative than what I've experienced during my three decades in practice, working mainly on public sector projects, primarily related to transportation and dams. A few things to consider:
- Dividing projects into phases, such as concept study, preliminary design, and final design, enables more accurate estimation of the level of effort needed to complete each phase of a project, so that there are less surprises for both the designer and client.
- Practicing within an engineer's areas of expertise also enables reduction in uncertainty about needed level of effort, and results in more efficient iteration to develop good design solutions. And of course we're legally and ethically obligated to practice only within our areas of expertise.
- It's important to have clients who understand engineering, and such clients will usually be reasonable as far as approving extra work orders.
------------------------------
Irfan A. Alvi P.E., M.ASCE
President & Chief Engineer
Alvi Associates, Inc.
Towson, MD 21204
Original Message:
Sent: 09-12-2019 08:21
From: Chad Morrison
Subject: Failure on Paper
As engineers our practice is set up for failure. Not the catastrophic physical failure of a structure, but the failure of an idea on paper. A design that just does not take off. This type of failure could be as small as a limit state not met (requiring upsizing) or a completed structure design that is never implemented. Sometimes, it is within our control as engineers when we start off on the wrong track and after several iterations arrive at the right destination. This trial and error process makes time estimation difficult and can result in different engineers completing the work in different amounts of time. Sometimes, it is outside the control of the engineer, when the item is totally eliminated from the scope by the client. Sometimes the work is paid for and sometimes it needs to be written off.
How do we explain this aspect of engineering to our clients, professional peers, and the general public? How do we prepare students who are entering practice for this reality of design work? How do we as engineers learn to cope with failure on a daily basis without getting discouraged?
------------------------------
Chad Morrison P.E., M.ASCE
Professional Engineer
Greenville RI
------------------------------