Cheat Sheet for Managers: 101 Ways to Rise Above the Pack

InsideCRM has an excellent cheat sheet for managers, covering topics such as:

- Body Language
- Meeting Deadlines
- Getting Along with Employees
- Managing Yourself
- Boosting Productivity
- Managing Finances and Resources
- Communicating with Clients
- Keeping Up with Change
- Resolving Problems
- Going Above and Beyond

I've read through the list and there are some excellent reminders and insightful tips here. This is the kind of list that's good to print out and read on the train, keep on your desk, and read periodically to renew your focus.

It's billed as a "common sense" list of advice, but I find that much of it is quite uncommon (you know what they say about common sense). Kudos for the folks at InsideCRM for putting this together.

Check it out...


The Manager's Cheat Sheet: 101 Common-Sense Rules for Leaders - Inside CRM

Management Truths: Can You Handle It?

Jack says you can't handle the truth. But if you're ready, I highly recommend Stephen Robbins' excellent book, The Truth About Managing People... And Nothing But the Truth.

Robbins has sold over 2 million copies, and I can see why. In plain, simple language, Robbins outlines 63 truths, supported by evidence, stories, and examples. Each truth is only a few pages, so you can open the book up at almost any page and find a gem. The whole book is under 200 pages in a small paperpack format.

The 63 common-sense truths span the areas of hiring, motivation, leadership, communication, team building, conflict management, job design, performance evaluation, coping with change, and managing behavior.

A few good lessons (paraphrased):

1) Productivity usually breeds satisfaction, rather than the other way around.

2) When interviewing, don't go on traits. Instead probe about past behaviors (i.e. "Tell me about a time when you ....")

3) Put people in jobs that match their personalities.

4) Out of all the traits people have, conscientiousness is the most frequent predictor of success.

5) Specific stretch goals produce higher output than generalized goals like "do your best."

6) Not everyone wants to participate in setting their goals. It depends on their nature, ability, time available, and other factors.

7) Judge behaviors, not people.

8) There's something to be said for "looking the part of the leader."

9) Expect the best and people will deliver. Expect the worst, and people won't dissapoint.

10) Experience isn't always a good indicator of success.

11) There's no ideal leadership style. Directive or supportive styles can work in different situations.

12) Teams often create negative synergy. Beware of loafers. Be sure to identify and measure individual efforts as well as team efforts.

13) Honor the work-life balance. Give flexibility and options.

14) Beware of the quick fix. What works for one company or problem doesn't always work for another.

For many more, and further explanations and examples, read the book!

Project Management Imperatives: Ten Keys to Success

Someone recently asked me what I felt the critical success factors were for any project (i.e. what were the top "must do's"). Although I can think of many more, here were what I felt were the top ten:

1) Get the roles right. (Insure accountability; use a RACI chart or Responsibility Matrix so roles are clearly defined. Insuring people understand their commitments up front will avoid problems later.)

2) Get the goals right. (Make sure all the key stakeholders agree on the goals. I've seen more projects go wrong for this reason than any other. Time spent here will pay dividends later.)

3) Get the current scope right. (I say "current scope," because change should be expected. Projects by default contain change because they are unique in nature. It's not whether you'll experience change, it's how you analyze the potential impacts and manage the approval of the change that counts. Agreed-upon and approved scope changes are perfectly acceptable, with one caveat: It's often wise to set a limit to the number of times scope can be changed for the current product release, and defer some changes to a subsequent release, else value gets delayed.).

4) Obtain commitment from the business, customers, and other stakeholders as to their part in the success of the project. (Many projects derail because the customer doesn't live up to their side of the bargain, doesn't understand their side of the bargain, or some other necessary constituent isn't cooperating for various reasons. Obtain the right commitment up front, starting with senior management.)

5) Determine the critical success factors and risks. (Critical success factors and risks go hand in hand. Many people ignore this or sweep it under the rug, and accept any related risks as a given. The critical success factors will identify related risks and help set expectations).

6) Set expectations. (This is frequently overlooked and is a key cause of failure. The sponsor, customers, and anyone impacted by the project must be given realistic expectations for what is needed from them, how long the project will take, how much it will cost, what the uncertainty factor is, what the available resources are, and anything else necessary to avoid surprises and/or an under-equipped effort.)

