Posts

Resource Management Strategies When Skilled Resources Are in Short Supply

Skill shortages have made resource management a significant challenge throughout the business world. That means, you need to ensure that your resources deliver the right output when it’s needed. Here are some tips to manage your skilled resources and make that happen.

  • Define workload priority with management. It’s rare to have a team member fully dedicated to your project; multi-tasking is commonplace. As you get team members assigned to your project, work with their managers to prioritize their assignments. That way, you and your team members will be in sync regarding the time they’re allocated to your project. For example, maybe a team member’s number one priority is to help the finance department close the monthly books, and their second priority is to work on your project. The best approach is to refrain from scheduling that team member on your project during the first week of every month. While inconvenient, it isn’t as painful as getting behind schedule because you scheduled your resource when they aren’t available.
  • Select team members whose skills match the difficulty of the task. You get the best results when a team member has skills that align with the difficulty of the work. If the task is too challenging, your team member could struggle, take too long, and become demoralized. Too easy and the task becomes more annoying than enjoyable—plus, this resource could be used to complete a more difficult task. In other words, the “best and brightest” staff member isn’t always the right person for a task.
  • Embrace positive conflict. Project managers sometimes avoid using team members who have a history of conflict with their colleagues. If the issue is a personality clash, it’s appropriate to find someone else. However, if the conflict relates to how to solve a problem or design a solution, conflicting opinions can generate more and better ideas. Although managing this positive conflict takes more time and effort, the project outcomes can be much better as a result. Take a page from the philosophy of former US President Abraham Lincoln; assemble a “team of rivals” to get the best project results.
  • Temporarily trade duties with team leaders or technical managers. Some team leaders and technical managers often wish they could drop their leadership and administrative duties and return to producing technical deliverables. Why not give them a chance to do just that? As a project manager, I’ve often temporarily taken administrative duties from a team leader or manager in exchange for them working on a technical task on my project. That gives a valuable resource the opportunity to practice their craft, and you get a better result for your project. It’s a win-win!

Do you have any tips or tricks for using skilled resources to the best advantage? Add them in the comments section!

For more about resource management, check out Daniel Stanton’s Project Management Foundations: Teams course.

Less Well-known Benefits of Procurement Management

Procurement management is all about bringing control to acquisition of parts and skills required for projects. But it also delivers additional benefits that you don’t often hear about:

Find long-term partners. Organizations often require parts or skill-based services on an ongoing basis. Well-crafted Requests for Quotation (RFQ) or Requests for Proposal (RFP) enable vendors to share their skills and abilities as well as the culture and business approach they take to serve their clients. Your RFQ or RFP can not only reveal the best alternative for your current need and can also identify a go-to business partner for the future.

Identify other solution options. Speaking of RFPs and RFQs, send requests that encourages vendors to provide a response to your specific solution request along with alternative solutions. That way, you might discover ways to address business needs better. The information you get can draw attention to the potential for a long-term business partnership (see point 1). 

Discover skill mixes available in the marketplace. While working on a leading-edge technical project, a vendor introduced me to a technical-skill mix that I didn’t know existed. I worked with my procurement team to describe the technical installation skills I needed to implement a set of technical tools. The vendor proposed experts with both technical implementation expertise and business analysis background required to fully configure and implement our tools more efficiently than if we did it ourselves. This skill mix decreased the project’s forecasted duration and made for a stronger business case to launch the project.

Support an efficient supply chain. Supply chain challenges are everywhere today, affecting virtually every business. The entry point to your supply chain is the vendor(s) who provide parts and products for your project. Being mindful of your supply chain requirements and performing sound procurement management helps you select vendors who can minimize or eliminate supply chain issues that can impact your project outcomes.

If you have other benefits you have obtained from procurement management, share them with your fellow project managers by posting in the comment section.

For more about procurement management, check out Oliver Yarbrough’s Project Management Foundations: Procurement course.

Less Well-known Benefits of Schedule Management

