Outcome-and-Impact Goal Test
Reject activity statements unless they define completion, change, and success.
- Difficulty
- Easy
- Time to result
- ~days to results
- Steps
- 5
- Confidence
- 97%
The Outcome-and-Impact Goal Test subjects every proposed goal to two independent questions. First, can the team articulate what completion looks like and determine whether the goal was actually achieved? Second, can they explain what meaningful change the completed work should produce and how they will judge that impact? Statements framed only as plans or activities fail the test because performing work does not establish an outcome. The method therefore separates execution from success: a team may finish an activity yet fail to create the intended effect. Rewriting goals around a concrete end state and an explicit impact criterion improves accountability, prioritization, and post-project learning while exposing work that has no defensible reason to exist.
Origin
One host described repeatedly applying these questions when reviewing company and team goals, especially goals phrased as plans or activities. Extracted from Marketing Against The Grain.
Core principles
- 01Activities are not goals.
- 02A real goal has an observable completion state.
- 03The goal must specify what changes when it is achieved.
- 04Success requires an impact criterion, not just finished work.
How to run it
- 1
Collect the Goal Statement
Write the proposed goal exactly as the team currently expresses it. Highlight language describing plans, effort, or ongoing activity.
Pro tip Watch for phrases such as “we plan to,” “support,” or “work on.”
Watch out Do not improve the wording before diagnosing what is missing.
- 2
Test Completion
Ask what it will look like if the goal has been achieved and how the team will know. Require an end state that can be judged clearly.
Pro tip Describe the artifact, capability, behavior, or result that will exist.
Watch out A list of tasks does not automatically define a completed outcome.
- 3
Test Change
Ask what becomes different because the goal was completed. Connect the work to a user, business, or team consequence.
Pro tip Name who experiences the change and what they can do afterward.
Watch out If nothing meaningful changes, reconsider why the activity is prioritized.
- 4
Test Impact
Specify the evidence that will indicate whether the change was successful. Distinguish successful delivery from successful effect.
Pro tip Use a metric or observable behavior appropriate to the decision.
Watch out Avoid vanity metrics that do not represent the intended benefit.
- 5
Rewrite or Reject
Rewrite the goal to include the concrete outcome and impact criterion. Reject or reclassify it as an exploratory task if those elements cannot yet be defined.
Pro tip Keep supporting activities in the plan, not in the goal statement.
Watch out Do not preserve a meaningless goal merely because work has already started.
In the wild
A company presents a team goal beginning with “we plan to” followed by a list of work. The reviewer asks what completed execution will look like, what will change afterward, and how the team will know whether the change was successful. When the team cannot answer, the statement is treated as activity rather than a real goal.
→ The planning conversation shifts from intended effort to a testable result and impact.
A product team replaces “improve onboarding” with a goal to let new users complete setup without staff assistance and to increase successful first-session activation from its current baseline to a defined target.
→ The goal now identifies both a concrete changed capability and evidence of successful impact.
Common mistakes
Calling Activities Goals
Planned tasks describe what the team intends to do, not what will be different when the work succeeds.
Stopping at Completion
A shipped artifact or completed project can still fail to create the intended user or business impact.
Using Ambiguous Success Language
Words such as better or improved do not establish how success will be judged without an observable criterion.
Is it for you?
Best for
It is best for managers and teams reviewing objectives, project plans, roadmaps, or performance commitments.
Not ideal for
It is not ideal for early exploratory work whose purpose is explicitly to reduce uncertainty before an outcome can be selected.
From the transcript
“Activities are not goals? Activities are not goals everyone.”
“So, how do you know if you did that or not? Like, articulate to me, like, what does it look like if you did that?…”
“And then tell me how you know if it was successful and impactful.”
From the episode
Steven Bartlett’s Exact Framework To Get +35 Million Downloads A Month (#155)