This scenario tests whether the candidate can identify performance gaps, address them directly, and put a practical recovery plan in place, which is core to tracking progress and managing risks in project delivery.
Structure the answer as a calm, private conversation first, then diagnosis, then a clear action plan with follow up. Show you focus on the work outcome and the person's development, not blame.
Start by saying you would schedule a private, one on one conversation, not an email or a group chat, and open it with a neutral observation like "I noticed the last two deliverables came in late and had some errors." From there, ask open ended questions to understand what is really going on, whether it is an unclear requirement, a personal issue, or a skill gap, and listen without interrupting. Once you have the diagnosis, shift into problem solving mode: agree on a written recovery plan that lists the next deliverable, the exact due date, and the specific quality checks you both expect, like a peer review or a formatting checklist. Say plainly that you will do a quick check in two or three days, not to police them but to remove any blockers early. If the errors persist after that, explain that you would escalate to HR or your project sponsor with documentation of the missed deadlines and the plan, because protecting the project timeline is your responsibility. Keep your tone firm but supportive, and avoid any apologetic language, since the goal is to fix the work, not to cushion the feedback.
Many Filipino candidates over apologize or soften the issue by saying something like 'Pasensya na po, pero kulang po kasi siya sa training' and then avoid assigning clear next steps. Instead, say directly that you would set a private meeting, name the missed deadlines, and agree on a written recovery plan.
Situation
In a previous role as a logistics coordinator, I was assigned to help manage a small system migration project with a five person team. One junior analyst on the team missed two consecutive data cleansing deadlines and the file he submitted had several incorrect customer account numbers.
Task
I needed to get the data cleansing back on schedule without demoralizing the analyst, and to correct the errors before they reached the migration test environment.
Action
First I checked the project tracker to confirm the missed dates and error patterns. Then I scheduled a private 15 minute check in with the analyst, asked open ended questions about what was blocking him, and listened before making assumptions. I discovered he was unclear on the validation rules and had been copying data from an old template. I walked him through the new validation checklist, agreed on a revised daily submission target, and set up a brief end of day check for three days to catch errors early.
Result
The analyst met the revised targets for the next three days and the corrected file was accepted by the migration team. The project stayed on track and he later told me the checklist made the task less stressful.
Private, specific feedback plus a clear process fix often works better than public criticism.
Write your own answer, then get instant AI feedback graded against:
Get AI feedback on your answer — free.
3 free AI-graded answers + 1 free mock interview, no card needed.
Sign Up FreeAlready have an account? Log in
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.