Objective setting
A team member's job description is designed to give an overview of the work they will be doing. It is unlikely however to include specific objectives. In a development programme, it should be possible to establish a formal system for discussing and agreeing objectives for months or possibly a year at a time. In emergencies, this is far more difficult as the situation will be changing rapidly and thus so will your organisation's response. You will also be under time pressure.
Risks
- Without clear and agreed objectives, team members may not understand what is expected of them, possibly work towards inappropriate objectives, and will justifiably resent subsequent appraisals which criticise them for not having correctly guessed what they were meant to be doing.
Way forward
- Regular (weekly?) team meetings which concentrate on action points with deadlines and those responsible, and review action points from previous meetings.
- Notes taken, shared and filed.
- Set more formal objectives as soon as possible - see Resources
This page was last updated by Phil Wilks on 28 April 2010 at 12:14:45 (2 years ago).
View page history (1 version).