Photo by Elena Mozhvilo from Unsplash

Besides bringing control to your project schedule, schedule management delivers additional benefits. Here are a few rarely-discussed benefits of schedule management. 

Defines elephant bites. The adage about eating an elephant one bite at a time works with projects, too. However, the phrase doesn’t mean much unless those bites are defined and are seen as reasonable. The work breakdown structure – as the basis for the overall project schedule – is the perfect tool for defining reasonable bites. Tasks represent the small chunks or bites that need to be produced to deliver the project. A good schedule helps you deliver a project successfully, because people can grasp those small bites and how their tasks contribute to the overall project objective.

Facilitates great how-to discussions. A company’s IT upgrade project team faced a dilemma: should they upgrade the network connections first, then the PCs, or the other way around? While there were technical pros and cons to each option, the schedule ultimately decided the sequence. Vendor resource restrictions determined the best approach — in some parts of the business, the PCs were upgraded first; and in others, the network was upgraded before the PCs. Without considering the schedule in the decision, it would have taken longer to complete the project. A better approach to completing the project was identified because of scheduling discussions.

Provides a defense against unreasonable expectations. A common challenge for project managers is handling expectations of the timeframe required to deliver project outcomes. The best tool for fact-based discussion of timeframe is a set of tasks defined and sequenced along with a reasonable time estimate for each task. That discussion becomes even more powerful if you’ve captured history of task completions, which reinforces your estimates for the current project. If the timeframe is too long,  you can use that information to ask your sponsor which tasks to cut or convey the risk from reducing the hours allocated to a task.

Gives you a map! Successful initiatives all share a common trait — there is a known and understood path from where things stand today to where you want to be. For projects, a sound schedule is that map. A complete schedule includes milestones and closing tasks, which serve as “X marks the spot” tasks that tie things together and confirm you’ve reached the treasure you were seeking. 

Have you come across schedule management benefits?

For more about schedule management, check out my Project Management Foundations: Schedules course. You might also want to watch my recent LinkedIn Office Hours session about evaluating schedule quality.

You Don’t Have to Feel So Alone

As a project manager, you have to make decisions, resolve conflicts, manage aggressive timeframes and make the most of small budgets. It can feel like you have to deal with these responsibilities all alone. Yes, your responsibilities are monumental. You won’t feel so alone if you follow these tips:

  • Work with your team members. Take time to work with your team on issues, idea generation, and solutions. It’s even more effective when you chat informally with team members at least 10 minutes each day. You won’t face obstacles alone and you’ll build stronger relationships, develop trust, and foster dedication with your team members. 
  • Show gratitude. Look for opportunities to say, “thank you.” When appropriate, acknowledge accomplishments with formal recognition programs or by taking a team member(s) out to lunch. Expressing gratitude helps build a unified team that will support you as a leader – and you won’t be on your own should things go astray. Do the same with your key stakeholders and project sponsor to build support you can count on when you need it.
  • Enhance your leadership approach. Project leaders have no choice but to rely on others. As you manage larger, more complex projects, the need to rely on others grows. View this dependency as an opportunity to delegate, train and learn from others. Your team members become stronger resources; you grow more familiar with your team’s deliverables; and project management becomes more of a team effort.
  • Leverage your network. Discuss your project with fellow project managers and get their perspectives. Use status reviews with your manager and/or project sponsor to share ideas and perspectives. Attend project management gatherings, like Project Management Institute® chapter meetings and network with other attendees. You might pick up a great idea to make you look like a hero on your project!

If you have more suggestions for reducing your sense of isolation, add them in the comments section.

For more about team building, check out Mike Figliuolo’s Building High-performance Teams course.

The Fine Art of Documenting Lessons Learned

