Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Best Practices Improve Customer Experiences
Categories:
Best Practices
Categories: Best Practices
| In order to survive, project-driven organizations must compete on many levels. Delivering on time, to cost and with quality is always important -- but so is the interaction and customer experience they provide during the project. Project-driven organizations must consider customer satisfaction as a critical success factor. Organizations that deliver projects that disregard customer needs create negative experiences and ultimately cause huge problems for the organization. Typically, project teams that fail to capture what the customer actually needs or wants end up getting the product or service wrong. This can happen because:
In my experience, organizations with project management practices that deliver positive experiences are customer-focused and have proactive, sound processes in place. They also have dedicated, responsive teams who are flexible and able to satisfy customer needs. I believe the following practices can help deliver a positive customer experience:
See more posts from Saira Karim. See Taralyn R. Frasqueri-Molina's post on The Benefits of a Change Control Board. |
6 Tips to Persuade Stakeholders to Say "Yes" to Your Project
Categories:
Human Aspects of PM
Categories: Human Aspects of PM
| "Advertising is fundamentally persuasion, and persuasion happens to be not a science, but an art." -- Bill Bernbach, founder of Doyle Dane Bernbach, an ad agency Starting a project is not always easy. It requires resources and changes the status quo, so there can be a lot of obstacles until you hear "yes" to a project. That's why you need to know how to effectively persuade your stakeholders to get on board with your project. Dr. Alan H. Monroe's motivated sequence pattern, created in the 1930s, is useful for doing so: 1. Attention: Capture your stakeholders' attention with an interesting opening statement, or share a statistic related to your project. 2. Need: Identify the need that your project will address and share it with your stakeholders. The more information you have about the business needs, the better the chance your project is approved. 3. Satisfaction: Let stakeholders know how your project will satisfy the identified business needs. In detail, describe the approach you'll use in your project to address the needs. 4. Visualize: Explain the 'perfect world' that will exist after the project has finished. Make it as vivid as possible -- explain how it looks, sounds and smells. Be very energetic and enthusiastic when you explain. 5. Action: Tell them what you need them to do. Let them know specifically what steps you are taking to achieve the vision you've just shared. The sixth element I would add is to tell a story to help you make your point. It could be real or it could be fictional, but remember that people are more likely persuaded when they hear or read a story that transports them. If a story is told well, we get swept up and are less likely to notice things that don't match up with our everyday experiences. Use your creativity -- find your own way to mix all of these elements and you can build a powerful tool to persuade even the most demanding stakeholder. How do you reach and influence your stakeholders as people, not just businesspersons? See more posts from Jorge Valdés Garciatorres. See more posts about stakeholder management. |
Posted
by Jorge Martin Valdes Garciatorres
on: February 06, 2012 11:33 AM
| Permalink |
Comments (4)
In Search of Project Management Stars
Categories:
PMI
Categories: PMI
| Every project professional knows the massive effort that goes into a project delivered on time, on budget and in sync with organizational strategy. Now's the time to put the spotlight on all that hard work. Established in 1989, the PMI Project of the Year Award recognizes the accomplishments of a project and project team for performance and exemplary execution of project management using processes and approaches consistent with A Guide to the Project Management Body of Knowledge (PMBOK® Guide) -- Fourth Edition. PMI encourages nominations for projects from around the world, regardless of size, industry or location. Anyone can nominate a project or be nominated for a project; PMI affiliation is not required. The winner will be announced in October at PMI® Global Congress 2012 -- North America in Vancouver, British Columbia, Canada. But you have to act quickly. Nominations for the 2012 PMI Project of the Year Award must be received by Thursday, 1 March 2012. Winning such a coveted professional award reaps many benefits for both organizations and individuals. These may include a boost in sales, attracting and retaining top talent, and gaining media exposure. It's also an excellent way to celebrate a project team's successes while affirming an organization's commitment to sound project management. For individuals, a professional award can enhance your résumé or CV and your career prospects. Last year's project entries represented a diverse array. The Prairie Waters Project, aimed at preventing water shortages in Colorado, USA, took top honors. The finalists included the EMAL Smelter Complex in Al Taweelah, Abu Dhabi, United Arab Emirates, and the Oak Grove Steam Electric Station in Franklin, Texas, USA. Learn more about the 2012 Project of the Year, download nomination guidelines and watch videos of 2011 award winners and nominees. Have you submitted your nomination yet? |
Build Generational Awareness on Your Project Team
Categories:
Generational PM
Categories: Generational PM
| There are certain interpersonal skills that project managers must master in order to analyze situations and interact appropriately, as outlined in Appendix G of A Guide to the Project Management Body of Knowledge (PMBOK® Guide)--Fourth Edition. The skills include political and multicultural awareness. But, since the project team environment has evolved over the last 10 years, I think a new interpersonal skill should be required, not only for project managers but also for team members and stakeholders: multigenerational awareness. Generations as cultures are based on invisible values, beliefs, attitudes and assumptions created by shared experiences and events. These differ across generations, and each will likely feel or behave differently in the same situation. The lack of cultural awareness may lead to a misunderstanding and misinterpretation of the situation. As a project manager leading a multigenerational team, you must know how to handle generational differences. Try to empathize with someone from a different generation and understand where he or she is coming from. Listen to the meaning behind words and interpret non-verbal clues rather than applying generational stereotypes. Focus on making that connection with individuals of different generations to build a meaningful relationship. When your multigenerational project team disagrees, in my experience, it's often because people are following those generational fundamental values. As the project manager, you need to assume a humble attitude and question rather than assert. Asking people to explain themselves before assuming anything shows respect. Building awareness around generational differences in your project team can ultimately help avoid any problems. Encourage your team to: Avoid making quick judgments of values. Try to understand the value and its historical reason. Values evolve as people live their lives in different periods of time. Define a balancing act. Figure out how to manage different perspectives and different ways to doing things. What are you doing to build generational awareness in your team? Read more posts from Conrado Morlan. Read Dmitri Ivanenko's post on Answering the Loaded Question in Project Management. |
Building Blocks of Project Work Planning
Categories:
Project Planning
Categories: Project Planning
| In my previous posts, I laid out the basics, the framework and the key documents for planning a project end-to-end. Now it's time to dive deeper. One of the most essential project planning stages is to establish the grounds for the project work. Planning and defining the project work starts with defining the "what" of the project. Before you can begin, you must understand the business needs and identify the project deliverables and its characteristics. You must set the boundaries of the project by establishing what the project will and will not deliver, and break down the project work into smaller and more manageable work units. The building blocks of project work planning have four main steps:
The requirements elicitation process should be facilitated and not done by yourself. Therefore, do this. Get the appropriate project stakeholders together. Organize focused requirements workshops. Interview, brainstorm and job shadow to glean information. Defining the project scope involves prioritizing the collected requirements, and deciding what's in and out of scope based on such factors as criticality, priority, urgency, constraints, complexity, risks and costs. The scope covers the project deliverables and all project requirements, along with their detailed descriptions and the related constraints and assumptions. The scope illustrates the entire work that the project will carry out, as well as the project boundaries. The part of the work planning that generates action is the Work Breakdown Structure (WBS). The WBS enhances the project scope understanding by decomposing the project work and deliverables into smaller and more manageable work units, also called work packages. The WBS defines granularly the "whats" of the project. Do you agree with these steps? How many steps do you use for project work planning? Read more posts from Marian Haus. |