Monday, March 21, 2011

Things we easily forget

Peeps, this is a bit of a random post, but one that discusses the items that are easy to ignore. PMing is not a job, its an ownership. Been making post-its for myself of things to engrain in my approach. The mess on my desk has become unbearable, so I am transferring it to this electronic medium!
Friendly & Firm can go together - No one likes a tight arse, dont be one. Break the formality while dealing with business users & put them at ease. Being formal (officious is worse) makes you come across as COLD in your relationships. Relationships salvage projects from tough situations, and without close bonds, you will be handicapped.
Protect the primary objective of the project - Most projects that are undertaken in an end user organization will usually get more than 1 streams of work. In such a situation, identify tehprimary objective and ensure that all decisions regarding scope, budget & delivery protect the primary goal of the project. IMPORTANT!
Retain the ability to Say "No" - Not all the items on the project wishlist can be taken. This trait separates the average PM's fromt he good ones. Say No firmly, but with firmer reasons to backup your argument.
"Plan" content and acceptance, not tool and beauty - This is a bug that infests a lot of PM. There is a lot of focus in getting the plan "finished" and making it "beautiful" rather than focussing on the content and buy-in. Follow 70/30 Spend 70% of the time getting buy-in & content and 30% to make it presentable.
Back your decisions and be seen as a prick vs Succumbing to what stakeholders say - Interesting one this is. But here is what i say. If you believe in something for the right reason, back it up to the hilt. People may not like it, but will recognize teh value later. Everyone likes a well deliverd project. Liking the PM is just an added advantage. Plus if "everyone" likes you, start getting concerned :)
Inheriting a team does not mean you need to retain it - Applicable when you walk in to an existing team. Take time, understand their capabilities , but do NOT be afraid to rejig them around if you believe that it will help the project.

No comments: