Charter Section Deep-Dive

Project Charter Objectives: Writing Outcomes Sponsors Approve in One Round

Most charter objectives fail two tests. They describe outputs rather than outcomes ("build a new portal" instead of "reduce support tickets by 30%") and they have no baseline, no deadline, and no measurement method. The rewrites below show what one-pass-approval objectives look like.

Outputs vs Outcomes

The single largest cause of charter rework is writing outputs (what the project produces) where the sponsor expects outcomes (what gets better as a result). Sponsors do not care that the team built a thing; they care that something changed in the business as a result. Compare:

Output (what the team builds)Outcome (what improves)
Build and launch a new pricing pageLift trial-to-paid conversion from 4.2% to 6.5% by end of Q3 2026, measured by Stripe + Mixpanel
Replace the payroll systemReduce payroll processing time per pay cycle from 12 hours to 4 hours and bring error rate below 0.5% within 6 months of go-live
Open a new distribution centreReduce average delivery time to West Coast customers from 4.2 days to 2.5 days by Q2 2027, while holding total fulfilment cost per order constant
Deliver a customer training programmeAchieve 70% certification pass rate on new platform among existing customer admins within 90 days of launch (current trained: 12%)

The 3-Objective Rule

Three to five objectives. Below three the charter is over-simplified; above five the team will struggle to optimise for all of them and the sponsor will struggle to remember any. The discipline is to identify the three most important outcomes the project must deliver and to defer everything else to the "non-goals" section.

If a stakeholder pushes for a sixth objective, ask which of the first five they want to drop. Charter objectives are not a wishlist; they are the commitment the project will be judged against. PMI Pulse data consistently shows three-to-five objective charters outperform charters with more or fewer.

SMART Checklist

Apply SMART to every objective before submitting the charter. If an objective fails any of the five tests, rewrite it. The SMART criteria builder walks through this in depth.

S

Specific

Names the metric, the cohort, and the measurement system. Not 'improve customer satisfaction' but 'lift CSAT (post-interaction survey, 5-point scale) from 4.1 to 4.4 in the support tier 1 cohort'.

M

Measurable

Numeric. If the metric is qualitative (e.g. 'pass GDS Service Assessment'), name the gate, the assessor, and the pass criteria.

A

Achievable

Within the team's capability and budget envelope. If achievement requires a 10x team or 5x budget, the objective is aspirational not achievable. Aspirational objectives belong in the company strategy, not the charter.

R

Relevant

Traceable to the business case and the organisation's strategy. If the objective is achievable but uninteresting, the charter should not be approved.

T

Time-bound

Has a specific deadline. 'By end of Q3 2026' is acceptable; 'as soon as possible' is not.

Before-and-After Rewrites (4 Industries)

Software / SaaS

Bad

Improve customer onboarding experience.

Not measurable. No baseline. No deadline. Could mean anything. The sponsor will approve and then re-define the success criterion at month 6.

Good

Reduce time-to-first-value from sign-up to first successful API call from 14 days (median, Q1 2026) to under 7 days by end of Q3 2026, measured weekly in the activation cohort dashboard.

Why it works: Specific metric. Baseline named with source. Target named with deadline. Measurement method defined.

Manufacturing

Bad

Modernise Packaging Line 7.

Output (we will modernise a line) not outcome (what gets better). Could be interpreted as 'replace some PLCs' or 'install full new line'.

Good

Lift Overall Equipment Effectiveness (OEE) on Packaging Line 7 from 62.3% to 84.7% within 6 months of commissioning, with planned shutdown contained to 3 weeks (2-23 Jan 2027).

Why it works: Specific metric (OEE). Baseline + target + deadline. Implementation constraint (3-week shutdown) named upfront.

Healthcare

Bad

Implement new patient records system.

Output not outcome. The system existing is not the goal; the system working and being used is the goal.

Good

Achieve 95% clinician adoption (defined as 80% of weekly clinical note authoring done in the new system) within 6 months of go-live, with no medication-error rate increase during cutover (baseline: 0.082 per 1,000 dispenses).

Why it works: Outcome metric (adoption + safety). Two complementary measures (one positive, one guardrail) prevent gaming. Patient-safety baseline preserves the floor.

Marketing

Bad

Increase brand awareness.

Not measurable without a method. 'Awareness' is a research concept; the charter needs to name the method.

Good

Lift unaided brand awareness from 4% to 11% within the target ICP (mid-market North American IT decision-makers), measured by an independent brand-tracker survey pre-campaign and 6 weeks post-campaign, n=400 each wave.

Why it works: Specific cohort (ICP). Method named (independent tracker). Baseline + target + sample size all named. The methodology is sponsor-approvable.

Frequently Asked Questions

How many objectives should a charter have?
Three to five for most projects. Below three the charter is over-simplified; above five the team will struggle to optimise for all of them. PMI's Pulse of the Profession data consistently shows projects with three to five clearly articulated objectives outperform projects with fewer (vague) or more (diluted) objectives. If you have eight objectives, you have a programme, not a project.
What is the difference between an objective and a deliverable?
An objective is the outcome the project achieves; a deliverable is a tangible artefact produced. 'Reduce customer churn from 8% to 6%' is an objective. 'Build a re-engagement email programme' is a deliverable. Deliverables exist to support objectives. Charters that confuse the two often produce projects that deliver everything on the list but achieve nothing the sponsor wanted.
Should objectives be ranked by priority?
Yes, especially if there is a possibility of trade-off between them. If 'lift conversion 20%' and 'reduce page load to under 1 second' are both objectives and they conflict, the team needs to know which wins. PMI recommends naming the relative priority at charter time, often as 'P1 must achieve, P2 strongly preferred, P3 stretch'. Drucker's MBO work and Doerr's OKR framework both emphasise the priority discipline as a precondition for objective-setting clarity.
Can charter objectives change after sign-off?
Rarely, and only through formal change control. The whole point of the charter is to baseline the objectives. If material change is needed, the charter should be re-approved by the sponsor with the new objective documented. Mid-project objective changes that bypass the charter are a major contributor to scope-creep failure patterns and are tracked in the project's lessons-learned log.
Should objectives include guardrail metrics?
Yes for high-risk projects. A guardrail metric is a constraint the project cannot violate while achieving its primary objectives. Example: 'lift mobile conversion 30%' (primary) paired with 'do not increase mobile bounce rate above 42%' (guardrail). Without guardrails, teams sometimes optimise the primary metric in ways that damage adjacent metrics (e.g. boosting conversion by adding aggressive popups that destroy user experience). The DORA research on software delivery metrics and the OKR practice on Key Results both treat guardrails as a discipline distinct from primary metrics.
How do agile project charters handle objectives?
Agile charters use the Product Goal as a long-term outcome statement, with measurable success criteria that the team revisits at every Sprint Review. The Product Goal is the agile equivalent of a charter objective; the Sprint Goal is the equivalent of a milestone toward that objective. The metric structure (baseline, target, deadline, measurement method) is identical to a PMBOK charter; the cadence of measurement is shorter.
Where can I learn more about writing good objectives?
Three sources widely cited in PM practice. Peter Drucker's 'The Practice of Management' (1954) introduced Management by Objectives (MBO) and remains the philosophical reference. John Doerr's 'Measure What Matters' (2017) covers OKRs as practised at Google and elsewhere. The PMI 'Standard for Program Management' (4th edition) covers objective-setting at the programme level and is the closest formal-methodology reference for charter-level objectives.

Related on this site

Updated 2 May 2026