Top Tags

Tag team

The (New) Hierarchy of Needs – Part V

[This is the final segment of a five-part series on project management that is based upon Abraham Maslow’s “Hierarchy of Needs”]

Problem Solving

The next level starts to go into the core of the project – problem solving.  This is essentially what all projects are about.

What is a problem?  A problem is an obstacle which makes it difficult to achieved a desired goal or objective.  Problem solving can be fun as it helps to build a certain skill set regardless of the topic.  In the project management space, problem solving is the name of the game.  While many problems may be obvious, there are many that will not be as obvious and may remain hidden.  It’s the job of the project manager to uncover these hidden problems and take steps to address them.

To ensure understanding, hidden problems are those that are known by the project team but aren’t being surfaced to project leadership.  Team members are more likely to hide problems if they don’t have confidence these problems will be addressed.  Problems can also remain hidden if there isn’t a clear understanding of who can solve them.

Your role as project manager is first and foremost your relationship with the team – if team members have a clear understanding of the objective and team organization, and have confidence in your ability to lead, problems will be raised much more rapidly and the team will be able to make greater traction in the long-run.

Thus, your ability to lead, instill “order” and “structure” and tackle the tough problems are all very important in this “layer”.

Momentum

At the top of the pyramid is momentum – that’s what ultimately keeps the project going!  Initial momentum naturally follows the layers just described, but it ultimately requires a core belief that the project will be successful.

As shared earlier, the ultimate goal of this new hierarchy is to have every team member reach their full potential.  While this is a lofty goal, if you want to deliver a quality product / service in a short period of time, this is what you need to shoot for.

As with any moving object, ensuring that you maintain positive momentum is ultimately dependent upon the source of “power.”  In a project, that source of power is the team and the hierarchy tiers that fall just below this one.  The more organized and refined the underlying layers, the less “friction” and the longer you can maintain positive momentum over the long-term.

References:

The Project Survival Kit

If you were deserted on a stranded island, what three things would you take with you?  While there is no official answer to this question, you could answer this question by identifying the core fundamentals of survival – essentially, food, water and shelter.  If your three things address these needs, you have a good chance of survival.

A similar stance can be said for project management.  All too often, managing a project introduces specific processes, tools, documentation and applications all of which are designed to streamline the act of project management, but may do the complete opposite in enabling true productivity.

I believe that there are three things one needs to have at her/his disposal to accomplish a specific task with a discrete number of resources.  These three things can be thought of as the “project survival kit” – their collective use allows one to “get the job done.

1. Description of the end-state – This 1-2 page document is an expansion of a traditional “scope” statement.  It provides a full picture of the project including artifact creation, team dynamics, communication plans and final deliverables.  The intent is to describe the “ideal” project in sufficient detail before you start working.  Think of it as your “map” to your destination.

2. Team Strengths and Personality Inventory – You have resources at your disposal, but how do you utilize their talents in the best possible way?  Know the strengths and personalities of your team members!  When the relationship is strong, anything is possible.

3. Organizational Chart – If you don’t know how project participants are “linked” to one another, your effectiveness as a project leader will be limited.  In addition, you run the risk of “crosstalk” (redundant and inefficient communication) between project participants which can impede progress.  Also, if there is more than one leader identified on the chart, you have a problem.

So, what am I leaving behind?

You’ll notice that I don’t have a timeline or project plan listed.  While I think a timeline is useful, I don’t think it’s one of the top three.  If you know what you are looking to accomplish, have a good sense of how the team will be organized to deliver this end-state, and their strengths, the project will move forward at it’s most efficient pace; a timeline isn’t going to matter.

I also don’t have risks identified.  Remember, anything can happen.  Even if you list all of the risks you know about, there are plenty of things that you likely don’t.  Spend your time on what’s happening now. If an issue exists, take action.

To be clear, I am not suggesting that you completely eliminate the use of supporting documents or forgo the use of a project plan if it provides a real benefit.

However, by looking at projects with a forward-thinking mindset, I think you’ll be less concerned about timelines, documentation, “CYA” strategies and risks / issues inventories.  Instead, you’ll be utilizing resources whose activities are all designed to achieve the end-state in the most efficient and enjoyable manner possible.

It’s about focusing your attention on the activities that truly matter, and isn’t that what getting things done is all about?