hardScenarioBehaviouralSeniorStaffLead
In standups you keep hearing engineers refer to a scaling limit as a known thing, but it has never appeared on any risk register or in any status report. What do you do with that?
5 min readUpdated 2026-08-15
Answer
Short answer
Widely known and never escalated usually means the risk has no owner and no threshold, not that it is being hidden. Get it written down with a trigger and an owner, and find out why the existing escalation path did not carry it.
Was this answer helpful?
Likely follow-ups
- The tech lead tells you the limit is real but two years away and not worth program attention. How do you test that claim?
- What wording would you put in the risk register for something you do not yet understand technically?
- How do you keep a risk visible for eighteen months without it becoming wallpaper that nobody reads?
- You later learn a principal engineer raised this a year ago and was told to stop blocking the roadmap. What changes in your approach?
Related questions
- A platform team your program depends on has just told you their deliverable will land three weeks late, and it is on your critical path. How do you handle telling the VP the launch date has moved?hardAlso on escalation and program-delivery5 min
- Tell me about a decision you had to make in minutes, with information you knew was incomplete.mediumAlso on escalation6 min
- One engineer is the only person who understands the payments integration, and four of your workstreams queue behind them. How do you manage that as a program risk?hardAlso on technical-risk5 min
- Two engineering teams in your program each insist their work has to come first, and both leads have dug in. You have no authority over either. How do you get to a decision?hardAlso on program-delivery5 min