By Christian Bisson, PMP
A deadline is the project objective defined in terms of time. But on some projects (a lot of them, unfortunately) the delivery date is not necessarily realistic.
When projects get delayed, the obvious solution is to push back the deadline. But it’s not so simple for every project.
Here are a few factors to weigh before deciding how to move forward when facing project setbacks:
The Client Relationship
Assuming the agency runs client-facing projects, not internal products, this is typically the most important reason to deliver a project on time. Happy clients bring in more projects—and other clients by word of mouth.
Determining whether or not your client will react negatively to a project delay may depend on the cause of the holdup. Is the delay related to client actions, such as adding new requirements or delivering assets late? Or is it due to internal errors, such as poor estimating or planning?
Keeping clients happy also presents a sort of balancing act for many agencies. You have to keep clients happy because they bring in the money that runs the agency. But, on the other hand, you don’t want your team members so bogged down with additional requests and revisions that they become tired or frustrated to the point they will leave.
Projects often have what we call hard deadlines, meaning the date cannot be changed under any circumstances. For example, in e-commerce, there are projects tied to holiday sales and, obviously, those dates cannot move. Missing those opportunities can have a drastic impact on sales. In these cases, it might actually be more cost-efficient to invest in more resources to speed up the project and have it ready on time.
The Big Picture
Delaying a project can have a direct impact on other projects, as well. Team members may be scheduled to move to another project once the first is completed, for example, so delaying that transition date can have a chain reaction on an agency’s planning. Talk to someone with a wide-angle view of the organization’s portfolio to better understand these potential implications.
There’s no magic solution for dealing with a delayed project. All you can do is balance the pros and cons and make a judgment call.
What factors do you typically weigh when deciding whether or not to push back the deadline on a delayed project? What advice do you have for other project managers facing a delay?
by Peter Tarhanidis
I’ve served in various leadership roles throughout my career. In one role, I worked with engineers to build and deliver a technical roadmap of solutions. In another, I was charged with coordinating team efforts to ensure a post-merger integration would be successful.
All of my leadership roles ultimately taught me there’s no-one-size-fits-all style for how to head up a team. Instead, the situation and structure of the team determines the right approach.
Traditional teams are comprised of a sole leader in charge of several team members with set job descriptions and specialized skills, each with individual tasks and accountability. The leader in this environment serves as the chief motivator, the coach and mentor, and the culture enforcer. He or she is also the primary role model—and therefore expected to set a strong example.
But, this traditional team setup is not always the norm.
Take self-managed teams, for example. On these teams, the roles are interchangeable, the team is accountable as one unit, the work is interdependent, the job roles are flexible and the team is multi-skilled, according to Leadership: Theory, Application, & Skill Development, written by Robert M. Lussier, a professor of business management at Springfield College in Springfield, Massachusetts, USA.
On a self-managed team, each person’s capabilities support the team’s overall effectiveness. While these teams do need to have their efforts coordinated, they spread leadership accountability across the group.
Members each initiate and coordinate team efforts without relying on an individual leader’s direction, according to Expertise Coordination over Distance: Shared Leadership in Dispersed New Product Development Teams by Miriam Muethel and Martin Hoegl.
Effective leaders adjust their style to the needs of varied situations and the capability of their followers. Their styles are not automatic. Instead, they get to know their team members and ensure their teams are set up to succeed.
How do you pick the right leadership style to use with your teams?
by Christian Bisson, PMP
The project manager role is often underestimated or inaccurately interpreted. Because organizations can have different definitions of what project management means, there is sometimes a lack of clarity around the role, especially for non-project management professionals. In this type of environment, people fall back on basic stereotypes.
If you find yourself typecast in one of these roles, take heart. You are not alone.
1. The Note Taker
One of the most stereotypical expectations of project managers is that they’ll be the meeting note taker. I’ve experienced this time and time again. During a large client presentation, for example, one of my colleagues was asked if he would be taking notes. He replied, “Well, I have a project manager for that.”
Yes, project managers take notes. But they shouldn’t be the only ones doing so. Meeting attendees tend to focus on the notes that directly impact their work. A designer, for example, will focus on conceptual and visual comments, while a developer will focus on features and functionalities.
Furthermore, if the project manager is leading the meeting it will break the meeting flow if he or she is also responsible for note taking.
2. The Meeting Organizer
Project managers will often be expected to set up meetings—and to a certain extent, that makes sense. For large meetings, such as internal presentations or milestone check ins, it makes sense to have the project manager take care of the planning. It allows him or her to rally everyone and set expectations for the meeting so the team can come in prepared.
But there is a line.
Teams shouldn’t expect project managers to organize meetings when they just need to gather for a brainstorm or a quick chat. Sadly, it happens. For example, I was once asked by a colleague from another office to book a meeting so that he could talk to another colleague that was sitting just 10 feet (3 meters) from him.
Project managers should encourage teams to be responsible for setting up those smaller meetings or one-on-ones themselves.
3. The Accountant
There is a misconception that the project manager is the only team member who should care about budgets, or worse, the only one that should be responsible for a budget’s health. This mindset is tough to change because it’s true that a project manager’s role, amongst other things, is to manage the budget.
However, the project manager cannot take everyone’s actions on his or her shoulders — and it wouldn’t be fair to expect that. If a feature was estimated at 50 hours and the team took 100 hours, it takes collaboration to fix the negative impact to the budget or schedule. The team must warn the project manager, everyone must discuss solutions, and then the project manager should take the appropriate next steps with stakeholders, etc. Obviously, this should be done as proactively as possible, not after the fact.
To think that no one should care about the budget, and only project managers should fetch this information and “figure it out” on their own is absurd. Yet, it’s a common expectation.
Have you found yourself in any of these scenarios? What other project manager stereotypes have you faced? How do you deal with these misconceptions?
By Peter Tarhanidis
These days there is such a high influx of projects and such a demand for project managers, but such a limited supply of practitioners. How can companies help their project professionals improve their skills and knowledge so that they can work to meet that need?
Leaders deliver more results by sponsoring grassroots project management learning and development programs. Common approaches and best practices are shared across all levels of project managers—ranging from novices to practitioners. Therefore, if an organization has more employees who can learn to leverage project management disciplines, then the organization can meet the increasing demand, and are more likely to develop mature practices that achieve better results.
One type of grassroots effort is to establish a project management community of practice (CoP). CoPs are groups of people who share a craft or a profession. Members operationalize the processes and strategies they learn in an instructional setting. The group evolves based on common interests or missions with the goal of gaining knowledge related to their field.
For project managers, there is a specific added benefit of CoPs. They bring together a group who are traditionally part of separately managed units within an organization focused on strategic portfolios and programs.
CoP members develop by sharing information and experiences, which in turn develops professional competence and personal leadership. CoPs are interactive places to meet online, discuss ideas and build the profession’s body of knowledge. Knowledge is developed that is both explicit (concepts, principles, procedures) and implicit (knowledge that we cannot articulate).
In my experience, I have seen CoP utilized in lieu of project management offices. The members define a common set of tools, process and methodology. The CoP distributed work across more participants, increased their productivity to deliver hundreds of projects, improved the visibility of the members with management and positioned members for functional rotations throughout the business.
Which do you think drive better performance outcomes—establishing hierarchal project management organizations or mature project management disciplines through CoPs?
by Dave Wakeman
Has your leadership style evolved to reflect the modern business environment?
Old leadership styles put a premium on command and control, which made sense when there weren’t so many specializations.
Now, our culture, and the way many of our projects are organized, requires that we are more collaborative and more focused on enabling our teams. Let’s call this “leadership by empowerment.”
Having fully engaged and empowered teams is now a key to project success.
If you are struggling with adopting this new leadership style, here are a few tips to help you build empowerment in your teams:
1. Focus on communication: With all of the tools at our disposal, you would think communication and information sharing would be easier than ever.
But it isn’t.
In most cases, it feels like our communications are hampered more than ever by all of the noise and demands from technology. But knowledge is empowerment and if you want to empower your team to maximize its impact, you need to renew your focus on communications and getting people the right information at the right time. You can do this by clearly spelling out the way that you will communicate with your team and how they should communicate back with you. You can create areas, tools and methods for accessing the most important information. A tool like Slack may be a way that you can better organize your information.
2. Allow your subject matter experts to be experts: In projects it is easy to lose focus on the fact that as the leader, you can’t know everything. This can cause project managers to want to dictate every action and every possible scenario to your team members, but that is a clear path to friction, delay and failure.
As the project manager, your job is to put your team of experts in a position to succeed. One way I do this is by setting outcome-based goals for my teams with clear check-in points so that I can understand the status of tasks and activities , but give my team members the power to do the work in a manner that they feel is best.
3. Provide continuous opportunities to learn and grow: We talk a lot about constant learning and development, but how much of that is just lip service? To help empower your teams, spend some time developing the skills that are truly going to help deliver better results for your organization (not just the ones that are going to help your team members learn something new).
You can do this by creating a training calendar or schedule that focuses on mission critical tasks, sharing best practices or interesting new ideas, or inviting in guest speakers.
Remember, your job is to use the tools you have at your disposal to make sure your leadership empowers your team to do the best work they can for you.
How do you empower your team members?
If you enjoyed this piece, you will really enjoy the weekly newsletter. It is my most personal and strategic content delivered each Sunday morning to your inbox. Make sure you never miss it! Sign up here or send me an email at firstname.lastname@example.org!