Crafting lessons learned can be tricky. Lessons learned should help future projects without criticizing anyone publicly. Here are a few guidelines for achieving those lessons learned goals. 

  • Identify recurring issues. Issues that are likely to re-occur if they aren’t addressed are significant lessons learned because they will help many future projects. Conversely, issues related to one-off technology or unique business processes won’t be that helpful in the future, creating useless entries to wade through in your lessons learned library.
  • Identify an avoidance or risk reduction strategy. Nothing is learned if you don’t document how to avoid the issue. Describe the issue or risk and explain what to do differently. Future readers need to understand the context, so be specific and include early warning signs for the issue. Entries with these details will help your project management peers (or yourself if the issue crops up after you’ve forgotten about it).
  • Improve project methodologies and guidelines. Lessons learned might present opportunities to improve your project management methodologies or templates. Write your lessons learned entries with this in mind. If your lessons learned entry can’t be applied to your methodology, there may be gaps in your project standards. For example, if your methodology doesn’t handle working with your procurement organization on vendor contracts, write your lessons learned entry to add that process to your project management methodology and template set.
  • Refrain from mentioning individuals or roles. Appropriate lessons learned talk about the issue that occurred and the approach for avoiding or reducing its impact to the project. Talk about outcomes and processes, not specific decisions or inaction. Don’t mention individual’s names. Mention roles only if absolutely necessary. 

Do you have tips for describing helpful lessons learned from your experience?

For more about lessons learned and project closure, check out my Project Management Foundations course.

Successful Eating Plans and Project Management Have a Lot in Common

Photo by Dan Gold from Unsplash

I enjoy cooking — and eating – and I also believe in the benefits of a healthy eating plan. A recent conversation reminded me of the similarities between successful eating plans and project management. So grab that acai bowl (or rice cake if you insist on dieting) and have a read.

  • The correct amount is ideal. Sufficient, not excessive calories are key to effective nutrition plans and project plans. Fewer people on a project are easier to manage, reduce communication problems and are more likely to work as a team. Just as you don’t want to eat more because you have low-cal foods on hand, don’t add project team members unless they have expertise you need. Using the correct amounts in your eating plan and your project will yield better results. 
  • The right mix is crucial. An eating plan includes a mix of nutrients to keep you healthy. A project also needs the right mix of technical leads, industry expertise, and action- and planning-oriented team members. Your project is apt to stall with an out of balance team. 
  • The timing of consumption matters. When you eat can be as important as how much you eat. Likewise, when you deploy project resources is important. Bring in experts too early and you might suppress your team’s ideas, because they defer to the expert. Bring in experts too late and you risk spending time and money on dead-end approaches they would know to avoid.
  • Produce early results. Eating plans that don’t generate recognizable early results might be dropped as unsuccessful. When stakeholders dedicate budget and critical staff time to the project, they want reassurance that they are making a wise investment. When you deliver early project results, your stakeholders will stick with you, just as you will stick to the menu when you feel healthier, stronger, and more energetic. 
  • Keep your eye on the goal. Persistence pays off! Whether your goal is health, strength, energy, or weight loss, keep your eye on your objective—and remember that progress won’t be consistent. That way, your chance of success increases. With projects, monitor performance and accept that business priorities and issues might impede project progress.

If you can think of other similarities, post them in the comments section. I’d love to add them to this list.

For more about project management, check out my Project Management Foundations course.

 

Must-have Hard Skills for Project Managers

Photo by Leon on Unsplash

A solid team can contribute to the broad range of skills needed to complete projects successfully. However, project managers must possess several skills to ensure project success:

Construct risk response plans. Although team members can identify risks, the project manager handles building and managing sound risk responses. Because the PM is the project liaison to the sponsor and senior leaders, the PM must be able to discuss, adjust, and deploy risk responses effectively.

Recognize schedule feasibility. Lots of schedules that are built don’t reflect reality. For example, feasible schedules include realistic expectations for team members’ weekly allocation the project. Schedules must also include realistic estimates of the effort to complete tasks. And fast-tracking or crashing built in the schedule must be sensible and doable. The PM must be able to spot these pitfalls and correct them. 

