2.9.4: Defining Success Before the Work Begins
- Page ID
- 49257
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
Defining Success Before the Work Begins
A C-Bay Planning Guide for Milestone 1
Introduction: Why You Must Define Success Before You Start the Work
Every project wants “success”—but without agreement on what that means, it’s just a buzzword. Your first responsibility as a planner is to create a shared, measurable, client-aligned definition of success before planning proceeds.
In professional planning, success criteria must be:
- Specific
- Measurable
- Agreed upon
- Relevant to the client
- Verifiable at the end of the phase
For UCMS, your job in Milestone 1 is to define success for the planning phase only, not for the final system implementation.
What Are Success Criteria?
Success criteria are observable, measurable conditions that confirm a project phase is complete and accepted. They:
- Set expectations
- Provide accountability
- Prevent scope creep
- Allow verification of progress
They answer:
“What must be true at the end of this work for everyone to say, ‘We did what we came here to do’?”
What Success Criteria Are Not
- Vague statements (“meet client goals”)
- General hopes (“deliver a great system”)
- Tasks (“complete the project”)
- Unmeasurable claims (“achieve satisfaction”)
If criteria cannot be verified or signed off by a stakeholder, they don’t belong in the charter.
C-Bay’s Guidelines for Strong Success Criteria
- Be Specific – Name the deliverable or outcome clearly
- Be Measurable – Progress must be objectively verifiable
- Be Time-Bounded – Tie to a milestone or deadline
- Be Client-Aligned – Written from the client’s perspective
- Be Phase-Appropriate – Focus on this phase only
Strong vs. Weak Examples
| Weak | Strong |
|---|---|
| “UCMS is satisfied with the planning process.” | “All UCMS stakeholders have reviewed and signed the final planning package by April 30.” |
| “Planning is completed.” | “Project Charter, Stakeholder Map, and Requirements Matrix are completed, validated, and submitted to UCMS leadership.” |
| “The team agrees on project goals.” | “All success criteria are reviewed and approved by C-Bay PMO and UCMS Sponsor before the milestone concludes.” |
Sample UCMS Success Criteria for Milestone 1
- Project Charter submitted, reviewed, and approved by the UCMS Dean and CIO
- Stakeholder map validated by both C-Bay and UCMS leadership
- Scope boundaries, constraints, and risks documented and signed off
- Preliminary planning schedule submitted with target dates for key deliverables
- All planning materials uploaded to the shared repository by milestone close
Tip: Include 3–5 criteria. More than five clutters focus; fewer than three weakens accountability.
How to Write Them
- Review the client’s expectations
- Think like the sponsor
- List your major outputs for this phase
- Make each outcome testable
- Use professional, neutral language
Common Mistakes
- Using vague or hedged language (“should be,” “ideally”)
- Including future-phase goals
- Writing from your perspective instead of the client’s