7) Beware of conflicting directives. (I call this the "Robocop Syndrome." In the film, Robocop, the titular robotic policeman goes on full tilt when he encounters directives that conflict with his primary directive. I see this happen often in organizations where a project sponsor demands something that is in conflict with other key stakeholders' wishes and/or top organizational directives. This could be covered under "goals" or "expectations," but it's so important that it warrants its own point. The project manager must head this off at the pass before the project goes down a rat hole it won't recover from.)

8) Plan Collaboratively. (The act of planning is not an isolated exercise. It's a collaborative exercise and should be done with the project core team and subject matter experts via some sort of facilitated brainstorming session---possibly with sticky labels on a wall.)

9) Beware of unilateral and granular "one-size-fits-all" solutions. (This is often ineffective, both as a project management methodology and a process implementation policy. Look at the big picture, and the potential variations. Keeping a framework high-level can allow for greatest flexibility and adaptability. Aim for principles over rules wherever possible. Use rules when safety is involved, regulatory requirements exist, or exact accuracy is needed---per Marcus Buckingham's guidelines from "First Break All the Rules.")

10) Don't let rank set you off course. (Often, a senior manager pulls rank and makes requests that are either detrimental, unwise, or in direct conflict with organizational goals. When this happens, see rules 6 and 7. It is the project manager's responsibility to set the right expectations, warn of potential risks, and head off potential conflicting directives at the pass.)

There it is. My list of "must do's." Project management isn't rocket science. In fact it's not a science at all. It's more of an art. Hopefully, the guidelines above can serve as a useful palette.

21 Success Secrets of The Beatles

One thing I enjoy doing is studying excellence. There's something about unique, extraordinary human achievement that I find fascinating.

I love studying it, dissecting it, and extracting lessons from it. It's what attracted me to write about Napoleon. It's what led me to explore lessons from Einstein. And it's what leads me to dive into lessons from The Beatles.

Like them or not, nobody can argue that The Beatles didn't achieve amazing feats. I doubt there will ever be another musical group that could rival them for sheer impact on the music scene and the world.

They were the first pop artists to record in stereo. They were the first band to experiment in the studio. They were the first band to list lyrics on their album. The list goes on and on.

But what made them so successful? And are the lessons applicable to building successful and innovative individuals and teams in business? Here are 21 lessons that answer definitively "yes."

1) Focus on Strengths - They focused on their strengths, doing what they do best (songwriting and performing).

2) Engage a partner - They got help (from Brian Epstein, their manager, and George Martin, their producer). They couldn't have achieved such heights on their own.

3) Differentiate! - They dared to be different, whether it was their suits, their hair, the instruments they experimented with, their neverending search for new chords, and so on.

4) Have key values - They stuck to principle themes, such as love, peace, and the search for truth.

5) Adopt a cause - In the band and in their solo careers, they always had a cause that they were passionate about, whether peace, vegetarianism, eastern philosophy, or some other passion.

6) Worship change - They weren't afraid to change, even in the midst of success. At the top of the moptop craze, they changed their style, then they changed again with Sergeant Pepper, which was a virtual celebration of change.

7) Broaden your horizons - They continuously sought self-growth, learning new philosophies, new chords and instruments, etc.

8) Be passionate about everything you do. They treated each deliverable (i.e. song) as THE hit, which is why their "B-sides" did better than most people's A-sides.

9) Embrace conflict - They readily embraced creative conflict and friendly competition. It was precisely the conflict and competition between Lennon and McCartney that made each of them strive for new heights.

10) Keep moving - Fast! - They recorded constantly, always looking for some new and unique angle. They recorded first and asked questions later.

11) RMF (Risk Magnificent Failures) - They experimented with new chords, new concepts, and had some celebrated failures (Revolution #9-although some liked it; the Magical Mystery Tour Movie, in which they filmed everyone on a bus in the hopes that something neat would happen--nothing did). In a sense, each album was also an experiment in some way.

12) Aim for the Skies - They thought big ("To the toppermost!" they used to say) and they believed it! Similar to Napoleon Hill's principles in Think and Grow Rich, they aimed high and got there.

