Activity, output, outcome and impact: How to tell the difference
Most achievement statements stop too early. “Attended meetings” and “prepared reports” tell us what happened, but not why it mattered. Other statements leap straight to major impact without showing what changed or whether anyone can verify the result.
Activity, output, outcome and impact describe different levels of evidence. Knowing which level you have helps you make a stronger claim without making a bigger one than the facts support.
Quick answer: An activity is the work you performed. An output is the immediate deliverable or service produced. An outcome is the observable change that followed. Impact is the broader or longer-term difference to customers, the organisation or another important group. A credible achievement should go as far along this chain as the evidence allows, but no further.
Quick guide
- Activity: What did you do?
- Output: What did your work produce?
- Outcome: What changed after the work?
- Impact: What broader or longer-term difference followed?
- Use the highest level you can support with evidence.
- Do not turn an expected benefit into a completed result.
- Use “contributed to” when the result depended on other people or external factors.
What counts as a work achievement explains why useful contributions include coordination, risk prevention and decision support, not only revenue or major launches.
What are activity, output, outcome and impact?
| Level | Plain-English meaning | Main question | Simple example |
|---|---|---|---|
| Activity | The work performed | What did you do? | Facilitated a planning workshop |
| Output | The immediate deliverable or service | What did the work produce? | Produced an agreed delivery plan |
| Outcome | A change in behaviour, condition, decision or performance | What changed? | Teams began using one set of priorities and dependencies |
| Impact | A broader or longer-term effect | What larger difference followed? | The program avoided recurring planning conflicts and improved delivery reliability |
Organisations do not always use these terms in exactly the same way. NSW Health describes program logic as a link between activities, outputs and expected changes over time. The OECD also separates outputs, outcomes and impacts into different levels of results.
For your career record, the label matters less than the distinction. Work performed, something delivered and a result achieved are not interchangeable.
A complete workplace example
This illustrative example starts with a project where several workstreams are using conflicting assumptions during testing.
| Level | Evidence from the example |
|---|---|
| Activity | Reviewed the open issues, met with workstream leads and facilitated a decision session |
| Output | Produced an agreed assumptions register, assigned owners and updated the test plan |
| Outcome | Workstreams resumed testing using one agreed set of assumptions |
| Impact | The issue did not reappear as a blocker during the remaining test cycle |
You could write it this way:
Coordinated resolution of conflicting testing assumptions across three workstreams, producing an agreed assumptions register and enabling testing to resume. The issue did not reappear as a blocker during the remaining test cycle.
“Saved the project” and “protected the full go-live date” would go further than this evidence allows.
Why the distinction matters in career writing
A task list usually contains activities:
- ran workshops
- prepared status reports
- supported testing
- responded to escalations
- trained users
- analysed requirements
The tasks may have mattered. The reader still cannot see why.
An achievement statement adds at least one more level:
| Activity-only wording | Stronger evidence-based wording | Level reached |
|---|---|---|
| Ran weekly meetings | Facilitated a weekly decision forum and maintained an agreed decision log | Output |
| Prepared status reports | Consolidated delivery risks into one status view used by sponsors to prioritise recovery actions | Outcome |
| Supported testing | Coordinated defect triage across business and technical teams, enabling blocked scenarios to return to testing | Outcome |
| Responded to escalations | Clarified ownership and recovery actions for a client escalation, restoring an agreed path forward | Outcome |
| Trained users | Delivered role-based training and reference guides for the new process | Output |
| Analysed requirements | Identified conflicting requirements and facilitated agreement on one approved process | Outcome |
You do not need to force every statement towards impact. Sometimes an output or outcome is the most honest place to stop.
Three workplace evidence chains
The examples below are illustrative. Replace them with facts and evidence from your own work.
1. Business analysis
- Activity: Interviewed users and mapped the current process.
- Output: Created a process map and documented decision points.
- Outcome: Stakeholders agreed which duplicated approvals could be removed.
- Possible impact: The revised process reduced handling time after implementation.
- Evidence needed: Approved design and before-and-after timing data.
2. Risk prevention
- Activity: Reviewed migration data and investigated anomalies.
- Output: Documented the issue and recommended a validation step.
- Outcome: The affected records were corrected before the next migration stage.
- Possible impact: Incorrect data was prevented from reaching production.
- Evidence needed: Defect records, validation results and migration approval.
3. Recommendation with an unknown final result
- Activity: Researched delivery options and consulted affected teams.
- Output: Prepared a recommendation with risks and implementation considerations.
- Outcome: The steering group accepted it for inclusion in the delivery plan.
- Impact: Unknown. Post-implementation results were not available.
- Evidence needed: Decision record and approved plan.
The third example still counts. The recommendation was accepted, and that is the last known result. Adding a later impact would make the story sound bigger, but less trustworthy.
How far should your achievement statement go?
Use this decision table.
| What you can verify | What you can safely claim | Example |
|---|---|---|
| Only the work performed | Activity | Facilitated five stakeholder workshops |
| A completed deliverable | Output | Produced an approved requirements pack |
| A clear change after the work | Outcome | Enabled stakeholders to agree the future process |
| A broader result with supporting evidence | Impact | Contributed to a verified reduction in processing time |
| A result expected but not yet observed | Intended outcome, clearly labelled | Designed the workflow to reduce duplicate handling |
| A shared result | Contribution, not sole causation | Coordinated the workstream that contributed to the successful release |
| No access to the final result | Stop at output or outcome | Recommendation accepted for implementation; later results unavailable |
Reaching the impact column is not the goal. Accuracy is.
Impact requires extra care
Impact sounds strategic, which makes it tempting. It is also where overstatement usually begins.
Other teams, leadership decisions, customer behaviour, resources and outside conditions can all affect a longer-term result. Australian program logic guidance warns that these outcomes take time and are harder to measure. The same caution belongs in your career claims.
Compare these statements:
Overstated:
My training program increased customer retention.
More credible when causation is unclear:
Designed and delivered role-based training adopted by the customer support team. Customer retention improved during the following period, although the result was influenced by several service initiatives.
Appropriate when only the immediate result is known:
Designed and delivered role-based training, with all targeted team leaders completing the program and receiving the supporting guide.
Do not claim causation when you can only show timing, association or contribution.
What evidence supports each level?
| Level | Useful supporting evidence |
|---|---|
| Activity | Calendar entries, task records, workshop agendas, meeting notes |
| Output | Approved documents, plans, decision logs, training materials, completed configurations |
| Outcome | Status changes, adoption records, resolved issues, stakeholder feedback, process observations |
| Impact | Benefit reports, verified performance measures, trend data, customer results, independent evaluation |
Do not copy confidential material into a personal system. A safe note about where the evidence exists is enough. Follow your employer’s rules for confidential information.
Ascending Careers keeps the source note and its evidence boundary together. When you turn that note into a resume bullet or interview story later, you can still see where the facts end.
A practical method for rewriting a task
Pick one task from your job description or weekly update. Ask:
- What did I do?
- What did the work produce?
- What changed?
- Is there a broader result I can verify?
For example:
Task: Coordinated user acceptance testing.
Evidence-based achievement:
Coordinated user acceptance testing across business and technical teams, maintaining the test schedule, defect triage and readiness view. This enabled priority issues to be resolved and the agreed critical scenarios to be completed before the next approval gate.
This reaches an outcome. It does not pretend the coordination guaranteed a successful go-live.
Use the same questions when you record a work moment in Ascending Careers. Capture what you know now. Work out how far the statement can go when you need it for a review, resume or interview.
Common mistakes
Treating effort as a result
Working long hours or attending many meetings may show effort, but it does not explain what the effort produced.
Treating a deliverable as an outcome
Creating a dashboard is an output. A decision made because of the dashboard is an outcome.
Treating an intended benefit as a completed impact
A new process may have been designed to reduce errors. That does not prove errors decreased.
Skipping directly from activity to major impact
“Facilitated workshops that transformed the organisation” leaves too much of the chain unexplained.
Claiming sole credit for shared results
Show your contribution without erasing the work of the wider team.
Inventing a metric
Do not add a percentage because the statement feels incomplete. A verified qualitative outcome is stronger than fabricated precision.
How to track achievements without feeling like you are bragging provides a practical method for recording shared and qualitative contributions accurately.
Frequently asked questions
Is an output the same as an achievement?
Yes, when producing it required judgement, skill or meaningful effort. If you know what the output enabled or changed, add that too.
Do I need to reach the impact level every time?
No. Many credible achievements end at output or outcome. Stop where the evidence stops.
What if my work prevented something from happening?
Record the risk, your action, the control or decision produced and the evidence that the risk was addressed. Be careful not to claim a disaster would definitely have occurred.
What if several teams created the outcome?
Describe the shared outcome and your specific contribution. Use phrases such as “contributed to”, “coordinated”, “enabled” or “supported” when they accurately reflect your role.
Can an outcome be qualitative?
Yes. An outcome may be an agreed decision, improved clarity, resolved escalation, changed behaviour, stronger readiness or reduced uncertainty. Explain what changed and what evidence supports the observation.
Describe the change, not only the work
Activities show what you did. Outputs show what you produced. Outcomes show what changed. Impact shows the broader difference.
Move along the chain one step at a time. When the evidence stops, so does the claim. That gives you a career story you can defend in a review or interview.
Capture one recent task today, then ask: What did it produce, and what changed?
Start your private career evidence record
Editorial note
The workplace examples in this article are illustrative. Terminology for outputs, outcomes and impact varies across organisations. Use your organisation’s definitions where required, and do not copy example results or metrics as claims about your own work.
References
- NSW Health, Program logic, updated 2026. https://www.health.nsw.gov.au/research/Pages/program-logic.aspx
- NSW Health, Developing and Using Program Logic: A Guide, 2023. https://www.health.nsw.gov.au/research/Pages/developing-program-logic-guide.aspx
- Australian Institute of Family Studies, How to develop a program logic for planning and evaluation, updated 2016. https://aifs.gov.au/resources/practice-guides/how-develop-program-logic-planning-and-evaluation
- Australian National Audit Office, Annual Performance Reporting, accessed 2 August 2026. https://www.anao.gov.au/work/performance-audit/annual-performance-reporting
- Organisation for Economic Co-operation and Development, Glossary of Key Terms in Evaluation and Results-Based Management for Sustainable Development, second edition, 2023. https://www.oecd.org/en/publications/glossary-of-key-terms-in-evaluation-and-results-based-management-for-sustainable-development-second-edition_632da462-en-fr-es.html
- Productivity Commission, Approach to performance measurement, Report on Government Services 2026. https://www.pc.gov.au/ongoing/report-on-government-services/approach/performance-measurement/