I dont know is the right answer - Support does not guess how Oracle does it, and LG questions are an Engineering/Product call not a Support call
Situation
With Bjorn about to dig into the LG U+ escalation and likely to reach out directly to support engineers, Peter set an information-hygiene rule and had Ryan Smith push it to his team. The rule has three parts: if the team does not know how Oracle is doing it, the answer is we do not know - not they must be doing blah blah blah; answer his questions truthfully but do not lead the witness; and the LG question itself is an Engineering and Product call, not Support. Ryan confirmed his team had acked it and named Amr as the likely contact point, and Peter said he was doing the same thing with Howard. Peter closed with answer his questions. No guessing.
Reasoning
Peter identified the specific failure mode: Bjorn will take a support engineers guess as gospel, and a guess about a competitors mechanism becomes a load-bearing premise nobody can retract. Speculation therefore does not just risk being wrong - it manufactures work and pain for CIQ. He also drew a lane boundary in the same breath: Support is a truthful witness on what tests were run, but the decision about whether CIQ pursues the Oracle-style path belongs to Engineering and Product. That keeps Support from being made the de facto authority on a commercial and architectural question. Notably he applied the identical rule to Howard, so it is a symmetric standard rather than a constraint on Ryans team alone.
Additional Context
Directly downstream of the 7/27 definitive no and the 7/28 three non-negotiables. Bjorn was actively reading Howards document and pressure-testing hypotheticals. Peter had earlier told Ryan the same message in writing, then reinforced it on a short call the same afternoon.
Observed Evidence
Verbatim in the Fathom transcript of the 7/28 16:01 call, and verbatim again in Slack where Ryan quotes Peters written instruction back and confirms his team acknowledged it. Peter then confirms with answer his questions. No guessing.
Matching Patterns
Confidence Breakdown
Reasoning Depth Analysis
Related Context
fathom
And not guessing. If Bjorn asks, how is Oracle doing this? If people on your team dont know how Oracle is doing it, the answer is, we dont know. Not, they must be doing blah, blah, blah. Because he is going to take that as gospel... I dont know is a super fine answer to something that we cant know... I just want to make sure we are not causing more pain and work for ourselves by guessing. (Ryan: Is he reaching out to people on my team?) He will reach out to Amr and want to understand things and exactly what tests were done... (Ryan: Let me ping Amr and get in front of it.) Im doing the same thing with Howard.
slack
Ryan quoting Peter back: If Bjorn comes asking about LG / or any How does Oracle do this types of questions, we need to be very clear about what we do and do not know. We dont know how Oracle is doing it is the right answer. And that is the truth, because we can guess, but we do NOT want to guess. He will be digging in and possibly reaching out to you guys for questions about how was the testing done, etc. Just be truthful, but dont lead the witness. This needs to be an Engineering / Product call. Not Support. -- Ryan: They have acked this. -- Peter: Thx. Answer his questions. No guessing.
Outcome
No outcome recorded yet.
Decision ID: aec0a3dc-d222-4452-858c-89b575dc26e9