Belief being tested: A team’s finished result tells the owner what each team member contributed.
A team can produce a useful result without making individual contributions easy to identify. The completed work shows what the team accomplished. The completed work may reveal much less about how the result became possible.
That difference matters when a company assigns responsibility, evaluates performance, or decides what to reward.
Alchian and Demsetz examine the problem in “Production, Information Costs, and Economic Organization.” Their model concerns team production in which individual contributions are costly to distinguish. A specialist monitor can help assess contributions. Giving the monitor a residual claim supplies an incentive to perform that monitoring.
The model does not establish that every worker avoids work, that observation is always accurate, or that more surveillance improves performance. Its explanation depends on assumptions about production, information, and incentives.
Residual Claimants brings the issue into an ownership setting: someone must attend to the company’s result while recognizing that the result comes from interdependent work. That operating argument does not turn an economic model into a universal method for managing people.
An invented proposal assignment illustrates the problem. A company prepares a customer proposal. An employee gathers the customer’s requirements. Another employee checks whether the company can deliver the requested work. A manager assembles and submits the proposal.
The customer accepts.
The visible result is a successful proposal. The result does not show whether careful questioning prevented a costly misunderstanding. The result does not show whether an employee corrected an unrealistic promise before submission. The result does not show whether the manager repaired missing work or merely combined complete contributions.
A shared success can conceal very different individual contributions.
The same problem appears when the proposal fails. The failure alone does not identify whose judgment was poor. The customer may have chosen a competitor for reasons unrelated to the quality of the team’s work.
The operating task is to examine the contribution as well as the outcome.
That requires knowing what each assignment was supposed to accomplish. Gathering requirements should produce usable requirements. Checking capacity should produce a grounded answer about capacity. Assembling the proposal should preserve the decisions the proposal depends on.
Without clear assignments, an owner may reward visibility rather than contribution.
The person who submits the finished proposal is easy to identify. The person who prevented an unworkable promise may leave little visible trace. If the company recognizes only the final presentation, the company risks making careful preventive work harder to sustain.
A measurement can consume attention without clarifying useful work. Message counts do not show whether an important question was answered. Time at a desk does not show whether a mistaken assumption was caught.
A useful measure needs a clear connection to the contribution being examined.
The monitor’s work also needs examination. A manager may favor activity that is easy to count. A manager may overlook a contribution that makes the manager’s own work less visible. A manager may avoid reporting a problem the manager should have caught earlier.
Assigning evaluation to a supervisor does not make evaluation automatically trustworthy.
An owner can ask what evidence supports the supervisor’s assessment. What was expected? What was delivered? What obstacle changed the assignment? What information would lead the supervisor to revise the conclusion?
Those questions make the evaluator’s judgment inspectable without pretending that judgment can disappear.