Communicate a Difficult Decision to Stakeholders
Company: Oracle
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
## Question
Describe a time you had to communicate a difficult technical or delivery decision to stakeholders. How did you explain the trade-off, handle disagreement, and maintain trust after the decision?
### Constraints & Assumptions
- Choose a decision that affected scope, timing, risk, or a promised outcome.
- Tailor the explanation to non-specialist stakeholders without hiding material uncertainty.
- Include alternatives and the decision owner.
- Follow through after the initial message.
### Clarifying Questions to Ask
- Should I choose an example involving a delay, reduced scope, or reliability risk?
- How much technical detail would you like in the story?
- May I discuss a decision that stakeholders initially rejected?
```hint Lead with impact and options
Explain what changed, who is affected, and the decision needed before presenting implementation details.
```
### What a Strong Answer Covers
- Early communication backed by evidence.
- Plain-language options, consequences, and recommendation.
- Honest uncertainty and a named decision process.
- Listening, written follow-up, and updated commitments.
- Evidence that trust or outcomes were preserved.
### Follow-up Questions
1. What was the strongest stakeholder objection?
2. What information did you deliberately omit or simplify?
3. How did you report progress afterward?
Quick Answer: Describe communicating a difficult technical or delivery decision that changed scope, timing, risk, or a promised outcome. Explain alternatives and uncertainty clearly, handle stakeholder disagreement, identify the decision owner, and show how trust was maintained.