What performance management action is appropriate for this situation?
Decision tree
hrperformance managementpeople managementemployee relations
Determines the appropriate performance management action for an underperforming employee. Use this tree to guide managers through a structured, fair, and legally defensible response to performance concerns. The outcome aligns with progressive discipline principles and HR best practice.
Overview
Decision Tree
Start: Is this the first time you are raising a performance concern with this employee?
yes
- Continues to question: Is the underperformance causing significant or immediate business impact?
no
- Continues to question: Has the manager documented the prior performance feedback in writing?
Machine-Readable JSON (Canonical Model)
View JSON
{
"_meta": {
"schema": "https://www.drawdecisiontree.com/decision-dag.schema.json",
"source": "https://www.drawdecisiontree.com",
"description": "DrawDecisionTree.com is a free tool for building, sharing, and embedding interactive decision trees. This file is the machine-readable export of a published decision tree. The `dsl` field contains the original source in the Decision DAG DSL; the `dag` schema is documented at the URL in `schema` above.",
"links": {
"interactive": "https://www.drawdecisiontree.com/t/drawdecisiontree/hr-performance-action.html",
"embed": "https://www.drawdecisiontree.com/embed/path/drawdecisiontree/hr-performance-action",
"dsl_reference": "https://www.drawdecisiontree.com/decision-tree-dsl-reference.html",
"guides": "https://www.drawdecisiontree.com/guides",
"schema_docs": "https://www.drawdecisiontree.com/decision-dag.schema.json",
"author_trees": "https://www.drawdecisiontree.com/trees/drawdecisiontree"
},
"generated_at": "2026-05-29T12:05:39.303Z"
},
"author": {
"handle": "drawdecisiontree",
"first_name": "Andrew",
"last_name": null,
"avatar_url": "1d32d828-b6ca-40ec-bdd7-771fe7b9c36a/avatar-1778531481027.svg",
"display_name": "Andrew"
},
"file": {
"id": "dc6d93a8-bdd0-4169-bf3f-9a162fa9040b",
"name": "What performance management action is appropriate for this situation?",
"public_slug": "hr-performance-action",
"updated_at": "2026-05-12T16:53:43.587978+00:00",
"url": "https://www.drawdecisiontree.com/t/drawdecisiontree/hr-performance-action.html",
"json_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/hr-performance-action/tree.json",
"dsl_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/hr-performance-action/tree.dag"
},
"meta": {
"description": "Determines the appropriate performance management action for an underperforming employee. Use this tree to guide managers through a structured, fair, and legally defensible response to performance concerns. The outcome aligns with progressive discipline principles and HR best practice.",
"mode": "decision",
"entry": "Q1",
"tags": [
"hr",
"performance management",
"people management",
"employee relations"
],
"image": "https://images.unsplash.com/photo-1552664730-d307ca884978?w=1200&q=80"
},
"questions": [
{
"id": "Q1",
"text": "Is this the first time you are raising a performance concern with this employee?"
},
{
"id": "Q2",
"text": "Is the underperformance causing significant or immediate business impact?"
},
{
"id": "Q3",
"text": "Has the manager documented the prior performance feedback in writing?"
},
{
"id": "Q4",
"text": "Is the root cause primarily a conduct issue (wilful non-compliance, attitude, or behaviour) rather than a capability issue (skills gap or lack of knowledge)?"
}
],
"outcomes": [
{
"id": "INFORMAL",
"label": "Informal Coaching Conversation"
},
{
"id": "DEV_PLAN",
"label": "Structured Development Plan"
},
{
"id": "PIP",
"label": "Formal Performance Improvement Plan (PIP)"
},
{
"id": "ESCALATE",
"label": "Escalate to HR / Legal"
}
],
"dsl": "dag: What performance management action is appropriate for this situation?\nversion: 1.0.0\nimage: https://images.unsplash.com/photo-1552664730-d307ca884978?w=1200&q=80\ndescription: Determines the appropriate performance management action for an underperforming employee. Use this tree to guide managers through a structured, fair, and legally defensible response to performance concerns. The outcome aligns with progressive discipline principles and HR best practice.\ntags: hr, performance management, people management, employee relations\nentry: Q1\n\nQ1: Is this the first time you are raising a performance concern with this employee?\n hint: Consider whether any prior conversations about performance have taken place, even informally. A \"first conversation\" means the employee has not previously been made aware that their output, behaviour, or results fall below expectations. If there has been a prior discussion — even a casual one — answer no. Be honest with yourself: a passing comment in a one-on-one does count as a prior conversation.\n yes -> Q2\n no -> Q3\n\nQ2: Is the underperformance causing significant or immediate business impact?\n hint: Significant impact includes missed deadlines on critical projects, customer complaints, revenue loss, safety issues, or material disruption to the team. Minor impact includes occasional errors, slower-than-expected ramp-up, or quality issues that are contained and recoverable. Be objective about the real cost of the current situation to the organisation — neither minimise nor exaggerate the consequences.\n yes -> Q4\n no -> [INFORMAL]\n\nQ3: Has the manager documented the prior performance feedback in writing?\n hint: Documentation includes written follow-up emails after conversations, notes recorded in a performance management system, meeting minutes, or formal review ratings. Verbal-only feedback with no written record significantly weakens the organisation's position if further action becomes necessary. Check the employee's file and any HR information system before answering — the existence of a paper trail is essential at this stage.\n yes -> Q4\n no -> [DEV_PLAN]\n\nQ4: Is the root cause primarily a conduct issue (wilful non-compliance, attitude, or behaviour) rather than a capability issue (skills gap or lack of knowledge)?\n hint: Conduct issues are where the employee could meet expectations but is choosing not to — examples include ignoring instructions, insubordination, persistent lateness, or disrespectful behaviour toward colleagues. Capability issues are where the employee is genuinely trying but lacks the skills, training, or support to succeed. This distinction is legally and procedurally critical: conduct and capability follow different pathways in most jurisdictions and conflating them creates significant legal exposure.\n yes -> [ESCALATE]\n no -> [PIP]\n\n[INFORMAL]: Informal Coaching Conversation\n color: #4ade80\n description: An informal, private conversation is the right starting point. The manager should clearly name the performance gap, explain the expected standard, and agree on specific improvement actions with a concrete timeline. This conversation must be documented with a brief follow-up email summarising what was discussed and agreed — even informal conversations need a written record. No formal HR process is required at this stage, but the record is essential if further action becomes necessary later. Schedule a follow-up check-in within two to four weeks to review progress against the agreed actions.\n code: HR_PERF_01\n\n[DEV_PLAN]: Structured Development Plan\n color: #facc15\n description: A structured development plan is appropriate where concerns have been raised previously but were not formalised in writing. Work with the employee to co-create a written plan that identifies specific performance gaps, measurable improvement targets, required support or training, and a clear review timeline of four to eight weeks. The plan should be signed by both the manager and the employee and stored securely in the HR system. This step protects the organisation legally and gives the employee a genuine, supported opportunity to improve before any escalation. Share the plan with HR before finalising to ensure it meets policy requirements.\n code: HR_PERF_02\n\n[PIP]: Formal Performance Improvement Plan (PIP)\n color: #f97316\n description: A formal PIP is warranted where prior feedback has been documented and the capability concern persists or is of sufficient severity. Engage HR before initiating the PIP to ensure the plan meets all legal requirements and company policy standards. The PIP must include specific and measurable goals, a defined review period (typically 30 to 90 days), explicit support commitments from the organisation, and clear consequences if the plan is not met. Hold regular documented review meetings throughout the PIP period. At the conclusion of the plan, communicate the outcome clearly and in writing — whether that is successful completion, extension, or further action up to and including termination.\n code: HR_PERF_03\n\n[ESCALATE]: Escalate to HR / Legal\n color: #ef4444\n description: Where the issue is primarily one of conduct rather than capability, the performance management pathway is not appropriate and HR — and potentially legal counsel — must be involved immediately. Conduct concerns may require a separate investigation, a disciplinary process, or both, and the procedural requirements differ materially from capability management. Attempting to manage a conduct issue through a PIP creates significant legal exposure and may be used against the organisation in any subsequent employment tribunal or litigation. Gather all relevant evidence, preserve communications without alteration, and contact HR to agree on the correct next step before any further conversation with the employee.\n code: HR_PERF_04\n"
}DSL Representation
dag: What performance management action is appropriate for this situation?
version: 1.0.0
image: https://images.unsplash.com/photo-1552664730-d307ca884978?w=1200&q=80
description: Determines the appropriate performance management action for an underperforming employee. Use this tree to guide managers through a structured, fair, and legally defensible response to performance concerns. The outcome aligns with progressive discipline principles and HR best practice.
tags: hr, performance management, people management, employee relations
entry: Q1
Q1: Is this the first time you are raising a performance concern with this employee?
hint: Consider whether any prior conversations about performance have taken place, even informally. A "first conversation" means the employee has not previously been made aware that their output, behaviour, or results fall below expectations. If there has been a prior discussion — even a casual one — answer no. Be honest with yourself: a passing comment in a one-on-one does count as a prior conversation.
yes -> Q2
no -> Q3
Q2: Is the underperformance causing significant or immediate business impact?
hint: Significant impact includes missed deadlines on critical projects, customer complaints, revenue loss, safety issues, or material disruption to the team. Minor impact includes occasional errors, slower-than-expected ramp-up, or quality issues that are contained and recoverable. Be objective about the real cost of the current situation to the organisation — neither minimise nor exaggerate the consequences.
yes -> Q4
no -> [INFORMAL]
Q3: Has the manager documented the prior performance feedback in writing?
hint: Documentation includes written follow-up emails after conversations, notes recorded in a performance management system, meeting minutes, or formal review ratings. Verbal-only feedback with no written record significantly weakens the organisation's position if further action becomes necessary. Check the employee's file and any HR information system before answering — the existence of a paper trail is essential at this stage.
yes -> Q4
no -> [DEV_PLAN]
Q4: Is the root cause primarily a conduct issue (wilful non-compliance, attitude, or behaviour) rather than a capability issue (skills gap or lack of knowledge)?
hint: Conduct issues are where the employee could meet expectations but is choosing not to — examples include ignoring instructions, insubordination, persistent lateness, or disrespectful behaviour toward colleagues. Capability issues are where the employee is genuinely trying but lacks the skills, training, or support to succeed. This distinction is legally and procedurally critical: conduct and capability follow different pathways in most jurisdictions and conflating them creates significant legal exposure.
yes -> [ESCALATE]
no -> [PIP]
[INFORMAL]: Informal Coaching Conversation
color: #4ade80
description: An informal, private conversation is the right starting point. The manager should clearly name the performance gap, explain the expected standard, and agree on specific improvement actions with a concrete timeline. This conversation must be documented with a brief follow-up email summarising what was discussed and agreed — even informal conversations need a written record. No formal HR process is required at this stage, but the record is essential if further action becomes necessary later. Schedule a follow-up check-in within two to four weeks to review progress against the agreed actions.
code: HR_PERF_01
[DEV_PLAN]: Structured Development Plan
color: #facc15
description: A structured development plan is appropriate where concerns have been raised previously but were not formalised in writing. Work with the employee to co-create a written plan that identifies specific performance gaps, measurable improvement targets, required support or training, and a clear review timeline of four to eight weeks. The plan should be signed by both the manager and the employee and stored securely in the HR system. This step protects the organisation legally and gives the employee a genuine, supported opportunity to improve before any escalation. Share the plan with HR before finalising to ensure it meets policy requirements.
code: HR_PERF_02
[PIP]: Formal Performance Improvement Plan (PIP)
color: #f97316
description: A formal PIP is warranted where prior feedback has been documented and the capability concern persists or is of sufficient severity. Engage HR before initiating the PIP to ensure the plan meets all legal requirements and company policy standards. The PIP must include specific and measurable goals, a defined review period (typically 30 to 90 days), explicit support commitments from the organisation, and clear consequences if the plan is not met. Hold regular documented review meetings throughout the PIP period. At the conclusion of the plan, communicate the outcome clearly and in writing — whether that is successful completion, extension, or further action up to and including termination.
code: HR_PERF_03
[ESCALATE]: Escalate to HR / Legal
color: #ef4444
description: Where the issue is primarily one of conduct rather than capability, the performance management pathway is not appropriate and HR — and potentially legal counsel — must be involved immediately. Conduct concerns may require a separate investigation, a disciplinary process, or both, and the procedural requirements differ materially from capability management. Attempting to manage a conduct issue through a PIP creates significant legal exposure and may be used against the organisation in any subsequent employment tribunal or litigation. Gather all relevant evidence, preserve communications without alteration, and contact HR to agree on the correct next step before any further conversation with the employee.
code: HR_PERF_04
Machine Access
- Static JSON:
/t/drawdecisiontree/hr-performance-action/tree.json - Live JSON (SPA):
/json/drawdecisiontree/hr-performance-action - Raw DSL:
/t/drawdecisiontree/hr-performance-action/tree.dag - Canonical HTML:
/t/drawdecisiontree/hr-performance-action.html
Questions in this decision tree
- Is this the first time you are raising a performance concern with this employee?
- Is the underperformance causing significant or immediate business impact?
- Has the manager documented the prior performance feedback in writing?
- Is the root cause primarily a conduct issue (wilful non-compliance, attitude, or behaviour) rather than a capability issue (skills gap or lack of knowledge)?
Possible outcomes
- Informal Coaching Conversation
- Structured Development Plan
- Formal Performance Improvement Plan (PIP)
- Escalate to HR / Legal
How to use this decision tree
Click "Open interactive version" to step through the questions. Your answers narrow the tree until a recommended outcome is reached. You can also embed this tree on your own site.
More decision trees by Andrew
Which API design pattern is right for my project?
Determine the right API design style for your integration scenario.
Authentication Method Selection
Authentication is a security-critical, high-friction decision to reverse — migrating users from one auth method to another requires coordinated password resets or credential migration campaigns. This tree eliminates methods that don't match your user type, enterprise requirements, and security posture, giving you a clear shortlist before you write a line of code.
Caching Strategy Selection
Premature or misapplied caching adds complexity — stale data bugs, invalidation logic, and distributed consistency problems — without solving the actual bottleneck. This tree routes you to the caching pattern that matches your data access profile, so you apply the right tool to the right problem rather than defaulting to Redis for everything.
CI/CD Pipeline Tool Selection
Choosing a CI/CD platform is a long-term infrastructure commitment — pipelines accumulate config, custom scripts, and team muscle memory that make switching painful. This tree eliminates tools that don't fit your source control host, infrastructure model, or team scale, leaving only the options genuinely viable for your situation.
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Answer a few questions to identify the most suitable cloud platform for your workload.
Container Orchestration Platform Selection
Container orchestration is foundational infrastructure — the platform you choose shapes how you deploy, scale, network, and operate every service you run. This tree eliminates options that don't match your operational maturity, cloud provider commitment, and workload complexity, so you land on the platform that fits your team today without over-engineering for a scale you haven't reached.