By Conrado Morlan
“Those who criticize our generation forget who raised it.” ―Unknown
I had the opportunity to attend PMI® Leadership Institute Meeting 2016—North America in San Diego, California, USA, and met PMI chapter board members from several countries.
An ongoing conversation during that meeting centered on how to renew and refresh chapter membership and appeal to younger generations.
One of the foundations that will help PMI chapters better interact with multi-generational communities is to develop and master “generational competence,” which according to Ceridian “describe the adaptations or competencies organizations must develop today to meet the very diverse needs of four generations in the workforce and the marketplace.”
While discussing the topic with my fellow chapter board members, I found there is a common belief that generations are defined by age when in reality generations are defined by common experiences and key events.
Also much of the research around generations and generational differences has grown out of the United States and therefore is U.S.-focused.
Here are some alternatives to the typical generational buckets:
Even individuals born in the same approximate marker years are defined differently by the events they have experienced. For example while the U.S. Baby Boomer generation is associated with the notion of the "American Dream,” the Unlucky Generation in China lived through three years of famine and cultural revolution.
At the same time, many of these generations are tied to stereotypes. For example, “Millennials are entitled narcissists,” “Gen Y looks for instant gratification,” “They are not capable of interacting offline,” are some of the comments I’ve heard. Stereotyping, however, fuels conflict within a multigenerational community.
What Generation Y Thinks
During the Leadership Institute Meeting, I looked for opportunities to speak with Generation Y attendees. Across the board, they felt PMI board members from older generations need to develop generational competence to bridge the gap of understanding. This competence will help them learn how to communicate, connect and engage with potential PMI members of different generations.
Membership campaigns will need to align with Generation Y values—happiness, passion, diversity, sharing and discovery, according to Patrick Spenner, a strategic initiatives leader at CEB.
PMI chapters will need to promote the profession as one that:
Perhaps the most important takeaway in my discussions with Generation Y members was that they reject generational labels. Call them young professionals
As a project manager volunteering for a PMI chapter, what is the most challenging situation you have faced within a multigenerational community?
Project Leaders as Ethical Role Models
Human Aspects of PM,
New to Project Management,
Nontraditional Project Management,
PM Think About It,
Reflections on the PM Life,
Categories: Best Practices, Career Help, Communication, Communication, Complexity, Ethics, Facilitation, Generational PM, Human Aspects of PM, Leadership, Leadership, New to Project Management, Nontraditional Project Management, PM Think About It, PMI, PMOs, Portfolio Management, Program Management, Project Delivery, Project Failure, Project Planning, Project Requirements, Reflections on the PM Life, Roundtable, Social Responsibility, Stakeholder, Strategy, Talent Management, Teams, Tools
By Peter Tarhanidis
This month’s theme at projectmanagement.com is ethics. Project leaders are in a great position to be role models of ethical behavior. They can apply a system of values to drive the whole team’s ethical behavior.
First: What is ethics, exactly? It’s a branch of knowledge exploring the tension between the values one holds and how one acts in terms of right or wrong. This tension creates a complex system of moral principles that a particular group follows, which defines its culture. The complexity stems from how much value each person places on his or her principles, which can lead to conflict with other individuals.
Professional ethics can come from three sources:
In project management, project leaders have a great opportunity to be seen as setting ethical leadership in an organization. Those project leaders who can align an organization’s values and integrate PMI’s ethics into each project will increase the team’s ethical behavior.
PMI defines ethics as the moral principles that govern a person’s or group’s behavior. The values include honesty, responsibility, respect and fairness.
For example, a project leader who uses the PMI® Code of Ethics to increase a team’s ethical behavior might:
Please share any other ideas for elevating the ethical standards of project leaders and teams, and/or your own experiences!
By Kevin Korterud
As both a project and program manager, I’m always keen to have projects and programs take the right first steps toward success. In the past, this would involve selecting the unified delivery approach used for all of the projects on a program. The idea was to impart consistency to the way projects were managed as well as produce common metrics to indicate progress.
It’s not that easy anymore. Today’s programs have projects with agile, waterfall, supplier, corporate and sometimes regulatory-mandated delivery approaches. In addition, these approaches as well as the different arrangements made with suppliers (e.g., time and materials vs. fixed price with deliverables) have dramatically increased the level of complexity and diversity of delivery approaches within a program.
So as a program manager, how do I keep all of these projects in sync no matter the delivery method? As a project manager, how can I execute my project in concert with the overall program in order to maximize the value that will be delivered, while avoiding schedule and cost overruns resulting from projects not operating in harmony?
These are emerging challenges for which there are no single easy answers, of course. But I have found a handful of tips useful in getting a program’s projects to operate in a synchronized manner. I’ll share the first few in this post and the final ones in my next post, appearing later this week.
1. Remember: There’s No Such Thing as Agile or Waterfall Programs
Given the mix of project delivery approaches, the program needs to properly segment work to manage the budget, resources and schedule regardless of the project delivery approach. In addition, the schedule alignment points, budget forecast process and deliverable linkages need to be identified between the various projects.
Typically, I find that while there is effort to plan for these items at the project level, the upfront effort for this harmonization at the program level is underestimated or sometimes left out altogether—program managers think the project teams will figure this out themselves. This sets the program up for schedule and budget overruns as well as overall dilution of the program business case.
Some ways for a program manager to harmonize projects on a program include:
2. Make the Correct Delivery Approach Choice Before a Project Begins
The type of delivery approach for a project is determined by the type of work being performed and the end consumer of the project’s deliverable.
For example, a project on a program that is slated to create a consumer portal would be a desirable candidate for an agile delivery method. Another project that involves heavy system integration that a consumer never sees would be a candidate for a waterfall approach. A project to pass data into a government system would likely have its delivery approach set by the governmental body.
So before a project starts, program and project managers should agree on the optimal delivery approach that is the best fit for the project.
Look for more advice in my next post on synchronizing a program’s projects, regardless of delivery method.
By Peter Tarhanidis
New and proliferating digital technologies are giving rise to new competitive businesses while transforming legacy organizations. It’s no longer just about the Internet, but increasingly tech-savvy users and inexpensive smartphones and tablets.
From an organizational perspective, it’s not just a matter of grappling with new technical platforms: The relationship between organizations and their customers is being transformed.
Before, the cornerstone of customer service was the golden rule: treat your customers the way you want to be treated. Customer relationships were facilitated and managed within just a few departments.
Disruptive technologies have enabled a shift to a new paradigm: customer empowerment. This ushered in the new platinum rule: treat your customers the way they want to be treated. Disruptive technologies integrate organizations to their digital customer experience and are simultaneously influenced by social, consumer and professional media portals like Facebook, Yelp, NetPromoter Scores, and LinkedIn.
Now, much of the work and measurement of this activity is shared across the entire supply chain of the customer journey, which requires more cross-team collaboration to report on the customer experience.
So the importation question has become: How can we make the digital customer experience flawless? This is the new competitive differentiator for companies. Those that stand apart in this respect build market leverage.
Project managers are one asset organizations have at their disposal to ensure success with this new digital customer experience dynamic. Here’s a four-stop roadmap for optimizing your organization for the brave new digital world we all live in.
How is your organization adapting to the new realities of our digital customer age? Please take a moment and share your thoughts.
By Kevin Korterud
I’m amazed at how often I receive requests for help creating an effective risk management process. These inquiries usually come from organizations with a risk management process that hardly anyone uses. Stakeholders, program managers, department heads and executives are mystified about why nobody is declaring risks on their projects, which can create the false perception that everything is going fine.
Why does this happen? One reason is that project managers believe making risks visible to leadership could impair their efforts. Another reason is an organizational culture that creates a negative perception of risks. For example, I have seen some highly entrepreneurial companies foster a mindset of rugged heroism, which causes project managers to think they have to fix everything themselves. In this project environment, project managers worry that escalation to leadership will be seen as a sign of weakness.
In fact, there’s no use pretending any project is risk-free. Risk management is an essential part of any project: Whether you’re climbing a mountain or changing a light bulb, there are always risks. For anyone who’s ever been leery about flagging risks, or is just looking for some new approaches, here are five tips.
1. Think of risk management as a way to get what you need, when you need it.
Project managers rarely have the financial or command authority to change schedules or release additional funding—that’s leadership’s job. For this basic reason, declaring and escalating risks enables leaders to provide risk mitigation assistance.
Making risks visible to your leadership gives them enough lead time to provide relief when it is needed, not weeks or months later when unmitigated risks turn into project problems.
2. Don’t forget: People can be risks, too.
I have seen many risk management plans focus entirely on things: systems that might not be ready, processes affected by outside regulatory bodies, estimates that were done in a hurry at year-end budget cycles, etc.
What project managers often fail to consider in their risk planning is that people can also be risks.
For example, let’s say your project sponsor is replaced by someone who has no experience in the subject areas of your project. This lack of experience initially will cause longer decision-making cycles as the new sponsor comes up to speed in the subject areas.
So be sure to include people risks in your risk register—they can affect your progress as much as more inanimate factors.
3. Create guiding principles for risk management.
While there may be a process in place for managing risks once they appear, quite often it is unclear to project managers when and how to escalate risks to higher levels in an organization based on their potential impact.
To create clarity and promote transparency around risk management, the best approach is to set guiding principles that govern the process. The rules should be simple and broadly communicated throughout an organization.
Examples of guiding principles include:
Declaring project risks demonstrates professional discipline that will be recognized by leadership.
A potential mitigation approach should be prepared for every identified risk.
Risks with greater potential impact need to be made visible at higher levels in the organization.
4. Use the 30/20/10 rule of thumb.
In my experience, the most frequent question asked by project managers is how many risks should be identified on a project. For example, a person might feel that a small project should have a small number of risks. But that’s not necessarily true, especially if a small project impacts a large population of people.
One risk management approach I recommend to project managers is the 30/20/10 rule, which starts with a broad slate of risks and narrows them down throughout the life of the project.
Here’s how it works: Identify risks at the beginning of the project that, if realized, would affect 30 percent of the schedule, budget or results. Midway through the project, the goal is to lower the potential impact of risks to 20 percent of the schedule, budget or results. By the end of the project, the project should carry risks containing no more than a 10 percent impact.
5. Don’t forget the bigger picture.
Project managers frequently tell me they would have finished a project on schedule, but team members were pulled into another project. Translation: another project was more important. And the strategic relevance of your project matters just as much as how you manage that project on a day-to-day basis.
To manage the risk of irrelevance, conduct an assessment on a recurring basis of how your project fits into your organization’s strategy and portfolio. Validate the relative priority of the project against other active and pending projects, and check on potential scheduling dependencies that may impact your plans, as well as any resource conflicts that may be triggered by other projects.
What techniques do you use to identify and mitigate risks on a project? If you’ve worked at an organization where flagging risks attracted negative attention from higher-ups, how did you deal with this challenge?