Project objectives are the discrete, measurable outcomes that a project is formally committed to delivering within a defined timeframe. In change management, understanding and accurately documenting specific project objectives is foundational to designing interventions that address the real drivers of the change and communicate its value to impacted stakeholders.
Definition and Distinction
Project objectives are distinct from project goals (broader strategic aspirations), project benefits (the value realised after project completion), and project deliverables (tangible outputs produced during execution). An objective is characterised by specificity and measurability: it articulates what the project will achieve, by when, and to what standard. The SMART framework—Specific, Measurable, Achievable, Relevant, and Time-bound (Doran, 1981)—is widely applied in defining project objectives.
In the change management context, project objectives provide the 'why' from the project's perspective. They inform the change manager's analysis of what is changing, for whom, and to what end—essential inputs to the change impact assessment, stakeholder engagement strategy, and training needs analysis.
Why Project Objectives Matter for Change Management
Clearly articulated project objectives enable change managers to:
link the change narrative to measurable outcomes;
identify which stakeholder groups are most affected by each objective;
design adoption metrics that align with the project's stated success criteria.
When project objectives are vague or absent, change plans risk being disconnected from project intent, reducing their effectiveness and making it difficult to demonstrate value (Hiatt & Creasey, 2012).
The tool guidance recommends using objectives already listed in the project charter, and adding only those that are generally accepted. This discipline ensures that change management planning is anchored to formally endorsed project commitments, rather than informal aspirations or personal interpretations.
Assessing and Documenting Project Objectives
Practitioners should extract objectives directly from the approved project charter or business case. Each objective should be reviewed for SMART compliance before entry. Where objectives in the charter are stated as goals rather than objectives (e.g., 'improve customer satisfaction' rather than 'achieve a 15% improvement in Net Promoter Score by Q4'), the change manager should clarify with the project manager or sponsor before adding specificity.
Example of a well-written set of project objectives: 'Reduce average accounts payable processing time from 12 days to 5 days by 30 June; achieve 90% user adoption of the new procurement system by end of Q3; reduce manual data entry errors by 40% within six months of go-live.' These objectives are specific, measurable, and tied to observable business outcomes.
Common Pitfalls and How to Avoid Them
Conflating objectives with benefits: Stating 'improve employee experience' as a project objective confuses a long-term benefit with a near-term deliverable. Objectives should be achievable within the project timeline, not post-project.
Listing too many objectives: Projects with more than five to seven stated objectives often signal unclear scope or inadequate prioritisation. A long list may indicate that the change manager has included all aspirations rather than confirmed commitments. Review with the project manager to confirm which are formally endorsed.
Using objectives that cannot be measured: Objectives such as 'enhance collaboration' or 'improve processes' are not objectives—they are aspirations. Insist on measurable criteria before documenting.
Not updating objectives as the project evolves: Project objectives can change during execution. Change managers should review and update the objectives field when the project undergoes significant scope changes or re-baselining.
References
Doran, G. T. (1981). There's a S.M.A.R.T. Way to Write Management's Goals and Objectives. Management Review, 70(11), 35–36.
Hiatt, J., & Creasey, T. (2012). Change Management: The People Side of Change. Prosci. https://www.prosci.com
Office of Government Commerce. (2009). Managing Successful Projects with PRINCE2. TSO. https://www.axelos.com/best-practice-solutions/prince2