1 min lesson
Keep technical claims current
State product limits precisely and use one clarifying question to narrow a broad scenario.
Step 1 of 2
"Before I choose a pilot, I need to know which teams and repositories are in scope, how developers use AI today and which security review controls the decision. Then I can choose a starting group, document the relevant data flows and set a measured expansion rule."
Do not turn one product setting into a complete privacy answer. Check current documentation for the feature, provider path, storage, retention and deletion before naming a guarantee. Record the source and date because product terms change.
When a scenario is broad, ask which outcome or blocker matters most. The answer may change the first user group, control review and measure you choose.