Related Posts
More Posts
Is there such a thing as "insurance law?"
Best resource to learn SQL?
Additional Posts in Leadership
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Is there such a thing as "insurance law?"
Best resource to learn SQL?
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site

Scan your QR code to download
Fishbowl app on your mobile

Hi!
Is him being “slow” actually a problem? Is his pace negatively impacting the results? What would be different if he were to be a bit faster? I think it would be important to start with answering these questions.
Then, depending on your answers, you may look into:
- are you (and other involved) setting clear deadlines and expectations for him?
- did you have a chat with him to inquire what support he might need in order to speed up a little bit?
- what’s causing him to be “slow”? Maybe there’re some steps he’s been currently taking that aren’t as necessary.
- what help he might need with his prioritising and time management?
Some ideas to look into. All the best :)
.
If this is an issue, it's important to identify the root cause, then come up with a solution. Maybe the issue is training, maybe it's staffing, maybe he's not aware that he's working too slow, maybe the deadlines aren't clearly defined, maybe the processes are different than at his old job and he hasn't figured it all out yet, etc. Or maybe he's just slacking.
The most important thing is to bring it up to him; if he doesn't know there's a problem, he's not going to know to address it.
Making sure deadlines are communicated is importation. If you do a check-in, let them know the feedback you received is mostly good except for timely responses.
In addition to all the above, the military has a saying, "Slow is smooth, smooth is fast"
Maybe so long as he gets his sh*t done and it's done well, Def have the conversation with him and see where and how you could set the expectation to see if he could gradually get faster without loss of accuracy?
Also, as part of the root cause search, it could be a number of issues, internally (E. G. previous company culture as suspected; was a toxic place where the tiniesr formatting error = reaming a new hole) external, (E. G. Your systems suck and everything is manual when other places are already automating and/or have better equipment/apps with productivity leaps).
Is their quality at the right level or too high?
Do they miss deadlines?