Clearing Your Team's Blind Spots
Consider a team in which all members are performing at the optimal level.
You would see them engaging internal and external staff members only when necessary. They would deliver on requirements without having to consult you every step of the way, allowing you to be the chief who oversees a big project from a higher level rather than micromanages.
When team members aren't performing at their optimal level they are often constrained by blind spots. These are the internal roadblocks specific to each team member that we often label as communication issues, team dynamics, management style, and cultural and organizational biases.
Having a blind spot means not being able to see the complete picture. When we can't see the complete picture, we make up what is hidden by using context such as our knowledge, experience, goals and motivation.
Blind spots limit us because we lack the runway length required to let our ideas take off; we impose constraints that prevent us from understanding the goal, coming up with solutions and choosing the one that works best.
To expand your runway requires a well-integrated framework of communication and teamwork based on two main principles: clearing those blind spots by empowering the team to help each other and owning your enterprise.
In part two, I will expand on the power of ownership and how to tie these principles together.
Can you think of the blind spots that you were faced with in any of your previous or current projects? What was your way of dealing with them, and what was the impact on the results you produced?
Incomplete requirements impact the definitions of deliverables and it ultimately blocks the expectations setting. In such scenario even a skilled resource fails to demonstrate his/her productivity. This can be minimized by involving the stakeholders, sorting out the partially / inadequately defined work packages, by seeking clarifications and by adapting iteration mode of delivery.
Lack of collaboration, improper alignment of goals, unable to visualize the risks, complete absence or inapt monitoring, lack of motivation etc. also generates blind spots.
Here communication plays the most effective role. As a regular project management practice, team should get engaged at each and every level of project cycle, all project issues, concerns should get discussed in war room and action items are meticulously identified to reach the project goals. Commitments from leadership team, team building exercise do make a positive impact in team conglomerate.
Blind spots can occur at any phase of project but mostly prevails during the initial stage of project execution.
The other approach I employed for a project that was new to our company and complex with aggressive schedule is to have the team work on the reference platform during planning phase (Scope/Resource drafted) make the team get the big picture and move on to the project platform during execution phase, that way you reduce learning curve and also will have the blind spots avoided in the long run.
Primarily we considered these the highly visible people with whom we interact (e.g., the Director of the "end-user" organization or signatories on our control gates). While the Signatories of a project are important, it may well be that a person not directly involved in your project has an interest and a controlling influence on your project.
Example, the director of the network on which your IT project is going to be hosted may have no idea or interest in your perceived value of the project; however, he or she can certainly bring pain. Relationships must be cultivated and communication is the key.
Please Login/Register to leave a comment.