Domain expertise. The PM must know enough about the project’s technical domain to work with technical domain experts. In other words, the PM shouldn’t be fooled by experts trying to escape probing questions. For example, a project manager experienced in IT won’t have an issue talking to experts deploying new IT tools. That same PM, assigned to a construction or mining projects could easily be deceived by “the experts.” Project managers can successfully manage projects without specific domain knowledge. However, that situation introduces risk and increases project personnel costs because domain experts need to partner with the PM.

Knowledge of both the technology and business environment. A project’s business outcome often requires different knowledge than what you need to know to build the deliverables that facilitate that outcome. Consider a hospital project to provide advanced medical diagnostic services. Understanding the financial and marketing objectives of the project is much different than understanding the technology used in the sophisticated medical diagnostic equipment that interprets medical test results. The project manager, who works with the team and customers, needs to understand both: what’s needed to produce deliverable as well as the viability of the business outcomes. 

Vendor and contract management. In projects involving significant contracted skills or components, the project manager must be able to manage vendors and their contracts to ensure that deliverables are created efficiently and interactions between vendors are in the project’s best interest, not the vendor’s. For example, customized technical components built for a project require the project manager to validate contracts as well as integrations between those components and other parts of the project solution.

Strategic thinking. In projects that significantly alter business direction, the project manager must be able to think strategically to ensure the approach supports specific project goals and fits into the sponsoring business’s strategic direction.

What other hard skills do you think project managers absolutely must possess?

For more about project management, check out my Project Management Foundations course.

 

Tips for Launching Projects Successfully

Photo by Leon on Unsplash

The fate of most projects is determined by how they’re launched. With a proper launch, the project has a good chance of succeeding. Botch it and the chance of delivering value is almost zero. Here are my top tips for nailing the project launch:

  • Develop a shared understanding of the project. You and your project team might have a solid grip on the project and what it will produce. One key to project success is making sure that your sponsor, project customers, vendors, and other key stakeholders also have a common, shared view of the project, its objectives, and how you will deliver business outcomes. Communicate meticulously to all stakeholders to create this unified project understanding. Without consensus, turf wars can arise, which can compromise funding, slow the project, and are difficult to recover from. 
  • Define metrics and targets. One of Stephen Covey’s 7 Habits of Highly Effective People is “Begin with the end in mind.” To do that, you need to define “the end!” Before you start a project, identify the target metrics and success criteria, so everyone understands early on what success looks like. If you don’t have tools to measure results, include tasks in your project plan to create those tools. Get consensus up front on how those tools will work, where the data comes from, and how the metrics will be calculated. Disagreement over measuring success not only kills projects, but does so at a very inopportune time — late in the project lifecycle.
  • Identify the skills required to deliver the project and how you will acquire them. A project team with the correct skills significantly increases your chance of project success. Many projects suffer from underestimating the challenge new techniques and technology present to project teams. People think “we’ll figure it out” or “our internal staff can learn.” That may be so, but you need to validate those assumptions early on. Work with your team to determine what they can and can’t learn. If using internal team members is impractical, include the availability and cost of consultants/contractors in your estimates. 
  • Touch base with powerful, out of scope stakeholders. Why would you work with stakeholders whose interest is out of your project’s scope? Because big issues can arise if they believe their business interests should be addressed in your project, and they find out they won’t be. Communicate with these would-be stakeholders in conjunction with your sponsor to ensure they understand their business interests are out of scope. That way, no big change requests land in your lap, creating tension and complexity in your project.

Do you have tips for launching projects that have helped you achieve project success?

For more about project launches, check out my Project Management Foundations course.

Improve Your Leadership Skills with Emotional intelligence

