Unclear project objectives are not just a planning problem; they are an adoption risk. When people do not understand what the change is meant to achieve, why it matters, what will be different in their work, and how success will be measured, they fill the gaps with local assumptions. PMI’s project-management guidance describes the change objective as shaping the “what, why, how, when, and who” of the change, while Prosci emphasizes that defining success early should include both project objectives and organizational benefits [PMI, 1983; Prosci, 2025]. (pmi.org)

For change managers, establishing objectives clearly is a governance, planning, and operating-model intervention. It creates the shared agreement that sponsors, managers, adoption leads, and impacted employees use to make decisions, prioritize support, resolve resistance, and track whether adoption is actually happening.

This action is the facilitated process of turning a broad change intent into documented, agreed, adoption-centered objectives. A good objective statement links the case for change, desired outcomes, scope boundaries, affected groups, decision rights, measures, and review cadence. HM Treasury’s Green Book recommends grounding proposals in a case for change, theory of change, business-as-usual baseline, SMART objectives, and strategic fit [HM Treasury, 2026]. (gov.uk)

Use this action at initiation, before detailed change planning, and again when scope changes, resistance increases, adoption data is weak, or leaders disagree about priorities. It is especially valuable when the project is technically clear but behaviorally vague: for example, a system is ready, but no one has defined what “using it well” means.

Before the session, gather the business case, sponsor intent, project scope, benefits hypothesis, impacted-group analysis, process maps, known risks, adoption data if available, and any non-negotiables. Invite the sponsor, project lead, change lead, adoption lead, HR or L&D partner, representative people managers, and credible employee or process representatives. CIPD notes that people need clear expectations, skills, resources, support, and accountability to perform well, and that employee voice helps people influence matters affecting their work [CIPD, 2026a; CIPD, 2026b]. (cipd.org)

The key decisions are: what outcome matters most, which groups must adopt new behaviors, what is in and out of scope, who owns each objective, what measures prove progress, and what cadence will keep the objectives alive.

A company is rolling out a new CRM. The initial objective says, “Launch CRM by September.” The change manager facilitates a reset. The revised objective becomes: “By November 30, 90% of sales representatives in North America will record qualified opportunities, next steps, and forecast stage in the CRM within two business days, enabling weekly pipeline reviews based on system data.” Supporting objectives define manager coaching, data-quality thresholds, training completion, and exception handling. The project is no longer judged only by go-live; it is judged by whether sales teams use the CRM in the way required to improve forecasting.

The sponsor owns the definition of success and resolves trade-offs. The project lead confirms scope, timeline, dependencies, and delivery feasibility. The change manager facilitates alignment, translates outcomes into adoption requirements, and maintains the objective log. People managers interpret objectives for their teams, coach new behaviors, and surface barriers. Adoption leads or super users provide local feedback and help validate whether the objective is practical. Impacted employees test whether the objective is understandable and whether the required behavior is realistic in the flow of work.

Avoid writing objectives that describe deliverables only, such as “system launched” or “training completed.” Avoid too many objectives; Green Book guidance notes that a small set helps maintain focus [HM Treasury, 2026]. Avoid private objectives that sit in a deck but are not discussed; MIT Sloan warns that private or infrequently reviewed goals can undermine alignment [MIT Sloan, 2018]. Avoid adoption measures that punish teams for barriers outside their control. Finally, avoid treating resistance as noncompliance before checking whether the objective is clear, feasible, resourced, and locally relevant.

Measure whether the action is working at three levels. At the governance level, check whether objectives are documented, owned, reviewed, and used in decisions. At the individual or group level, track speed of adoption, ultimate utilization, and proficiency, which Prosci identifies as core adoption outcomes [Prosci, 2025]. (prosci.com) At the business level, assess whether the adoption objective is producing the intended benefit, such as fewer errors, faster cycle time, better customer experience, or improved compliance.

Leading indicators include manager confidence, employee understanding, training-to-use conversion, support-ticket themes, and repeated questions. Lagging indicators include sustained usage, performance outcomes, benefit realization, and reduced workarounds.