By Peter Tarhanidis, PhD
I’ve been fortunate to have a career that constantly challenges me and my team to apply new approaches to achieve an organization’s mission. I believe that adapting these contemporary management practices and innovative operating models has helped me become the project leader I am today.
Below are select project initiatives that have helped me develop my skills:
What themes have you identified in your career? How have you broadened your range?
By Conrado Morlan
“An investment in knowledge always pays the best interest.” ―Benjamin Franklin
I’ve heard from colleagues in project management that they don’t have access to professional development opportunities to help them improve and increase their capabilities. That led me to do some research. I found Training magazine's Training Industry Report, which is recognized as the training industry’s most trusted source of data on budgets, staffing and programs in the United States. It found that U.S. companies spent over US$90 billion on training and development activities in 2017, which represents a year-over-year increase of 32.5 percent.
With that information on hand, I took the opportunity to ask my colleagues if the companies they work for are among the organizations spending money on training and professional development.
Some of them were fortunate to work for companies with professional development budgets, but they didn’t take the training due to their workload or personal reasons. In other words, the opportunity was there but it was neglected.
For those who worked for companies without professional development dollars, their main complaint was that the company did not appreciate them and the opportunities to develop more capabilities were so limited.
I asked them: Who takes charge of your professional development? You, or the company you work for? Many of them responded that the responsibility fell to the company they work for, because training would help create a more competitive workforce, increased employee retention and higher employee engagement. I agree on all the benefits the company would get, but ultimately the individual is responsible for their professional development.
I have worked for both types of companies. In the ones with development budgets, I saw former colleagues neglecting opportunities because “they did not have time,” they did not like to travel or simply because they felt it was not needed. In the ones without budgets, I heard the same claims mentioned above.
While working for the latter type of company, I took ownership of my professional development. Instead of seeing roadblocks, I saw opportunities, which led me to do the following:
So do not solely hold the company you work for responsible for your growth. Take charge of your professional development. After all, if you do not invest in yourself, nobody will.
How do you take charge of your own professional development?
By Peter Tarhanidis, MBA, Ph.D.
In project management, your presence as a leader is vital to your success. But how do you begin to refine this skill set? Start by considering what kind of presence you convey, and how that presence impacts your influence with teams.
Underlying a leader’s presence are sets of behaviors and actions directed toward team members in various situations. A leader must distinguish between the two prevailing behavioral approaches. In the task approach, leaders accomplish their goals by setting structures, organizing work, and defining roles and responsibilities. The relationship approach, on the other hand, employs behaviors to help teams feel at ease within a variety of situations.
In other words: Is the leader driven to treat team members as valued individuals and attend to their needs, or do they see team members as a means to achieving a goal? This approach will affect a leader and their team’s performance.
Project managers are constantly combining these two approaches to influence teams and attain a goal. Clearly, there are certain behaviors that emerge in one’s presence which increase one’s influence over teams. Examples include humility, honesty, confidence, composure and emotional intelligence. But the truth is, influencing teams takes a great deal of time and energy. There is only a certain amount of time and energy one dedicates in every moment. For many project managers this creates a challenge: What can a leader do to be present in every moment?
The opportunity does exist for leaders to train themselves to be present. By applying a certain regimen of actions, a leader can apply a thoughtful approach to increasing their presence. Dedicating yourself to increasing your energy and presence will result in positively influencing teams. Below is a list of four actions to help unleash one’s performance through increased energy, focus and presence:
Let me know how you unleash your performance. Please share your top behavior picks, why they define your presence, and how you successfully increased your influence with teams!
by Kevin Korterud
I always enjoy hearing about the early careers of the project managers I meet. In almost every conversation, the subject turns to when they were team members being led by a highly capable senior project manager who provided guidance in starting up, executing and sometimes turning around projects.
It’s also not uncommon to hear stories of the worst project manager they ever worked for. These stories, while not as glowing, also influenced their careers around what not to do. By probing a bit deeper, they offered up observations of certain behaviors that created havoc, dissatisfaction and quite often failed projects.
From these observations of the worst-ever project manager, I started to put together my own thoughts on who I would select for this inglorious label. After careful consideration, I arrived at the only logical choice: me. In my early years as a project manager I managed to consistently demonstrate all of the behaviors of poor project managers.
Here are my votes for the most significant behaviors that led to consistently poor performance as a project manager early in my career:
When I was a project team member I relished the thought of one day having a business card with an impressive title of project manager. My thought being once I received that lofty title, it would allow me to be successful at whatever project I was assigned to lead. In addition, the acquisition of that title would instantly garner respect from other project managers.
I failed to realize that most project managers are already quite proficient at leading teams and producing results. The title comes with a heavy burden of responsibility that was exponentially greater than what I had as a project team member. As a team member, I didn’t realize how much my project manager shielded me from the sometimes unpleasant realities of projects.
The satisfaction of acquiring the title of project manager can be very short-lived if you’re not adequately prepared. My goal became to perform at the level at or above what the title that project manager reflected.
2. I Talked Too Much
Perhaps I was wrongly influenced by theater or movies where great leaders are often portrayed in time of need as delivering impressive speeches that motivate people to outstanding results. I remember quite clearly some of the meetings I led as a new project manager that quite honestly should have won me an award for impersonating a project manager.
Meetings were dominated by my overconfident and ill-formed views on what was going right and wrong. In addition, I also had the false notion that I had the best approach to all of the risks and issues on the project. No surprise that this mode of interaction greatly limited the size of projects I could effectively lead. Essentially, it was a project team of one.
After a while, I started to observe that senior project managers spent a fair portion of the time in their meetings practicing active listening. In addition, they would pause, ponder the dialogue and pose simple but effective probing questions. When I started to emulate some of these practices, it resulted in better performance that created opportunities to lead larger projects. “Less is more” became a theme that allowed me to understand the true problems and work with the team to arrive at effective mitigations.
One of the most critical components of any project is the people that comprise the team members and stakeholders. As a new project manager, I tended to over-engage with stakeholders and team members by attempting to instantly resolve every issue, whether real or perceived. My logic was that if I removed any opportunity for dissatisfaction then project success would be assured.
I failed to realize this desire to completely please everyone quite often resulted in pleasing nobody. In addition, I also managed to pay insufficient attention to the key operational facets of a project: estimates, forecasts, metrics and other essentials needed to keep a project on track. Furthermore, the business case for the project gathered almost no consideration as I was busy trying to make everyone happy as a path to results.
Over time I began to adopt a more balanced approach that allowed me to spend the proper level of engagement with people, processes and the project business case. This balanced approach allowed me to have a broader span of control for factors that could adversely affect a project.
For all the things we have learned over the years as project managers, it sometimes causes me to wish for a time machine to go back and avoid all of the mistakes we made. But then, we would not have had the benefit of the sometimes-traumatic learning experiences that have made us the project managers that we are today.
Did you ever consider yourself to be the worst project manager you ever worked for? I think we all were at one point in our careers.
by Linda Agyapong
"Who" really is a stakeholder?
I enjoy breaking down some of the buzzwords in project management.
In my previous post, we looked at “project success” vs. “project management success.”
Today I’d like to focus on “stakeholder”—one of the most buzzworthy terms.
For this discussion, let’s check in with our three favorite project managers: Jim, Mary and Alex. They have been tasked with a major construction project in Europe. On the first day of their kickoff meeting, as they were documenting their project charter, they got stuck because the three of them could not agree on identifying all the stakeholders for the project.
Turns out the targeted site for the construction project had a natural habitat for a specific kind of protected species—the moor frog.
Jim and Mary jointly agreed that moor frogs should never be considered as stakeholders of the project—after all, they were not humans. But Alex maintained that they should be considered as stakeholders because the frogs would either be significantly affected by the project, or they would significantly affect the project.
Alex then explained that the classic definition of a stakeholder—from the legendary business theorist R. Edward Freeman—did not segregate animals from humans, nor living things from non-living things. In his award-winning book, Strategic Management: A Stakeholder Approach, Mr. Freeman defined a stakeholder as “any group or individual who can affect, or is affected by the achievement of the organization's objectives.” He subsequently clarified that this definition can be expanded further to cover anything that the organization significantly affects, or is significantly affected by it.
Alex added that the very issue had been argued in the journal article Project Temporalities: How Frogs Can Become Stakeholders by Kjell Tryggestad, Lise Justesen and Jan Mouritsen. These authors took the stance that the natural habitat of the frogs provided some benefits to people in the community, such as via food, recreation or entertainment. Because of that value, the moor frogs should be classified as stakeholders.
Robert A. Phillips and Joel Reichart argued the opposite in their article, The Environment as a Stakeholder? A Fairness-Based Approach. They said that this natural habitat cannot be classified as a stakeholder because, “only humans are capable of generating the necessary obligations for generating stakeholder status.” Their basis was that stakeholders can only impact a project when they “make themselves known as part of the empirical process to develop the project.”
Tryggestad, Justesen and Mouritsen, however, advised that non-living things could be actors of the project if they make a visible difference within the project, such as significantly impacting any of the triple constraints of the project (namely time, cost and scope). Their rationale was that “an actor does not act alone. It acts in relation to other actors, linked up with them.” The frogs were then considered to be “an entity entangled in a larger assemblage consisting of both humans and non-humans.” At the end of their research, the frogs were classified as actors or stakeholders of the construction project.
To bring it home, Alex calmly advised his colleagues that the frogs have peacefully lived in that part of the community for several years. To avoid incurring the residents’ wrath, they should classify frogs as stakeholders and subsequently make the necessary arrangements to appease the community accordingly.
In the end, Jim and Mary unanimously agreed to this great suggestion.
I encourage you to think outside the box to identify all the potential stakeholders for your upcoming projects. Good luck!