Showing posts with label leadership. Show all posts
Showing posts with label leadership. Show all posts

Saturday, June 8, 2013

Not Claiming the Hero Title, but...

I recently read an article on CNET.com that struck a chord with me. It was about Nextdoor.com, a social networking website designed specifically for local neighborhoods.

As I read more and researched the website, a feeling built in me that this was a good thing. Good enough that I wanted to help make it a success in my neighborhood. That feeling came from a long held realization that our local neighborhoods are becoming less and less connected, less known to each of us

At the time, I was searching for a project to do for the High Performance Leadership Project requirement in my Toastmasters Educational Program. Nextdoor Neighborhoods seemed ready made for that. However, although it had already been founded on a trial basis, it was languishing with only 4 members out of 10 required to successfully found the neighborhood. And, it was in the last 5 days of its 30-day trial period.

I saw that my first step was to ensure that the neighborhood was made permanent. Over the next few days I visited neighbors and contacted those who had previously shown an interest but had not joined. I am pleased to say that, by the end of the trial period, we had 14 members and became a permanent Nextdoor Neighborhood. (We currently have 30 members!)

Then, I started the HPL process, which includes assignments that will be familiar to all PMs. Those assignments include: Learning About Leadership, Choosing Your Objective, Winning Commitment to Your Objective, Working the Plan and Analyzing and Presenting Your results.

So far, I've completed the first 2 assignments, including making an initial presentation to my Poway Black Mountain Toastmasters Club a couple of weeks ago. (I won a ribbon for Best Speaker!)  You can review the presentation here: Nextdoor Central Rancho Bernardo Project Presentation.

I'm just now beginning the Initial Planning of the project, although I do have some rough idea of what I'll be doing. Some of what will be required are:

  • recruit neighbors to be a part of my team
  • complete the project planning process
  • win the commitment of team members to that plan
  • use the plan to spread the word about Nextdoor Central Rancho Bernardo
  • build out membership to be a signifcant percentage of the total residents of the neighborhood
I am excited about this project. It gives me a chance to both complete an assignment that I need to do for Toastmasters and to complete a project that will benefit my neighborhood.

Oh, and if you explore Nextdoor.com for yourself and find that your neighborhood has not yet been founded, ask me for a referral. Currently, Nextdoor.com will give a $50.00 Starbucks card to both of us. 

What a deal!

Friday, May 31, 2013

PM History Lessons: Battle of Saratoga

In a recent edition of the Projects At Work newsletter, I found PM History Lessons: Battle of Saratoga. (See Battles of Saratoga) Stories about the people who fought the war that gained my country's independence have always been some of my favorite topics to read. And, when the reading ties so directly into my professional life, I am especially interested.

Some have said that the fact that a small, scraggly and widely dispersed band of upstarts defeated the worlds most powerful military was mostly the result of luck. Well, maybe so. But the thing about luck is that it seems to profit much more those who are prepared to take advantage of it than those who are not.

That truly seems to be the case in our Revolutionary War. This article recounts eight key points in which leaders on one side or the other were either prepared to take advantage of a lucky break or not. Prepared to even make their own luck. That preparedness, or lack of, made key differences in success or failure as each side struggled to successfully complete the project at hand.

Here are the eight points the article discussed at which attention, or lack thereof, to some key tenets of good project management made a huge difference in the outcome of the project.

1. Choose the best leader
The earliest decision that will have the greatest impact on the success of the project is choosing the right project manager. In the project that became known as The Battle of Saratoga, the British decision to choose General John "Gentleman Johnny" Burgoyne over General Sir Guy Carleton was made based upon mostly political reasons. Carlton had already successfully encountered the American forces in major battle. He knew the terrain. But Burgoyne was close to the decision makers and got the job. Choosing Carleton might have made a world of difference in the outcome.

2. Agree on the plan with major stakeholders and communicate that plan
General Sir William Howe commanded the British army in new York and was assigned a key role in the British plan. The orders that he received from London did not correctly state the scope of the plan he was to complete. Not only did it not explicitly state what he was to do, but, most critically, it did not properly communicate what was to be excluded. Howe effectively took himself out of the plan by deciding to engage in a little gold plating by attacking Philadelphia which was not in the plan and moved his army out of range to provide the key support he was supposed to provide for Burgoyne.

