Performance Problems Are Often Design Problems

The problem to solve

A missed outcome matters. But a performance conversation becomes unreliable when it skips the conditions under which the work was supposed to happen. Generic job descriptions, shifting priorities, unclear authority, and absent feedback can all make a capable person look like the problem.

This is not an argument for avoiding difficult accountability. It is an argument for making accountability specific enough to be fair and useful.

The Work & Theory principle

Performance follows the design of the role. A Performance Contract makes purpose, outcomes, expectations, authority, feedback, development, and consequences explicit before the organization evaluates performance.

Diagnostic questions

Use the role holder's actual work, not a generic competency list.

• Was the expected outcome defined and prioritized?
• Did the role holder have authority to make the decisions required?
• What dependencies or workload constraints affected delivery?
• What feedback occurred before the outcome was due?
• What evidence distinguishes a capability gap from a design or context gap?

Practical next actions

Choose one missed outcome. Reconstruct the role conditions around it with the manager and role holder. Name what should be adjusted: outcome, scope, authority, support, capability, or expectation.

Then set the next measurable outcome and a feedback point while the work is still underway. Do not wait for an annual review cycle to learn whether the design is working.

Related artifact and pathway

Turn the agreement into a Performance Contract for the role. Where similar failures occur across roles, use the Health Check to test whether Performance or Design is the system-level constraint.