This screen tests your facilitation and people skills when the team is tired or resistant. Employers want to see if you can keep a lessons learned session productive without authority, which is common after handoff.
Acknowledge the team member's frustration first, then briefly reframe the session around reducing future pain. Describe how you would keep the meeting short, structured, and action oriented, and give a specific example of a past time you handled a similar resistant participant.
Begin by genuinely validating the frustration, not just paying it lip service. Say something like, "You're right, the project is done, and I know your plate is full, so let's make this worth your time." This immediately lowers the temperature and shows you are on their side, not defending a bureaucratic process. Then, reframe the meeting in practical terms: frame it as a way to avoid repeating the same painful problems, such as the late-night deployment or the vendor delays that caused overtime, on the next project. Offer to make the session tight, say thirty minutes, and commit to producing a short list of action items that you will actually circulate and follow up on. In a Philippine BPO or shared services setting, you can also remind them that the next project might be with a different client or account, so their input here protects their own future workload. If resistance persists, pivot to a specific question aimed at their expertise, like asking what one thing they would change about the onboarding process, which gives them ownership. Remember to keep your tone conversational and unhurried, and if the room stays tense, you can offer to take the discussion offline with two or three people and share the summary later. The goal is to show that you can turn a mandatory meeting into a practical tool, not a burden.
Some candidates respond defensively with, 'Kailangan kasi, standard process yan, so mag-participate ka na lang.' That creates more resistance. Instead, validate the concern and connect the meeting to a concrete benefit like avoiding repeated issues on the next project.
Situation
In my previous job as a project coordinator for a client onboarding, I was asked to facilitate a post project review with the implementation team. One senior specialist pushed back at the start, saying the project was finished and the meeting was a waste of time.
Task
I had to get honest feedback and keep the session productive without making the specialist defensive or shutting down the discussion.
Action
I acknowledged his concern and reframed the meeting as a way to reduce rework on the next client rollout, then asked him directly for one thing that would have made his job easier. I kept the session to thirty minutes, used anonymous sticky notes for feedback, and focused only on actions we could control, not blaming individuals.
Result
The specialist contributed three practical suggestions. Two were adopted in the next onboarding template, which saved about four hours of rework per new client.
A short action focused retrospective can turn a skeptic into a contributor when you tie it to their own pain.
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.