3. Understand the environment and obstacles
The British army was trained to fight on the terrain most prevalent in Europe, open plains. The Americans lived, worked and now fought in vastly different terrain. Not only were the British not trained for the rugged, forested terrain of North America, Burgoyne chose not to modify his tactics to account for the difference. A good project manager should always be alert to situations when excellent training may be the wrong training. In this case, Burgoyne made a critical mistake.

4. Don’t underestimate resistance
Burgoyne's decision not to modify his tactics had a ripple effect on how well he understood the risks he would be facing. By not studying the terrain and understanding the tactics that would best work in it, he lost the opportunity to properly identify the risks associated with it. Muddy roads, even no roads, slowed his progress. Hazards easily thrown down by the Americans disrupted plans and slowed progress even further. These delays forced them to face a better prepared American force in a brutal northeast winter for which the British were totally unprepared.

5. Use expertise at hand
On the American side, General Horatio Gates, in Albany, the key milestone of this project, was prepared to take advantage of a bit of luck that came his way. A Polish national, Thaddeus Kosciuszko, had been assigned to Gates' command. Kosciuszko happened to be the worlds's preeminent expert on artillery bombardment. He was assigned the task of stopping Burgoyne. And he did!

6. Use special resources effectively
Gates had the luck of having another special resource at hand. Colonel Daniel Morgan led a force of about 400 expert marksmen who could hit their targets at distances far beyond the range of the average British infantryman. These men would be what we today know as snipers. Gates gave Morgan the task of disrupting the British forces by bringing his men's expertise to bear on high-level British officers. They were successful and many young British lieutenants suddenly found themselves in charge of much larger larger forces than they were fully prepared to command.

7. Avoid personality conflicts
Gates had under his command the obstinate and temperamental General Benedict Arnold. Today we remember Arnold as the traitor of the Revolutionary War. But many historians rate him as the best field commander in the American army.  And, he was the hero of Saratoga. Almost not, though. Gates and Arnold had violent disagreements over several issues leading Gates to strip Arnold of his command. Even so, in a key engagement that was going badly for the Americans, Arnold commandeered a horse, charged to the battlefront and turned the tide of the battle. A good project manager will make all efforts to to use patience and compassion to help calm the histrionics of a temperamental team member. Gates was lucky in that, even though he did not handle the matter well, Arnold was prepared to do "whatever it takes" to win the battle.

8. Don’t underestimate unanticipated consequences
At Saratoga, both sides were only trying to win a battle. But the consequences of that battle extended far beyond the fields of Saratoga. France had been sitting on the sidelines, waiting to make the decision of whether to side with the Americans in their confrontation with the British. Gates' victory was the signal they needed. For Gates it was an unintentional consequence. But the Americans knew they desperately needed a major ally in this war. And I'd bet that somewhere in the back of his mind, General Gates understood that success in the project at hand might lead to cascading events that would yield major benefits.

Before Saratoga things were not going well for the American cause. Their victories had been few and had not had the lasting impact needed to change their fortunes. The Battle of Saratoga was the turning point. The errors in the planning and execution of the British plan coupled with competent execution by the Americans led to the surrender of the "invincible" Army of the King to a ragtag bunch of American farmers, businessmen and other ordinary citizens.

While they didn't think of themselves as project managers, the leaders on both sides were engaged in a major, long-term project with crucial consequences. The Americans, who successfully utilized important project management skills are my hero project managers of American history.

Monday, November 19, 2012

Captain Derek Silvercloud, Hero, Team Leader Extraordinaire

I'm a fan of science fiction. I love the way future technical, social and myriad other possibilities can be woven into stories that tell us about who we are and who we might be. But I've never been much of a fan of the fantasy side of science fiction. You know, with all the magic and elves and such.

