As a manager, it is important to understand not only the strengths of your team, but also your team’s weaknesses.
Often you find yourself wondering during team meetings what is going wrong. Why is your team not reaching the potential you know to be possible?
You may even find yourself wondering if the issue is not the team as a whole, but a singular team member.
This team member always has an excuse for why materials are not ready on time, and these excuses may even sound reasonable to you. After all, you understand all too well the chaos that is your team workflow.
As a manager, it’s vital that you remain objective and not allow yourself to make subjective decisions based on your gut. But it can be hard to turn subjective decisions to objective ones if you have no way to gather evidence.
This situation is even harder to make if your team works remotely.
But what if we told you there was a solution that will help you verify these internal ponderings about your team?
What if we told you there was a way to create a complete overview of your team’s tasks, dependencies, and goals – all in one place?
One singular overview could help you, as a manager, to find the objective truth about your team.
For example, you could ask yourself if the team as a whole which needs to be addressed, or a singular team member.
It saddens us to say it, but sometimes there are team members that hold back the rest of the team from reaching their full potential.
This isn’t to say these team members are awful people; they may not even realize that they are the drag on the team’s value creation.
Once upon a time, we ran into this problem on our own team. We were growing explosively, and we couldn’t have been more excited.
However, as our team grew, our workflow and value that was created didn’t line up with where we thought we should be. In fact, it felt more chaotic than our early days with a smaller team and smaller projects.
We hoped that this would only be a temporary problem. After all, we were growing, and we needed to give the team a chance to figure out our workflow and culture.
But after a few meetings, we realized that all of the problems we were encountering could be tied back to one team member.
This team member always claimed to be busy, but they always had an issue getting materials in on time, and often materials were incomplete.
Now we heard reasonable excuses. That they were waiting on materials from a client or another team member, or that they couldn’t finish one task because they were working on another.
Does any of this sound familiar to you?
This team member was in a creative role, and we understood that sometimes creativity needs wiggle room regarding time, but this made it very difficult to accurately predict how much time should be given to his tasks.
So we developed three simple steps to discover the truth to the question of whether the team or a single team member is holding us back.
First, we created a team workload overview with LogicalPlan. In this overview, we were able to see all the projects and tasks for the team, specifically filtered to show only tasks associated with this single team member.
The workload overview allowed for us to see this team members current work capacity. We could also pinpoint where there may be potential delays.
Essentially, this overview allowed us to see the interconnected web of our team visually.
Second, we created one singular source of truth for our team. A place where all the communications, materials, and attachments for projects were accessible to the team.
We connected these communications and materials to the respective tasks and projects, so no one on our team had to waste time hunting them down.
Once we made this change, we were able to see where the materials were truly missing and where the delays were.
The final step was to onboard the entire team into LogicalPlan.
Now, this is more than getting them to log in. You have to educate your team on the importance of using LogicalPlan, adding tasks, materials, and communications as they go through their personal workflow.
If there are tasks and materials not being added to the team’s workflow with LogicalPlan, then it is challenging to check your team’s overall workflow accurately.
So make sure to get your team invested in this solution.
With these three simple steps, we quickly realized that our gut was right. It was a team member, not the team, creating a drag on our workflow.
After we ended our partnership with this team member, our workflow sped up, and our team began to create value on a new scale.
We promise you, using these steps and LogicalPlan, you can discover if you have the right individuals on your team.
Does any of this ring any bells for you and your team? Is it possible that your team is being held back?