How many times have you read an article with manager or supervisor techniques and come away disappointed that you could not use them as a project manager? They are meant for entrepreneurs, those with direct reports in operations or just make assumptions that are not true for you.
It's frustrating because no manager could use help more than a project manager with temporary teams, temporary efforts and a rotating list of skeptical stakeholders. Luckily, you are able to use many of the same tactics, certainly those that focus on influencing and motivating rather than those leveraging your authority over salary and career advancement.
This blog has covered many of these techniques over the years. The techniques below allow you to get the most out of a project team even if it is temporary, and not burn the individuals out or misuse them or abuse them. The best techniques allow you to end up with project team members who would be glad to join your team again.
Help project team members with their personal advancement
You may not be able to promote workers or give them new roles in the organization, but you can help them meet their career development goals.
Help the changing team work together better
You may know tactics related to helping individuals work better. For example, you may be able to recognize ways to set up an individual for success in their role. What you may not have practiced previously is techniques used to help the entire team work together better. This is more important in projects where workers enter and exit the project work at different times. When new members enter a team, act to minimize the “bond” that the existing team members have.
Make sure your employees feel a sense of accomplishment
We often talk about motivating workers by giving them positive reinforcement publicly. But we do not always focus on a related technique of helping them feel a sense of accomplishment. This turns out to be important – especially important in environments where a feeling of accomplishment is more rare. Examples of such environments are those that commonly have long projects, or where resources move quickly from project to project without having a chance to think about their impact.
These tactics will not only motivate your project workers, they will help make you stand out as a more sophisticated project manager. When you get results and have a motivated team, you are a valuable resource in any organization.
In my article this month I discussed tactics to assist you with strategy implementation by maintaining the proper culture. That article did not look at troubleshooting tactics, but I'm rectifying that here with several troubleshooting tactics that will help you take your career to the next level. You might want to check out the article first to make sure you get certain background information.
On to troubleshooting. Recall that in a project or program closely associated with strategy implementation, you as a project manager have a critical role in helping achieve the business strategy. That gives you a certain prestige, power, cache. Don't be afraid to use it. But use it wisely by taking careful steps.
Characterize identified obstacles to escalate properly
Suppose you identify an obstacle to implementing business strategy such low participation by one or more stakeholders. Is the cause simple overallocation or actually resistance to the strategy? Those are two very different situations. If you can, you need to know before you can effectively intervene.
Problems that stakeholders report that are from known competing priorities or reduced resources are common and can be handled through your typical risk and issue management. On the other hand, problems arising from certain "silos" that do not want to participate, require a different tactic.
What would be the cause of resistance to the business strategy? Some individuals, job roles, or departments can be affected negatively by the strategic plan being implemented. Jobs can be lowered in prestige, shifted around the organizational structure or even lost. Implementing business strategy is serious business. And you can represent danger as the project manager. Even if the fear or anxiety is unfounded resistance can still affect your "strategy" project and must be dealt with.
What might you hear from a stakeholder or partner if there is resistance to the business strategy? Hint: You will not hear "I disagree with the business strategy." But listen for phrasing like in these examples:
Or you may get a tip off from another stakeholder or sponsor that one or more stakeholders are known to be negatively affected by the strategic changes and then see actual resistance.
Intervene effectively for resistance to the strategy
Suppose that you have followed all these steps and identified and have evidence that a stakeholder Is not participating because of resistance to the strategy itself. In this case you must use a very specific type of intervention that is unlike the regular risk and issue management process you normally follow.
Projects implementing business strategy are not given to just any project manager. You have to be able to handle the basics without thinking too much because you are dealing with higher-level risks and stakeholders - and the stakes are greater. Succeed by using your understanding of business relationships and breaking down complex problems into step-by-step solutions.
This is the fourth post in a series related to Robotic Process Automation*, begun in association with PMI's Information Systems and Technology Symposium, June 14, 2017, where I presented Becoming an RPA-Ready Project Manager. You can filter posts in this blog to find all related to "RPA". You can also watch that presentation for PDU credit.
Without the right prepared resources during organizational change, frustration will be the order of the day. Deadlines will cause conflict. The much-touted vision will ring hollow. Success will be difficult.
In an initiative where organizational change is brought about by automation, including rolling RPA projects, resources have to be available at certain times to complete specific work. If they are not available, then the frustration spiral takes over. Examples below from such a hypothetical organizational change show how to identify and deal with resource problems and how to avoid errors managing resources over which you have control.
Organizational Change Effort Role: RPA Project Team Business Process Specialists
Potential Problem: You lead an RPA project that will be completed within a couple of months and representatives from the business that know the process to be automated are not available or not assigned near the point at which you are to start. This could be due to:
…or other reasons
What You Can Do as Project Manager: No matter what the reason that caused the problem,
Organizational Change Effort Role: Change Specialists
Potential Problem: Your project is dependent on a separate effort to communicate about the change in advance and to get general agreement with the vision but evidence you see does not indicate that the communication has occurred, or the vision has been accepted. This could be caused by:
…among other reasons.
The result is that certain project team members, partners, stakeholders are not hurrying to work with you. They do not know what your project is. Or they are avoiding your project.
What You Can Do as Project Manager: No matter what the reason that caused the bad communications, you must act when the environment is not conducive to success. In any organizational change effort,
There are many other roles in an RPA project, but the example of business process specialists is good to address because success of the project is mostly dependent on their availability. Likewise, there are many roles in a large organizational change effort, even one that is solely built around continuous automations. Change specialists are key to setting up a positive environment for you to manage your project. Unfortunately, you as a project manager have less authority to manage problems associated with roles outside the scope of your project. Still, your usual tactics of (a) direct communications with constructive problem-solving and (b) risk management are useful there as well. Using those tactics will make you a positive force against frustration in organizational change.
(If you are thinking that Resources needs certain skills for automation projects and organizational change then you are correct, but we will deal with the issue of skills in a future post.)
* Robotic Process Automation: Configuring a software robot, using one of the relatively new tools available, to complete a certain part of a work process formerly completed by FTEs. RPA is not Artificial Intelligence, but simply a way of automating the execution of well-defined business rules. Projects are short and bring quick benefits to the organization.
If you were to go back through postings on this blog over the many years that it has been in existence, you would find that many of the tips and tactics covered fall under the category of “ways to improve the work environment so that workers can do their best”. To be able to manage an environment is a high-leverage technique for a project manager. You would do well to identify and build as many skills in this area as you can.
Here’s one now!
A recent study helps you understand in a more sophisticated way how to interact so that you create a more productive environment for your project team.
Before getting into the details of the study and pulling out useful tactics for a project manager, it’s useful to ask yourself: Is it better for me to appear as competent or to appear as warm? You might think it is best to be both. You might think it is more important for you to appear competent because your team does not have to like you, they just have to respect your authority and ability.
There are certainly different ways to look at this and, of course, different project managers have different personalities. But if your objective is to create a productive workplace, it is important to strike the right balance in a given situation, to understand what behaviors create the environment where workers will thrive. This study helps you do that - with a little help from my tactics provided after the description of the study.
The study was supported by Carnegie Mellon University and led by Shereen J. Chaudhry, who was trying to determine how and why people use apologizing, thanking, bragging and blaming. The study used clever scenarios with winners and losers and researchers monitored what happened on live chats after the winner was revealed. Sometimes the environment and outcome was fixed to really test researcher's predictions. (Hard to tell whether that would have been fun or just a little creepy.) Researchers interviewed participants afterwards to gather more information.
The outcome of the study confirmed predictions and made additional discoveries, including:
You can employ certain tactics based on this information, such as
Managing the amount of thanking, apologizing, bragging and blaming turns out to be a powerful tool in your tool set.
Before hearing the results of the study, would you have anticipated that appearing warm was more important than appearing competent in such social interactions? Would you have managed these kinds of interactions as recommended above?
Ah, the luxury of having an active task with an end date that is far away. You can concentrate on the tasks that are more urgent, making sure the team focuses on getting those done on time. There will be plenty of time to bring attention to that non-urgent task later.
That is, until the day when you think, "Is that task due already? Last check it was only 25% done and now there is only 10% time remaining!"
A long-duration task could be a task that takes many weeks to complete in a project where tasks typically last a week or two. There's been no mistake. It has been scheduled that way. A long design task, for example, to complete a single critical, difficult display for stakeholders. Or a long development task that takes the effort of many specialists who are working part time on the project, increasing the duration, but not the total effort. The key characteristic is that the task has been set a long duration by the team or owner (or you!) and now it is in progress in your project along with many other tasks that have due dates much sooner.
Consider this situation an opportunity, a way to exhibit your more advanced execution skills and maintain focus on active tasks with long durations. Build or strengthen this habit by using certain tactics and staying "above the fray" in your meetings
Stay Above the Fray . . . Inexperienced practitioners can wait too long to start checking on tasks that start weeks or months before they end. You can probably remember meetings where you allowed task reviews in meetings to be all about the urgent. That's what people want to talk about. But long-duration tasks have long durations for a reason. Effort needs to be expended the whole time. If inadequate effort is expended because of overconfidence, distractions or too much time allocated to urgent tasks, then the group completing the task will have lost the opportunity to do needed work.
Use Effective Task Management Tactics . . . Manage long-duration activities to set up task owners and yourself for success. If you wait until too close to the end of the task to start checking in, then you lose the opportunity to intervene.
A big part of keeping project execution on track is keeping long-duration tasks on track. The ability to get these type of tasks completed is a routinely useful skill that you can improve to increase your success and that of the teams who make up your project workforce. And if those who can possibly pay you the big bucks happen to notice, all the better.