uuid:
  - value: ac0f7677-9ca2-4b20-a00f-0264a3aab2c6
langcode:
  - value: en
type:
  - target_id: daily_email
    target_type: node_type
    target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
revision_timestamp:
  - value: '2025-05-11T09:00:50+00:00'
revision_uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
revision_log: {  }
status:
  - value: true
uid:
  - target_type: user
    target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
title:
  - value: |
      Outcomes or output
created:
  - value: '2022-12-05T00:00:00+00:00'
changed:
  - value: '2025-05-11T09:00:50+00:00'
promote:
  - value: false
sticky:
  - value: false
default_langcode:
  - value: true
revision_translation_affected:
  - value: true
path:
  - alias: /daily/2022/12/05/outcomes-or-output
    langcode: en
body:
  - value: |
      <p>I was reading a Twitter thread recently that <a href="https://twitter.com/allenholub/status/1594786089994067969">started with this tweet</a>.</p>

      <p>TL;DR:</p>

      <blockquote>
        <p>"Measuring output (e.g. velocity) is a waste of time. It's outcomes you care about - customer happiness."</p>
      </blockquote>

      <p>This is definitely something that I agree with.</p>

      <p>I can't remember the last time I looked at an output burndown chart or a velocity score.</p>

      <p>I'd rather focus on what outcomes have been delivered and adding value to clients and customers.</p>

      <p>What features did we release, what bugs did we fix, and what impact and value did that provide?</p>

      <p>What increased revenue or improved a customer's experience?</p>

      <p>I may have a sprint or cycle where I only deliver one or two large tasks, but those are major features that have been requested, a bug affecting a user's experience, or a task that unblocks future tasks.</p>

      <p>In that situation, my velocity may not be good and could be improved by working on multiple smaller tasks, but which outcomes provide the most value?</p>

              
    format: full_html
    processed: |
      <p>I was reading a Twitter thread recently that <a href="https://twitter.com/allenholub/status/1594786089994067969">started with this tweet</a>.</p>

      <p>TL;DR:</p>

      <blockquote>
        <p>"Measuring output (e.g. velocity) is a waste of time. It's outcomes you care about - customer happiness."</p>
      </blockquote>

      <p>This is definitely something that I agree with.</p>

      <p>I can't remember the last time I looked at an output burndown chart or a velocity score.</p>

      <p>I'd rather focus on what outcomes have been delivered and adding value to clients and customers.</p>

      <p>What features did we release, what bugs did we fix, and what impact and value did that provide?</p>

      <p>What increased revenue or improved a customer's experience?</p>

      <p>I may have a sprint or cycle where I only deliver one or two large tasks, but those are major features that have been requested, a bug affecting a user's experience, or a task that unblocks future tasks.</p>

      <p>In that situation, my velocity may not be good and could be improved by working on multiple smaller tasks, but which outcomes provide the most value?</p>

              
    summary: null
field_daily_email_cta: {  }