As project managers, we don’t simply manage work, deliverables, and documentation – we lead and support the people on our project teams. Emotional intelligence (also known as Emotional Quotient or EQ) helps us do that. Here’s how enhancing your EQ can help:

  • Relate to people working from home. Working with others is challenging even when you work side by side. Interacting with people onscreen amps up the level of difficulty. Although some people work from home and love it, others wish they were in the office. EQ helps you relate to and support your team members through their struggles. Your supportive leadership makes all your team members feel more comfortable with their work environment, which means a better chance of meeting project objectives.
  • Deal with people under stress. Stress creates obstacles for project managers and can significantly decrease project success. Stress often arises from business challenges like reactive decisions, irrational or missing responses to project problems, and fear about speaking the truth regarding project difficulties. With solid EQ, you will be able to recognize the root cause of these issues. Work through stressors with your stakeholders to ease their minds and deliver project outcomes.  
  • Manage excessive workload. Many businesses suffer from too many concurrent projects, competing operational responsibilities and being short-staffed – whether in your business or third parties you contract with. Pushing a schedule and managing to deadlines doesn’t guarantee progress. To negotiate deadlines and obtain staff to complete tasks, you need to understand the delivery pressure others are under – and that takes EQ.
  • Work across cultures. Project managers often work with people from different cultures, whether they represent different geographic regions in your country or different countries altogether. We are all human and have the same emotions behind our reactions. However, how emotions are triggered can vary across cultures. The higher your EQ, the more you will recognize these emotional triggers and the signals indicating the presence of emotions. That enhances your ability to work with stakeholders, no matter their cultural background. 
  • Apply change management if needed. Success goes beyond delivering project deliverables. For example, installed software doesn’t represent a successful result if the client isn’t tech-savvy and requires training and support to achieve the desired benefits. You might need to apply change management to achieve business outcomes, which requires skill, leadership expertise, and EQ. Whether you perform change management or depend on change managers, you need to understand what drives successful change management, which takes EQ.

For more about Emotional Intelligence, check out Gemma Leigh-Roberts Developing Your Emotional Intelligence course and Britt Andreatta’s Leading with Emotional Intelligence course.

Tips to Reduce Project Chaos

People problems, business pressures, and creating unique results come with unexpected challenges. Dealing with chaos is one more thing project managers must do. Here are a few tips for reducing project chaos.

Research past lessons learned. Capturing lessons learned is often like wishful thinking. People talk about doing it, but rarely get around to it. If that’s the case in your organization, don’t give up. Instead, ask project managers and sponsors in your business about the problems they’ve seen on their projects. If your organization has a lessons learned database, examine it thoroughly. By understanding past issues, you can build insightful risk and contingency plans. And those plans can help you quickly identify the root cause of potential issues and address them before they create chaos in your project (and your life!) 

Watch for changes in stakeholder behavior. When stakeholders get stressed, their behavior usually changes. They might get more talkative, less talkative, or voice concerns about your project out of the blue! Don’t just wonder what that’s about. Initiate 1-on-1 discussions with stakeholders to identify what’s going on with them. Showing compassion for your stakeholder and your project outcomes creates trust, which can lead to learning more about potential problems. That leads to greater insights and less chaos!

Evaluate and respond to baseline variances. Be sure that you understand your baseline metrics for scope, schedule, cost, and quality. When Those metrics are off by more than 5%, determine the cause of that variance. And when the variance goes beyond 5%, jump into gear to get things back on track — and share the status and your actions with your project sponsor. Proactive communication about issues and responses can instill confidence in your project leadership, which means fewer “please explain” type of meetings, and – you guessed it — less chaos!

Focus on what’s important versus what’s urgent. If something is important and urgent, by all means, focus on that first! After that, work on important issues and don’t get distracted by urgent yet unimportant things like a ringing/chirping telephone. Minimize distractions by turning off your phone, pausing email notifications, and hanging a do not disturb sign on your door. That way, you address the most vital tasks on your project. Less chaos! 

 

Projects will always involve unexpected or sudden changes. These tips can calm things down for you and your project team. Do you have tips to share for reducing project chaos? If so, share them in the comments!!!

 

For more about reducing project chaos, check out Chris Croft’s Project Management: Solving Common Project Problems course.