Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Build a Business Case for Lessons Learned
Categories:
Lessons Learned
Categories: Lessons Learned
| If you are not having project reviews and meetings to address lessons learned, it may be that your project sponsors do not count these as valuable activities. You know better, but how do you make a convincing argument to have project reviews? You must take the discussion with your project sponsor to a different level. It's not "we just need to know what happened." It's "we want to take action and get better results the next time around." The lessons learned meeting could make you aware of changes that may be needed to turn business from being bleak to being more successful. Give your sponsors succinct reasons to pursue assessing projects to make improvements. Consider these tips to influence your supporters: Gather statistics and determine what you need to measure. If your company is concerned about quality, chart examples of projects where quality was lacking. If ROI for projects has not been good, share those examples. Share success stories. Bring up achievements that occurred because of the attention on improvement. Discuss the situations that will make a difference to the bottom line. Make a plan. As a project manager, you already know that planning is important. Prepare a well thought-out plan for gathering and presenting the lessons learned. Then use the newly acquired knowledge. How have you built a business case for lessons learned and project reviews? |
Why Getting Mad Can Benefit Your Projects
Categories:
Human Aspects of PM
Categories: Human Aspects of PM
| "Get mad, then get over it." --Gen. Colin Powell, USA (Ret.) Generally, people consider anger to be a negative emotion. But it doesn't have to be. Let's review the positive side of anger: Anger can benefit relationships. Many of us are told to hide our anger, but doing so could be detrimental to your relationships. For example, if you're angry because of a mistake that a project team member has made and you don't speak up, he won't know that he has done something wrong. He will probably keep doing it and enter into a vicious cycle. On the other hand -- if justifiable and aimed at finding a solution --expressing dissatisfaction can strengthen relationships. Such honest communication can help solve problems among stakeholders and build cohesiveness into your team. Anger can motivate. Anger can prove to be a powerful motivation force, helping you "go the extra mile" and keep working despite problems or barriers. For example, if you're criticized for your work, you may feel further motivated to do better because you are angry and want to prove that you can improve your level of performance. In project management, if we are able to produce what is called "positive anger" in our team, they will be more motivated to achieve results. But don't make a team member mad just for the sake of it. Find the right words to push them in the right direction. Anger can indicate an optimistic personality. Ironically, happy people have something in common with angry people. Both tend to be optimistic. Take the study of risk management, for example. Dr. J.S. Lerner, professor of public policy and management at the Harvard Kennedy School of Government, found that angry people expressed optimistic risk estimates. Estimates of angry people more closely resemble those of happy people than those of fearful people. It's okay to get mad, but always behave professionally and treat people respectfully. Don't let wrong behavior undercut a right message. At the end of the day, we're all human. We all have feelings, one of which is getting mad. Use positive anger when you can. Above all, be able to communicate when you're angry in a way that doesn't undercut your message. Have you ever used anger in a positive way in your projects? Read more from Jorge. |
Craft "High-Quality" Requirements
Categories:
Project Planning
Categories: Project Planning
| Project requirements derive from concrete business needs or business-use cases and constitute the foundation for the project work. Without requirements, projects cannot exist. Incomplete and unclear requirements may result in project failure. Moreover a significant part of project rework is attributable to problems with the project requirements. On the other hand, requirements that are clear, complete and understood by all the parties are of "high quality." They build a solid foundation for the project work. Collecting high quality requirements can be a challenging endeavor for several reasons: • Stakeholders often don't speak the same language (business vs. technical) • Stakeholders have different understandings and views of the product • Stakeholders have different backgrounds and expertise on the matter It may not be the project manager's role to collect, qualify and write requirements. But he or she is often the one planning the framework and determining or approving the guidelines by which requirements are elicited, qualified and accepted. The following guidelines should help in collecting high-quality project requirements: 1. No requirements without a use case Usually, requirements can be linked to concrete business cases, which are generally task- and user-centric. Use cases help understanding the requirements' context and purpose. 2. Requirements language Pay attention to the wording. Avoid ambiguous words. Use words and terms consistently. You might consider using a glossary of terms to ensure common understanding. Avoid words that have subjective meaning (nice, substantial, safe, simple) and that enforce direction weakly or that undermine commitment (often, always, partially, usually). Use "shall" or "must" instead of "should" or "might." Remove any room for interpretation. Avoid the usage of "and/or" together or "including but not limited to." 3. Requirements characteristics checklist Build a checklist of requirements characteristics that are relevant to your project's quality standards. Evaluate each requirement against the checklist. Here are 10 characteristics that I successfully use to evaluate the quality of requirements: Atomic: Is this a single requirement or multiple requirements in one? Complete: Is this comprehensive enough to start working on it? Traceable: Is this related to a use-case or need? Logical and Clear: Does it make sense? Does it leave no room for interpretation? Consistent: Is this consistent with the project objectives and other related requirements? Measurable: Is this measurable once a solution is delivered? Compliant: Is this aligned to the current product features, system architecture and legal framework? Feasible: Is this realistic and doable given the complexity and the project context and constraints? Necessary: Is this really required given the project objectives and constraints? Or is it more of a want than a need? Prioritized: What are its criticality, urgency and priority? What best practices do you use to ensure that project requirements are of high quality? |
Inspire Your Multigenerational Team
Categories:
Generational PM
Categories: Generational PM
| Although the multigenerational team has always existed, project performance can be affected by the project manager's leadership style. The project manager must inspire the members of different generations while recognizing and reconciling generation gaps to develop a healthy environment within the team. To do so, you must: 1. Win the team members' trust and loyalty Successful leaders need people around them who share the same mission and vision, and are enthusiastic about it. As a project manager, you must win the trust of the people you are leading. Your experience as project manager and confidence in your ability to succeed will inspire and make people believe in your capacities as project manager, regardless of what generation they are part of. 2. Do things differently Think about new and different ways to approach a project or project tasks. Get feedback from your team members and peers to use different approaches, tools and techniques when addressing project tasks. This will motivate your team members to take a more active role in the project. 3. Thank those who help your project to succeed Project success depends on how well the project team performs. Great leaders know that showing appreciation is a great way to show people they are valued, which everyone appreciates. Say "thank you" and recognize publicly those who helped the project to succeed. Define and communicate to the project team a recognition system and, from time to time, let them know how much you value their efforts and how much they mean to your organization. As a project manager, what are you doing to enhance your leadership skills? How do you lead and inspire multigenerational project team members? Read more about acknowledgement. |
The "Other-Conscious" in Public Speaking
| In my last post, Contagious Enthusiasm in Public Speaking, I talked about how being overly self-conscious can inhibit your effectiveness as a public speaker. I also know that public speaking is a valuable way to enhance your career growth. I promised to explore the idea of being fully "other-conscious" a little more deeply. Communication, of course, is what we project managers spend the majority of our time doing. Public speaking is common enough for us. All communication is about sharing meaning. To be effective, we need to have a good understanding of whom we are talking to and what will influence his or her understanding of the message we are trying to communicate. The best communicators have a keen ability to be very attuned to the other person. It helps them develop a rapport that makes real understanding happen more readily. Effective public speakers bring this ability to the group setting. They master the ability to be dialed in, not to the group, but rather, to many individuals simultaneously. Some people who are extraordinarily good in "one-on-one" situations can be very ineffective as public speakers because they find it so distressing. Much of what people find distressing stems from self-consciousness -- they are overly concerned with how people perceive and react to them. Forget self-consciousness. Be other-conscious. If everything we do is focused entirely on the listener as an individual, it can help us have the kind of rapport essential for good two-way communication. The mistake people often make is to view public speaking as addressing an audience -- a nameless, faceless and even a potentially hostile audience. Rather, we should view our listeners as a collection of individuals with whom we need to establish separate relationships in order to effectively communicate with them. But don't ignore yourself in the process. On the contrary, because of the importance of the speaker's role, visibility, prominence and leveraged influence, the speaker must pay particular attention to him or herself. And that means, with a mind toward the other. What do you think? Does being self-conscious help you be other-conscious in all communications, not just public speaking? Read more about speaking in your project management career. Get more career help. |