outputs-vs-outcomes

Outputs vs. outcomes: what's the different and why does it matter?

https://github.com/joelparkerhenderson/outputs-vs-outcomes

Science Score: 44.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
    Found CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
  • Committers with academic emails
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (6.0%) to scientific vocabulary
Last synced: 7 months ago · JSON representation ·

Repository

Outputs vs. outcomes: what's the different and why does it matter?

Basic Info
  • Host: GitHub
  • Owner: joelparkerhenderson
  • Default Branch: main
  • Homepage:
  • Size: 7.81 KB
Statistics
  • Stars: 16
  • Watchers: 2
  • Forks: 1
  • Open Issues: 0
  • Releases: 0
Created over 6 years ago · Last pushed about 1 year ago
Metadata Files
Readme Code of conduct Citation

README.md

Outputs vs. outcomes

What’s the difference between outputs and outcomes? Outputs are "The What". Outcomes are "The Why".

What’s the difference between outputs and outcomes?

Outputs are "The What".

  • Outputs are the stuff we produce, be it physical or virtual, for our customers.

  • Examples: products, services, profits, revenues, reports, workshops, transactions, tickets, plans, etc.

  • An output is what is created at the end of a process.

  • Focus is activity-driven.

  • Typically immediate; when you complete a process, you get an output.

Outcomes are "The Why".

  • Outcomes are the benefits that our customers receive from our stuff.

  • Examples: a happier person, a stronger relationship, a change in behavior, a greater understanding, a satisfied customer, etc.

  • An outcome is the achievement that occurred because of the the work.

  • Focus is impact-driven.

  • Typically not immediate; when you complete a process, you measure the outcome over time.

Why does it matter?

The differences between outputs and outcomes matter because success is all about outcomes, not outputs. Good projects plan for the outputs to lead to outcomes.

When you understand the words, then you can communicate more clearly with stakeholders, such as your customers, investors, partners, donors, and the like.

When you aim your organizational goals toward outcomes, rather than outputs, then you're aiming toward impact, rather than activity.

Measurement of outputs and outcomes

Outputs:

  • Measurement tends to be in terms of: counts, commodities, completions.

  • Measurement example: number of products we built last month.

Outcomes:

  • Measurement tends to be in terms of: efficacy, efficiency, effectiveness.

  • Measurement example: customer satisfaction score as it changes over time.

Outcome management

Identify a target, which is a goal, or purpose, or mission, etc.

Identify the target's indicators, which are quantitative and show in real time whether you are on track or not.

Present the target and indicators, in terms that everyone understands.

Work toward the target, and use the indicators and any other evidence to course correct.

Present achievements that demonstrate the true value of what the organization is doing.

Present achievements in ways that important audiences can understand.

Outcome vs. impact

Impact is the degree to which the outcomes are attributable to the organization's work.

Example: the impact of the a soup kitchen is the degree to which a reduction of hunger in the population they serve is attributable to its efforts. Suppose a soup kitchen starts serving more meals; the meals are outputs. Suppose a soup kitchen observes that hunger is subsequently less prevalent in the population it serves; the reduction in hunger is an outcome. However, the reduction in hunger might be attributable to something other than the meals, such as an improving economy, or an unrelated school lunch program, or some other activities that are not part of the soup kitchen’s efforts.

Outcome objectives

Growth example:

  • Improve {topic} growth. Objective: grow {x%} during {timeframe}. Measure growth by {metric}.

Score example:

  • Boost {topic} score. Objective: increase from {x} to {y} by {date}. Measure score by {metric}.

Rate example:

  • Accelerate {topic} rate. Objective: achieve {throughput} by {deadline}. Measure rate by {metric}.

Related

See also

Owner

  • Name: Joel Parker Henderson
  • Login: joelparkerhenderson
  • Kind: user
  • Location: California

Software developer. Technology consultant. Creator of GitAlias.com, NumCommand.com, SixArm.com, and many open source projects.

Citation (CITATION.cff)

cff-version: 1.2.0
title: Outputs vs. outcomes
message: >-
  If you use this work and you want to cite it,
  then you can use the metadata from this file.
type: software
authors:
  - given-names: Joel Parker
    family-names: Henderson
    email: joel@joelparkerhenderson.com
    affiliation: joelparkerhenderson.com
    orcid: 'https://orcid.org/0009-0000-4681-282X'
identifiers:
  - type: url
    value: 'https://github.com/joelparkerhenderson/outputs-vs-outcomes/'
    description: Outputs vs. outcomes
repository-code: 'https://github.com/joelparkerhenderson/outputs-vs-outcomes/'
abstract: >-
  Outputs vs. outcomes
license: See license file

GitHub Events

Total
  • Push event: 1
  • Fork event: 1
Last Year
  • Push event: 1
  • Fork event: 1

Committers

Last synced: 10 months ago

All Time
  • Total Commits: 16
  • Total Committers: 1
  • Avg Commits per committer: 16.0
  • Development Distribution Score (DDS): 0.0
Past Year
  • Commits: 1
  • Committers: 1
  • Avg Commits per committer: 1.0
  • Development Distribution Score (DDS): 0.0
Top Committers
Name Email Commits
Joel Parker Henderson j****l@j****m 16
Committer Domains (Top 20 + Academic)

Issues and Pull Requests

Last synced: 10 months ago

All Time
  • Total issues: 0
  • Total pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Total issue authors: 0
  • Total pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 0
  • Pull requests: 0
  • Average time to close issues: N/A
  • Average time to close pull requests: N/A
  • Issue authors: 0
  • Pull request authors: 0
  • Average comments per issue: 0
  • Average comments per pull request: 0
  • Merged pull requests: 0
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
Pull Request Authors
Top Labels
Issue Labels
Pull Request Labels