Codify how engineering answers sales - bugs get fixed, out-of-scope features get a no, and the only next step is Product not re-escalation

Situation

Coming out of the LG episode Peter laid down the operating rule in writing in the temp-lg channel: Engineering will respond to sales requesting a fix for a bug and will deliver that bug fix without product involvement. Engineering response to a sales request for a new feature that falls outside currently supported builds or plans is no. The step after that is for Product to get involved. In the meeting he attached three companion rules: re-escalation after an answer has to stop, engineering should stop saying you can try it and it might work in favour of that is not supported, and CIQ must present a unified front so no internal voice tells a customer something is a bug after engineering has ruled it is not. He also drew the line between discussion time and decision time - internal deliberation should not be shown to sales as if it were still open.

Reasoning

Peter diagnosed the LG drag-out as a process failure rather than a technical disagreement. Sales asked, got an answer, escalated, got the same answer from him, and escalated again - which teaches the org that persistence changes outcomes. He explicitly does not want to discourage sales from asking, so the fix cannot be punishing the question; it has to be a defined path with a terminal node. Routing the terminal node to Product rather than back to Engineering puts the cost-benefit call with the function that owns it, and keeps engineering out of relitigating. The stop-saying-you-can-try-it rule is a response to compounding fog: when language, culture and timezone gaps already exist, a hedged answer is read as a soft yes. The unified-front rule targets the specific harm of internal disagreement leaking to a customer.

Additional Context

Ryan asked Peter not to put a pin in this and requested a shortened escalation path for sales. Justin pointed out the real failure was earlier - the initial hedged answer was never escalated for a decision, and the later escalation happened only after the predicted failure occurred. Peter attributed part of the problem to five years of CIQ saying yes to close deals, and said the untraining will only happen through some pain.

Observed Evidence

Written doctrine posted in-channel plus three separate spoken formulations in the meeting - the escalation-must-stop rule, the not-supported messaging rule, and the unified-front rule.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis