Conflicts of Interest — Confidentiality & Outside Relationships
I Had Lunch With My Close Friend Who Now Works at Our Competitor. The Conversation Drifted to Work. No Documents Were Shared, and No Secrets Were Told — but I Confirmed We’re Moving in a Particular Direction. Is That a Compliance Problem?
A real conflict of interest and confidentiality scenario — with three decision options and the right answer.
Quick Answer
Does confirming non-public company information in a casual personal conversation with a friend who works at a competitor constitute a confidentiality violation — even when no documents were shared, and nothing was explicitly secret?
Yes. Confidential information does not have to be formally classified or documented to be protected. Non-public information about an organization’s strategic direction, product plans, or competitive positioning is confidential regardless of how it is communicated. A casual confirmation in a personal conversation is still a disclosure. The fact that the recipient is a close personal friend does not reduce the competitive harm — it may increase it, because a friend at a competitor who receives competitive intelligence from a trusted source is more likely to use and share it than a stranger who obtained it through other means.
The Situation
A product manager has a close friend — someone they’ve known for seven years — who recently left their previous employer and joined a direct competitor in a senior strategy role. They meet for lunch every few weeks. The employee attended a product strategy session last week that covered a new market segment their company plans to enter in Q3—an initiative that has not been publicly announced.
Over lunch, the friend mentions that their new company is deciding which adjacent markets to pursue next and asks, half-jokingly, “Are you guys looking at the same things we are?” The employee doesn’t share any specifics — no pricing, no timelines, no product details. But they say, “Honestly, probably yes — there’s a lot of overlap in where both companies are headed.” The friend nods and changes the subject. The employee doesn’t hesitate. Two months later, their company’s Q3 initiative launches — and the competitor launches a nearly identical program three weeks earlier.
What Should the Employee Have Done?
Choice AThe conversation was fine — no specific confidential information was shared. Saying “there’s overlap in where both companies are headed” is a vague observation, not a disclosure. The competitive outcome was likely a coincidence and would have happened regardless.
Choice BDecline to engage on any work-related topic with the friend — redirect the conversation when it moves toward competitive territory, and after the lunch, disclose to a manager that a close friend now works at a direct competitor in a strategy role and ask how that relationship should be managed going forward.
Choice CContinue meeting the friend socially but make a personal rule not to discuss specific projects or timelines — keeping conversations at a general industry level without involving Compliance or management.
The Right Call
Choice B — Redirect in the moment and disclose the relationship to management.
Choice C is the most common response and the most self-defeating one. Drawing the line yourself — deciding what is and is not disclosable at a general industry level — is exactly the kind of individual judgment call that creates compliance risk. The employee isn’t in a neutral position for that conversation. They have recent access to non-public competitive intelligence, a close personal relationship that makes sharing feel natural and harmless, and no framework for where the line actually is. Management and Compliance have the framework. The employee’s job is to flag the relationship and let them draw the line.
Why This Is Harder Than It Looks
Confirmation is disclosure — even without specifics.
The employee confirmed that the two companies are heading in the same direction. To a strategist at a competitor, that confirmation is valuable competitive intelligence — it narrows the field of strategic possibilities and validates a direction the competitor was already considering. “We’re probably looking at the same things” is not vague background noise. It signals from a knowledgeable insider that the competitor’s strategic hypothesis is correct. That confirmation has real value to the competitor, regardless of the employee’s intent.
The personal relationship is the risk amplifier — not the risk reducer.
The employee’s instinct is that the friendship makes the conversation safe — they trust their friend, they’re not being formally interrogated, nothing is being recorded. But the friend’s trust in them is exactly what makes the intelligence valuable. Competitive intelligence from a trusted insider who shared it casually—not from a formal competitive analysis—is more credible and actionable than information obtained through formal channels. The friendship is not insulation. It is exposure.
A close personal friendship with someone at a direct competitor is itself a disclosable conflict of interest.
When the friend took the competitor role, the relationship changed from a personal friendship to a personal friendship with a potential conflict-of-interest implication. Most COI policies cover relationships that could influence professional judgment, including a close friendship with someone who now works for a direct competitor and with whom the employee has regular contact. The employee should have disclosed the relationship when the friend changed roles—not because the employee did anything wrong, but because the organization needed to know to manage it appropriately.
How to Use This Scenario in Training
Add This Scenario to Your Code of Conduct Training
Use realistic workplace scenarios like this one to help employees move beyond policy awareness and practice applying your Code of Conduct to decisions they may actually face.
Add This Scenario to Your Conflict of Interest Training
Use realistic scenarios like this one to help employees recognize conflicts of interest as they arise in everyday work, and practice deciding when to disclose, step back, or ask for guidance.
Run This Scenario in a Team Meeting
Turn this workplace decision into a 15-minute, manager-led discussion. Employees consider what they would do, discuss the options, and practice applying company policy before the pressure is real.
Frequently Asked Questions
Does having a close personal friend at a competitor need to be disclosed as a conflict of interest?
It depends on the nature of the employee’s role and the friend’s role at the competitor. An employee with access to non-public competitive intelligence who has a close personal friendship with someone in a strategy role at a direct competitor has a relationship that could — even without any intent — result in the disclosure of confidential information. That relationship is worth disclosing so management can assess whether any guardrails are appropriate. The disclosure is protective of the employee as much as it is of the organization.
Can an employee still see a friend who works at a competitor socially after disclosing the relationship?
In most cases yes — with agreed guardrails. The most common outcome of disclosing a friendship with a competitor employee is a brief conversation with management about how to handle the relationship appropriately, which typically results in guidance like “keep conversations clear of work topics” or “flag it if a conversation goes somewhere uncomfortable.” The disclosure is not a prohibition on the friendship. It is an acknowledgment that the relationship exists so the organization can provide appropriate guidance.
What should an employee do if a work conversation has already happened and they’re not sure whether something confidential was disclosed?
Report it to a manager or Compliance as soon as possible — ideally the same day. Describe what was discussed and what information was shared, even if the employee believes it was not specific enough to be confidential. The assessment of whether information was confidential and whether harm occurred belongs to Compliance, not to the employee who had the conversation. Voluntary disclosure, even of a situation that may turn out to be harmless, creates a far better record than a later discovery that the employee knew something had happened and said nothing.
More Conflicts of Interest & Confidentiality Scenarios
|
My new manager asked me to share my former employer’s pricing strategy. It’s in my head. Is that a problem? |
A data scientist rebuilds their former employer’s proprietary algorithm at a competitor from memory. |
Browse all conflicts of interest scenarios. |
Want These Scenarios in Your Compliance Program?
Xcelus builds scenario-based training that covers confidentiality obligations, competitor relationships, and casual disclosure situations that most compliance programs miss.
© 2005–2026 Xcelus LLC. All rights reserved. This content is for training and discussion only and is not legal advice; consult qualified counsel about your organization’s specific obligations.