Don't replace employees in the middle of the project!
Article#: 00023
Date: 2020-07-18
Author: Radim
It is very inefficient to replace employees before completing a project.
Recruit the right people.
Engage people who like to do their jobs completely.
It can lead to unexpected problems in the project if an involved person leaves the project before the project is completed.
Make sure that your candidate is a type of a "completer" guy before you hire him or her.
Ask for references and contact people who have previously worked with the candidate and ask them:
- Whether the person met deadlines.
- Whether the person gave 100% complete results.
- How the communication with the person was.
- Whether there were some crisis situations with the person.
- Whether they would hire the person again.
If you've hired a responsible person, he or she will endeavor to perform the task completely.
It is usually not convenient to replace an assigned person because he or she is late with the task.
Check the progress of the project regularly to see if it is moving forward.
Does the assigned person strive to complete the task?
Ask the assigned person for their ideas on how to speed up the progress.
Help when the person asks, but let the assigned person do the job.
© Radim-Automation, 2020–2025. All rights reserved.
Sharing of this article is permitted with proper attribution (link to the original page).
Related previous articles:
- Develop a sense of responsibility!
- Recruit and retain the best employees!
- Get the things done with a small, motivated team!
Related next articles:
- Assign tasks efficiently!
- Get and stay in the flow!
- Realize every good idea ASAP!
- Keep the answers to the question "Why"
- I can see what you can not see
- Store email messages in the project folder!
- Do you really want to start with this?
- Is the way really the goal?
- Prepare a good project plan and keep it up to date!
- Write down your best practices and processes!
- Set your goals for today, tommorow, this week ...
- Are the people planned for this task really available?
- Appoint a representative!
- Who knows it?
- Write and accept only readable code!
- Use a usefull styleguide!
- Why do automation projects fail?
- Project leader
- Learn from your journey!
- Knowledge gained from a completed project is priceless
- Visual modeling
- My boss was a hero
- Maintain order in the program code
- Dedicated employees
- An irreplaceable employee
- Hidden dangers during commissioning
- The false illusion of rapid progress
Comment#: 00001
Date: 2022-12-26
User: Radim
"It is important to distinguish between adding resources to a project that is in trouble and simply reacting in a "knee-jerk" fashion by increasing funding. It is true that, conscientiously applied, additional resources in the form of personnel, support, and money can help a project. This is particularly true in situations in which initial funding was too low, throwing the project's completion into question from the beginning. Howerver, before simply reacting in a panic mode to project troubles, the first step is to conduct a realistic analysis of where the project currently is, how it got there, and how additional funding can bring it back on target."
- Jeffrey K. Pinto, Om P. Kharbanda. Business Horizons (1996). How to fail in project management (without really trying) (Page 50).
Comment#: 00002
Date: 2023-07-11
User: Radim
"New risks are also emerging in automated production, because who will restart a plant or even just a machine if the staff responsible for it at the time of shutdown are no longer working in the same plant. The transfer of knowledge, for example about the last software versions or settings, becomes indispensable. If you do not have the processes and the right solution in place, you risk everything. At this point, trends such as deploying increasing amounts of robots can only help to a limited extent, because even robots are dependent on updates and a certain level of maintenance."
- Curated by Statista, supported by octoplant by AUVESY-MDT. No Fatalism in Manufacturing. Exciting Insights from Leading Studies. (Page 5)
- https://info.auvesy-mdt.com/hubfs/Statista%20ePaper%20EN%20-%20AUVESY-MDT.pdf
Comment#: 00004
Date: 2023-08-25
User: Radim
"We all have ideas. Ideas are immortal. They last forever.
What doesn't last forever is inspiration. Inspiration is like fresh fruit or milk: It has an expiration date.
If you want to do something, you've got to do it now. You can't put it on a shelf and wait two months to get around to it. You can't just say you'll do it later. Later, you won't be pumped up about it anymore.
If you're inspired on a Friday, swear off the weekend and dive into the project. When you're high on inspiration, you can get two weeks of work done in twenty-four hours. Inspiration is a time machine in that way.
Inspiration is a magical thing, a productivity multiplier, a motivator. But it won't wait for you. Inspiration is a now thing. If it grabs you, grab it right back and put it to work."
- Jason Fried, David Heinemeier Hansson. 37signals (2010). Rework.
Comment#: 00005
Date: 2023-10-04
User: Radim
"Never discourage anyone who continually makes progress, no matter how slow."
- Plato
Comment#: 00007
Date: 2023-10-06
User: Radim
"Having the right boss early in your career is a huge blessing."
- Sandeep M.
Comment#: 00008
Date: 2024-03-25
User: Radim
Remove the "ballast" from the program!
Only include things in the program that are really needed. Unnecessary parts of the code in the program become obsolete, untested, raise unnecessary questions and are a source of ambiguity.
Sometimes it is a good idea to try more than one way in practice to find out which way is the best. However, once we have decided on a particular approach, it is important to consolidate our methods and remove the outdated ones. By removing "ballast" from the program, we eliminate potential sources of confusion and improve the overall quality of the code.