The Situation
Youre being asked to deliver work faster than your team can realistically achieve.
The Answer
Pushing back isnt about saying noits about reframing the decision. Senior stakeholders usually want outcomes, not specific timelines. Your job is to make the trade-offs visible.
Start by clarifying the requirement: whats the real priority? Speed, quality, or scope? You rarely get all three.
Then respond with options, not resistance. For example: We can deliver by that date if we reduce scopeheres what would drop or If we keep full scope, the realistic timeline is X .
Quantify impact where possible. Missed testing, increased risk, or team burnout are all real costs. Make them explicit without sounding defensive.
This shifts the conversation from can you do it? to which trade-off do we choose? which is where good management decisions happen.
What to Do Next
- Clarify the true priority (speed vs scope vs quality)
- Prepare 23 delivery scenarios with trade-offs
- Communicate impact in concrete terms (risk, quality, effort)
- Avoid emotional languagestay factual
- Get agreement on the chosen option
Common Mistake
Saying thats not possible without offering an alternative.
Source: Based on real delivery pressure scenarios in IT teams
Bring this to your AI Companion
The answer above is universal. Your situation isn't. The Companion takes this same situation and works through it with you — with your team, your stakeholders, your context.
Reflect with the Companion