Transparency builds trust, but not everything should be shared in every context. The judgment about what to share, how much detail to provide, and what might create unnecessary concern is one of those things that separates experienced professionals from inexperienced ones.
Why this matters
Too little transparency erodes trust. Clients feel like you're hiding things, and they're often right. Too much transparency can overwhelm, create anxiety about minor issues, or share things that are inappropriate for the context. The balance is about professional judgment.
The principles
Share what affects them. Anything that impacts timeline, budget, quality, or scope should be communicated. That's the baseline.
Problems come with solutions. Don't hide issues, but present them paired with what you're doing about them. "We hit a bug, here's how we fixed it" is very different from "everything is on fire."
Err toward more transparency, with appropriate framing. When in doubt, share. But frame it well. There's a difference between "heads up about a minor issue we've already resolved" and "OH GOD THERE WAS A BUG."
Some things stay internal. Team personality conflicts, individual performance issues, internal debates about approach that were resolved. These are your problems to manage, not theirs.
What good looks like
Transparent but appropriate: "We hit a database optimization issue this week that added two days. It's resolved, we've added monitoring to catch similar issues early, and we're still on track for October 15. No action needed from you."
Why It Works
Shares the issue. Provides resolution. States impact. Doesn't create unnecessary anxiety.
Appropriate discretion about team changes: "We have a transition happening on the team. I'm managing it to ensure zero impact on your project. Your primary contacts stay the same."
Why It Works
Acknowledges something is happening. Focuses on what they care about (project impact). Doesn't dump internal HR details on them.
What bad looks like
Too transparent: "The developer made a huge mistake and we spent all week fixing his terrible code. I'm so frustrated with the team right now. Everything is a disaster behind the scenes."
Why It's Bad
Internal drama, undermines confidence, creates anxiety.
Too opaque: a major issue happened last week, resolved now, never mentioned. Client discovers it later.
Why It's Bad
Feels like hiding. Damages trust when discovered.
Tips
- Ask: "Does this affect their outcomes, decisions, or understanding?"
- Share problems with solutions: "Issue happened, here's how we solved it"
- Protect internal team dynamics. Your team's interpersonal stuff is yours to manage.
- Don't speculate in writing. Share when you know.
- Remember written communication is permanent. Choose words carefully.
- When unsure, discuss verbally first, summarize in writing second.
How this connects
This combines proactive communication (sharing the right things at the right time), delivering bad news (how to frame problems), executive communication (appropriate detail for the audience), and professional judgment.
Things to try
- Review your last few client updates. Was the transparency level right?
- Before sharing an issue, ask: "Does this need to be shared? How should I frame it?"
- Practice: "Here's what happened, here's the impact, here's the plan."
- When unsure whether to share, ask a colleague: "Would you mention this to the client?"