What tools or techniques do you use to ensure effective knowledge transfer within engineering teams, especially when team members leave or the project transitions? We try to maintain adequate documentation and deploy standard trainings.
1
I'm a junior engineer, but I inherited a project mid-construction because the designer left. I wasn't around for the early phases, but now I’m running the site meetings. I'm stressed about the technical gap and being asked questions I don't know the answers to. I don't want to appear clueless in front of the clients, even though I am. Is it okay to say that I don't know, but I will get back to them? Or does that look unprofessional?
My manager takes my work (which takes hours), feeds it to AI, and tells me to match the AI's output. Except the AI version makes zero sense for the actual project. I'm so annoyed and checked out that I'm skipping crucial steps in my workflow, making things worse. I used to love this work, but now I’m losing all passion. Has anyone dealt with a boss like this, or is it time for me to quit?
How do you know when it’s time to leave a job vs. stick it out and push through a rough patch? For me it comes down to whether the core reasons I took the role are still intact. If the work is still interesting and the people are decent, a rough patch is survivable. But if I’m dreading Mondays every single week, that’s usually a signal worth listening to.
Often the hand over is only a few weeks in length. Generally, someone will write a detailed report of each project they are working on giving a list of each document and it's relevance to the project. Then there is a hand over meeting (or a couple). It's tough when some projects are years in the making, but it seems to be working more or less.
For sure