Project Management

Don't Make Individual Team Members Blow Their Own Horn

From the Strategic Project Management Blog
by
As an "accidental" project manager, it's very satisfying to contribute to the project management community online with anecdotes and stories I've picked up from my own experience. I hope you enjoy our daily conversation.

About this Blog

RSS

Recent Posts

Tell Me You're Going to Get This Done

Quiting Isn't Easy if You Never Do It

Getting in the Way of Peak Performance

The Agony of Defeat?

Nobody Likes Being the Heavy

Categories

decision-making, empowering team members, project leadership, project management, project management fundamentals, project success, project teams, struggling projects, work management

Date

linkedin twitter facebook Request to reuse this  


Employee RecognitionI once worked with a guy who felt the need to take credit for anything good that happened within his department. If anyone noticed something the team had worked on in a positive light, he took credit for it. "Yeah, that was my idea," he would say. On the other hand, if it was something that wasn't as positive, he would blame the team. Most of us had skid marks on our backs where the bus had slammed on the brakes for another pass.

Needless to say, it didn't really take very long for him to expose himself as the fraud he was. Ultimately the team didn't like him, his boss didn't respect him and he was sent packing.

As a project leader (or any kind of leader for that matter) I think it's important to appropriately recognize achievements. In a recent article titled How to Build Trust When Your Team Doesn't Know Each Other, written by Wayne Turmel for Bnet, Turmel suggests, "There are many ways to show off the competence of team members. When you have message boards and social network tools, there are opportunities to answer questions, refer other team members and generally offer individuals a chance to shine they might not otherwise get. As the manager, take the chance to commend workers in ways that let the entire team know who did such great work."

In many organizations that espouse a top-down command-and-control management approach the only time anyone hears from the boss or their manager is when there's something to do or something is wrong. I like the idea of making it a point to look for ways to show off the competence of my team—to share their accomplishments with my superiors. It creates an atmosphere where people aren't afraid to speak with me and makes it a lot easier to have those sometimes difficult conversations when there are problems.

There's nothing wrong with finding ways to shine the light on exceptional effort or an exceptional member of the team. What's more, although money is a motivator for performance, it isn't the only motivator. Most people leave their employment for reasons other than money. Maybe their commute was too long, maybe they didn't like the job—but it's more than likely they didn't feel their contribution was recognized and appreciated or they didn't like the boss.

Over the course of my career, I've noticed the times when I've been the most successful have been the times when I've been able to facilitate an atmosphere where individual members of the team could shine and be recognized for what they bring to the effort. When my need to shine is superseded by the ability of individuals on my team to shine, projects have been more successful, the team is happier and as a result, it reflects well on me.

As a side note, in most cases, praise for a job well done should be specific and public. Vague platitudes aren't worth the wasted words. "Jones, the extra work you did to get the Acme project in on time really made the difference," is much more effective than, "Good work everyone."

Specific and public is how I try to address praise to members on my team as opposed to reprimand, which should be handled privately—unless you want to do irreparable damage to personal relationships (which are the foundation of project leadership in a world where most of the time everyone on the project team is usually a dotted line on the org chart).

What do you do to recognize exceptional work or exceptional team members?
 


Posted on: June 01, 2011 12:40 PM | Permalink

Comments (5)

Please login or join to subscribe to this item
avatar
Wai Mun Koo PMO Director| Intergraph PP&M Singapore, Singapore
I will do it (praise) openly and sincerely. Selecting the right occasion and place to do it is equally important to make it effective.

Praises are somthing delicate that we need to handle with care. Too much of it, in my opinion, will make it a habit for all people to expect it whenever they have done something regardless whether they deserve it or not. The worst part is, they might even have a negative feeling if they didn't get any praise eventually. Next, too much praises also make it less 'precious' and 'exclusive'. People will feel numb immune to it the next time you praise them. Use it with cautious and with purpose (just like antibiotics).

avatar
Patricia Davis-Muffett Chief Marketing Officer| IPS Learning Arlington, Va, United States
I think a mix of quiet and public praise is essential to good team dynamics. Rewarding and thanking folks privately is critical, but occasional public recognition (especially if you can call out more than one person or put it in the hands of a very senior executive to actually say the words) makes a big impression!

avatar
Dr. Paul D. Giammalvo Sr. Technical Advisor| PTMC/APMX Jakarta Selatan, Indonesia
Ty, unlike you, I am NOT an "accidental" project manager. "Construction Project Manager" was what I wanted to be when I grew up back in the 1960's and it is still what I want to be when I grow up, some 50 years later.

My reason for writing is how do you consider project management to be "strategic"? If we look at the definition of "strategy" in the context of business, we find "Long-term action plan for achieving a goal." (http://www.investorwords.com/4775/strategy.html) So if projects have a defined start and a defined finish, and are generally short term in nature, doesn't that definition apply more appropriately to PROGRAM management than it does to PROJECT management?

Taking a broader or more traditional look at the definitions of "strategy" http://en.wikiversity.org/wiki/What_Is_Strategy%3F_Why_Study_Strategy%3F we can readily see from Von Clausewitz four levels, that project management/project managers are not high enough up in the decision making process to be "strategic" decision makers. Using Von Clausewitz' model, at best we are Tactical, and although we clearly may be working on strategic projects within the organization, I can see no way to justify any claims that project managers are making strategic rather than tactical decisions, even though the projects we manage may be considered to be strategic in nature.

BR,
Dr. PDG, Jakarta, Indonesia
http://www.build-project-management-competency.com

avatar
Sylvie Edwards Professor/Program coordinator| Durham College (DC) Whitby, Ontario, Canada
Ty, good article to make people review and look at their rewarding mechanisms and processes. I know that as a consultant in this environment it is really often very hard to do anything with rewarding other than praise. That should be done in the appropriate tone, commensurate with the work accomplished, at the right moment and in front of the proper audience.



As for Dr Paul above... you are missing the BOAT. In most organizations that I work for doing projects is a means of attaining objectives that are outlined in their strategy. Therefore, doing projects is providing the foundation to strategy and part of it. Not every company works with programs, portfolios defined in the matter that you take it to the letter... A definition is that... but trust me it has evolved considerably and means more than a corporate long-term action plan.

avatar
Dr. Paul D. Giammalvo Sr. Technical Advisor| PTMC/APMX Jakarta Selatan, Indonesia
Sylvie,
Thanks for enlightening me!!

But before you accuse me of missing the boat, did you bother to read von Clausewitz 4 Levels of Strategy? Sure, a project can be initiated to achieve a strategic objective, but that alone does not make the project management strategic.

The problem as I see it is one of lexicon....... "Strategy" sounds exciting and important, but how many project managers have sufficient decision making authority to make STRATEGIC decisions?

Not sure which sector you work in, but I get to see a pretty good cross section as a consultant, and there are precious few project managers who even have sufficient authority to make TACTICAL decisions, much less make strategic ones. And even though they may be working on a project which was initiated to achieve a strategic objective, does not necessarily make project management as a delivery method strategic.

BR,
Dr. PDG, Jakarta, Indonesia
http://www.build-project-management-competency.com



Please Login/Register to leave a comment.

ADVERTISEMENTS

"The industrial revolution was neither industrial nor a revolution - discuss"

- Linda Richman

ADVERTISEMENT

Sponsors