A good bit of what we discuss here relates to day-to-day operations. While a lot of operations probably seems simple and obvious, it’s the number one issue I see in companies. I suspect you’ve experienced, owned or worked at a company whose operations are a disorganized mess. Common problems shouldn’t be common at all, right? Let’s see if we can chip away at a few of these and get your operations polished up.
Somewhere in your company, there’s someone who is “under performing”. Not doing their job, not doing it well, It might be that they’re not doing the work in what their peers would consider a normal amount of time. IE: They’re slow. Slow can be OK for some work, but sometimes it isn’t.
As managers / leaders, this is your responsibility. The cause doesn’t matter. If they aren’t doing their job, it’s because their direct manager isn’t finding out why, attempting to fix it and circling back to hold them accountable. Is their direct manager isn’t doing those things? Ultimately, that manager’s performance is your responsibility. Does the under performer work directly for you? If you aren’t finding out why this is happening and you aren’t holding them accountable, it’s your responsibility. While this may seem like a difficult source of hand-wringing and drama, it doesn’t have to be.
Sometimes, an employee doesn’t know what is expected of them. Not kidding. You might find this surprising, but a list of duties, deliverables and responsibilities is useful to an employee. Nothing says “This is what you are responsible for. I will be looking these things when I assess the quality of your work.” better than a list.
Maybe they need training. When you discuss that list of responsibilities with the employee, make sure they are confident that they can achieve those things and have the right skills to make them happen. If they can’t, find training for them.
Training didn’t help. Nothing did.
If training doesn’t improve their performance, a new role might. They might hate some aspect of their work – work that someone else might love to do. Guess who’ll do it better?
Find them a new role that fits who they are, what they can do, what you need, etc. If you can’t do any of that, help them find a role somewhere else. Few “bad hires” are bad people that you’d never recommend to someone else, but they do exist. It takes too long to find and hire a good candidate to simply discard them because you put them in the wrong role, or didn’t train them well.
EVERYONE else in the department (probably in the company), already knows this person needs a new role, more training, or a different job at a different place. They know you aren’t doing anything about it and they’re not happy about that. They know it affects the security of their job, among other things. They’re right to be disappointed.
Disasters in advance
We’ve all seen these. A big project is coming. There are obvious bumps in the road. No one says a word because predicting disaster is “not being a team player” or similar. To a point, that’s correct. Predicting disaster is of no value, but preventing them is huge.
There’s a better way. Ask everyone: “What could go wrong? What could cause this project to fail?” Make it clear that it’s a positive thing to produce this list, as you want to avoid the team player baggage. Discuss this for each step of the planning, creation, deployment, and ongoing operational stages.
Once you have that list, discuss each one. Not only will you be better prepared (and perhaps plug a hole), but you may end up figuring out an issue no one saw when the conversation started. You’ll also help everyone think about hardening their part of the project, no matter what that means. You may find that items on the “What could go wrong?” list end up as a standard task in that kind of project. Would your company benefit if everyone was thinking about these things earlier in the project timeline?
Don’t ignore the smallest items on the “What could go wrong?” list. The tiniest thing can create a small failure that cascades to a massive one. Review each one and move on. If it isn’t handled, the affected team can take care of it and report back when it’s been handled.