THE SHORT ANSWER

Business productivity is the useful output or value produced relative to inputs such as time, effort, money and capacity. A productive workflow protects quality and customer value while reducing avoidable cost, delay and attention—not merely increasing task volume.

Measure value, not motion

A balanced productivity view
DimensionQuestion
OutputWhat useful result was completed?
QualityWas it accurate and fit for purpose?
TimeHow much elapsed and working time did it require?
CostWhich people, tools and resources were consumed?
FocusDid the work displace something more valuable?
ImpactDid it improve a customer or business outcome?

Productivity ratios relate outputs to inputs, but a business must still define a worthwhile output. Sending twice as many low-value reports is not an improvement.

Evidence & context: OECD

Activity can hide weak work design

Full calendars, rapid replies and large task counts can coexist with waiting, rework and unclear decisions. A faster step can even move a bottleneck downstream.

Begin with one repeated outcome

  1. Name the customer or business outcome.
  2. Record volume, quality, cycle time and avoidable rework.
  3. Identify which work requires judgment.
  4. Choose one change and compare the same measures afterwards.

Next, define the workflow that produces the outcome.

Apply the idea to one real workflow

Choose one current workflow. Record the present outcome, the proposed change, the accountable owner, the most important exception or failure, and one before-and-after measure. Test the smallest safe version before expanding it.

Sources & further reading

  1. Measuring Productivity: OECD Manual

    OECD. Official measurement guidance relating outputs to production inputs. Business teams still need quality, customer and outcome measures rather than treating activity volume as value.

  2. Measuring the benefits of your service

    GOV.UK Service Manual. Guidance connecting time, cost and service measures to outcomes and benefits. It does not provide universal automation ROI assumptions.

Examples and exercises are illustrative unless attributed to a source. No independent expert review is claimed.

A correction, a counterexample or an experience worth sharing?

Join the conversation ↗