Key takeaways
- Quiet quitting is a label for limiting work, not an explanation of someone’s motives.
- Completing agreed duties without volunteering for extra work does not establish poor performance.
- Discuss the actual responsibilities, workload and support with the employee.
- Agree a next action and review evidence about the work rather than guessing disengagement.
Quiet quitting is a term commonly used for limiting work to the duties someone considers part of their job. It can describe different situations, so the label alone does not explain an employee's experience or performance.
Discuss the work and expectations directly. Completing agreed duties without volunteering for extra tasks does not establish a performance problem.
Describe the change you have observed
Use a specific observation about the work rather than guessing a motive. Ask whether responsibilities, priorities or circumstances have changed.
Being quiet in a meeting or declining an optional activity does not establish disengagement. Give the employee room to explain their perspective.
Clarify the agreed responsibilities
Review the role, goals and expectations together. Discuss any difference between what the manager expects and what the employee understood.
Explain which work is required and which is optional. Review workload and resources when expectations have expanded beyond the original arrangement.
For an illustrative Support Specialist at a fintech infrastructure company, declining an optional lunchtime learning session does not explain the quality of their work. If an agreed handover is incomplete, discuss that specific handover: what information was required, what the employee understood and which competing work or missing support affected it. Agree a realistic priority and review the next handover. The fintech infrastructure employee journey gives context for the role's introductions, learning and support.
- 01
Observation
Describe a specific task or deadline and what happened, without calling the employee a quiet quitter.
- 02
Employee perspective
Ask what the employee understood the priority to be and which work, information or support affected it.
- 03
Next step
Agree the priority and any support or workload change, then set a date to review the actual task.
Ask about support and working conditions
Invite a conversation about obstacles, recognition and development. The employee may have an issue with the work, need support or be maintaining an agreed boundary.
Use coaching leadership questions to explore the difficulty. Keep the conversation connected to the employee's explanation rather than a generational stereotype.
Agree what happens next
Record the responsibility, support or clarification that follows from the discussion. Arrange a review when there is an action to check.
The employee experience guide can help examine recurring issues across the organisation. Keep any performance concern grounded in the agreed work and relevant evidence.
Where CapoFine fits
Coordinate the welcome in Onboard
Onboard connects employee tasks, introductions, learning and manager conversations in a journey from preboarding through day 90.