13) Talent matters - When all is said and done, they had the right talent. All the other elements wouldn't have helped if they didn't have a natural talent for music. Luck helps, but if you have the right talent in the right job, the luckier you get.

14) Use your whole brain - They used the left and right sides of their brain---using the right side when freeflowing creativity and innovation were needed, and the left side when the proper structure was important.

15) Have Fun!!! - Above all, they had plenty of fun, and even stressed the importance in the song "She's Leaving Home" (about a girl who left home to explore "something inside that was always denied for so many years---She's having fun, bye bye.")

16) Never Conform - They didn't conform to standard education, which led to their unorthodox style. In fact, I've noticed most great pop musicians hold their instruments "the wrong way." Tom Peters pointed the same thing out about great Tennis players and their rackets.

17) Field the right team - They were built for synergy -- each were different but shared the same values. The whole was truly greater than the sum of its parts.

18) Get noticed! - They wouldn't have gotten anywhere if they didn't get noticed in the first place. How did they get noticed? By playing in public, where they could get noticed. This should stress the importance of networking. Be seen.

19) Prototype and Test! - They prototyped and tested zillions of versions of their songs. For each hit, there were about 20 alternate takes in different styles and genres. And they practiced each version over and over.

20) Study the greats, Then forget them. - They didn't begin in a vacuum. They studied their idols, such as Chuck Berry, Carl Perkins, Fats Domino, and others. If you want to succeed at something, a good place to begin is studying those who have succeeded before. But then make your own way, just like The Beatles did. Carve your own niche.

21) Be Authentic - They were authentic to who they were - British lads from Liverpool.They could sing colorful lyrics about places like Penny Lane and Strawberry Fields, and could talk about TV shows like "Meet the Wife" ("It's time for tea and Meet the Wife" from "Good Morning"). They could sing about these things because it's who they were, not because they were trying to be cute or clever. It's important to be true to who you are, not who you'd rather be.

Is the Role of the Project Manager in Jeopardy? - An Editorial

A few weeks ago, I posted a blog about the new Program Management credential from PMI. In it, I referenced PMI's definition of a program manager vs. project manager in their FAQ page.

