Can you describe a time when you had to gather requirements from multiple business stakeholders who had conflicting priorities? How did you handle it?
RoleBusiness Analyst
DifficultyMedium
TopicBehavioral
Asked at
Why This Is Asked
This assesses your ability to manage conflicting requirements from diverse stakeholders, critical for a CIS implementation where billing, customer service, and meter-to-cash teams often have competing data needs.
General Approach
Use the STAR format to describe a specific past experience. Emphasize active listening, neutral facilitation, and a data-driven approach to finding a compromise. Show that you can navigate organizational dynamics without escalating conflict.
General Answer
Start by naming the project and the stakeholders plainly, then walk through your process of turning their competing demands into a shared goal. Say that your first move was to listen to each side separately, without taking sides, and to write down what each team truly needed rather than what they asked for. Explain that you then mapped those needs onto the project's core objective, which for a utility like Meralco often means balancing operational accuracy with customer experience and regulatory deadlines. Be honest that you did not aim for a perfect compromise, but for a traceable decision, so you ranked the requirements using clear criteria like impact on billing accuracy, implementation cost, and DOLE or ERC compliance where relevant. Describe how you brought the stakeholders back into one room, presented the trade-offs in a simple visual format, and let them react before you locked the scope. Mention that you confirmed the final agreement in writing and set a review point, so no one felt blindsided later. Keep your tone neutral and collaborative, and if you slip into Taglish, use it to show warmth, not frustration, like saying "nagkasundo naman kami sa priority" rather than blaming anyone.
PH Interview Gotcha
"Sir, minsan kasi ang hirap kausap ng ibang department, paiba-iba ng sabi." Instead, explain how you structured communication to achieve clarity, not blaming other departments.
Sample STAR Answer▾
S
Situation
In my previous role as a Business Analyst at a telecom company, I was tasked with gathering requirements for a new customer portal. The Sales team wanted a feature-rich interface to showcase all promos upfront, while the Customer Service team insisted on a simplified view to reduce call inquiries. Both had valid points and were passionate about their needs.
T
Task
My responsibility was to elicit and document requirements that would satisfy both departments without delaying the three-month project timeline.
A
Action
I first conducted separate interviews to fully understand each team's pain points and priorities. Then I organized a joint workshop where I used a prioritization matrix to rank features based on business value and user impact. I facilitated a discussion that led to agreeing on a modular dashboard: a summary view for quick service requests, with expandable sections for promo details. I documented the consensus in a requirements specification and circulated it for sign-off within the same week.
R
Result
Both departments approved the final requirements, and the portal was delivered on schedule. Post-launch, customer call volume dropped by 15%, and the sales conversion rate from portal visits improved by 10%.
Key Takeaway
Structured facilitation and focusing on shared business outcomes turn conflicting requirements into alignment.
Attempt Your Answer
Write your own answer, then get instant AI feedback graded against:
- •STAR Structure
- •Specificity & Numbers
- •Ownership Language
- •PH Workplace Context
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
Share Your Answer (0)
Sort
Sign in to join the conversation.
No answers shared yet — be the first to show how you'd approach this.