Transparent Leadership
Transparent leadership means giving the people around you, your team, your spouse, your partners, an honest read on where the business actually stands, the wins and the problems both, not a curated status update. The way Ben Laws frames it with the founders he coaches, most leaders aren't dishonest, they're just blind to their own wins, so every conversation leaks stress and nothing else. Fix the ratio and you fix the trust. A founder who reports both sides builds a team that can read the real state of things without needing him in the room.
Your spouse can tell something's off before you say a word. Your ops lead reads it in how fast you walk into the building. No one in your orbit gets a full update on the business. They get a weather report, and lately the forecast has been nothing but storms.
That's not honesty. It's a leak. You think you're protecting people by not burdening them with the good stuff while you're drowning in the hard stuff, or by staying vague so no one worries. What you're actually doing is training everyone around you to brace for bad news every time you open your mouth.
What transparent leadership actually means
Transparent leadership isn't telling your team everything. You're not obligated to narrate every number, every scare, every call that didn't land. Ben Laws, who coaches founder-operators through exactly this, treats transparency as a strategic choice, not a confession booth. The real question before you share anything is simple: is this going to help the person hear it, or is it just easier for you to say?
What it does mean is giving the people who depend on you an accurate read, not a curated one. If the only data your team, your spouse, or your partner ever gets from you is the problems, you haven't given them transparency. You've given them a distorted sample, and they'll build their whole sense of how the business is doing off of it.
You're reporting the valley and skipping the summit
There's a specific failure mode Ben sees constantly in founders, and it isn't dishonesty. It's a kind of blindness. He calls it the curse of knowledge: you've climbed so many mountains in this business that the summits don't register anymore. A deal that would have floored you three years ago barely gets a mention at dinner. Meanwhile every valley, every scare, every rough call still lands at full volume, because fear doesn't get numb the way accomplishment does.
So the people closest to you end up with a badly skewed picture. "All she hears is the valley," Ben tells founders. "But she doesn't hear your mountaintop summits because you're just so used to them." You're not hiding the wins on purpose. You've just stopped noticing them as news.
His line for the fix is blunt, and it's the whole thesis in six words: "if you're going to share the shit, you got to share the cake." Every problem you report needs a win in the same conversation, or you're not reporting the business. You're reporting your stress level.
- Every conversation opens with a problem
- Wins go unmentioned because they feel normal to you
- People start dreading your name on the calendar
- Updates feel honest but train constant worry
- You become the only honest read on the business
- A real win named before the hard thing
- Problems still get full, honest air time
- People stay steady instead of swinging between extremes
- Trust compounds because the picture is accurate
- The team can read the business without you in the room
Skip this and you create whiplash, not honesty
When a founder only communicates trouble, the people around them don't settle into steady awareness. They swing. One week it's "we might lose the Henderson account," the next it's "we just landed the biggest month in company history," and no one got the connective tissue in between. Ben calls this exactly what it is: communication whiplash. It feels honest in the moment because every individual update was true. Strung together, it trains your spouse, your leadership team, or your board to dread your name on the calendar.
The fix isn't a bigger disclosure. It's ownership of the pattern. Ben coaches founders to reframe the miss directly: "Rather than 'I didn't update the plan,' it's like, 'I didn't share with you so that we could update the plan together. And that is a total miss on my part.'" That's the difference between an omission and a decision. One just happens to you. The other you can actually fix.
The one-sentence habit that rebuilds it
Ben uses a simple opener to retrain this in a team, a leadership meeting, even a marriage: before anyone reports a problem, they share one exciting thing they're thinking about, then name three big wins they're genuinely excited about. It sounds almost too small to matter. It isn't. It flips a "misery loves company" check-in, where everyone competes to have the worst week, into something that actually builds the culture instead of eroding it.
Run this before your Monday meeting, your weekly call with a co-founder, or the drive home. The problems still get air time. They just don't get to be the only thing anyone ever hears from you.
- 1Share one exciting thingBefore anything else, name something you're genuinely thinking about or looking forward to.
- 2Name three real winsSpecific, recent, yours or the team's. Small counts. The point is noticing them again.
- 3Then report the problemSay the hard thing in full. It still gets honest air time, it just isn't the only thing said.
- 4Own the pattern, not just the updateIf you've been one-note lately, name that directly instead of letting it go unspoken.
How you communicate when you need something
Transparency isn't only about news flow. It shows up in how you ask for things. Ben teaches founders a reframe he calls the buyer/seller model: when you need a stakeholder, a partner, or an employee to say yes to something, you are the seller, and your job is to help them become a genuinely good buyer. Not through pressure. Through making the value as legible to them as it already is to you.
That takes a specific kind of generosity he names "smart intelligence," not how smart you are, but how smart you make the other person feel in the exchange. Founders default to proving they're right. The ones who actually get buy-in make sure the other person understands the stakes well enough to choose it themselves.
This matters more as the company scales, and it's part of what lets you build a business that runs without you. Curt Steinhorst, who helps organizations build trust in high-performing teams, named the cost of skipping it on the podcast: "You can't build trust if you don't protect attention." Give people a real, honest signal and they lean in. Give them noise, or nothing but bad news, and they start protecting themselves from you instead of working with you. Steinhorst's own research on this points at what actually scales: not more individual output, but coordination, trust, and the willingness to let someone run without a hundred alignment meetings. That's the whole reason transparent communication compounds. It's what lets people act without checking with you first.
What this is actually worth
This isn't a soft skill you get credit for. It's infrastructure. A founder who only broadcasts problems becomes the single point everyone routes through for an honest read on the business, which is its own version of key-man risk. A founder who reports both sides, consistently, builds a team and a family that can read the real state of things without you in the room.
Mark Gaunya, who spent three decades building a health insurance company on the belief that people deserve honest pricing before they buy, put it simply on the show: "Transparency is a principle, not a product." You don't install it once and move on. It's a habit you run every week, the same way you'd run a Five Dial or a cash number. If your business is supposed to run without you eventually, the people in it need to be able to trust what you tell them long after you've stepped back, and that's worth building on purpose, not leaving to whatever mood you walked in with today.
How to start this week
Pick the next conversation where you're about to report a problem, to your spouse, your team, your board. Before you say it, name one real win first, even a small one. Then say the hard thing. That's the whole mechanic, and it costs you one sentence.
If the trust gap you're feeling is less about what you share and more about how your team handles hard feedback, how to give constructive feedback is the next piece. And if the deeper issue is that no one feels safe saying anything to you at all, start with how to build team culture.
What to actually do
Transparency is a ratio, not a confession
You're not obligated to share everything. You are responsible for making sure problems aren't the only data people ever get from you.
You've gone numb to your own wins
The curse of knowledge works in reverse too: your summits stop registering as news while every valley still lands at full volume. People only hear the valley.
Share the cake with the shit
Ben's rule: every hard update needs a real win named in the same conversation, or you're reporting your stress level, not the business.
One-note updates create whiplash
Swinging between 'we might lose the account' and 'best month ever' with no connective tissue trains people to dread hearing from you.
The fix is one sentence
Name one win, then say the hard thing. Run it before every check-in and the ratio rebuilds itself.
It's infrastructure, not a soft skill
A founder who only reports problems becomes a single point of honest truth the business can't run without. Transparent reporting is what lets a team trust the picture after you step back.
From the podcast
Common questions
What is transparent leadership?
Why do I only ever talk about problems with my team or spouse?
How do I communicate honestly without worrying everyone?
What is communication whiplash?
Is transparent leadership the same as oversharing?
Does transparent leadership actually affect what a business is worth?
Is your team bracing for you, or trusting you?
This is the work Ben does with founder-operators every week. Not a messaging template, but rebuilding the honest ratio between what's hard and what's working, so the people around you can read the real state of the business without you in the room. If your updates have gone one-note, let's talk.
Work with Ben