Should we report tasks completed or outcomes delivered?
Activity-outcome confusionUse task measures for execution coordination and outcome measures for value decisions. Neither should be presented as a substitute for the other.
What to do now
- Clarify the decision audience
- Separate activity from accepted output
- Connect outputs to intended outcomes
- Report both where the distinction matters
When to escalate
Escalate when
Activity volume is being used to claim unverified business success.
Who decides
The metric owner and relevant decision maker
Example
A report shows completed configuration tasks and separately whether users can complete the target workflow.
Mistake to avoid
Celebrating hundreds of closed tasks while the essential service is unusable.
Prevent a repeat
Check data freshness and meaning, and verify that the measure improves decisions rather than encouraging cosmetic progress.
Suggested ApprovedFlow setup
- Projects
- Tasks
- Timesheets
- Documents
Use the underlying named records and evidence when explaining a metric; validate any dashboard behavior against the current implementation. See the platform
Related cases
- How do we report forecast changes over time?Lost forecast history
- A report needs manual copying from several systems. What should we automate first?Fragile reporting pipeline
- How do we measure PMO effectiveness?PMO activity-versus-outcome confusion
- The product has many features but poor task completion. What should we prioritize?Feature output over user outcome