Answer.

History of the issue:

In large-scale IT projects, multiple stakeholders may present requirements that not only differ but directly contradict each other. The quality of conflict resolution directly impacts the timelines, costs, and success of the project.

Problem:

Unnoticed or ignored contradictions between requirements lead to diluted responsibility, dissatisfaction among business parties, rework, and delays in releases. The lack of a formalized procedure for identifying and reconciling conflicts is a common reason for the failures of major projects.

Solution:

The systems analyst uses proven approaches: interest and goal analysis of each stakeholder (stakeholder mapping), facilitation techniques (workshops, retrospectives, “brainstorming”), constructing contradiction matrices (conflict matrix), paired comparison of requirements (prioritization matrix). They apply the "why-why analysis" method to uncover the root causes of expectations, and then develop compromises or creative solutions, documenting key agreements.

Key features:

Identification of all influence groups and sources of requirements
Maintaining a transparent logic for documenting and resolving conflicts
Supporting communication and facilitating discussions

Trick questions.

Is the customer's priority always decisive in case of conflicting requirements?

No, sometimes technical constraints, legislation, or critical non-functional metrics take precedence over individual business wishes, and the analyst must convey this.

Is compromise always necessary?

Not always: sometimes one side must concede if it's critically necessary for architecture, legislation, or reducing key risks.

Can we skip documenting the results of conflict resolution if everyone agreed in the meeting?

No, key decisions must be documented, otherwise, after several iterations, "emotional amnesia" or a revision of the agreement may occur.

Common mistakes and anti-patterns

Making decisions based only on the volume or position of the customer.
Ignoring the involvement of all stakeholders.
Leaving verbal agreements without written traces.

Real-life examples

Negative case:

In the project of creating a medical portal, the requirements of the patient community regarding anonymity contradicted the Ministry of Health's registration rules. The team looked past this and implemented a compromise "by eye". Upon market entry, the project failed the audit, and the product was revised only after six months.

Pros:

Quick release

Cons:

Extensive revisions
Financial and reputational losses

Positive case:

The analyst conducted a facilitated session with both sides, highlighted critical requirements (law, security), and described alternative scenarios that considered everyone's interests. All agreements were documented and approved by the legal department and business.