I recently found myself reading just such a science fiction/fantasy novel, though. Actually, I started reading it once and, as soon as I encountered the elves and the magic, I put it aside. I am so glad I came back to it. Otherwise, I would have missed a fun reading experience centered around an almost perfect (he's only human, after all) example of a great team leader.

The book is Voidhawk by Jason Halstead and is available on Amazon in hard copy or as an eBook. It's the story (actually Book 1 of 4) of the captain and crew of the good ship Voidhawk as they sail the Void seeking a livelihood and finding plenty of adventure to go along with it.

In project management, servant leadership is a powerful concept for developing and leading a powerful project team. Captain Silvercloud  epitomizes that concept. Some examples (based on principles detailed in Absolute Beginner's Guide to Project Management,also available on Amazon) are:

  • He always seeks to find what he can do to help his crew be successful at their jobs. He understands that he can't sail the ship on his own.
  • He is always willing to listen to his crew. He shows remarkable patience with them, whether he agrees with their comments or not. He's smart enough to know that he may have to deal with the situation suggested by the comment regardless of how he feels about it.
  • He puts himself in the others' situation and tries to understand how to make his interests also serve their interests.
  • He accepts responsibility for the team's results. He takes initiative and steps into action when situations develop that are a threat to his team and their mission.
  • He encourages collaboration and trust in all team members. Each team member is empowered to take action when they feel it is required for the success of the team.
  • He fosters growth and improvement in every team member. Each individual is encouraged to find and use the unique skills that they can bring to the team.
  • He seeks input and feedback from the team and any others whose interests are associated with the interests of the team. While he accepts the responsibility for making the decisions, he solicits team input to his decision making process.
  • He finds ways to gain acceptance and action from team members and other's through influence and persuasion. Manipulation is avoided (except on the bad guys, of course, he's not perfect).
  • He brightly illuminates a principle of strong integrity and uses his power in a strong but ethical way.
Following these principles, Captain Silvercloud takes a collection of leftover and salvaged equipment and people gathered from some unlikely sources and melds them into a ship and crew that is fiercely loyal to one another. The story illustrates that, in a collaborative and encouraging environment, even the least likely candidate can express a special talent that is of enormous value to the team.

It may not be classic literature and it does have a few problems, mostly editing. For instance, I think someone could have easily caught some of the typos with just one quick reading of the book. From what I've seen, this is a problem shared with many newer publications, but I still don't think it should be acceptable.

If you are a project manager (or not!) and you are looking for a fun read with a little magic and adventure, then here is a great choice  Add in consideration of the relevant pointers on leadership and team building and I think this would be a very enjoyable combination of diversion and educational experience.

Saturday, April 28, 2012

Holy Moses! The Original Hero Project Manager

In his recent article for
     titled  Holy Moses! How to Lead to the Promised Land,

Geoff Loftus wrote about Moses and his great project to lead the Israelites to the Promised Land. I had already been thinking about Moses as a part of another project, so it really caught my attention.

First, let's address the title of this blog. Was Moses the first Hero Project Manager? Why wouldn't God get that title?

Well, even with all the wonderful things that God brought forth, such as creating the Heaven and the Earth and all things in between, I wouldn't consider him a project manager. Being omniscient, he had no need for a detailed plan, he KNEW how to complete his undertaking. Being the source of all things, he had no budget and no concerns of resource shortages. Being eternal, he had no time constraint.

How about other project managers before Moses? Noah built The Ark to save two of every creature on earth from the coming flood. Joseph prepared a land of safe haven in Egypt for the Canaanites to escape the famine. Surely they could be candidates for the Hero Project Manager title.

But both Noah and Joseph managed projects with one great difference from Moses' project. They both had hope of enjoying the fruits of their labor. Moses, on the other hand, sacrificed any hope of personally making it to The Promised Land in a heated negotiation with his sponsor, God, over whether the people should all be smitten for their terrible transgressions, such as worshiping at the altar of the Golden Calf.

Even with no hope of reaching the project goal personally, Moses was still faithful to his commitment. He interceded with his sponsor on behalf of the clients and, alternatively, lead his team and stakeholders to understand unpopular conditions of that sponsor. He maintained his integrity throughout a long and arduous project, even when the goal seemed unreachable. While he was firm and resolute in his adherence to the plan, he also was flexible enough to allow his plans to change when new situations arose.

Moses completed his project successfully even though he faced some of the most extreme obstacles. His sponsor didn't just think he knew it all, he DID know it all. His path was blocked by some unimaginably difficult obstacles. His stakeholders often lost all interest in the project. Who would have blamed him for resigning.

He persevered, though, and his people reaped the untold rewards of his dedication.

Moses was truly a Hero Project Manager.

Sunday, April 22, 2012

Project Manager for Heroes

Mike Pungercar, of Springfield, Oregon, is a Hero Project Manager. There's no doubt about it in my book.

I read about Mike's project in an article, Flights give vets the hero treatment, in the online edition of the Register-Guard of Eugene, Oregon. Mike is project manager for South Willamette Valley Honor Flight, a part of the nationwide Honor Flight project. This project's mission is to take veterans of World War II on a visit to the World War II Memorial in Washington, DC.

As we are reminded in the article, we are losing this generation of heroes at a rate of about 850 per day. The day will soon come when we will no longer be able to honor them in person. We'll only have the memories of their sacrifice. And, a little farther down the road, it will only be something to read about in history books.

Today, though, we are honored to still be able to know them, to speak with them and to express our gratitude for their service. Maybe their actions in the war were heroic, or maybe they were only relatively routine. But, as far as I'm concerned, they all played an important part in an effort that helped preserve our way of life, our world.

File:US landings.jpgMy father fought in the South Pacific as a tail gunner for the Army Air Corps and later as a member of the Military Police corps. He was involved in action all along the chain of islands that lead from Wake Island around the southern rim of the Pacific through New Guinea and Guadalcanal, finally ending up in Tokyo. He didn't talk much about it. When he did,  at the time, I didn't realize just what he had gone through. Now, in retrospect, I am sad that I didn't understand, while he was here, what he experienced. I know I still don't fully grasp it. I've not been in combat situations, so I can't grasp it.

At least, thanks to books and movies and other sources, I do better understand what he and so many other men and women did for us. Daddy died over thirty years ago, before I understood, as I do today. I never paid him, in person, the honor he deserved.

So, Mike Pungercar is a Hero Project Manager. A hero for heroes.

And, today, I promise I will, in some way, contribute to Mike's project. Will you?

Tuesday, April 17, 2012

6 Project Leadership Super Powers - PM Hut

On the blog Project Management Hut Ty Kiisel posted an article, 6 Project Leadership Super Powers, that ties in nicely with the theme of this blog. While I contend that we all need to be heroes and avoid trying to be superheroes, Ty makes a good case for trying to make sure we do our best to fit these six "super powers" into out project manager tool kit.

Here's the opening paragraph.It is an interesting and fun-to-read article.


6 Project Leadership Super Powers

April 17, 2012 | Author: PM Hut | Filed under: Leadership


6 Project Leadership Super Powers
My friends and I will sometimes debate whether Superman or Batman is the more interesting superhero. Technically, I guess Batman isn’t a superhero at all, he’s just a very disturbed guy who has the ability to create some incredible crime-fighting gadgets that make him appear to be a superhero (he’s my choice for most interesting superhero, by the way).
Superman, on the other hand, has a number of very incredible superpowers that make him more than a match for the average villain. The “Man of Steel” is too squeaky-clean and unbeatable to be really interesting in my opinion. Give me a flawed, kind of messed-up superhero for real “interesting” potential.
A couple of years ago I came across...

Monday, April 16, 2012

Was Benjamin Franklin a Hero Project Manager

Most Americans would agree that Benjamin Franklin was a hero. Among so many other things, he was instrumental in the founding of our country, the United States of America. He is certainly one of my heroes.

Without studying his project management abilities very deeply, I can guess that his character traits would have made him an excellent PM. But he was certainly not a superhero. In reading about him, he didn't seem to try to be. Even in his own writings, he admits that he was constantly struggling to learn to apply the qualities of a strong character to his life. He wanted to consciously practice desirable character traits until they became so deeply a part of his character that he unconsciously practiced them. They ultimately became, not traits he tried to exhibit but, traits he possessed in his core being.

Benjamin Franklin worked to ingrain within his character traits such as integrity, responsibility, commitment, humility, patience and courage. He monitored his actions and interactions with others to determine if he was successfully applying those traits. He sought ways to correct any tendencies to stray from those principles of good character. He was committed to becoming a man of good character.

In an article that I found through LinkedIn's Toastmasters Int group, Wyn N. Davies asks Are You a Pilgrim or a Tourist? Wyn speaks of life in general, but his message applies to us as project managers directly. Are you just a tourist in the role of project manager? 


Or are you a pilgrim, committed to BEING a project manager. If so, you will follow Benjamin Franklin's example and constantly try to build into your core character those traits that make us heroes. Traits such as cooperation, sound reasoning, perseverance and integrity. 


With that commitment you will be someone's project management hero.

Saturday, April 7, 2012

Want to be a Guest Contributor?


Add Your Thoughts About Being a Project Management Hero

Maybe you agree with what has been posted here. Or maybe you don't. Either way your opinion will add to the conversation. We are bound to learn more about who we are and what we are trying to do if we have an open dialog with others.

One way to add to the conversation is to comment on the articles that are already here. I welcome all appropriate comments, although I do reserve the right to hide those I think are inappropriate.

Another way to add to the dialog is to be a Guest Contributor. If you find that you feel the need to write a comment that gets to be longer than a few paragraphs, maybe it should be a post all on its own.

Or, if you read a relevant article somewhere else, maybe we should re-post it here. You'll get credit for finding the article and the author will get credit and more readers through the links on this page.

Your post can be your original content or it can be a re-post from another source. Just make sure proper credit is given with links to the original article.

If you have an idea for a post you would like to submit, leave a comment to this post. I'll contact you and we will make arrangements to post your article.

Hero... or Superhero

As I stated in my first post, of the article  The Project Manager, a hero in Project Management
Posted by Marian Woods on March 22, 2012 at 12:57pm 
Project Managers  , Marian's article was the inspiration for this blog. I will be writing about and collecting stories about project managers and their projects. And, yes, some of them will be heroes.

After adding Marian's article to my blog, I re-posted it in some project management discussion groups on LinkedIn. The result was some quite lively discussions about the concept of the project manager as a hero. In a way, I think the discussions got off track a little from the intent of the original article. At least, in my opinion.

The main message that I took away from Marian's article was the importance of six basic skills in effective project management. Those are:

  1. Communication
  2. Team building
  3. Problem solving
  4. Leadership
  5. Commitment
  6. Organization

Monday, March 26, 2012

The Project Manager, a hero in Project Management

The Project Manager, a hero in Project Management:
Posted by Marian Woods on March 22, 2012 at 12:57pm
Project Managers
After reading some articles on the importance of a good project management tool it got me thinking about the human aspect of project management , that being the project manager! What makes a project manager stand out from the rest of the team? And what skills do the need to hold in order for the project to be successful?
The project manager is the leader of the pack when it comes to project management, they are thoroughly involved in the running of a project before, during and after it is completed. The project manager gives the project team the necessary direction needed for them to work together and get the job done! A major part of the project manager’s job is to organize and control the work flow between the project team members to ensure that the work gets completed on time and precisely.
So what makes a first-class project manager? For the most part a project manager possesses the practical skills and organisational view needed to manage a project accurately; however it’s the skills that can’t be taught that really makes a project manager stand out from the rest.
  1. Communication: A project manager needs to possess this skill if he/ she are to effectively discuss the conditions of the project to the project team members.
  2. Team building: A project manager is the ring leader and must have the ability to bring the team members together. The project manager will build a team with different skills who are able to work together on any given project.
  3. Problem solving: Problems will arise and a project manager won’t always have the luck where he/she can predict them. However whether they are prepared or not they must have the skill and knowledge to be able to deal with the problem before it has an impact on the overall project. Therefore it is extremely important that a project manager has the ability to solve problems as they hit.
  4. Leadership: A project manager is answerable to any aspect of a project and consequently needs to show leadership skills. The “will say will do” skill is critical to project success.
  5. Commitment: Having the commitment to see a project through and ensuring that the project is completed in line with the project plan, expected results and goals is vital in the project manager’s role.
  6. Organization: A project manager needs to be able to visualize the project right up to the end, in order for them to have the ability to organize the workload of the project into sections and across multiple resources. Right person for the right task is order of the day.