Compensation Design Reasoning Chain
Block ID: 506e8b37-2949-4dd0-9f9e-2343d41c8273
Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.
Template
Reason through the compensation or incentive design in {comp_context}, remembering that people optimize what you pay them for, including the parts you didn't intend. (1) Start from the behavior you actually want, because a comp plan is a behavioral instruction, and the central risk is that it rewards a proxy that diverges from the real goal — paying salespeople on booked revenue when you need retained revenue, for instance, buys exactly the wrong sales. (2) Trace every way the proposed plan could be gamed or produce perverse behavior: what's the most lucrative thing someone could do under this plan that doesn't serve the business? If there's an easy way to hit the number while hurting the goal, people will find it. (3) Balance the components against the behavior: fixed pay for stability and retention, variable pay for the outcomes you want to drive, and ensure the variable part is tied to things the person actually controls, since rewarding people for outcomes outside their control breeds cynicism. (4) Check the interaction effects: individual incentives that undermine teamwork, or short-term incentives that sacrifice the long term. (5) Weigh internal fairness and external competitiveness, since a plan that feels unfair or below market fails regardless of its cleverness. (6) State the recommended design, the behavior it drives, the gaming risk it must guard against, and the guardrail metric to catch abuse — because the test of a comp plan is the behavior it produces, not its elegance on paper.
Variables
| Name | Type | Required | Trust level |
|---|---|---|---|
| comp_context | yes |
compensationincentivesorg-designchain-of-thought
Ratings
0.0
Overall (0)
0.0
Accuracy
0.0
Consistency
0.0
Clarity
0.0
Efficiency
Benchmarks
Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.
Log in to rate this block.
Submitted by James P FounderMod via mcp · 2026-07-18