In organisational change management, project objectives describe the specific results a change initiative is expected to achieve for the business and for its stakeholders. They provide direction, enable alignment, and serve as the basis for measuring whether the change has delivered its intended benefits. In project management literature, objectives are commonly defined as specific, measurable, and time-bound statements of what a project will achieve by its completion. (atlassian.com) When applied to change management, these objectives must also reflect the “people side of change”, ensuring that adoption, behaviour change and usage are explicitly included. (prosci.com)
Where Project Objectives Are Typically Documented
In many organisations, project and change objectives are distributed across several artefacts:
Business case or investment proposal
These documents typically describe the problem or opportunity, expected benefits, and high-level success criteria, which together provide a first articulation of project objectives. (Project Management Institute)Project charter or mandate
Project management standards view the charter as the primary document defining the project’s purpose, objectives, and high-level requirements from the outset of planning. (Project Management Institute)Corporate strategy and portfolio documents
Strategic plans, portfolio roadmaps, and performance scorecards often contain higher-order strategic objectives from which individual project objectives could be derived. (Project Management Institute)Regulatory, policy, or compliance requirements
For regulatory or compliance-driven changes, objective statements may be found in external regulations, internal policies, or risk-management documentation. (Department of Finance)
Clarifying Objectives When They Are Not Documented
When objectives are incomplete, fragmented, or undocumented, they can often be clarified through structured conversations with key stakeholders:
Executive sponsor or project owner – accountable for the business outcomes and are usually best placed to articulate how success will be judged.
Strategy or transformation leaders – they can often translate strategic goals and performance targets into specific project objectives. (Project Management Institute)
Business process owners and product owners – these roles are usually able to specify operational outcomes, process performance, and user behaviour changes from their understanding of the project objectives. (Asana)
Project manager or PMO – able to ensure that clarified objectives are integrated into plans, scope, and governance mechanisms. (project-management.com)
Typical clarifying questions include: which business problems must be resolved; what will observable success look like; which metrics or indicators will be used; which groups must change behaviour; and by when. These discussions are often used to refine candidate objectives into SMART (see below), testable statements. (wrike.com)
Characteristics of Well-Articulated Project Objectives
Across project and change management guidance, high-quality project objectives share several characteristics:
Specific and outcome-focused
Objectives describe a clearly defined end state rather than activities. For example, “increase first-contact resolution to 85%” is more effective than “improve customer service”. Project management sources emphasise that objectives articulate what will be achieved, not how it will be done. (Project Management Institute)Measurable and time-bound (SMART)
Many frameworks advocate SMART objectives (Specific, Measurable, Achievable, Relevant and Time-bound) to support planning and performance evaluation. (wrike.com) In change initiatives, measures may include both business outcomes (e.g., revenue, error rates) and adoption indicators (e.g., percentage of users actively using a new system). (Whatfix)Relevant and strategically aligned
Well-articulated objectives are explicitly linked to organisational strategy and higher-level goals. Project and strategic management literature stresses that objectives should be quantifiable expressions of strategic intent, forming a clear chain from vision and strategy to projects and outputs. (Project Management Institute) Change management methodologies similarly emphasise alignment with strategic goals and business outcomes. (prosci.com)Unambiguous and testable
Guidance on goal setting stresses that meaningful objectives must be framed so that achievement can be objectively verified against a specific target. Testable and tangible objectives are better than ambiguous ones. Some projects will have easier testable metrics (such as logins per day for a system implementation) while others will be driven by behaviour outcomes (HR complaints per month in the case of a type of culture change) (projectmanagement.com)Inclusive of the people dimension
In change initiatives, objectives that address only technical deliverables are sometime incomplete. Change management sources highlight that success depends on individual adoption and sustained use; therefore, well-articulated objectives often include a specific behaviour change. (prosci.com)
Common Pitfalls in Articulating Project Objectives
Literature on project and change failure repeatedly highlights poorly defined objectives as a critical risk factor. (Accidental Project Manager) Common pitfalls include:
Vague or non-measurable wording
Objectives such as “improve communication” or “enhance efficiency” provide little guidance without defined metrics or targets. Several sources identify vague objectives and lack of clear measures as a leading cause of project drift and scope creep. (Accidental Project Manager)Confusing activities with objectives
Statements like “implement new CRM software” or “roll out training” describe deliverables, not outcomes. Guidance on project objectives emphasises the need to distinguish outputs from the results they are expected to produce. (atlassian.com)Ignoring the people side of change
Objectives that focus only on project management milestones (e.g., system go-live) and omit adoption or usage targets run the risk of not delivering the ROI of a project. As an example, launch the new CRM system is a poor objective.Conflicting or unprioritised objectives
Internally inconsistent, or unranked objectives make trade-offs impossible and contribute to late delivery or failure. Studies of common mistakes often highlight poorly structured objectives as a major source of risk. (Asana)Failure to review and update objectives
Some sources note that objectives are set once and then not revisited, even when assumptions or external conditions change. Regular review and adjustment are recommended to keep objectives relevant and achievable. (Productive)
References
Asana. “How to write an effective project objective, with examples.” (Asana)
Atlassian. “Project objectives: What they are & how to write them.” (atlassian.com)
Government Technical Advisory Centre (GTAC). Guide to Project Planning. (gtac.gov.za)
PMI. “Vision – strategy – objectives – projects – outputs, and return.” (Project Management Institute)
PMI. “Project Planning as the Primary Management Function.” (Project Management Institute)
Prosci. Various articles on organisational change management and project-level change management. (prosci.com)
Smartsheet. “SMART Goals in Project Management.” (smartsheet.com)
Asana and other project risk/best-practice articles on common pitfalls and lack of clear objectives. (Asana)