A project manager, according to PMI, has the following responsibilities (I've put some of the key points that jumped out at me in bold):

• Perform their duties under general supervision and are responsible for all aspects of the project for the life of the project
• Lead and direct cross-functional teams to deliver projects within the constraints of schedule, budget and resources
• Demonstrate sufficient knowledge and experience to appropriately apply a methodology to projects that have reasonably well-defined project requirements and deliverables.

A program manager, according to PMI, has the following responsibilities (again, I've bolded the key points):

Under minimal supervision, program managers are responsible and accountable for the coordinated management of multiple related projects directed toward strategic business and other organizational objectives. These programs contain complex activities that may span functions, organizations, geographic regions, and cultures. Program managers build credibility, establish rapport, and maintain communication with stakeholders at multiple levels, including those external to the organization.

Clearly, a program manager must be closely tied to the strategic goals and benefits, monitor the program accordingly, and have a strong connection to senior management. And I also feel that the new credential seems on the surface to set the bar appropriately high.

But I can't help but feel that, in contrast, the PMP credential is losing steam. First, there are myriad organizations virtually guaranteeing an "instant-PMP" after a crash course and some tweaking of one's background experience (although PMI is now doing audits of work experience).

Second, a project manager must, in many cases, go beyond the PMP/tactical focus and possess the same traits and skills that PMI has designated as requirements of a program manager, especially in the case of an enterprise and/or global project, such as a business transformation effort. I realize PMI's role definitions are a way to differentiate and justify the new certification and I suppose one could organize their effort into a "program" to qualify for that certtification, but in these changing times (and with greater challenges for project managers), I think PMI needs to evaluate and revamp the PMP certification as well.

When I do presentations on principle-based leadership training, I have a slide where I present what I call "The PM Challenge." I present it as a boxing match. In one corner, we have a project manager, armed with MS/Project and the PMBOK, but lacking:

• Business Acumen
• Leadership Skills
• Conflict Management Skills
• Negotiation Skills
• Presentation Skills
• Communication Skills
• Strategic Intuition

In the other corner, we have the "challenger," represented by "the project," with the following characteristics:

• Global, virtual team
• Complex technology
• Complex change
• Multiple vendors
• Offshore resources
• Conflicting Stakeholders
• Scrutinizing Executives

Such a project manager, without the appropriate leadership and soft skills, doesn't stand a chance. Wouldn't a person with the skills PMI describes as a "program manager" be more apt to have success?

In the latest PM Network magazine from PMI, there are not one, but TWO articles that illustrate this point. One is titled "Project Management 2.0: Project Management is at a Crossroads," by Peter Fretty. The other is titled "No Limits," by Marcia Jedd, and talks about what project managers must do to crash through the glass ceiling and elevate it from the tactical trenches.

Perhaps a start would be to take a new view of project management beyond just "executing to a set of requirements to deliver on-time and on-budget." The current tactical focus might explain the consistent failure rates of projects. One problem is that PMI has traditionally "followed common good practices in the field," which of course is what a standard is supposed to do. The problem is that common practices have brought common results, which aren't all that good. Time for an upheaval. Perhaps they need a section, apart from the "standard" itself, for "new frontiers in project management," which could outline those who are breaking the mold with good results.

I'd be interested in others' thoughts on this topic. Who knows---It just might help drive requirements for the next version of the PMBOK and/or PMP credential.

Software Projects Doomed From the Start; Blame the Stakeholders

OK, maybe this doesn't top the skateboarding dog (see yesterday's post), but here's an extremely compelling article from the Defense Acquisition University (DAU) on why most software projects are doomed to failure.

Thanks to PMForum for posting this in their news section.

The article states that most software projects come nowhere near their original baselines (although they may come closer to approved revised baselines). It says that stakeholders and the organizational environment, more so than lack of project management skills, bear much of the blame. Here's a quote:

"No amount of training in the technical skills of program management will overcome the simple truth that, as a PM, you cannot make people do what you need them to do. This is the root cause of many software-intensive program failures. Stakeholders often cannot agree on priorities, refuse to standardize business practices, take off on their own proprietary solutions, or simply refuse to participate in the program."

The article also says that the original plans are usually unrealistic to begin with, and underestimate the organizational challenges. It says we make matters worse by holding project managers accountable without giving them the necessary support to be successful.

"... Most expectations of contemporary programs are unrealistic. The cruel reality is that we train PMs and drop them in an organizational 'shark tank' that opposes many of the principles they have just absorbed in their training. Program managers often find themselves in a superfluous role, accountable, yet powerless. "

The article proposes a system of observing stakeholder behavior and rewarding and discouraging behavior as appropriate. Of course, an organization must recognize the problem and commit to doing something about it.

Senior leadership must be actively involved in fostering the changed behaviors. Otherwise, software projects will continue to be underestimated and mired in conflict, despite the best training, the best EPM tools, and the best processes.

I highly recommend reading the full article, "Irreducible Truths of Software-Intensive Program Management", by David Cottengim.

PMFORUM, Connecting the World of Project Management PMFORUM Breaking News: MOST SOFTWARE PROJECTS ARE DOOMED TO FAILURE ACCORDING TO PENTAGON PAPER

Outsourcing Project: Lessons Learned

I would like to have been at this project close-out briefing, at the completion of the outsourcing transition. ... Let's see ... what lessons have we learned? ... Update code of business conduct?

... "Indian outsourcer Wipro selected Morgan Stanley as the lead underwriter in its ADR listing on the New York Stock Exchange. Later, Morgan Stanley tapped Wipro for some IT work. " ...

Via InformationWeek Weblog: Morgan Stanley E-Mails Reveal Outsourcing's Dirty Little Secret

Via Wipro Code of Business Conduct (PDF): "A conflict of interest exists where the interests or benefits of one person or entity conflict with the interests or benefits of the Company. ... "

Via Morgan Stanley Code of Ethics: "Employees and officers should promptly report any potential relationships, actions or transactions (including those involving family members) that reasonably could be expected to give rise to a conflict of interest to Law or Compliance. ... "

Laws Of Project Management

Although I found this article under jokes at funnymail.com, some of these are no laughing matter. A few of my favorite "laws" of project management include:

1. No major project is ever completed on time, within budget, with the same staff that started it, nor does the project do what it is supposed to do. It is highly unlikely that yours will be the first.

2. The effort required to correct a project that is off course increases geometrically with time.

Corollaries:
a. The longer you wait the harder it gets.
b. If you wait until the project is completed, its too late.
c. Do it now regardless of the embarrassment.

3. Anyone who can work effectively on a project part-time certainly does not have enough to do now.

Corollaries:
a. If a boss will not give a worker a full-time job, you shouldn't either.
b. If the project participant has a time conflict, the work given by the full-time boss will not suffer.

4. Projects progress rapidly until they are 90 percent complete. Then they remain 90 percent complete forever.

For more Laws of Project Management see:
The 15 Laws Of Project Management

Integrity is Job One

Integrity not only means that your actions are aligned with your words, it also implies that both are ethically bound. Most importantly, it implies 360-degree accountability, meaning that you are accountable above, below, and sideways, in the organization.

That's not to say you can't make a final decision (and indeed you must), but you need to observe, listen, and consider all angles and impacts before making what you feel is the right decision for the organization. And, for real success, you need to do it quickly. This is done easier in an environment of decentralized-decision making, operating under a set of basic guidelines and high level objectives.

When operating in a more autocratic environment, it can be challenging, especially if the orders conflict with your better instinct.

Here's a great quote I came across in a Tom Peters presentation. The quote comes from Colonel John Boyd, the legendary fighter pilot who founded the concept of OODA loops (Observe, Orient, Decide, and Act), which also helped organizations like Toyota become so successful.

“If your boss demands loyalty, give him integrity. But if he demands integrity, give him loyalty.”

-- BOYD: The Fighter Pilot Who Changed the Art of War (Robert Coram)

This is a motto we should all carry with us.

Process vs. Freedom; Finding the Right Balance

There's a great article in Computerworld about finding the balance between having well-defined, repeatable processes and allowing businesses (and project managers) the freedom to innovate. A flexible approach is key.

Here's an excerpt from the article:

Studies have shown that the consistent use of processes increases repeatability, productivity and quality while decreasing project delivery time. But these same processes can appear as a wall to the business people who are pressured to get
their ideas to market. The project team ends up on the battle line between the program management office (PMO) enforcing the procedures and the business people seeking to retain their freedom.

The article goes on to suggest ways to minimize conflict and satisfy both audiences. Read on...

Surviving Process Without Going Berserk - Computerworld

Keeping Projects Positive; Watch Out for Those Seagulls

From the Wall Street Journal Executive Career site comes some good advice for managers leading organizations (or project managers leading projects) through dark times. And dark times are the norm these days, with offshore outsourcing, cutbacks, and short-term focus an epidemic in America.

Three bits of advice are:

1) Avoid Seagull Management: Don't focus on the negative by swooping down, crapping all over everything, making a lot of noise, and then flying off. Avoid negative judgment and try to "catch people doing something right" Positive reinforcement is key.

