V4U Uday Mahajan's exp.

Uday's Selected Snaps

Monday, February 28, 2011

Keeping Track of Customer Complaints

Know The Current reaction of an Indian, Click on http://viewsofuday.blogspot.com/

Keeping Track of Customer Complaints

Managing customer expectations is a very challenging job that requires constant attention. However, just as important is keeping track of all the customer complaints that are raised and what was done to address them. Over time this is a great way of understanding what went right / wrong with the project.
While there are a number of companies out there that have a defined process in place to capture and address customer complaints there are instances where information falls through the cracks. So it becomes the onus of the project manager to ensure that a record is kept of all such interactions ( both good and bad ).
To Automate or Not?
Another question you need to ask yourself is whether it would make sense to automate a process that captures and keeps track of customer complaints.  The idea is to track, step by step, the escalation route a customer complaint takes when entered into the system.
I do understand this is a question that should be directed to the team handling process automation within the organization instead of project managers, however being the end users of such a system it would be interesting to understand what you think of it.
Now lets presume you agree, and that you have a system up and running, how do you think this information should be handled?
Being confidential in nature you might want to consider closing off access to only allow certain people within your team from interacting with this system.  Senior Managers and group heads can then pull out reports that could give them an idea of how well / or badly a customer’s perception of the project is and can be invaluable in providing early warnings of when a projects starts to fail.
What are the Benefits of putting such a system / tool in place?
  • Greater control over the format of complaints coming in
  • Ability to track how complaints are being handled and the escalation routes being taken
  • Provide early warning signals to senior managers
  • Ability to understand what went wrong / right with the project.
  • Transparent communication / Improving client relations

 

Tuesday, February 15, 2011

5 Tips on Project Reporting

Know The Current reaction of an Indian, Click on http://viewsofuday.blogspot.com/

5 Tips on Project Reporting
  1. Project status: Create a weekly Project Status Report to show your actual vs. planned effort, percent complete and actual vs. forecast spend. Specify the number of open risks, changes and issues, and state whether action by your Sponsor is required to resolve them. Also show the forecast amount of time, effort and money required to finish the project. Always try and forecast as accurately as possible. Never forecast optimistically, always conservatively.
  2. Task completion: You need to regularly show your Sponsor your progress against the tasks listed on your schedule. Create a summarized view of your project plan and update it to reflect the percent complete for every task. Then append this summary view to your Project Status Report. This way, your Sponsor can drill down to see further information about each task, if they want to.
    By offering your Project Sponsor both summary and detailed information weekly makes them feel like your project is an "open book". They will have all of the information about your project at their finger-tips. This way, you will get more buy-in from your Sponsor and more support when it's needed.
  3. Milestones: You need to add Milestones to your project plan to show when the major project deliverables will be produced. You then need to report on the progress of each milestone to your Sponsor. Show the percent complete of each milestone, and again, forecast the completion dates.
    Here's another tip: You will get more out of your team if you motivate them to complete milestones, as opposed to tasks. That's because people are usually proud of the things that they have achieved in life (i.e. milestones), as opposed to the things they have done to achieve them (i.e. the tasks).
  4. Getting help: Project Sponsors don't always want to hear "we're on track and under budget" in their project reports. They just want to hear the truth. So if you’re behind schedule and you need help to get back on track, then tell your Sponsor about it in your project reports.
    State exactly what you need from them. Show them that you're doing the best you can and that you’re the best person for the job, but that you still need their help to deliver the project. If you need more time, money or resources, then ask for it. Don’t be afraid. And remember, the best time to ask for help is before you really need it. This gives you contingency, because it always takes time for help to arrive.
  5. One version of the truth: Your project reports need to depict "one version of the truth" to your team. Keep them 100% accurate and be as open as possible about real issues that are affecting your team. Remember that if you communicate an issue to your Sponsor, then it becomes their issue to fix as well. Reporting issues is a great way to share the responsibility for fixing them.
 - Uday Mahajan