Related Posts
Visual Storyteller
Hi All, My Junior has decided to put paper, as she wanted to pursue Cdac course from Sept-22. She just informed that she signed a bond of 2 years and currently she has completed 1.7 years in HCL. What should she do now? Results is on 10-aug and she decided to put paper on that day itself (Earlier she told the same to Sr. manager) Kindly suggest if any action would be taken by HCL OR No experience letter would be shared with her. Regards, HCL Technologie HCL Technologies HCL Technologies
Previous GSAPers how were you notified? Phone?
Should I shave my beard for MBA interviews?
Hi Fishes, Wish you a great day ahead 😊🤗.
Pro
Chief
Additional Posts in Mechanical Engineering
Hmm. I’m attracted to engineers..
Bowl Leader
Bowl Leader
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Having a background and some idea of what is being discussed is great. Project managers that I work with focus on the higher level/ big picture, and while it can be great to have a different insight into the specific details, it can also be good to just let the others at it.
Thanks for sharing
It is critical to have a functional understanding of the product being deployed / designed. You obviously don’t need to understand every detail, as that is the role of other engineers. If someone tells you that there is a problem with “X”, you need to understand how that plays into the bigger picture and who to engage to drive resolution.
You should try to understand what is going on at a high level but you don't need to be able to do every step yourself. The point of project managment is to facilitate communication between resources, maintain schedules, and help resolve issues.
I'm in electronics manufacturing. On our product development projects our project managers don't need to know how to code, design circuits, design housings, or program the machines that build them, but they do need to know what each of those groups do, how they interact with one another, and in what order they need to be completed.
If your company has its shit together you should have work instructions that define the project life cycle at a high level and you should know those forward and backwards. If they don't, you should be meeting with each individual group/discipline and trying to get an understanding of thier function, goals, and needs.
As an example, with me being in the manufacturing side I need to be able to build a product repeatably thousands of times per day. The guy that designs a housing in a cubicle off site should care about that but doesn't always. I need to recieve designs for DFM (design for manufacturability) review at a stage where my team can make recommendations and the suggested changes can still potentially be implemented into the design/prototypes.
If there isn't good cross functional communication and the schedule isn't followed, DFM might be skipped or too late and someone might tool a housing that doesn't go together well in production. At best it could be difficult and expensive to make, at worst it might not be buildable and result in a very long and expensive delay to go back and do the changes later.
Yes or you’re a bad pm
General knowledge is fine, what you really need to know is what they are supposed to do and what do they need before each team can do what they are supposed to do.