Chapter 02 / 20
2. Four Perspectives on Value
Provisional draft. These short chapters are not approved for publication. Original practitioner interviews, deeper reporting and author review remain outstanding.
Imagine four people assessing the same proposed rollout. A director points to more merged changes. A finance partner asks whether expenses fell or margins rose. A reviewer worries about a growing queue. A junior engineer wants to know whether the new workflow still teaches them to judge their own work. These are illustrative positions, not quotations or findings from one organization. They reveal four different units of value.
Begin with the customer. Can a person accomplish the intended job with less delay, confusion, or risk? The person buying a product, the person using it, and the person whose data it processes may have conflicting interests. Count successful tasks and harms in the relevant segments, not just aggregate activity. A feature used by many people may still fail those who need accessibility or a reliable recovery path.
The company needs sustainable return. It may gain contribution margin, reduce an actual expense, avoid a cost it would otherwise have incurred, reduce expected losses, or create capacity for worthwhile work. Do not call all five "savings." IBM's published ROI method distinguishes freed capacity from booked cost reduction and includes review and operating costs. Its reported return is a vendor-published model for its own product, not cash that another firm can budget before running a test.
The team needs a system it can keep operating. Throughput purchased by shifting verification to another team's nights and weekends is not an uncomplicated improvement. The Superhuman/AWS account reports more merged PRs among the same cohort of engineers while median PR cycle time stayed around 20 hours. That describes additional output and an unchanged median per-change delay; it does not tell us the return to customers or the whole company's profit. Look at end-to-end waits, rework, incident load, and who absorbs them.
The individual is not merely a unit of team capacity. Useful work, autonomy, pay and fair recognition, safety, and practice that builds judgment matter even when nobody can assign them a dollar value. Anthropic's employee research reports broader reach and faster exploration alongside worries about debugging practice and mentoring. Those are perceptions from a particular workforce, not a measured decline in skill. They are still reasons to ask a human question before imposing a usage quota.
The four perspectives need not all show immediate gains. An investment in a safer release may temporarily slow a team while protecting customers. The honest decision states who bears that cost, why it is justified, and when the trade-off will be reviewed. Some conditions—privacy, safety, fair treatment—are boundaries, not commodities to exchange for more generated work.
At the junction: Write one sentence for each perspective about a proposed AI use. For each sentence, write an observable indicator and one way it could mislead you. If the company sentence says "hours saved × salary," ask whether anyone's payroll actually changed or whether capacity was put to useful work.