Reader situation
Professional communities work because people share real experience: what went wrong, what they learned, what they’re struggling with. That experience usually involves other people and organizations. Sharing it carelessly can break trust with employers, colleagues and the community itself.
Central idea
Sharing professional experience carries responsibilities to employers, colleagues and other contributors. Consider consent, confidentiality and attribution before sharing, and withhold details when removing names would not adequately protect the people involved.
Practical steps
- Sensitive information. Before you share, identify what’s sensitive. That includes confidential business information, such as figures, plans, clients and contracts, and personal information about colleagues, such as performance, health or personal circumstances. Check any confidentiality agreements that apply to your work. Information you learned in confidence from a colleague or client remains confidential, even if you’ve since left the role.
- Permission. If your story involves another person’s work, decisions or words, ask whether they’re comfortable with you sharing it. If you can’t ask, or they say no, share only what concerns your own actions and learning.
- Anonymization limits. Removing names doesn’t always protect people. Job titles, team sizes, locations, dates and unusual details can make a situation recognizable, especially in small industries. Ask yourself whether someone who knows your work could identify the people involved. Combining details is a particular risk: each one may be harmless on its own, but together they can point to a specific person or organization.
- Attribution. Credit ideas and work to the people who contributed them, where they’re comfortable with that. Don’t present a team’s achievement as yours alone, or share another member’s contribution elsewhere without permission. Some people prefer not to be named at all, so ask how they’d like to be credited.
- When to withhold details. If the lesson can’t be shared without exposing someone, share a more general version, or don’t share it. A useful lesson is rarely worth damaging trust.
Worked example
Fictional example
Elif wants to share a lesson about handling a difficult client in a Circle for consultants. Her first draft mentions the client’s sector, city and project size. She realizes that others in her small industry could identify the client, so she removes those details and keeps only what she did and what she learned. She also removes a comment about a colleague’s mistake, since he hasn’t agreed to it being shared. The revised post still explains how she reset expectations with the client, which is the part other consultants can use.
Boundaries
- Private Circles aren’t confidential. Members can remember and repeat what they read.
- If you’re unsure whether something is confidential, assume it is.
- If you share something by mistake, remove it as soon as you can and tell anyone affected.
One action to try with a professional peer
Before sharing your next professional story, ask a peer whether they could identify anyone involved. Adjust the details based on their answer.
Discussion prompt
How do you decide what to leave out when sharing a lesson from your work?
