You are managing a project where the Sales Director is asking for an additional feature that would delay the launch by two weeks, while the Operations Manager insists the launch must proceed on the original date. How do you handle this situation?

Situation

In my previous role as a project coordinator at a BPO company, I was helping manage the rollout of a new CRM tool for the sales team. Two weeks before go-live, the Sales Director asked to add a custom reporting module, while the Operations Manager wanted the original date to avoid disrupting daily workflows.

Task

My task was to resolve the conflict without damaging stakeholder relationships and to recommend a decision that balanced scope, timeline, and business value.

Action

First, I met separately with each stakeholder to understand their underlying goals: Sales wanted better pipeline visibility for the next quarter, while Operations feared extra training time during peak season. I then quantified the impact of the delay by building a simple cost-benefit analysis showing a two-week delay would cost 3 potential client deals worth around PHP 1.2 million, while the feature could increase forecast accuracy by 15%. I presented both options in a joint meeting and proposed a compromise: launch the CRM as planned, then release the reporting module as a Phase 2 enhancement six weeks later, which satisfied both the timeline and the Sales Director's need for data.

Result

Both stakeholders agreed to the phased approach, and the CRM launched on schedule. The reporting module was delivered seven weeks later with minimal disruption, and the Sales Director later reported that the new reports saved his team 4 hours per week.