Two quality attributes are in direct conflict and both stakeholders say theirs is non-negotiable. How do you resolve that?
Answer
Short answer
Express both attributes as measurable scenarios, then lay out the intermediate designs so the choice is between numbers rather than adjectives. Where the conflict is genuinely irreducible, escalate to whoever owns both consequences and record what was sacrificed, with a trigger for revisiting.
The interviewer is testing whether you can reason about quality attributes as trade-offs rather than slogans. Quality attributes often conflict: lower latency can reduce durability, stronger consistency can reduce availability, and tighter security can reduce usability. In architecture shorthand, each NFR needs a measurable scenario, and an NFR that conflicts with another NFR needs an explicit decision about which one wins in which context.
Was this answer helpful?
Likely follow-ups
- How do you write a quality-attribute scenario that a test can fail?
- The stakeholder with more organisational power is technically wrong. What do you do?
- Which conflicts can be dissolved by changing the architecture rather than choosing a side, and which cannot?
- Six months on, the sacrificed attribute is now the one causing complaints. How should the original decision have prepared for that?
Related questions
- The business says the system must be highly available. How do you turn that into a number, and what does that number cost?mediumAlso on quality-attributes4 min
- A stakeholder tells you the system must be scalable. How do you turn that into a requirement you can design and test against?hardAlso on quality-attributes7 min
- How do you force product leadership to prioritize paying down toxic technical debt in a hyper-growth scale-up that only cares about shipping features?hardAlso on stakeholder-management3 min
- Tell me about a time you had to deliver with unclear requirements or a deadline you did not believe in.mediumAlso on stakeholder-management6 min