2) Embrace Conflict: Conflict isn't a bad thing if it's managed. On the contrary, it can lead to true progress. If everyone agrees all the time, things can get stagnant. The main thing is to encourage a collaborative atmosphere and work to solve the problem instead of assigning blame.

3) Good Comes Out of Bad: Look to make lemonade out of lemons. If there are problems or issues, look at it as an oppportunity for improvement.

I would say that these rules should apply in any circumstance, whether amid economic strife or not. They're also very much aligned with Peter Senge's "learning organization" approach. For more, read on...

CareerJournal Management -- Career Advice for Managers

Results vs. Process - Revisited

The other day, I posted a blog on results vs process. The conclusion I came to was that for projects (which are by nature of limited duration), it was more important to do what it took to assure good results than to blindly follow process.

Of course, the definition of "good results" must be agreed upon. I also added the caveat that this does not apply to processes that must be observed to assure adequate results.

While I still fully believe this approach is true as a guiding principle for project managers, I've come across two good arguments in defense of process in general:

1) Results are often uncontrollable, while processes (if maintained) can at least assure more consistent results over the long haul. Uncertainty is a given, and good processes will allow for that and plan for that.

2) Conflict should always be expected, and should be used to improve processes rather than be seen as an impediment to results. Conflict is a good thing. Unresolved conflict is not.

