
Consultants are brought in specifically to change how teams work, so resistance to change is the default condition they're hired to navigate: this tests influence without formal authority.
Spend most of your answer on how you built buy-in (small wins, involving skeptics early, data over opinion) rather than the improvement itself: the interviewer is evaluating your change-management approach, not the technical fix.
Begin by grounding your story in the reality that resistance rarely means laziness, it usually means fear of extra work or fear of being proven wrong. Say plainly that you started by listening, not presenting, and that you scheduled informal one-on-ones with the most vocal skeptics first, because in a Philippine team setting, public challenge is often softened by private agreement, so you need to find the real objection behind the polite nod. Explain that you asked them what part of their current process ate the most time, and then you used that exact pain point as your entry, building a small pilot that only touched their workload, not the whole team's. Emphasize that you made the change tangible within a week, showing them a before and after of their own steps, and that you credited their input in front of the manager, which is crucial in a culture where saving face matters more than being right. Acknowledge their extra effort during the transition, even a simple thank you in a group chat goes far, and use a Taglish phrase like pinakita ko sa kanila na hindi na kailangan ng triple type to signal you understood their daily grind. Close by noting that once the first skeptic became your champion, the rest followed, and that you kept the momentum by reporting small wins weekly, not by declaring victory.
Some candidates default to 'I convinced them with a meeting and PowerPoint' but in Philippine office culture, personal connection matters more. Don't boast about forcing change; instead, say you acknowledged their extra effort and demonstrated how the change would actually lighten their load. Taglish phrases like 'pinakita ko sa kanila na hindi na kailangan ng triple type' builds trust.
Situation
As a consultant at a Philippine shared services center for a European insurance company, I was tasked with improving the policy renewal processing time. The 12-member team had an average turnaround of 5.2 days against a client benchmark of 3 days, but most were comfortable with the existing manual checks because they feared automation would affect accuracy.
Task
I needed to design and implement a process change that would reduce turnaround to under 3 days while gaining buy-in from the team, who were skeptical that any change would just add more work.
Action
I started by spending two days shadowing the three most vocal skeptics and noting exactly where they had to re-key data across systems. I then presented findings in a team huddle, acknowledging their frustrations first: 'I saw that you manually copy the same client name four times; that must be annoying, and I agree it's waste.' I proposed a macro that auto-populated those fields and asked them to test it on 10 real cases. When errors dropped from 12% to 2% on their test batch, they began volunteering suggestions for other automation points. I incorporated three of their ideas into the final workflow, which made them feel ownership.
Result
Full implementation reduced average turnaround from 5.2 days to 2.1 days, exceeding the target. The team’s overtime hours dropped by 40%, and they adopted a continuous improvement board themselves, flagging two more manual tasks they wanted to automate next quarter.
True buy-in comes from involving skeptics early and letting their own data prove the improvement, not from top-down persuasion.
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.