By Conrado Morlan
The number of credentials offered by professional associations, hardware and software vendors and other organizations has grown sharply in the last decade. So have the number of credential holders.
There’s much to be said for certifications. Many companies require a certification to advance along their career path. In addition, salary surveys show that, overall, credential holders earn more.
On the other hand, some professionals and employers are not fans of certifications. They argue that many people have forged a career and reputation without them, that accelerated changes in science, technology and government regulations makes certifications hard to maintain, and that the cost and time of pursuing credentials are too high.
I see the value of certifications from two perspectives: the value given by the credential itself, and the value of my contributions to the credential.
The value given by the certification is the importance of the knowledge gained through earning it, the reputation of the institution or professional association that awards it, and the certification’s years on the market.
The value of my contributions to the credential has to do with how it engages me to actively research trends within my profession. This process can help experienced practitioners turn into thought leaders who share their experiences leading and managing projects across the globe. In other words, the value of a certification can cascade beyond the credential holder. Knowledge is shared with other practitioners, helping them to advance in the profession.
Yes, it’s true that some credential holders fall behind and don’t keep up with the latest knowledge and/or renew their credential. Other credential holders don’t follow the established code of ethics, which harms the reputation and value of the credential. But such misbehavior or lack of up-to-date knowledge isn’t the fault of the credential or the credential-awarding organization.
PMI, for example, has a strict renewal process for the Project Management Professional (PMP) certification that requires certification holders to earn a specific number of credits per cycle to keep the credential current. And over the 30+ years since the PMP was created, those requirements have been updated to cover market and industry demands.
You may be wondering why I didn’t mention the cost of certifications, and whether they’re worth paying. To me, it’s a no-brainer. I take my professional development personally and always recall former Harvard University President Derek Bok’s quote, “If you think education is expensive, try ignorance.”
If you’re a certification holder, how do you measure its value?
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 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.
Witnessing so many unsuccessful projects these days, I keep asking myself why execution continues to fall through the cracks while organizations apparently grow in project management maturity.
If organizations are more mature in project planning, why aren’t we reaping better results? It’s easy to see we have an execution gap.
I think this is because some project managers are so immersed in the minutia of best practices that they don’t understand the big picture.
They don’t understand that project management processes, tools and techniques are only a means to an end. The final goal of every project is to jointly create value by engaging stakeholders to build a unique result under constraints (scope, time, cost and more). In other words, a successful project delivers benefits and satisfies stakeholders.
Execution demands proactivity. Project managers should embrace change, keeping their eyes wide open to take their project plans out of the paper. Making things happen is easier when you have a good plan, but it still demands a lot of energy and motivation.
Practitioners sometimes put their well-crafted, detailed plans on a pedestal as trophies of great project management. In fact, planning is only half, or less, of the way to the finish line.
To paraphrase the boxer Mike Tyson, “everybody has a plan until they get punched in the face.” The real world is volatile and complex; missing and incomplete information is the norm. Will your plan survive the challenge? It depends on how well you execute. As many in the military learn, strategic, tactical and operational plans need to be executed with maximum agility. Adjustments, adaptations and unexpected decisions must be made along the road to project completion.
To execute well, you need clear goals, resilience, flexibility and a high degree of “alertness.” The OODA loop, created by John Boyd, revolutionizes goal-centered execution by adding flexibility and velocity in the decision-making process. Here are the four steps.
Figure 1- OODA loop (Source: Defense and the National Interest)
Next time you start execution on your project, put the OODA loop to work for you. It will guide you through the project plan as a series of linked decisions to help you make sense of the environment, update the plan and observe results.
If you have any comments—or perhaps a negative or positive story about execution—please share below. Thanks!
Seattle's Troubled Tunnel: 3 Communications Tips for Regaining the Public's Trust
Human Aspects of PM,
PM & the Economy,
PM Think About It,
Categories: Best Practices, Change Management, Communication, Complexity, Ethics, Generational PM, Government, Human Aspects of PM, Leadership, Lessons Learned, PM & the Economy, PM Think About It, Program Management, Project Delivery, Project Failure, Project Planning, Social Responsibility, Stakeholder, Strategy, Teams
One of the biggest public works projects in the United States right now has some major problems. It’s a more than $3 billion effort in Seattle, Washington to replace the Alaskan Way Viaduct, an aging elevated highway on the city’s waterfront, with a 2-mile-long tunnel. If you’ve been keeping an eye on the project, you know that the tunnel-boring machine (dubbed “Bertha”) broke down more than a year ago, creating various challenges and overruns. Public outcry is mounting.
Now, if you’re like me and believe in the power of communication to ensure that projects run more smoothly, the tunnel project has highlighted the need for more openness, better stakeholder management and speaking to your audience in understandable ways, instead of falling into buzzwords or corporate speak.
If I were working on the project right now, here are three things I would look at to regain the public’s trust and help everyone in Seattle and the state of Washington understand exactly where the project is.
1. Be willing to convey incomplete information. The project’s big challenge is that the machine built specifically for drilling the tunnel encountered a setback when it struck a metal pipe during the excavation process. Unfortunately, it took project leaders over a week to convey the extent of Bertha’s problem, the course of action and any sort of timeline to get things back on track. Since Bertha stopped working in December 2013, information has trickled out to stakeholders.
The project’s leaders could have set a much different tone early on by stating what they know and what it means to the project—along with an acknowledgement that they really aren’t 100 percent sure what the solution is, and a clear statement that they will work to provide status updates to all stakeholders as often as possible.
Instead, it’s been “hard to get straight answers,” as the Seattle radio station KUOW put it.
2. Be honest. This really goes hand in hand with the first point about having the confidence to convey information that is accurate, even if it is incomplete. The public has begun to doubt that project leaders are being honest about the tunnel’s current status and future. This is partly because when the city’s department of transportation (DOT) or the state government has updated the community about the project, they have given information that seems farfetched and is tough to believe in light of Bertha’s lack of progress.
Case in point: A DOT official recently toldSeattle’s City Council that the project was “70-percent complete.” That claim was met with a great deal of skepticism by journalists and members of the community.
The lesson for project managers is: Don’t fudge information to avoid blowback. In the long run, you are putting your project at a strategic disadvantage because you may lose funding or you may come under heavier oversight…or worse. So just explain things in an honest and forthcoming manner.
3. Be consistent in the delivery of information. A lack of consistent communications has been one of the big failings for the Seattle project team. And when there’s an information void, it will usually be filled by something you aren’t going to like. In this instance, the lack of communications has led to a real breakdown of trust.
That’s why you need to make a plan for communicating consistently with stakeholders. It should include the best ways to communicate with specific stakeholder groups, and a plan for gathering accurate, up-to-date information from the project team. To ensure timely gathering, build the consistent delivery of information into day-to-day project activities. Set a schedule of when you want your team members to communicate information to you, and hold them accountable.
In turn, you need to inform key stakeholders of when and how you’ll communicate information to them, and then stick to that plan.
In most cases, communications comes down to recognizing the importance of clarity in effective project leadership. In Seattle, you can see what a lack of a clear process can do to the trust between stakeholders and the project team. I’m confident that most unsuccessful projects began to unravel when communications stopped being clear and consistent.
What do you think?