Please login or join to subscribe to this thread
I see Goal comes before KPI. All project has a Goal. The Goal should be fix, unless it is officially modified in Change Management.
The KPI is set so you know you are progressing towards the goal, and in the end whether achieve the goal. So the KPI should be set by key stakeholders in the project planning stage. I said stakeholders because you may need to regularly report the KPI to your client, so it does not limit to team members. Team members may come in or leave the project during the course, so you cannot wait for all team members to set the KPI. You may further enhance the KPI, but it is better through the Change Management process so everyone understands the reason of the change and then formally follow it.
Are you attempting to have a set of KPIs for each team member or by trade? What are the focus areas that you are trying to improve upon?
Not every performance indicator will run the course of a project, some will be relevant to the start of the project, and some will only be able to be used in the latter stages. They can also evolve.
However, before you implement them, there are a few things you need to understand to ensure each KPI is effective:
- What your objectives are
- How do you know when you have hit your benchmark
- Who your audience is
- What metrics you will use
- What data do you need to produce those metrics
- Where is the data sourced from
- What frequency will you need the data
- Who is responsible for collating and presenting this data
If your KPIs are aligned with your business strategy, there are credible, relevant, unambiguous, and your project is able to act upon the information being provided, then they can be introduced at any time in the project’s life cycle.
One thing to be careful: KPIs are useful to show trends over time. If you add them too late or change them too much/often, you may wind up with insufficient information to see progress.
Firstly you should identified your target by using KPIs as a monitoring/actionable methodology for your project.
Secondly, Many KPIs you can be managed it; Like (Quantitative, Qualitative, Leading, Lagging, Input, Process, Output, Practical, Directional, Actionable and Financial Indicators).
You should select which ones are applicable for your case and now that too many KPIs will lead to confusion and could start sending false positives to the project stakeholders, sponsor and team members; additionally, overloading the usage of KPIs will eventually lead to the situation of ‘noise’, whereby so many factors are monitored that it becomes a blur.
Thanks for your replied. And now I have better understanding on the KPI and goals. My target to set the KPI for the project and for the team member under me. Let say we have a few goal that project that has been set, now I plan to segregate each of my team member towards the goal.
In order to align all project team member toward our project's goal, I plan to set each of individual team member with their KPI. Not only that, my intention at the end of the project, i could assess their performance towards the GOAL by achieving individual KPI set early of the project. It is okay if my planning like that?
Also, need opinions from the rest. If the goal is the same, how we want to determine the task or divide the workload among our team member, let says all the same discipline Mechanical Engineering. Most of the team member will be do the same things;
Shall I create WBS, to further divided the works and than arrange between my team members?
I definitely agreed with your, the KPIs set should credible and only a few one that applicable. If too many also, may not good for the team, and might distract the focus to achieve the major KPIs.
I think that the answer is in your question.
we initially setting the KPI at early stage of Project, and the KPIs we further enhance through out the project?
I think that we have to initially set-up the KPI, but we also have to further enhance them with the passage of time. But the most important part of using KPI is that we have to set up every-time the KPI according to the project requirements. But sometime we consider project of same types and try to implement the KPI from other project because that project was the same nature. So I think that it is very critical that every project should be deal separately and KPI should be set up according to the project requirements.
Thanks for your feedback. Noted to apply similar kind of project KPI to other projects should try to avoid. Sometimes even the project look alike same in nature, my details requirements will be much more different.
Please login or join to reply