Start with the gap you can observe: a missed deadline, inconsistent quality, slow follow-up, poor prioritization, or another result the role is expected to deliver. “Be more productive” is too vague to diagnose or review.
For an individual, the gap might be missed deadlines, inconsistent quality, slow follow-up, or difficulty prioritizing. For a team, it may be unclear ownership, overloaded capacity, weak handoffs, or a tool that creates more administration than value.
What work performance includes
Performance is broader than output volume. A practical review considers:
- results and goal attainment;
- quality and error rate;
- timeliness and reliability;
- judgment and problem solving;
- communication and collaboration;
- customer or stakeholder impact;
- compliance with role and policy expectations;
- development of the skills the role requires.
Do not use online status, keyboard activity, or time at a desk as a substitute for this picture.
A seven-step performance improvement plan
-
Define the gap with evidence
Replace “needs to be more proactive” with an observable statement: “Three of the last six client reports arrived after the agreed date, and two required correction for missing source data.”
Describe the required standard, recent examples, and business impact. Confirm that the standard is realistic and applied consistently to comparable work.
-
Ask what is causing the gap
A performance problem can come from several places:
Ask a different question for each possible cause. If priorities conflict, decide which assignment should come first. If capacity is the issue, test whether the workload fits the available time and reduce scope, rebalance, or staff. If skill is missing, use training, practice, and examples. If work waits or repeats, remove process friction. If the tool is slow or duplicated, repair or simplify it. If motivation is the concern, reconnect the work to its purpose and consequence. Use a formal management or HR process only after expectations and resources are clear.
Ask the employee or team for their view before deciding. Explanation is evidence to test, not an automatic excuse or proof.
-
Set a small number of outcomes
Choose one to three measurable outcomes for the next review period. Examples:
- deliver the weekly report by 3 p.m. Thursday with all required fields;
- reduce avoidable invoice corrections from 8% to below 3%;
- acknowledge priority customer requests within the agreed service window;
- complete the certification and demonstrate the process on two supervised cases.
Include quality. A speed target without a quality measure can encourage shortcuts.
-
Remove one meaningful blocker
Do not assign the employee every solution at once. Choose the constraint most likely to change the result: clarify intake, reduce work in progress, add a template, schedule training, assign a mentor, repair an integration, or shorten an approval path.
-
Agree on support and ownership
The employee owns the commitments within their control. The manager owns clear priorities, resources, timely decisions, feedback, and escalation. Write both sides down.
-
Review progress frequently enough
Use short progress conversations rather than waiting for the next annual review. The cadence should match the work: weekly for high-volume tasks, milestone-based for projects with long cycles.
A useful check-in asks:
- What was committed?
- What was completed and accepted?
- What changed?
- What is blocked?
- What decision or support is needed?
- What will be different before the next review?
-
Decide based on the pattern
If performance improves, reinforce the practices that worked and gradually reduce oversight. If the same gap persists despite clear expectations and support, follow the company’s performance-management process with HR guidance where appropriate.
Ways employees can improve their own performance
Build a weekly priority view
List the outcomes that must be true by the end of the week. Confirm their order with the manager. Keep a separate backlog so lower-priority work does not compete visually with current commitments.
Break large work into reviewable milestones
An early outline, sample, calculation, or prototype exposes misunderstanding while correction is still cheap.
Protect focus
Silence non-urgent alerts, batch routine communication, and reserve blocks for difficult work. Tell coworkers how urgent requests should reach you.
Ask for specific feedback
“What is one change that would make this deliverable more useful?” produces better guidance than “Any feedback?”
Track repeated friction
Keep a short record of blockers, rework, and recurring manual steps. A pattern gives the manager something concrete to fix.
Ways managers can improve team performance
Make tradeoffs explicit
When new work arrives, say what moves. Employees should not be forced to guess which promise to break.
Measure outcomes and flow
Combine completed work and quality with cycle time, blocked time, workload, and customer impact. A dashboard used to monitor employee performance should explain the system, not publish a simplistic leaderboard.
Match oversight to risk
New, high-risk, or recovering work may need more frequent review. Proven employees handling stable work need less. Explain the reason for the cadence and reduce it as confidence grows.
Give feedback close to the event
Use the specific situation, the observable behavior or output, its impact, and the expected change. Avoid labels about attitude or personality when a work example is available.
Recognize strong work precisely
Name the action and value: “You surfaced the data gap before the customer review, which let the team correct it without moving the deadline.” Specific recognition teaches the standard.
A 30-day improvement example
Gap: Monthly close tasks arrive two days late and contain avoidable reconciliation errors.
Outcome: Complete assigned close tasks by noon on day three with no unresolved variance over the stated threshold.
Actions: Use a standardized checklist; complete training on the reconciliation tool; review the first two files with a senior analyst; escalate missing source data after four hours.
Manager support: Freeze non-close work during the first three days; respond to escalations within one business hour; confirm the threshold in writing.
Review: Ten-minute check-in each close day and a full review after the next cycle.
Using activity data during a performance review
KeepActive can help computer-based teams understand work-time patterns and application use on approved devices. It may reveal excessive switching, unplanned after-hours work, or low adoption of a required system. Those signals should start a conversation, not determine a performance rating. Pair them with deliverables, quality, workload, and employee context under an ethical monitoring policy.
Separate clarity, capability, capacity, and conduct
The same missed deadline can have four different causes. Clarity means the expected result or priority was not understood. Capability means the person needs knowledge, practice, or a better tool. Capacity means the workload or dependency made the commitment unrealistic. Conduct means the expectation was clear, feasible, and supported, but was still ignored.
Test the categories in that order and record the evidence. Clarify the requirement, provide the missing support, remove an overload or blocked dependency, and observe the next comparable commitment. A formal performance response is more defensible after the manager has ruled out a broken assignment and a broken system.
Make the improvement plan specific and testable
Agree on the gap in observable terms, change one or two conditions, and review enough real work to judge the effect. A vague promise to “try harder” gives neither the employee nor the manager anything useful to manage.
FAQ (Frequently Asked Questions): Find Answers and Solutions:
What are three ways to improve work performance?
Clarify the most important outcome, remove the largest blocker, and establish a short feedback cycle. Those actions usually produce more value than adding a long list of personal productivity tips.
How should a manager discuss poor performance?
Use specific examples, state the expected standard and impact, ask about causes, agree on support and commitments, and set a review date. Follow company policy and involve HR when the situation may become formal.
How do you measure improvement fairly?
Compare like-for-like work over a reasonable period. Use outcomes, quality, and timeliness, then consider workload, case mix, dependencies, and changes in the operating environment.
Can monitoring data be used in a performance review?
It can provide context when the use is lawful, transparent, relevant, and reviewed by a person. It should not be treated as conclusive proof of performance or misconduct without corroborating evidence.
Contents
Share this post