Making the Exchange Visible
The payoff table is a team-level visibility tool. It maps each member's contributions against the team's outcomes and tracks whether recognition and compensation are proportional to value created. The table does not require mathematical precision — it requires honesty. Its purpose is to surface mismatches between what people contribute and what they receive, so the team can address them before resentment compounds.
Structure
The table has four columns per team member:
Contribution. What does this person bring to the team? Name the specific outputs, skills, or functions. Avoid role titles — "project manager" is a label; "coordinates deliverables across three workstreams, manages client communication, and maintains the schedule" is a contribution.
Outcome link. Which team outcomes depend on this contribution? If the contribution cannot be linked to an outcome the team values, it is either invisible (underrecognized) or unnecessary (carried by inertia). Both conditions require examination.
Current return. What does this person receive? Compensation, equity, recognition, learning opportunity, network access, creative fulfillment — whatever the team uses as currency. Be specific. "Fair compensation" is a claim; "$X salary plus Y% equity plus weekly public recognition of deliverables" is a return.
Proportionality assessment. Does the return track the contribution? This is a qualitative judgment, not an accounting entry. The question is whether a disinterested observer, seeing the contribution and the return side by side, would judge the exchange as roughly fair. Where the answer is no — where someone contributes significantly more than they receive, or receives significantly more than they contribute — the team has a justice gap.
How to Build It
Build the table collaboratively. Each member fills in their own contribution and return columns, then the team reviews together. The collaborative process matters — it surfaces disagreements about what constitutes contribution, which outcomes matter, and whether the exchange is fair. These disagreements are data. Suppressing them is how teams develop hidden resentment; surfacing them is how teams practice the Trader Principle.
Review the table quarterly, or whenever the team's composition, goals, or compensation structure changes. The table is a living document — it tracks the exchange as conditions evolve, not as they were at the moment of founding.
Sample Payoff Table
Table 2.1.4-1 — Payoff Table: Sample Team Assessment
A partial payoff table for a four-person product team. The "Proportionality" column surfaces justice gaps the team can address before resentment compounds.
| Team Member | Contribution | Outcome Link | Current Return | Proportionality |
|---|---|---|---|---|
| A — Lead developer | Builds core product; resolves critical bugs; mentors junior developer | Product functionality, release schedule, team capability | $145K salary, 4% equity, public credit in release notes | Roughly proportional — compensation tracks output |
| B — Designer | Creates UI/UX for all features; runs user testing; maintains design system | User experience, retention metrics, brand coherence | $110K salary, 2% equity, no public credit | Gap — design system maintenance is invisible; no recognition for mentorship-equivalent work on design standards |
| C — Operations | Manages client communication, invoicing, compliance, internal scheduling | Revenue collection, legal standing, team coordination | $85K salary, 1% equity, "support role" label | Gap — coordination work is structural but classified as support; return underweights contribution |
| D — Junior developer | Implements assigned features; writes tests; documents code | Feature velocity, code reliability | $75K salary, 1% equity, learning access | Roughly proportional — return includes developmental value (mentorship, skill growth) |
The table reveals two common patterns. Member B performs invisible work — maintaining the design system — that sustains outcomes without producing visible artifacts. Member C carries structural load classified as "support," a label that compresses real contribution into a low-status category. Neither finding requires immediate action. Both require the team to look at the exchange honestly and decide whether the current terms match the actual architecture of contribution.
What It Reveals
The most common finding is asymmetry: one or two members contributing disproportionately, with recognition and compensation lagging their output. The second most common finding is invisible work: contributions that are real but unrecognized because they do not produce visible artifacts — coordination, mentorship, conflict resolution, institutional memory.
Neither finding is a crisis. Both are information. The payoff table converts informal intuitions about fairness into structured evidence, giving the team the basis for a conversation that might otherwise remain a grievance.
Change Log
- 18 Mar 26 — Added a sample payoff table (Table 2.1.4-1) with a four-member team example showing proportional returns, invisible work, and misclassified contribution, plus an interpretive paragraph below the table.
- 17 Mar 26 — Lowercased "payoff table" in body text and standardized "Trader Principle" capitalization; revised the subtitle to be more descriptive; bolded "honesty" and "justice" as key terms.
- 17 Mar 26 — Initial publication.