Team Performance Diagnosis Chain

validated business chain v1.0.0 cc-by-sa

Block ID: fd2a5cd4-f946-4b0e-b005-312c6d55e0ab

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Diagnose the underperforming team in {team_context} before intervening, since the wrong intervention on a misdiagnosed problem makes things worse. (1) Define the underperformance concretely against a clear expectation — what output or behavior is falling short, by how much — because "the team isn't performing" is a judgment, not a diagnosis, and acting on the impression rather than the specific gap leads to blaming people for a systemic problem. (2) Run the classic diagnostic split: is it a can't or a won't? A capability gap (skills, tools, unclear goals, insufficient resources) is a fundamentally different problem than a motivation gap, and treating a resourcing problem as a motivation problem (more pressure) predictably backfires. (3) Check the system before the individuals: unclear priorities, conflicting incentives, broken processes, or a bottleneck outside the team often cause what looks like a people problem — and blaming individuals for a broken system is the most common and most damaging management error. (4) If it is individual, distinguish a widespread issue (pointing to leadership, culture, or structure) from a specific person's issue. (5) Consider whether the goals themselves were realistic, since a team missing an impossible target isn't underperforming. (6) State the diagnosed cause, whether it's capability, motivation, or system, and the intervention that fits it — resisting the reflex to add pressure before understanding why the gap exists.

Diagnose the underperforming team in {team_context} before intervening, since the wrong intervention on a misdiagnosed problem makes things worse. (1) Define the underperformance concretely against a clear expectation — what output or behavior is falling short, by how much — because "the team isn't performing" is a judgment, not a diagnosis, and acting on the impression rather than the specific gap leads to blaming people for a systemic problem. (2) Run the classic diagnostic split: is it a can't or a won't? A capability gap (skills, tools, unclear goals, insufficient resources) is a fundamentally different problem than a motivation gap, and treating a resourcing problem as a motivation problem (more pressure) predictably backfires. (3) Check the system before the individuals: unclear priorities, conflicting incentives, broken processes, or a bottleneck outside the team often cause what looks like a people problem — and blaming individuals for a broken system is the most common and most damaging management error. (4) If it is individual, distinguish a widespread issue (pointing to leadership, culture, or structure) from a specific person's issue. (5) Consider whether the goals themselves were realistic, since a team missing an impossible target isn't underperforming. (6) State the diagnosed cause, whether it's capability, motivation, or system, and the intervention that fits it — resisting the reflex to add pressure before understanding why the gap exists.

Variables

Name	Type	Required	Trust level
team_context		yes

team-performancemanagementdiagnosischain-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.

Submitted by James P FounderMod via mcp · 2026-07-18