My clarification of "results over process" is this:

• When defining processes, don't make the processes so heavy and bureaucratic that they impede results.
• Introduce processes slowly. Don't expect overnight results; Follow a maturity model and strive for continuous improvement.
• Relentlessly search for less invasive ways of accomplishing control.
• For each potential new process, use the"Five Why's" (asking "why" five times until you determine if the process in question is really needed). If in doubt, don't add it.
• Allow room for people to make decisions. If a principle will work just fine to help keep people on course, then don't institute an unnecessary process. Not everything can or should be "process-ized." Generally, aim for principles over processes wherever possible.

I do think Toyota has it right. By focusing on long-term results (i.e. continuous improvement) over short term results, continued success is more assured. By we don't want to unnecessarily impede short term results either. We can walk this balance by keeping our processes lean and giving project managers the freedom and confidence to do what is right to successfully deliver a project. People are ultimately our best asset.

Project Success Equation; The REAL Triple Constraint

We've all heard the issues over the triple constraint, and whether it should include scope, time, and cost, or other factors as well. But the "real" triple constraint often goes unnoticed. And that is the old trio of "people, processes, and technology".

We need to invest in all three in order to have project success. By "people," I'm not only referring to investing in leadership training for project managers, but also to having an organizational structure that's aligned and not set up for conflict.

And, while processes are critical, some things cannot be "processized," such as leadership and stakeholder management. And processes alone, without the technology to make it efficient, can also be a burden.

So next time you're analyzing the success or failure of your project, consider the impact that people, processes, and technology had on that result. There may be some eye-openers.

Are Your Project Managers Leaders?

If you ask someone who just worked on a great project to rate the project manager, very rarely will you hear them say the following:

"Great! He really knows his MS/Project!"
"Wow! She's a wiz with Earned Value!"
"Top notch. You should see how he links all the dependencies together."
"Stupendous! She can do a backward pass with her eyes closed!"

More than likely, you'll here something like:

"He was extremely visible and gave us the confidence that someone was running the show."
"She was able to remove all of our barriers and communicated extremely well throughout the project."
"He was really on top of the issues, yet didn't micromanage"
"She offered clear guidance and goals, and fully engaged the team, soliciting our input wherever possible."

See a pattern? While it's important to master the "mechanics" of project management, ultimately it's all about leadership --- the soft skills. Unfortunately, when organizations send their project managers to training, they tend to focus on tools training, or training in project management fundamentals. Certainly these are valuable, but the real need (and most frequently ignored area) is training in the soft skills.

And the best way to train people in soft skills is some kind of course that offers simulation training. It's good to understand theory around conflict management and psychology, but there's nothing like simulation training to really sink in.

So, if you want to really make a difference in how your project managers are perceived, focus on leadership training, including team leadership, presentation skills, communication, conflict management, negotiation, assertiveness, motivation, and other soft-skill topics that can define people's perception of the project manager.

Project Management Soft Skills; Communications, Conflict Management, Ethics, and More

With all the focus on project management techniques, such as planning, scheduling, cost management, etc., it's easy to forget that communication is 90% of a project manager's job. And that includes conflict management, resolving ethical dilemmas, team building - all the soft skills that can make or break projects.

In fact, most project failures are in some way tied to a lack of communication. I've seen many projects where all the techical stuff was done right, but the project was perceived as a failure due to poor communication. Likewise, I've seen project where one mistake after the other was made, but the project was seen as a shining success because it was well communicated.

The site below offers a wealth of valuable articles on the soft skills of project management, including communication, conflict management, ethics in project management, organizational development, and more. Perusing these articles would be time well spent by any project manager or leader.

Point Lookout Archive by Topic - Chaco Canyon Consulting

Managing Conflict the RIght Way

As we know, Project Management is all about communication and people. And whenever people are involved, conflict is bound to arise, whether among the project team, with customers, with stakeholders, or with the sponsor.

Conflict Management is a vital skill for anyone in business, but especially so with project managers.

Here's a great writeup from the University of Nebraska-Lincoln regarding conflict management...

Managing Conflict Successfully, HEG83-181-A